-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bosean FS-5000: History not downloading correctly #97
Comments
I need a repeatable list of steps that showcase the error. |
Did you try connecting to your counter with a serial terminal like, for instance, https://www.putty.org/ ? Try the following command:
|
Putty reads all the data successfully. Geigerlog also reads all history data. But when I try to read new history data, FS-5000 immediately restarts and Geigerlog gives "Could not download history". I'm going to repeat flashing firmware. Could it help if I send firmware 256 KB .bin copy, that is in my device now? |
Please do so. |
That's it |
It's a great thing you made a flash memory snapshot that allows reproducing the error. Unfortunately I haven't been able to reproduce the error in my simulator. I'm going to ask you to confirm a couple of events, just to make sure there is no fault in datalog recording. I'm going to assume your device's clock is correctly set. I'll also provide dates and times in UTC time.
Question 1: Is all of this correct? If it is, it would mean that datalog recording is working correctly. Question 2: When sending the |
I've found the answer of first part of my question.
For second part of my question. I tried to repeat the situation to convince if it wasn't sporadic.
It seems that after reading some big amount of new history data, FS-5000 doesn't enable to read new history anymore. |
It's a great thing you made a flash memory snapshot that allows reproducing the error. Unfortunately I haven't been able to reproduce the error in my simulator. I didn't make a flash memory snapshot - I reload firmware with radpro-flashtool-2.0 and took the previous firmware from backup directory I'm going to ask you to confirm a couple of events, just to make sure there is no fault in datalog recording. I'm going to assume your device's clock is correctly set. I'll also provide dates and times in UTC time. Between 2024-06-09 10:48 and 2024-06-09 11:17 you restarted your device several times without the ok/power button. At 2024-06-11 05:14:33 you changed the clock back for a few seconds, and at 2024-06-11 05:14:41 you changed it forward, also for some seconds. - It could be that I connected device to Geigerlog and was the time synchronizing. Question 2: When sending the GET datalog request through PuTTY in the flash memory snapshot state, do you get to see some response? How much time passes between submitting the request and the device restarting? The exact timing would be greatly helpful. |
I insist on this. |
in the flash memory snapshot state, - please comment more what is it? |
I mean this: open PuTTY, type |
After typing GET datalog and pressing Enter, immediately I see receiving data on putty screen. |
That video was tremendously useful! Now I know where to look for the error. |
I am not able to reproduce this issue. I'll be gathering more history data and see then. |
I also reflashed firmware and started accumulating history data |
No need for that, the problem has been identified. |
Yup, I can reproduce this. I gathered about 13h of data -> loaded all history in |
The issue was that downloading partial data logs didn’t trigger the watchdog timer frequently enough, causing the device to reboot. Could you test https://github.com/Gissio/radpro/releases/tag/2.0.1beta3? I've also added data log reset (with little flash memory wear). |
Tested. Everything works. Data logging reset too. Thank You, Gissio very much! |
Would someone be so kind to test #96 on the FNIRSI GC-01? |
#96 testing: I flashed test3 firmware made from src to GC-01 with Geeky Ch32 MPU, without R38-51mOm load resistor. |
The data from FS-5000 are on the beginning of graph and there are some data on the end of graph. On GC-01 everything OK.
It seems that on FS-5000 after 1 hour of datalogging we get a normal graph.
After 13 hours I've red successfully new history data. And then after 0.5 hours a couple of times I tried to read new history data - the FS-5000 restarts, and I was getting the message "Could not download history" on Geigerlog. Didn't help neither restarting Geigerlog nor manually restarting FS-5000.
The text was updated successfully, but these errors were encountered: