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
Pypilote Opencpn compass conection doesn't work
#1
I am using RP3 with OpenPlotter 2.0.1-beta and mpu92. It worked before upgrade. 

Detected IMU compass mpu9255

localhost:3000 ok

localhost:20220 connection in OpenCPN no response
Signal K Instrument no response 
Should I downgrade? How?

Boot log:
Checking OpenPlotter autostart... | enabled
Checking user "pi" password... | changed
Checking screensaver state... | enabled
Checking headless state... | disabled
Checking OpenPlotter packages source... | added
Checking Signal K server... | running
Checking I2C sensors... | I2C enabled | not running
Checking OpenCPN... | not running | autostart disabled
The default OpenCPN connection is missing and is not getting data from Signal K. Please create this connection in OpenCPN:
Network
Protocol: TCP
Address: localhost
Data Port: 10110
Checking My App dummy sensors... | not running
Checking Pypilot... | Only compass
Please enable a Signal K connection fot Pypilot Signal K data
Checking Moitessier HAT... | not attached | I2C enabled | SPI enabled
Moitessier HAT driver is not installed.
Checking serial connections alias... | All your serial connections have an assigned alias
Checking serial connections conflicts... | no conflicts
Checking network connections conflicts... | no conflicts
STARTUP FINISHED

Signal K - NMEA 0183 output (server)
TCP openplotter.local:10110
TCP 10.25.1.87:10110
OpenCPN connection (server)
UDP openplotter.local:20220
UDP 10.25.1.87:20220
Internal Pypilot Signal K server (server)
TCP openplotter.local:21311
TCP 10.25.1.87:21311
Pypilot Signal K output (client)
UDP openplotter.local:20220
UDP 10.25.1.87:20220
Smile Daniel, Sailing Rocinante
  Reply
#2
pypilot has input and output of nmea0183 on 20220. Maybe you tried to make a signalk connection in opencpn which is a very new feature and doesn't work with pypilot.
  Reply
#3
Photo 
Tnx for quick response. I used the SD image with the OpenPlotter 2.0.2-beta. Since the NMEA didn’t work, I tried to change a few things. 


The only thing in Pypilot mentioned under “Connections” is Signal K:Heading, Heel, Pitch. -> Should I remove that and make a NMEA connection?


https://drive.google.com/file/d/1b-2ZSoQ...sp=sharing
Smile Daniel, Sailing Rocinante
  Reply
#4
In pypilot "only compas" mode you get signal k data in UDP localhost 20220. You have to create that connection in SK and use "signal k to NMEA 0183" plugin to get data in opencpn by TCP localhost 10110
In pypilot "autopilot" mode you get NMEA 0183 data in TCP localhost 20220. You have to create that connection in SK and you will get NMEA 0183 directly in opencpn by TCP localhost 10110.

Remember, remove any opencpn connection. You have to set just TCP localhost 10110 imput in Opencpn to get data from SK.

this will be easier when we have documentation Smile
  Reply
#5
This is very confusing because there are multiple paths and conversions of data possible.

There is a pypilot plugin of openplotter which converts pypilot signalk into signalk node which can then be converted to nmea0183 available on tcp 10110. pypilot directly provides nmea0183 on port 20220 or assigned serial ports. So far output is only to tcp connections, but it might be useful to be able to assign particular serial ports to output certain nmea data, it just isn't supported or implemented yet.

Sean
  Reply
#6
(01-07-2020, 12:43 PM)Sailoog Wrote: Now I managed to get it run with the autopilot" mode. Thank you very much Sean for all the help you gave me. I am going to use the Openplotter with the autopilot on my yacht sailing for a year from July. If you need any help with the documentation, tell me, I am fluent in German and Norwegian. Cool
Smile Daniel, Sailing Rocinante
  Reply
#7
(01-07-2020, 05:07 PM)seandepagnier Wrote: This is very confusing because there are multiple paths and conversions of data possible.

There is a pypilot plugin of openplotter which converts pypilot signalk into signalk node which can then be converted to nmea0183 available on tcp 10110.    pypilot directly provides nmea0183 on port 20220 or assigned serial ports.   So far output is only to tcp connections, but it might be useful to be able to assign particular serial ports to output certain nmea data, it just isn't supported or implemented yet.

Sean

Yes, it is a little bit confusing but I hope it will get easier with documentation.

Lot of people will use "the only compass" mode and we prefer to generate SK data for heading, pith and roll instead of NMEA 0183 because SK node server can not parse XDR sentences for pith and roll. We use UDP localhost 20220 for this. SK node server can convert pith and roll into NMEA 0183.

When using the "autopilot" mode, NMEA O183 data is generated for heading, pith and roll in TCP localhost 20220 but we need to keep UDP localhost 20220 only with pith and roll SK data to get these data into SK node server. This time conversion from SK to NMEA 0183 for pith and roll is not necessary.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)