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.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
NMEA2000 data into SignalK
#1
I have hit a brick wall and I am hoping for help getting NEMA 2000 data into my Signal K server from my Actisense in NGT-1 USB unit. I have limited experience with both Linux and signal K, but I am not afraid to get my hands dirty. I've searched all over the forums and cannot find a way to solve this issue. My goal is to get all of the boat's data into signalK so I can stream it to my iPad via Wi-Fi and eventually monitor the boat remotely.

The NGT-1 is plugged in to a USB hub and the hub connected to the raspberry pi. The NGT-1 is recognized as a device and as a connection (colored blue), but I am not seeing any useful NMEA2000 data come through the signal K server. I am getting useful data out of my USB GPS and AIS set up, so that part is working.

A data dump from the system is below.  My questions are:
  • Is there anything obviously out of whack from the data below? 
  • How can I log data that may be coming in via the USB port or through the serial connection to see if there are any obvious issues? 
  • What is the best way to troubleshoot this?

Thanks for any help you can provide.

Basics:
System Raspberry Pi 5 2Gb
Openplotter 4.xx
signalK v. 4.1.0

Connections:
Data type:NMEA 2000
Enabled: yes
ID: can0
NMEA 2000 Source: Actisense NGT-1 (calnboatjs)
Serial port: /dev/ttyOP_can0
Baud rate: 115200

Devices tab:
USB port: 3-2.1:1.0
device/dev: ttyUSB0
alias/dev: ttyOP_can0
vendor: 0403
product: d9aa

Devices: details
CURRENT_TAGS: systemd:
DEVLINKS: /dev/serial/by-id/usb-Actisense_NGT-1_25712-if00-port0 /dev/serial/by-path/platform-xhci-hcd. 1-usb-0:2.1:1.0-porto /dev/ttyOP_can0
DEVNAME: / dev/ttyUSB0
DEVPATH:/devices/platform/axi/1000120000.pcie/1f00300000.usb/ xhci-hcd.1/usb3/3-2/3-11/3-2.1:1.0/ttyUSBO/tty/ttyUSB0
ID_BUS: usb
ID_MM_CANDIDATE: 1
ID_MODEL: NGT-1
ID_MODEL ENC: NGT-1
ID_MODEL_FROM_DATABASE: Actisense NGT-1 NMEA2000 PC Interface
ID_MODEL_ID: d9aa
ID_PATH: platform-xhci-hcd.1-usb-0:2.1:1.0
ID_SERIAL: Actisense_NGT-1_25712
ID_SERIAL SHORT: 25712
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ffffff:
ID_USB_INTERFACE_NUM: 00
ID_USB_MODEL: NGT-1
ID_USB_MODEL ENC: NGT-1
ID_USB_MODEL_ID: d9aa
ID_USB_REVISION: 0600
ID_USB_SERIAL: Actisense_NGT-1_25712
ID_USB_SERIAL SHORT: 25712
ID_USB_VENDOR_ID: 0403
ID_VENDOR: Actisense
ID_VENDOR_ENC: Actisense
ID_VENDOR_FROM_DATABASE: Future Technology Devices International, Ltd
ID_VENDOR_ID: 0403
MAJOR: 188
MINOR: 0
SUBSYSTEM: tty
TAGS: systemd:
USEC_INITIALIZED: 3317040
Reply
#2
A further datapoint on this issue. I just tried with candump, and I got nothing at all. I know there's data on the N2K network, since it's getting picked up by other devices on the network (chart plotter etc.). Does this indicate that data is not getting from the serial port into the can connection? Any ideas on troubleshooting that?
Reply
#3
Another datapoint. Here's what I get in trying to see what's happening on the serial port. Looks like gibberish. Wrong data rate?

$ cat /dev/ttyOP_can0
?????????????????????p???`???????????p????????????????????????????????????????????p???????????????p???????????????`?????????????^C

$ od -x < /dev/ttyOP_can0
0000000 0000 00e0 fc00 8070 e0e0 1cf0 e000 0000
0000020 e0e0 fc80 1c1c 000c 0000 0000 e000 0000
0000040 0000 0000 0000 0000 1c00 1c00 e000 0000
0000060 0000 0000 0000 0000 00e0 fc00 0000 e000
0000100 0000 e0fc e080 f0e0 001c 00e0 e000 80e0
0000120 1cfc 0e1c 0000 0000 0000 00e0 0000 0000
0000140 0000 0000 0000 001c 001c 00e0 0000 0000
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)