125 GPS Receiver not connecting after E80 Factory Reset

[kwkisiel]

Chuck

Thanks for your reply and after doing some additional troubleshooting, I believe it's the GPS Receiver that is bad but please correct me if I'm wrong. Summary of problem:

1. E80 MFD would constantly reboot.
2. 125 GP Receiver stayed in the flashing red mode.

Here's what I did:

1. Noticed that when the MFD went into the reboot mode, the Drive Capacity in Use was at 99-100%. A Factory Reset would bring this down to zero and the system would work as normal. However, I've noticed that the used capacity would slowly creep back up.

2. Disconnected all the cables on the MFD except power and after a factory reset everything worked as normal (i.e., no random reboots).

3. Added back all the cables except for the SeaTalk and the system worked as normal.

4. Checked the connection for the SeaTalk and all was tight and secure. Only the GPS receiver and SmartPilot are on the SeaTalk line.

5. Replaced the battery in the GPS (I didn't know there was a battery in there) but had no effect on getting a successful boot (flashing green status).

6. Disconnected the (yellow) SeaTalk input/output wire to the GPS receiver. This supplied power to the GPS without the MFD knowing it was there. The MFD is working as normal (except for the slow increase of the drive capacity usage). The GPS is still blinking red.

Conclusion: I'm assuming that the GPS receiver should boot and lock onto the satellites with just power and not require hand-shaking with an MFD. If that's the case, then I have a bad GPS receiver. If the receiver is bad what would be a good replacement (and easy to install on the SeaTalk network)?

If the receiver does require a connection to the MFD, could upgrading the software from version 5.52 to 5.69 be causing the failure to boot?

Finally, what is causing the MFD data capacity usage to increase? Shouldn't the software periodically clean up the drive and keep it from getting full?

Again, thanks for your help.