Thread: Zumo 345LM reduced connectivity issues with Basecamp

With GE I was able to download and install the cards again.
From the backup I could restore some directories like POI / Themes

Connecting now to BC and also to MapSource give no error message at all and the device is poperly displayed as zumo 345 and device id
Also the card is shown as CN 2022.10 and not the Foursquare map.
Even transfer options to the device can be adjusted.


It looks like some files messed up the communication and now everything works fine.

Spoiler: screenshot

[Only registered and activated users can see links. ]

Edit:
Today I discovered the real cause of the problem:
I was comparing both the device and a backup on an SD card.
I tried some things on both and I messed up again the zumo communication by copying some .unl and .gma files from the backup .\System\Map\ directory to the zumo device.
Removing the .unl and .gma files which do not belong to the Foursquare map and a clearnonvol action, did the job much faster than before.

So in .System\Map\ the only files there are:
D4935220A.gma
D4935220A.img
D4935220A.unl

So a combination of Foursquare Maps and City Navigator can really mess up the system.