OpenMarine
Raspberry Pi 4 released! - Printable Version

+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: General discussion (https://forum.openmarine.net/forumdisplay.php?fid=2)
+--- Thread: Raspberry Pi 4 released! (/showthread.php?tid=1855)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21


RE: Raspberry Pi 4 released! - Didier B - 2019-09-12

(2019-09-12, 04:22 PM)rastam4n Wrote:
(2019-09-12, 03:56 PM)Didier B Wrote:
(2019-09-12, 03:37 PM)rastam4n Wrote:
(2019-09-12, 12:26 PM)PaddyB Wrote: Or if sigK is working could you add an input type 0183, source serial?

This does not seem to work, says it cannot read property 'pipe' of undefined


Only way I have been able to get it to work is to add a serial connection withing opencpn, would love to get this working in OP

For me it worked nicely (my usb gps is an Ublox-8) : 
  • in SK : Added one connection, input type NMEA, Enabled Yes, Logging YES, serial port : /dev/ttyACM0, Baud rate : 9600, Validate checksum Yes, Apply, Restart ;
  • Then added in OpenCPN Options, tab Connection, Add Connection, network, input, TCP, Address : 10.10.10.1:10110, port 2927, priority 1, OK, and worked perfectly ... 
(beginner's luck, maybe ...)

well something is amiss... 10.10.10.1:10110 is basically saying "localhost"  port 10110 and then adding port 2927? shouldn't it be 2947?
also everything I have read says to use /dev/ttyUSB0  

Which instructions did you follow .... there is a lot of conflicting posts our there re Opencpn and openplotter and how to do this correctly.

also when you say NMEA do you mean 2000 or 0183?

I have it working but only through opencpn, and only via the serial connection, I read this is not correct and it should be done through SK... not sure why it matters... would be great to understand why

You are right Rastam4n, excuse my clerical mistake, it is 2947, not2927, and in my post NMEA means NMEA0183, SK only offers me the choice between /dev/ttyAMA0 and /dev/ttyACM0, no /dev/ttyUSB0...
The only help I got was by the fellow's posts in this  thread, specially : https://github.com/SignalK/signalk-server-node/blob/master/raspberry_pi_installation.md#real-inputs
Ii seems important to restart SK server after any change in the configuration ...


RE: Raspberry Pi 4 released! - Sailoog - 2019-09-13

The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.


RE: Raspberry Pi 4 released! - Max1947 - 2019-09-13

(2019-09-13, 02:47 PM)Sailoog Wrote: The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.

Hi, I've tried all the ways, everything works fine, but I can't configure the gps on usb and make it read signalK. I look forward to seeing that OP 2 is complete. Great anyway and good. Good job ! Tongue Big Grin


RE: Raspberry Pi 4 released! - Sailoog - 2019-09-13

(2019-09-13, 03:29 PM)Max1947 Wrote:
(2019-09-13, 02:47 PM)Sailoog Wrote: The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.

Hi, I've tried all the ways, everything works fine, but I can't configure the gps on usb and make it read signalK. I look forward to seeing that OP 2 is complete. Great anyway and good. Good job ! Tongue Big Grin

But you should be able to do it because OP2  serial app will no make any difference for this. What happens with your GPS an SK, any error?


RE: Raspberry Pi 4 released! - rastam4n - 2019-09-13

(2019-09-13, 03:39 PM)Sailoog Wrote:
(2019-09-13, 03:29 PM)Max1947 Wrote:
(2019-09-13, 02:47 PM)Sailoog Wrote: The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.

Hi, I've tried all the ways, everything works fine, but I can't configure the gps on usb and make it read signalK. I look forward to seeing that OP 2 is complete. Great anyway and good. Good job ! Tongue Big Grin

But you should be able to do it because OP2  serial app will no make any difference for this. What happens with your GPS an SK, any error?

Yah I am having similar challenges

1. in opencpn localhost and port 10110 for gpsd is producing no data stream... although I am not sure what data it would see without being able to setup SK the gps in SK
2. in SK the connections only produce errors 
screen shots attached


RE: Raspberry Pi 4 released! - Sailoog - 2019-09-13

Remove all connections you have in opencpn. You have to have only this connection:
network
TCP
address: localhost
port 10110
input

You do not need gpsd at all.

Then, in SK be sure your GPS is working at 4800 bauds and that the system has assigned /dev/ttyUSB0 to your device. Unplug any USB serial device to be sure of this.


RE: Raspberry Pi 4 released! - MatsA - 2019-09-13

(2019-09-13, 04:16 PM)rastam4n Wrote:
(2019-09-13, 03:39 PM)Sailoog Wrote:
(2019-09-13, 03:29 PM)Max1947 Wrote:
(2019-09-13, 02:47 PM)Sailoog Wrote: The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.

Hi, I've tried all the ways, everything works fine, but I can't configure the gps on usb and make it read signalK. I look forward to seeing that OP 2 is complete. Great anyway and good. Good job ! Tongue Big Grin

But you should be able to do it because OP2  serial app will no make any difference for this. What happens with your GPS an SK, any error?

Yah I am having similar challenges

1. in opencpn localhost and port 10110 for gpsd is producing no data stream... although I am not sure what data it would see without being able to setup SK the gps in SK
2. in SK the connections only produce errors 
screen shots attached

Hi ! in the empty box, in SignalK, to the right You must write /dev/ttyUSB0  The drop down list just shows You the available values. Not Cristal clear ;-)

A really good explanation how OP works is available at this link 

https://docs.sailoog.com/openplotter-v1-x-x/how-does-it-work

from the 1.2 documentation.

Updated my blogpost, at the end of the post for Beta V2 install, with the connection between OpenCPN and SignalK

https://pysselilivet.blogspot.com/2019/08/openplotter-beta-v2-quick-install-guide.html

Maybe it should be added by default by the install programs ? 


RE: Raspberry Pi 4 released! - Max1947 - 2019-09-13

(2019-09-13, 04:22 PM)MatsA Wrote:
(2019-09-13, 04:16 PM)rastam4n Wrote:
(2019-09-13, 03:39 PM)Sailoog Wrote:
(2019-09-13, 03:29 PM)Max1947 Wrote:
(2019-09-13, 02:47 PM)Sailoog Wrote: The logical in OP2 for serial connections is the same than OP1, forget OpenCPN connections! You only need to have there the connection with SK (NMEA 0183 - TCP localhost:10110).

In OP1 we had serial tab to define serial devices and it was creating a connection in SK silently for users.
In OP2 we will have the serial app to define the serial devices (udev rules) but all serial ant network connections must be done in SK. It does not make sense doing this silently because now the SK interface is more than acceptable and users should be aware of this.

Hi, I've tried all the ways, everything works fine, but I can't configure the gps on usb and make it read signalK. I look forward to seeing that OP 2 is complete. Great anyway and good. Good job ! Tongue Big Grin

But you should be able to do it because OP2  serial app will no make any difference for this. What happens with your GPS an SK, any error?

Yah I am having similar challenges

1. in opencpn localhost and port 10110 for gpsd is producing no data stream... although I am not sure what data it would see without being able to setup SK the gps in SK
2. in SK the connections only produce errors 
screen shots attached

Hi ! in the empty box, in SignalK, to the right You must write /dev/ttyUSB0  The drop down list just shows You the available values. Not Cristal clear ;-)

