Lowrance HDS Waypoint Synchronization Issue
The HDS system in my boat has been running flawlessly for over a year until earlier in the week when I suddenly began to have waypoint sharing issues between the units. The system consists of an HDS 10 and a HDS 7 on the bow and another HDS 10 and 7 on the console. All are linked with Ethernet and NEMA 2000. I am also running 2 Structure Scans (bow and transom), a LGC 4000 antenna, water temp probe, and a weather module. A NEP completes the Ethernet linkage. All are running Ver. 3.5 software.
Five days ago everything was working perfectly. I unhooked the locators, which I have done on several occasions over the last year, to take the boat in for engine repair. Thursday morning I reinstalled them, making sure each unit went back into its respective location. After power-up I asked the system to “Delete All” waypoints because I was going to load a different waypoint file. The waypoint deletion was very slow and did not complete correctly (this was a first). The waypoints from the HDS 10 on the bow where I requested the deletion were erased, but only portions were erased from the remaining locators. I requested another “Delete All” from the console HDS 10 and that command cleared the waypoints from the remaining units. I loaded the new waypoints from the console HDS 10, and they loaded on all the units in the expected time period.
While fishing, I added a new waypoint on the console HDS 7 and noticed that it did not appear on the bow HDS 10 or 7. It did appear on the console HDS 10. I added another…same thing. I added another from the bow HDS 7, and it appeared on all 4. Throughout the day I began adding and trying to delete waypoints from the system. The addition was random. Sometimes they would appear on all 4, sometimes on 2, sometimes on 3. Occasionally only the original unit would contain the waypoint. It did not matter which unit created the waypoint, the results were the same. ..random appearance across the network.
Deleting is also very random, and in general the system adds waypoints more universally than it deletes them. It absolutely will not delete a waypoint from all 4 units. Throughout this entire process I also noticed that the bow HDS 10 was running excruciatingly slow; pausing a significant amount of time for each command. This has never occurred before. The other 3 units were running typical speed without delay.
Another interesting note. Let’s say you create waypoint 001 and it appears on the other three units. Now you delete it from one unit. It will not delete from all, but maybe 2 of them. Now you go back to one of the other units and delete it there. Now it is gone from all 4. The next waypoint you create will be 002, rather than the expected 001. Exported files only show the visible waypoint numbers.
In order to troubleshoot the problem I first checked the NEMA sharing statements on all the units and they were activated to send and receive NEMA data. The backlight synchronization was working perfectly, as was the LGC 4000 and the water temp probe. Sonar and Structure Scan transducer sharing was working. In the ‘Device List” all components were recognized and valid. I did an Auto Configure, but nothing changed. The NEMA diagnostics indicated activity but showed an error, so I reset NEMA. Nothing changed. Powering off did not help.
Thinking the issue could be memory related; I cleared all the files (waypoints, screenshots, and logs) and then purged the memory on each unit. I removed all the mapping chips, and then repowered the units. Working with waypoint 001, the results were the same. A new waypoint randomly appears across the other 3 units, and it can never be deleted from a single unit. Even after deleting it on multiple units, the number remains active in the count log. The next waypoint will be 002. Even after clearing all memory data and removing the mapping chips, the bow HDS 10 continued to run very slow.
I have spoken with Lowrance Customer Service twice and been through their basic 20 question cookbook (same questions both times). No resolve. I have done everything I know to do, short of resetting factory defaults.
Has anyone ever encountered and corrected this issue?
Thanks in advance for your help.