V-2000 problem reading tracks via iPhone / unusual folders on drive
Quote from anonymous on November 10, 2026, 4:25 pmwe'd like to report a problem we ran into with the V-2000 over the weekend, but first the good news: we took the loggers along to a search dog exam in the forest, and André and Mia passed! During the exam, the dog ran 4.6 km. I'm attaching a picture of the map and of the successful team.
Afterwards, however, we were unable to read out the tracks on our iPhones via OTG, and we have to admit that we were quite disappointed at first. We had told the examiners about the V-2000, and they were very interested. Unfortunately, we couldn't show them the track on the spot. Fortunately, the readout worked on a Mac later on, and we are now sending them the map and Mia's route afterwards.
We noticed that something seems off with the drive:
- On the V-2000 drive there is a folder called "LOST.DIR", which contains no files. We could also see this folder on the iPhone.
- On the Mac we additionally see a folder called "System Volume Information", which contains the missing tracks.Interestingly, one of our two loggers worked correctly and created a new folder at the change of the month, while the other one showed the behavior described above.
I'm attaching a ZIP file with the content of the drive, so your engineer can have a look.
Could you please let us know whether this is a known behavior and what we can do to make the readout on an iPhone work reliably? Being able to check the tracks directly in the field is important to us, especially when others are interested in seeing the results right away. We're happy to provide more details or run further tests if needed.
we'd like to report a problem we ran into with the V-2000 over the weekend, but first the good news: we took the loggers along to a search dog exam in the forest, and André and Mia passed! During the exam, the dog ran 4.6 km. I'm attaching a picture of the map and of the successful team.
Afterwards, however, we were unable to read out the tracks on our iPhones via OTG, and we have to admit that we were quite disappointed at first. We had told the examiners about the V-2000, and they were very interested. Unfortunately, we couldn't show them the track on the spot. Fortunately, the readout worked on a Mac later on, and we are now sending them the map and Mia's route afterwards.
We noticed that something seems off with the drive:
- On the V-2000 drive there is a folder called "LOST.DIR", which contains no files. We could also see this folder on the iPhone.
- On the Mac we additionally see a folder called "System Volume Information", which contains the missing tracks.
Interestingly, one of our two loggers worked correctly and created a new folder at the change of the month, while the other one showed the behavior described above.
I'm attaching a ZIP file with the content of the drive, so your engineer can have a look.
Could you please let us know whether this is a known behavior and what we can do to make the readout on an iPhone work reliably? Being able to check the tracks directly in the field is important to us, especially when others are interested in seeing the results right away. We're happy to provide more details or run further tests if needed.
Quote from GPSWebShop Official on November 10, 2026, 4:27 pmHere are the comments from the Columbus engineering team:
===========================================
The issue that prevents an iPhone from recognizing and reading track data from the V-2000 appears to occur under the following circumstances:
Based on our findings so far, the issue can occur when the V-2000 has previously been accessed on a Windows computer and files have been cut and pasted on the device. If the same V-2000 is then connected to an iPhone, the iPhone may fail to recognize it.
We suspect this may be related to the way different operating systems access the V-2000's storage. For example, Windows and iOS may create their own system files (such as Recycle Bin folders) on the device. If the USB cable is disconnected directly without safely ejecting the device first, these operations may not be completed properly, potentially resulting in the issue described above.
We are currently working on firmware improvements to address this issue.
In the meantime, you can try restoring the V-2000 to its factory settings. After the reset, if the V-2000 has not been accessed by Windows (i.e., Windows has not written any additional system data to the device), you should find that the iPhone can recognize the V-2000 and read its track data normally.
For instructions on how to restore the factory settings, please refer to:
https://cbgps.com/v2000/manual/knowledge/factory_reset/factory_reset.htm
Here are the comments from the Columbus engineering team:
===========================================
The issue that prevents an iPhone from recognizing and reading track data from the V-2000 appears to occur under the following circumstances:
Based on our findings so far, the issue can occur when the V-2000 has previously been accessed on a Windows computer and files have been cut and pasted on the device. If the same V-2000 is then connected to an iPhone, the iPhone may fail to recognize it.
We suspect this may be related to the way different operating systems access the V-2000's storage. For example, Windows and iOS may create their own system files (such as Recycle Bin folders) on the device. If the USB cable is disconnected directly without safely ejecting the device first, these operations may not be completed properly, potentially resulting in the issue described above.
We are currently working on firmware improvements to address this issue.
In the meantime, you can try restoring the V-2000 to its factory settings. After the reset, if the V-2000 has not been accessed by Windows (i.e., Windows has not written any additional system data to the device), you should find that the iPhone can recognize the V-2000 and read its track data normally.
For instructions on how to restore the factory settings, please refer to:
https://cbgps.com/v2000/manual/knowledge/factory_reset/factory_reset.htm