Regarding the slow download: Maybe your device is in overwrite mode (when it was erased) and in that case BT747 usually downloads the entire log. You can avoid this either by setting the mode to 'STOP' or by selecting 'Normal download'.
Regarding the HDOP field: The field will not be available in the output if it has not been recorded - that is: you must enable it before you do the track. If it is still not available afterwards, either: the logger does not accept to change the log format (Holux is the king of not accepting settings), or, there is some 'issue' in BT747. As the field is avaible (but empty) in the CSV file it looks like it was detected during conversion that the HDOP field has been enabled, but that none of the positions that you are looking at has a value for it.
Hi Yves Regarding the slow
Hi Yves
Regarding the slow download:
Maybe your device is in overwrite mode (when it was erased) and in that case BT747 usually downloads the entire log. You can avoid this either by setting the mode to 'STOP' or by selecting 'Normal download'.
Regarding the HDOP field:
The field will not be available in the output if it has not been recorded - that is: you must enable it before you do the track.
If it is still not available afterwards, either: the logger does not accept to change the log format (Holux is the king of not accepting settings), or, there is some 'issue' in BT747.
As the field is avaible (but empty) in the CSV file it looks like it was detected during conversion that the HDOP field has been enabled, but that none of the positions that you are looking at has a value for it.