Drive with ios APP strange Measurement

[Lugulbanda]

today i made a drive, and uploaded it form my iphon, and as i wanted to edit its metadata, i notices something strange... https://api.safecast.org/en-US/bgeigie_imports/33852

Attention! This log file contains: 「Invalid timestamp(s): 1331, which may signify spatial error.」 「Invalid GPS location(s): 1082 flagged by device.」

3003-0130.LOG Number Of Lines 0 Number Of Measurements 0

Process Log

PROGRESS Process File (0 lines) Import bGeigie logs (none found) Compute latitudes & longitudes Approved by moderator … Added to Safecast database

on the end of the drive, i noticed the app signals me GPS Signal not found, but this drive was open wide on air, i reseted the device a few times, also with sd card out, but the GPS didnt came back then as i was thinking something is not right the device and app were working like everyday...

any clue what could chause that ? if i look on the API Map the location is correct and the Points were they should be..

so why a GPS Fail i wounder.... if every Dot is exactly were it should be...

the measurements bevore this drive and after this drive were all ok withou any errors, but this one is one big error with only the shown map as working part, it may be my imagination, but can it be this is chaused, cuz u turn the button to mysievert instead to CPM and store data on the SD Card, ?

[thinrope]

I looked at the data you submitted to the API as 33852/3003-0130.LOG and indeed it contains very wrong timestamps...

$BNRDD,3003,2007-00-00T11:24:08Z,29,5,9991,A,5034.2987,N,00830.4857,E,138.40,V,8,103*58
$BNRDD,3003,2007-00-00T11:24:13Z,30,4,9995,A,5034.2861,N,00830.4760,E,139.40,V,8,105*5A
$BNRDD,3003,2004-00-00T11:24:18Z,30,2,9997,A,5034.2562,N,00830.4656,E,139.10,V,8,105*59
$BNRDD,3003,2004-00-00T11:24:23Z,29,3,10000,A,5034.2220,N,00830.4546,E,139.50,V,8,103*66

