Error in compiling if SQMSUPPORT is to be activated
ESP32 mySQM+ Sky-Meter/Weather Station with loads of features
Brought to you by:
brownrb
Menu
▾
▴
Hi Robert,
I want to use this project with ASCOM so I go and activate everything in accordance with the documentation. Unfortunately i get the following error while compiling before sending:
exit status 1
'sqmsendreadrequest' was not declared in this scope --- this is on comms.h
Further on, I get error 'mySQMreading' was not declared in this scope --- nd this I'm not sure where it is.
Can you help out to try to fix this?
THanks
Miguel
Try firmware release 106
The use of #LOCALSERIAL and #SQMSUPPORT is for use with APT only - it is not for use with ASCOM
The ASCOM OC drivers for mySQM+ are either mySQMPLUSTCPIPASCOM or mySQMPLUSUSBASCOM depending on if you are using TCPIP or USB with the controller.
Last edit: brownrb 2020-12-07
Robert I did and it compiles just fine, but now I get error while trying to use the usb program and the ascom program. See pics attached.
Thanks
Miguel
Please appreciate that this is avery compilcated system and I am not looking over your should to see what is going on or what you did etc. You really need to document step by step what you did.
Why?
Because the only way I can offer help is to try and reproduce what you did in the chance that I can also generate the same error here oin my equipment.
see pg3 of PDF
WHAT YOU NEED TO PROVIDE WHEN ASKING FOR HELP
• A detailed explanation of the problem outlining what happens and steps required to reproduce the
problem
• Your controllerconfig.h file so we know how to reproduce your settings
• A copy of your data_per.jsn file is very useful
• A list of the actual sensors connected to your controller
• Any modifications you have made to the existing official release code - you must use the
the official release unmodified you will be asked to only use the existing official release code; no
support is available to help debug your code alterations]
• We assume that you are using the current recommended versions of Arduino, Packages and
Libraries as outlined in the Readme.md and firmware files. If this is NOT the case, you need to use
the recommended versions for your environment]
• Your OS version, firmware revision number, and version numbers of applications you are using that causes the issue
AND
if you are using USBSERIAL - enable the error logging file in the windows app then connect etc - until the problem appears. Once you have closed the app I need the error logging file
If you are using USBSERIAL with ASCOM - enable the TRACE ON of the ascom driver setup when selecting the driver and send me the ASCOM trace logs found in documents\ascom\logs xxx\
Zip it all up and send to me at my gmail or yahoo email address - not here - not on sourceforge
I actually have no idea what you were trying to do.
You have used the Windows app and then also the ascom? Together? At same time?
Lets just concentrate on one of these at a time, it makes it a whole lot easier. Resolving one might help with the other.
So lets start with programing the controller with SERIALMODE (and NOT SQMSUPPORT)
then use the windows usb app to try and connect/
lets start with that
I actually have no idea what you were trying to do.
You have used the Windows app and then also the ascom? Together? At same time?
Lets just concentrate on one of these at a time, it makes it a whole lot easier. Resolving one might help with the other.
So lets start with programing the controller with SERIALMODE (and NOT SQMSUPPORT)
then use the windows usb app to try and connect/
lets start with that
Just a quick question - what baud rate did you set for the COM Port - PDF says 115200
Robert,
my apologies to jump in so fast and not providing any valuable info.
I went to restart my computer and made sure that all libraries were the correct ones, which they were. I flashed once again the code, making sure I had set it up properly and all worked in termos of USB SERIAL connection and ASCOM.
I still didn't activate the SQM, but will do so tonight.
Your USB application allows the system to write a Boltwood file every x minutes. Is it possible to have such feature within the code, because as far as I tested, once USB connection goes OFF, no more text file update.
I'll keep you informed, thanks for the patience though!
Miguel
Storing the data on the controller itself is not a good idea - for a whole heap of questions. Even if there was a lost connection - as we do not know how long it will be before normal service is resumed - there are practical limits on how often and howm much data can be written on chip.
The controller is really designed to use WiFi rather than USB.
In any case, if a connection is lost, data is also lost -
I understand what you say about how old the data is, but that's when you can cover with other failsafe features like checking how old is the data.
When I wrote within the code, I mean to have a feature that would write a file to the computer, like your USB program does, but I don't even know if that is even possible. Right now, I can use the system as either an observing conditions system or as weather station that produces a text file in boltwood format, but not both, hence my question. I will gladly build another one, I always buy 2 or 3 units of each component, but if it that is possible, I find it to be a more complete system.
Thanks
Let me see if I understand this
You want to use the ASCOM driver yes?
You would like the ASCOM OC driver to also output a Boltwood file?
ASCOM is pretty much a standard I guess and we really shouldn't be doing NON ASCOM things in and ASCOM driver.
I really do not understand why your are using ASCOM though. What is the client app that requires you to use ASCOM?
There is obviousy little support in ASCOM for doing that - it has a pretty much closed definition of the methods and properties supported by the driver. However, that does not mean to say it can't be done,
I will await your response before I put my thinking hat on.
Regards
Robert
Robert,
I use Voyager automation program to deal with my astrophotography sessions unattended. It's like APT but created with different mindset. One user on your other SQM project uses it and you guys fixed an issue so the Observing Conditions data would be retrieved by the program. This is done through ASCOM driver with your project.
More info on this feature in the program in here
On the other had, the same program uses AAG Cloudwatcher or Boltwood/Clarity file to generate suspend/exit/resume/ok events, It doesn't need to have ASCOM connection, just needs to read the file. More info in here.
That's the only reason I had to ask for such feature. I think I understand the whole purpose of your projects, allow people to build something useful to them and cheaper, so I understand that you might want to keep this as basic and functional as possible.
Thanks for considering this, though.
One last thing, sometimes it seems the info about dewpoint is lost somewhere because not every time I start the connection, the value will be read. Any known issue already identified or just me?
Best
Miguel
"One last thing, sometimes it seems the info about dewpoint is lost somewhere because not every time I start the connection, the value will be read. Any known issue already identified or just me?"
This has not been reported before. I would need the log file generated by the driver to be able to troubleshoot that. You enabled the log file on the setup form (properties) of the driver - assuming for ASCOM? if the problem is with the Windows app then I would need the log file from that
Sometimes you have to think a little differently when using these Wifi capable controllers like the mySQM+
Let me explain
If you were running the controller in Wifi mode (accesspoint or standionmode) - then you can use the TCPIP ASCOM driver to get access for Vogager via ASCOM.
You could then use the Windows TCPIP application at the same time to write the Boltwood file.
or
You could also use the Windows TCPIP Logger application at the same time to write the Boltwood file.
So what you want to do right now is already possible and does need any rewrite or additional code.
Robert,
I tried your suggestion and everything works like a charm. I need to have WiFi available in the backyard, but that's the easiest to solve.
Thanks for the support provided!!