This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Raymarine autohelm 3000 with Radio Nav Interface Z075
#1
   

##(A good deal of related and helpful information for noobs like myself learning how NMEA devices are connected surfaced at this thread on making a gps puck feed data to an old Standard Horizon vhf radio: http://forum.openmarine.net/showthread.php?tid=1815 )

My Tartan 37 has a working Raymarine 3000 which used to be driven through a Raymarine Z075 Radio Navigation Interface by a very old external GPS, now dead. This autohelm works fine with its internal compass in the controller unit.

I've recently built OpenPlotter into an RPi3B+ with a dAISy hat. It's set up to run headless via wifi with VNC, or by sharing data over Kplex. Works great with OpenCPN, and iNavx. Now I'd like to try using OpenCPN to drive the autohelm through that Z075 radio nav interface to track a course.

It's difficult to find tech data about that interface unit. I've read that it uses either or both of NMEA0180 and NMEA0183 sentences,  and I've also read (but not confirmed) that it uses the XTR sentence (not XTE) to command a left or right turn to the helm motor. The interface has a gain selector control which is set according to boat speed. I've not used this unit, but presume it would work if it receives the x-track error information in a form it can understand.

I understand that XTR x-track is a "dead reckoning" measure, while XTE is a "measured" x-track error. I'm guessing that XTR has been deprecated in favor of XTE, but I don't know if one would be the working equivalent of the other.

I've read extensively about the Pypilot project, and eventually would like to build or buy a TinyPilot unit to use to run my helm motor. But first, I'd like to know if it is possible to make OpenCPN running in my Rpi unit under OpenPlotter generate the correct NMEA sentences to drive the Raymarine Z075 radio interface, to track a course.  I'm thinking that my existing 3000 motor controller (and the spare that came with the boat) would do fine service if I could figure out how to feed the turn commands to it through the Raymarine interface.

Has anyone tried this?  I'd deeply appreciate any insights to using my existing hardware, at least for the time being. Thanks in advance for whatever anyone shares on this topic!
  Reply
#2
[quote pid='8997' dateline='1558715449']
Hi, I have this interface whit Autohelm 3000 on my boat, I used it for long time by a signal from Garmin GPS 128 and it work fine. now I'm trying to make it work by controlling it from Opencpn but I have problems. The signal reaches the interface because the two LEDs stop flashing but the course corrections have no effect. even when I set a route on the Garmin, which still sends the position signal to the PC with opencpn the LEDs stop flashing but no course correction, when the Garmin was connected directly to Z075 everything worked. I don't know if you've made progress in your tests but let's keep in touch.


##(A good deal of related and helpful information for noobs like myself learning how NMEA devices are connected surfaced at this thread on making a gps puck feed data to an old Standard Horizon vhf radio:  http://forum.openmarine.net/showthread.php?tid=1815  )

My Tartan 37 has a working Raymarine 3000 which used to be driven through a Raymarine Z075 Radio Navigation Interface by a very old external GPS, now dead. This autohelm works fine with its internal compass in the controller unit.

I've recently built OpenPlotter into an RPi3B+ with a dAISy hat. It's set up to run headless via wifi with VNC, or by sharing data over Kplex. Works great with OpenCPN, and iNavx. Now I'd like to try using OpenCPN to drive the autohelm through that Z075 radio nav interface to track a course.

It's difficult to find tech data about that interface unit. I've read that it uses either or both of NMEA0180 and NMEA0183 sentences,  and I've also read (but not confirmed) that it uses the XTR sentence (not XTE) to command a left or right turn to the helm motor. The interface has a gain selector control which is set according to boat speed. I've not used this unit, but presume it would work if it receives the x-track error information in a form it can understand.

I understand that XTR x-track is a "dead reckoning" measure, while XTE is a "measured" x-track error. I'm guessing that XTR has been deprecated in favor of XTE, but I don't know if one would be the working equivalent of the other.

I've read extensively about the Pypilot project, and eventually would like to build or buy a TinyPilot unit to use to run my helm motor. But first, I'd like to know if it is possible to make OpenCPN running in my Rpi unit under OpenPlotter generate the correct NMEA sentences to drive the Raymarine Z075 radio interface, to track a course.  I'm thinking that my existing 3000 motor controller (and the spare that came with the boat) would do fine service if I could figure out how to feed the turn commands to it through the Raymarine interface.

Has anyone tried this?  I'd deeply appreciate any insights to using my existing hardware, at least for the time being. Thanks in advance for whatever anyone shares on this topic!
[/quote]
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)