i think my device is somehow damaged...

47 views
Skip to first unread message

Lugul banda

unread,
Jun 18, 2018, 2:05:44 PM6/18/18
to Safecast Device Discussions and Support
today i did 2 MEASUREMENTS one wich runs smoothly ... and the second one was not even listed under the current day packed, but i found the second measurement under this file 


https://api.safecast.org/en-US/bgeigie_imports/36526 auto name of the file 30030000.log thats what i dont understand



https://api.safecast.org/en-US/bgeigie_imports/36525  auto name of the file 30030618.log thats what i expect

anyone wich can give me a hint ?

extreme2themax

unread,
Jun 18, 2018, 2:54:05 PM6/18/18
to Safecast Device Discussions and Support
My unit has done that a few times as well, i think it is because the GPS hasnt fully locked on by the time the unit starts to record data.  Strangley it usually only happens if it is the 2nd time the unit has been switched on that day, so insteda of adding to the existing file, it starts a new one called 0000, but think it only happens about 2-3% of the time

Lugul banda

unread,
Jun 18, 2018, 7:54:21 PM6/18/18
to Safecast Device Discussions and Support
yes but what happens if u upload and aprove it, if that happens more times, i remember if i try to upload data wich i allready have, it sayes  allready present.. can this zero file multiple times  be uploaded without loosing its data?

Jan Helebrant

unread,
Jun 20, 2018, 2:58:20 AM6/20/18
to Safecast Device Discussions and Support
Hi,
this happens occasionally also with our devices. I think it happens if somehow bGeigie begins to write the file before getting GPS coordinates and GPS time/date and so both the filename and the first rows are wrong (but not the measurements itself).

BTW I attached fixed file for you :-)

Jan

Dne pondělí 18. června 2018 20:05:44 UTC+2 Lugul banda napsal(a):
30030618_upload.LOG
Reply all
Reply to author
Forward
0 new messages