-
Hello! Thanks for this very cool software! But I have one issue (using current version 1.3.0). The graph is not showing and the memory is getting nothing. I can read from the SQM, the software displays the last averaged reading, temperature, etc, but nothing is plotted and nothing is saved. https://i.postimg.cc/kGxfRM9Z/image.png APT and NINA gets the data correctly from the SQM Server. I have enabled file logging. Any ideas? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi there, Sorry you are having problems. I suspect there is nothing drawing due to there being no Raw Value being detected, I can see this in your image the first value Latest Raw Reading is empty. Can you try a couple of things so I can see what's going on.
Send me some screenshots of what is displayed on your system, and before / after you send the UX command, do you see the latest message update with any difference before and after on the U response I am wondering if it is maybe an old firmware of your unit etc. If you look at the unit information on my screenshot vs your screenshot, you can see the Protocol / Model / Feature Version are vastly different. Thanks, |
Beta Was this translation helpful? Give feedback.
-
Further to my post above, I dug through my code and it will only draw data on the graph when it sees a new DataRecord being added to the DataStore. The code that creates a DataRecord, is looking for both the UX and RX (raw and averaged) data responses from the SQM unit before creating a record. I'm still leaning towards firmware versions at this point, until you can feedback on the UX response test. |
Beta Was this translation helpful? Give feedback.
-
Manually triggering a UX command appeared to kick start the updating, underlying reasons for it not functioning as designed initially is not understood as the software does the ix, rx and ux commands on initial connect, then does the ux and rx polls at required interval. First occasion this behaviour has been seen, so will monitor for future occurrences before changing any code as may have been a local 'glitch'. Sending the Manual Command via the Serial Poll status bar context menu as a workaround on the occasion resolved. |
Beta Was this translation helpful? Give feedback.
Manually triggering a UX command appeared to kick start the updating, underlying reasons for it not functioning as designed initially is not understood as the software does the ix, rx and ux commands on initial connect, then does the ux and rx polls at required interval.
First occasion this behaviour has been seen, so will monitor for future occurrences before changing any code as may have been a local 'glitch'.
Sending the Manual Command via the Serial Poll status bar context menu as a workaround on the occasion resolved.