- Last Active
I spent part of my career in the IT (information technology) world. My wife is still involved with IT. Even back in the 90's I was amazed at how willing company management was to connect all their computers to the wide wide world with only a firewall between them and people willing to extort them.
Firewalls only provide a layer of security. Not total security. This stuff has been happening for a long time and management of companies not hit by such still don't get it.
Even for those that do, their IT infrastructure is so tied to connectivity now they will spend a lot of money, probably as much as the ransom money to change how their IT functions at base levels to add more layers of security.
I'd think the issue is with the GPSmap. When my Garmin Edge does a similar thing with my HR monitor or speed/cadence sensor, It's typically been the Edge device. I'll have to go in an re-pair the device and save the pairing. Typically does happen around battery replacement time, but it's been awhile since I've had to mess with that.
The last time I had issues though was three years ago. It happened with a new HR strap, I called Garmin and it still ended up being the Edge unit. The Garmin rep over the phone had me do several things and I don't quite remember what or the order I did them. So give them a call and see what they say. Even if you are long out of warranty, they may offer you a flat rate repair that typically is a replacement with a refurb'd unit for a very low cost that might be worth it.
There is a menu item in the GPSmap that might be some steps you need to go through again..........
I'll probably get too annoyed with it again and uninstall it from my phone. But it is nice being able to share locations that Google maps can find but Garmin can't with my DS61. Sad that there is so much of what I consider bloatware attached to it. Presumably too many features just make it more difficult to keep everything running right without bugs or annoyances.
It's an old and discontinued product. So maybe one will turn up eventually on ebay or elsewhere if you only want the same. I don't know the number of pins on your device, however for my garmin marine products, I was able to use the same power/data cable with three maybe four or more different chartplotters that were brand new products over the course of 12 years.
I think the last garmin chart plotter I got circa 2016 did require a change, but I don't remember whether it was because of the unit having more pins or just that a reconfiguration of the boat required a longer cable and the original had be cut too short. To late to check now, unfortunately I'm without a boat now.
So you've got a good chance, I think of finding something used on ebay of a different and newer model that will still have the same pinout. Likely, if you aren't using this in conjunction with other nema enabled devices, then you probably are only using two wires in the current cable. They are just the positive and negative power wires. Don't be afraid of a new device with more wires. Because if you still don't need it to talk to other nema enabled devices or turn on a additional alarm, then you still will only need two of the wires in the cable connected to anything.
I don't understand your concern here. Being mounted as a portable device, which should give it a removal policy of "3", is the safest method to protect it from corruption due to unexpected removal. The other removal policies do nothing to ensure a better outcome, they just let Windows and other programs behave in a riskier manner.I am not happy that the 680T is definitely mounted as a portable device and not needing safe release.
You can verify the removal policy when the device is connected by right clicking on any storage device in the file explorer and selecting "properties" then the "hardware" tab, then select the correct device from the list and then the "properties" button near the bottom, then the "details" tab, then select "removal policy" from the dropdown list. If it is a "3", then Windows will not cache writes to that device. It is write caching which causes file corruption due to unexpected removal.