OpenMarine

Hi,  I have just finished installing a B&G WS310 wind sensor, and can't seem to get data from it to display in OpenPlotter.  I am using latest versions of both OpenCPN and OpenPlotter on an RP5 with the MacArthur hat, so basically an all-new system, both hardware and software.  I see incoming traffic on the status led on the mac hat, but cannot get the wind data to display on a dashboard.  So far, I have AIS working, and the autopilot (pypilot) seems to be working too, in "bench mode"--I haven't yet done a sea trial.  As I am new to the open source navigation world, I suspect there is something I have yet to do to configure the connection between the nmea0183 ports on the hat and OpenCPN.  After spending considerable time in Signal K configuration and the "Connections" menu on OpenCPN, I realize I need some help to sort this out.  The manufacturer's manuals and specs make it seem as if the WS310 "speaks" nmea0183, but I'm wondering if the data on the oem cable is somehow made proprietary, and can't be read by the rp/mac?

I didn't see any mention of the speed of the NMEA0183 connection in the manual for the WS310 that I found on the web, so my guess would be 4800 bps. If you haven't already done so, try setting serial speed to that. If that doesn't work, try 38400.

It could also be a polarity problem: https://macarthur-hat-documentation.read...tml#wiring

Thanks to both Adrian and Sailoog for your replies... I was fairly sure of the wiring, which I believe IS correct. Being a rather persistent, even stubborn, sort of person, I just kept on making changes to all of the variables available in the menus of Main/Serial and and Main/Signal K until I got some wind data presented on the default dashboard... That now does seem to be working, using the nmea0183 Port 2 on the RF5 (UART4), and a speed of 38400. I wish I knew what exactly I did to get to this result, because I know I will need to understand this system more fully when I begin using it in earnest, starting with coastal cruising in the US Pacific Northwest, and western Canada.

I continue to have a problem (according to "Check Systems") with CAN device connection to OpenPlotter: when performing system check I get the message: "There is no Signal K connection for interface can0", where can0 is the alias assigned to (I think) the nmea2000 bus, connected to the RP5 as described in the OP documentation. This connection uses UART1, is Signal K, and baud rate is 115200 (which was set by default when I created the connection). My nmea2000 (canbus) currently is being used only to connect my AIS transponder, which is an em-trak B954 model, purchased new 3 months ago. AIS data seems to be working fine, presenting on the OP chartplotter, so I am not sure why I get the above message about not having a Signal K connection...

Additional problems I have not figured out yet are 1) heading information does not show up on OP's dashboards; and 2) my Halo+ radome does not initialize and display on the chartplotter screen. I have tried (repeatedly installing, uninstalling, reinstalling radar plugins, with no success. Troubleshooting LED codes on the radome itself indicate that the (ethernet) connection to the RP5 is "normal", and on the RP5 the tiny little led status lights on the rj45 socket indicate incoming data, so the problem appears to be at the RP5, or between the RP5 and the monitor I have connected to it. (and yes, openGL is selected).

I will soon be attempting my first sea-trial of pypilot, which in my case is driving an old CPT autopilot motor, driving a belt & pulley on the helm's wheel. The motor seems to be driving the wheel nicely in response to trial inputs on the autopilot gui, at least in my slip at the marina. I'm excited to give it a try under-way!

Thanks for any suggestions you may have on the remaining problems described, and THANK YOU SO VERY MUCH for your efforts to democratize the world of marine navigation electronics!

Gene

(2024-09-05, 07:44 PM)Kitsatoo Wrote: [ -> ]Thanks to both Adrian and Sailoog for your replies...  I was fairly sure of the wiring, which I believe IS correct.  Being a rather persistent, even stubborn, sort of person, I just kept on making changes to all of the variables available in the menus of Main/Serial and and Main/Signal K until I got some wind data presented on the default dashboard...  That now does seem to be working, using the nmea0183 Port 2 on the RF5 (UART4), and a speed of 38400.  I wish I knew what exactly I did to get to this result, because I know I will need to understand this system more fully when I begin using it in earnest, starting with coastal cruising in the US Pacific Northwest, and western Canada.

I continue to have a problem (according to "Check Systems") with CAN device connection to OpenPlotter:  when performing system check I get the message:  "There is no Signal K connection for interface can0", where can0 is the alias assigned to (I think) the nmea2000 bus, connected to the RP5 as described in the OP documentation.  This connection uses UART1, is Signal K, and baud rate is 115200 (which was set by default when I created the connection).  My nmea2000 (canbus) currently is being used only to connect my AIS transponder, which is an em-trak B954 model, purchased new 3 months ago.  AIS data seems to be working fine, presenting on the OP chartplotter, so I am not sure why I get the above message about not having a Signal K connection...

Additional problems I have not figured out yet are 1) heading information does not show up on OP's dashboards; and 2) my Halo+ radome does not initialize and display on the chartplotter screen.  I have tried (repeatedly installing, uninstalling, reinstalling radar plugins, with no success.  Troubleshooting LED codes on the radome itself indicate that the (ethernet) connection to the RP5 is "normal", and on the RP5 the tiny little led status lights on the rj45 socket indicate incoming data, so the problem appears to be at the RP5, or between the RP5 and the monitor I have connected to it.  (and yes, openGL is selected).

I will soon be attempting my first sea-trial of pypilot, which in my case is driving an old CPT autopilot motor, driving a belt & pulley on the helm's wheel.  The motor seems to be driving the wheel nicely in response to trial inputs on the autopilot gui, at least in my slip at the marina.  I'm excited to give it a try under-way!

Thanks for any suggestions you may have on the remaining problems described, and THANK YOU SO VERY MUCH for your efforts to democratize the world of marine navigation electronics! 

Gene

did you  write up on the CPT i was wondering if this could work... please post details

It was really simple. My boat came with a very old CPT Autopilot II system comprising a drive/control unit that contains the motor and the control electronics. There was a separate sensing unit, a photo-optic compass, that no longer worked, so I decided to keep the drive system already installed on the helm and simply drive the motor with the new Pypilot motor controller I purchased. It was simply a matter of connecting the motor power wiring to the new controller, and it now drives the wheel nicely. I was able to purchase a new pulley and belt, which had deteriorated. CPT is still in business, and still making all of the original components, which is quite something to say after 30+ years!