web analytics

Forum

Welcome to the Marine Electronics Forums presented by Panbo and SailBits.

Furuno MFD12 to Raymarine EV-400 pilot issues after software upgrade  

 

Tim Goodyear
(@timg)
Active Member
Joined: 5 months  ago
Posts: 3
July 4, 2018 10:00 am  

I recently helped a friend update the software on his Raymarine autopilot and instruments (by loaning an es127 to do the updates from).  After updates, the autopilot displays “no navigation data” when put into track mode with the Furuno 3D MFD12 in Go To mode to a waypoint.

We tried downgrading the software to a version very similar to what he had originally per a Raymarine FAQ related to Garmin MFD’s with this issue, but with the same symptoms.

Reverting to the latest software allowed Track to operate after manually setting Variation on the P70 (another hint from a Raymarine FAQ), but only to Waypoints created directly on the MFD, not to Waypoints or Routes uploaded to the MFD from Time Zero Navigator software.

Any thoughts on how to debug (I will log N2K data tomorrow when tracking to both types of waypoint), other software versions to try, other solutions to getting Raymarine pilots to work with 3rd party MFD’s?

Equipment / software versions below.

Thanks!

Tim

Original - working as expected

EV1 v1.11 / ACU400 v1.10 / P70 v2.17 / Furuno MFD12 1950055-02.11 / Time Zero Navigator 3.0.0.129 Build 2.12.603.0

Upgrade 1 - no ability to track to any waypoint

EV1 v2.17 / ACU400 v2.23 / P70 v3.07

Upgrade 2 - can track to MFD-created waypoints after manually setting variation

EV1 v3.0 / ACU400 v2.23 / P70 v3.07

Downgrade per Raymarine FAQ - no ability to track to waypoint

EV1 v1.11 / ACU400 v1.13 / P70 v2.17

Other equipment on SeatalkNG network - Icom VHF, Seatalk / Seatalk NG converter to interface ST60 instruments and transducers, i70 instrument

 


ReplyQuote
Tim Goodyear
(@timg)
Active Member
Joined: 5 months  ago
Posts: 3
July 6, 2018 2:19 pm  

A quick update - the Furuno MFD was not sending Magnetic Variation PGN (127258).  Once that was set to send (with the latest Raymarine Software), the "No Navigation Data" message from the P70 went away.  This seems to be different behaviour than earlier versions of the Raymarine Autopilot software. 

The AP now tracks to Waypoints / Routes either manually set up on the Furuno MFD12 3D (when it displays the correct Waypoint name) or sent from Time Zero Navigator Software on a laptop to the MFD (when it displays a random Waypoint number on the "Do you want to Navigate to ####" message, not the Waypoint name displayed on the MFD).  I will work with Furuno / Maxsea on that issue,

Thanks,

Tim


ReplyQuote
Ben Ellison
(@ben-ellison)
Member Admin
Joined: 9 months  ago
Posts: 61
July 6, 2018 2:26 pm  

Thanks, Tim. But I'm a little confused; do you really mean that changed what PGNs a Furuno MFD12 sends with Raymarine software? Also, could you please link to that Raymarine FAQ?

My sense is that Variation can cause various issues on N2K networks, and it's often hard to know where it's coming from. So thanks for describing your issue here as others may run into similar (and I personally have a possibly related Heading issue on my Raymarine network that I haven't solved yet).


ReplyQuote
Tim Goodyear
(@timg)
Active Member
Joined: 5 months  ago
Posts: 3
July 6, 2018 2:55 pm  

Hi Ben,

The PGN's that the Furuno MFD was sending didn't change, but I believe the later versions of the Raymarine Software required Variation to be present where earlier ones did not.

Raymarine Technical Forum, "No Navigation Data" reported when engaging Track mode - Garmin chartplotter
http://forum.raymarine.com/showthread.php?tid=3007
This has instructions to downgrade software to EV1 v1.11, ACU400 v1.13, P70 v2.17 and is now recommended for Garmin MFD's on N2K and legacy Raymarine MFD's on a Seatalk to Seatalk NG converter

Raymarine P70 software release notes for version 3.07 (the current version)
http://www.raymarine.co.uk/view/?id=3803
Variation entered in User Preferences is now applied locally and globally on the STng bus. This corrects a problem introduced in v3.05 whereby the Evolution Pilot, if interfaced to a Seatalk1 Chart Plotter via a STng converter, would not enter Track Mode and alarm "No Navigation Data". If the system has this issue, set the Variation to ON and apply the local variation for that region. Variation can also be set on an i70. If Variation is already present on the STng network the p70 controller will revert to Slave and the problem will not occur

Note that this was not the environment we had on board, but it seemed pertinent to the behaviour.

Thanks for the site - really interesting stuff always!

Tim

Tim Goodyear
Tayana 48, Mojito
Grenada (for now)


ReplyQuote
Ben Ellison
(@ben-ellison)
Member Admin
Joined: 9 months  ago
Posts: 61
July 6, 2018 2:59 pm  

Thank you, Tim. It takes a global village to sort this stuff out 😉


ReplyQuote
Share:


  
Working

Please Login or Register