Error 10053 & 10054 when converting RDP139 to C-Map

Entropy

New member
Hoping someone on this Forum can provide some guidance as to the next steps to get this working. We were attempting to upgrade a Furuno Navionics RDP139 running Firmware 2023.2 to C-Map by first upgrading the firmware then performing the conversion. All was going swimmingly when everything hung at 62% completion of the conversion with error 10053 & Error 10054. Here is the process:

Laptop used was Windows 10 Professional with USB 3 to Ethernet Dongle.
Laptop battery was fully charged and plugged into a Main AC Power source. All Power Saving features on Laptop disabled.
All Firewalls and Antivirus also disabled on Laptop.
Furuno MJ6 to RJ45 cross over cable was used to connect laptop to Network port on RPD139.
Laptop Assigned static IP of 172.31.200.2 with a Mask of 255.255.0.0
RDP139 IP discovered from unit as 172.31.3.2
Ping Test used to confirm communication between the Laptop and the RDP139 – successful, no dropped packets.
Ran firmware upgrade (netupdate.exe) on Laptop following instructions in "Navnet_loader_software_addendum_2.pdf"
Communication established, Old and New .SRM files created successfully.
Firmware upgrade completed successfully.
Upon reboot RDP139 shows Firmware 2024.3
Reran Program (netupdate.exe) again on Laptop. Program detected that RDP139 Firmware was now current with program and proceed to Conversion Section.
Selected “1943 xxxx (CMAP)” from list to convert the RDP139 to C-Map
Conversion Program initiated and Old and New .SRM Files created successfully on laptop hard drive.
Conversion started and Status Bar progressed to 63% when Error 10053 and then Error 10054 occurred and the conversion process hung.
No longer able to establish communication with RDP139 via program or ping
RDP139 beeps twice on power up, but screen remains blank.

:angry

Any Assistance would be greatly appreciated. Thanks
 

Attachments

  • IMG_3.JPG
    IMG_3.JPG
    90.2 KB · Views: 1,008
  • IMG_2.JPG
    IMG_2.JPG
    109.9 KB · Views: 1,008
  • IMG_1.JPG
    IMG_1.JPG
    109.3 KB · Views: 1,008
Yes ran netupdate.exe as administrator. Ping test and Firmware upgrade went through without issue. So I don't think it is a communication issue. Something hung the conversion process at 62%.
 
Most likely needs to be done with a PC that is XP or older. Newer windows has too many firewalls and AV programs that end up causing problems.
 
Back
Top