It would be very interesting to have the "smart dowload" function resuming dowload from the last one even if the memory has been filled up in the meanwhile, thus allowing for the creation of a semaless log bigger than the device memory.
Here is an example: suppose the device can store 100 poiints, and I'm starting from a fresh erased memory.
I record 40 points, then download them without erasing the memory.
Then I record 40 more points. When I dowload them, the "smart dowload" function recognize that the first 40 are already dowloaded, and dowload alny the last 40 (actual behaviour). I'm still not erasing the memory.
Then I record 40 more points, thus overwrtiting the first 20 (I had only 20 free in memory). At this point, BT747 reports the device memory as not corresponding to the log file anymore, and ask for overwriting or choosing a different filename.
It would be nice if the software can recognize (expliting the point from 20 to 80, that are present both on the device and on the log file) that it can dowload points 80 to 100 and 1 to 20 and append them to the previous log file, thus creating a 120 pints long logfile with contiguos, seamless recording.
Log in to post a comment.