2016-09-08, 02:59 PM
Hi
Second chance:
Oziexplorer uses NMEA data from OpenPlotter by TCP via WiFi
In this case, GPS and AIS receiver are connected to the physical ports of OpenPlotter. OpenPlotter sends the NEMEA data on TCP data in system_ output (localhost, port 10110)
On the PC with Oziexplorer set VSPE in this mode:
Create a device type "connector" for example COM10 (this is a virtual port)
Create a device type "TcpClient" TCP COM10 => 192.168.1.7 (this is the IP address of RPi (it must be fixed type)
Device set:
Host TCP 192.168.1.7 (this in my example)
Remote TCP port 10110
serial port COM10 (speed 38400, DTR / RTS no, no parity, 8 bit data, stop 1)
Create a device "Splitter" COM10 => COM1 (COM1 for example, if it is available, or any other available COM)
COM1 is a virtual port that provides the NMEA data in splitter mode, this allows you to set the COM1 as a data input in oziexplorer both GPS data input and AIS data input without creating conflict
Ciao
Second chance:
Oziexplorer uses NMEA data from OpenPlotter by TCP via WiFi
In this case, GPS and AIS receiver are connected to the physical ports of OpenPlotter. OpenPlotter sends the NEMEA data on TCP data in system_ output (localhost, port 10110)
On the PC with Oziexplorer set VSPE in this mode:
Create a device type "connector" for example COM10 (this is a virtual port)
Create a device type "TcpClient" TCP COM10 => 192.168.1.7 (this is the IP address of RPi (it must be fixed type)
Device set:
Host TCP 192.168.1.7 (this in my example)
Remote TCP port 10110
serial port COM10 (speed 38400, DTR / RTS no, no parity, 8 bit data, stop 1)
Create a device "Splitter" COM10 => COM1 (COM1 for example, if it is available, or any other available COM)
COM1 is a virtual port that provides the NMEA data in splitter mode, this allows you to set the COM1 as a data input in oziexplorer both GPS data input and AIS data input without creating conflict
Ciao
Renato