richardmh
commented
9 years ago Thinking about it... Because lots of people have existing versions of FRDL, keep what it writes to logger.frdl exactly as it is now. Fix for new version is to have the new second file contain only the logger id info so it is usually read-only. This will fix the problem in new versions of FRDL while retaining backwards-compatibility with old versions.
An added bonus might be for it to copy the content of the new file to logger.frdl in the case when it sees logger.frdl is empty. This will improve reliability in older versions.
Very happy you have taken a look at FRDL after so long!
In fact FRDL works quite well, but it has one common problem: Sometimes, when people pull the USB plug too quickly the configuration file FRDL writes on the logger [logger.frdl] is left with null content which then stalls the read next time the logger is plugged in. No track data is lost and the fix is simple but a nuisance:
This always happens quite a few times in every competition and it would be really good to have a fix.
Simple solution is to have TWO configuration files on the logger. Retain logger.frdl, but only keep basic logger ID stuff in it so it is ONLY written when you change logger identification. This is usually only done once before the event so the file will always be read-only during the event thus making chance of corruption much smaller. All the other stuff FRDL writes to a logger whenever you connect it to FRDL should go in a different file which is non-critical if it gets corrupted.
More complicated solution is to make FRDL much simpler.... The original idea of two different 'modes' is really not necessary, the entire 'Download only' mode should be deleted, and I've been meaning to do this for years but never seem to get the time....
ps I didn't find a way of contacting you directly, but you can find me via the FRDL website www.flymicro.com/frdl
Richard