Was the file edited in some way (I don't see the usual header)? Did you submit it via https://api.safecast.org/en-US/bgeigie_imports/new with a browser or some other app?

Since the coordinates look OK most of the time, I am suspecting the GPS didn't catch the timestamp properly on init but decided to start logging.

What firmware are you using (should be displayed on power on)? Where from did you download it?

[Lugulbanda]

1. No i just started my bgeige nano, like every time, then start my ios app, and after connection bootup is finished i press start measure..

2. after i was on the drive back i took a small rest, and as i wanted to continue the drive i noticed the app had stopped the measurement, because i noticed the ios app was in the discard upload map mode...

3. so i pressed upload, and then the cloud button again..

4. as i wanted to finish the rest of the drive, and started the the drive ap again i got the message "no GPS" , which was impossible cuz my rest was open in the wide with no high mountains around me...

 5. so i reset the app, i reset the nano, nothing same error, i took out the SD card, reset it again and still no GPS, so i let e nano hang out and started the drive without starting of the app, as suddenly the GPS came back and i made the short measurement after that one,

on that day i took 4 measurements, 3 were totaly ok no problems, only this one, and this one was like the others directly uploaded from the ios drive-App, without any changes in the data, 

Actually I dropped my micro SD holder somewhere. so I can't check if I had the button for store on nano active, if the holder appears, I take a look into the SD Card and if a file is present I will upload it to GitHub...

best wishes, Frank

PS: I don't know who had the problem, the ios app the nano or the ios drive app, but for some reason the ios drive app had the message NO GPS Signal. maybe a ios problem, as soon i find my SD holder i maybe

[Lugulbanda]

30030130.log thats the file from my nano SD Card

[thinrope]

I see your device is:

# format=1.3.4nano
# deadtime=on

and here is the error (flipping 2018-01-30T17:07:54Z into 2000-03-00T17:07:54Z), while GPS=A with 7 satellites in view... then back to normal 28*5=140s later

$BNRDD,3003,2018-01-30T17:07:44Z,23,2,62,A,5051.6589,N,00804.8337,E,274.20,A,7,104*4B
$BNRDD,3003,2018-01-30T17:07:49Z,26,5,67,A,5051.6766,N,00804.8567,E,274.30,A,7,104*40
$BNRDD,3003,2000-03-00T17:07:54Z,25,2,69,A,5051.6950,N,00804.8819,E,274.30,A,7,104*41
$BNRDD,3003,2000-03-00T17:07:59Z,27,2,71,A,5051.7119,N,00804.9018,E,274.50,A,7,104*4D
$BNRDD,3003,2000-03-00T17:08:04Z,31,5,76,A,5051.7368,N,00804.8930,E,273.40,A,7,104*4D
$BNRDD,3003,2000-03-00T17:08:09Z,30,4,80,A,5051.7675,N,00804.8697,E,272.90,A,7,104*4E
$BNRDD,3003,2000-03-00T17:08:14Z,34,6,86,A,5051.7977,N,00804.8355,E,272.50,A,6,117*4B
$BNRDD,3003,2000-03-00T17:08:19Z,32,1,87,A,5051.8332,N,00804.8152,E,272.00,A,6,117*42
$BNRDD,3003,2000-03-00T17:08:24Z,29,0,87,A,5051.8667,N,00804.7902,E,271.50,A,7,104*45
$BNRDD,3003,2000-03-00T17:08:29Z,29,0,87,A,5051.9038,N,00804.7628,E,271.70,A,7,104*40
$BNRDD,3003,2000-03-00T17:08:34Z,34,6,93,A,5051.9440,N,00804.7606,E,270.70,A,7,104*45
$BNRDD,3003,2000-03-00T17:08:39Z,35,2,95,A,5051.9820,N,00804.7774,E,270.00,A,7,104*42
$BNRDD,3003,2000-03-00T17:08:44Z,34,1,96,A,5052.0175,N,00804.8009,E,270.00,A,7,104*48
$BNRDD,3003,2000-03-00T17:08:49Z,31,2,98,A,5052.0489,N,00804.8344,E,270.60,A,7,104*47
$BNRDD,3003,2000-03-00T17:08:54Z,29,0,98,A,5052.0739,N,00804.8724,E,270.30,A,7,104*4F
$BNRDD,3003,2000-03-00T17:08:59Z,28,1,99,A,5052.0813,N,00804.9018,E,269.70,A,7,104*41
$BNRDD,3003,2000-03-00T17:09:05Z,25,2,101,A,5052.0806,N,00804.9145,E,269.40,A,7,127*78
$BNRDD,3003,2000-03-00T17:09:10Z,21,0,101,A,5052.0730,N,00804.9627,E,269.00,A,7,184*7E
$BNRDD,3003,2000-03-00T17:09:15Z,17,2,103,A,5052.0688,N,00805.0282,E,267.30,A,8,94*4D
$BNRDD,3003,2000-03-00T17:09:20Z,18,2,105,A,5052.0737,N,00805.1001,E,268.70,A,8,94*44
$BNRDD,3003,2000-03-00T17:09:25Z,20,2,107,A,5052.0825,N,00805.1729,E,273.50,A,7,184*7E
$BNRDD,3003,2000-03-00T17:09:30Z,25,5,112,A,5052.0915,N,00805.2492,E,276.60,A,7,184*78
$BNRDD,3003,2000-03-00T17:09:35Z,24,5,117,A,5052.0997,N,00805.3192,E,279.60,A,7,184*78
$BNRDD,3003,2000-03-00T17:09:40Z,25,3,120,A,5052.1078,N,00805.3885,E,282.70,A,7,185*7B
$BNRDD,3003,2000-03-00T17:09:45Z,30,6,126,A,5052.1181,N,00805.4591,E,284.20,A,7,185*72
$BNRDD,3003,2000-03-00T17:09:50Z,32,4,130,A,5052.1409,N,00805.5246,E,284.80,A,8,93*4B
$BNRDD,3003,2000-03-00T17:09:55Z,32,0,130,A,5052.1761,N,00805.5779,E,288.70,A,8,93*4D
$BNRDD,3003,2000-03-00T17:10:00Z,38,7,137,A,5052.2185,N,00805.6287,E,291.40,A,7,185*75
$BNRDD,3003,2000-03-00T17:10:05Z,38,2,139,A,5052.2620,N,00805.6815,E,293.60,A,7,127*7A
$BNRDD,3003,2000-03-00T17:10:10Z,41,3,142,A,5052.2975,N,00805.7395,E,294.30,A,7,127*72
$BNRDD,3003,2018-01-30T17:10:15Z,41,2,144,A,5052.3214,N,00805.8075,E,293.60,A,7,185*7D
$BNRDD,3003,2018-01-30T17:10:20Z,41,2,146,A,5052.3385,N,00805.8805,E,291.70,A,7,127*74

Note that the XOR checksum (last 2 chars after *) is correct for all lines, thus (almost) eliminating Fio->SDcard error. It is a bug in the firmware :-(

I had another read of the code and I see something we added to TinyGPS.cpp which can be suspect... https://github.com/Safecast/bGeigieNanoKit/blob/master/TinyGPS.cpp#L218

Have you, by chance, soldered the GPS module battery backup and installed a (CR2032) battery (manual says do not do this)?

[Lugulbanda]

ahm whats the difference into the batterie?

[thinrope]

The difference is ... I don't know. I am suspecting it may change the way GPS is being reset and the code I highlighted may do something else. But most devices are without a battery, as requested in the build instructions, so having a battery is "not well tested case".

[Lugulbanda]

hm iam not shure what u mean, i just build in the GPS Module wich came with the nano, i didnt attach any other battery then the nano battery itself on the board.

[thinrope]

I am not sure the iOS app cares about the switch position... May be @Frangible can confirm?

[Lugulbanda]

hi i resumed my memory of that day, i guess the Problem was i switsched the write data switsch on the nano to mµsievert for a surfacemeasurement and forgot to switsch it back to write mode, thats, why my upload from the nano direc has not a single data of that drive... 30030130 from nano upload, looks like the switsch not only prevent data from wirte to sd card, it also stops the timelogdata from transfering to the ios drive app.... @Azby @thinrope @Frangible

[Lugulbanda]

https://github.com/Safecast/Drive-ios/issues/12 took me alot of time and testing, but there is my final @Azby @matschaffer @thinrope @Frangible @seanbonner