Page 1 of 1

Firmware bug found (GPS LED), and suggestion

Posted: Sat Apr 20, 2013 12:39 am
by GameboyRMH
I found a firmware bug, if you start and then stop logging using the trigger button, the GPS light turns off and will stay off until you power-cycle the unit. I don't know how to check the firmware version currently installed, but my unit was one of the first Data Junkie packages.

Also, a suggestion: The yaw sensor should be flipped from how it is now by default, so that it gives negative values on left turns and positive values on right turns, to match the default X-axis accelerometer output.

Posted: Sat Apr 20, 2013 12:18 pm
by GameboyRMH
Update: turns out I had 1.1.6, upgraded to 1.1.8, sorry if the bug was already fixed.

Here's another area that could use improvement though, the log files save to the first unused rc_(number).log, so if you save rc_1.log, rc_2.log and rc_3.log, and then delete rc_2.log, the next log you make will be rc_2.log instead of rc_4.log which could be confusing because they're no longer in chronological order.

Posted: Sat Apr 20, 2013 1:41 pm
by Alex W
I noticed the same thing with the GPS LED, but I also noticed that it didn't happen every time, seemed to be a very intermittent problem. I have since updated to 1.1.8 as well, but I haven't yet played with it enough to see if that behavior is gone.

Regarding the log file names, my preferred solution there would be to pull the date and time from the GPS and name them with that, then you would always know which log is which. Ideally it could also figure out what time zone you are in based on the GPS and convert the time to local time in a standard format, but having a timezone setting in the config wouldn't be bad either. How difficult would this be to implement?

Posted: Sat Apr 20, 2013 6:45 pm
by brentp
Timestamping the logfile based on the GPS time is a great idea. We'll get it on the list. Not too difficult to implement, I would imagine.

Posted: Tue May 28, 2013 4:50 pm
by brentp
We're testing the timestamping in the logfile right now; watch for it in the next firmware release!