A really good explanation how OP works is available at this link 

https://docs.sailoog.com/openplotter-v1-x-x/how-does-it-work

from the 1.2 documentation.

Updated my blogpost, at the end of the post for Beta V2 install, with the connection between OpenCPN and SignalK

https://pysselilivet.blogspot.com/2019/08/openplotter-beta-v2-quick-install-guide.html

Maybe it should be added by default by the install programs ? 

In OpenCPN it is configured as both a serial USB and a network (localhost -10110). If I remove the tick from the network, the GPS does not transmit. Do you miss anything?


RE: Raspberry Pi 4 released! - rastam4n - 2019-09-13

(2019-09-13, 04:22 PM)MatsA Wrote: Hi ! in the empty box, in SignalK, to the right You must write /dev/ttyUSB0  The drop down list just shows You the available values. Not Cristal clear ;-)


Thank you MatsA
OK, well yah that was not very obvious from a newbies point of view, nor were the other empty boxes where I just made up labels. 
The old version doesn't have as many fields so the documentation does not cover some of this...
Glad there are people like yourself that are interested in making all this a little more user friendly. 
I looked at your blog, nice clear instructions.

Thanks
Pete


RE: Raspberry Pi 4 released! - MatsA - 2019-09-14

(2019-09-13, 08:42 PM)rastam4n Wrote:
(2019-09-13, 04:22 PM)MatsA Wrote: Hi ! in the empty box, in SignalK, to the right You must write /dev/ttyUSB0  The drop down list just shows You the available values. Not Cristal clear ;-)


Thank you MatsA
OK, well yah that was not very obvious from a newbies point of view, nor were the other empty boxes where I just made up labels. 
The old version doesn't have as many fields so the documentation does not cover some of this...
Glad there are people like yourself that are interested in making all this a little more user friendly. 
I looked at your blog, nice clear instructions.

Thanks
Pete
Thx, nice it worked !