Hi,
I've planned to get NMEA data (wind) to the pypilot. I have a raymarine system, so its running seatalkNG. I do have a DigitalYacht iKonvert Gateway (USB), NMEA2000 to NMEA0183 converter that has an USB output and gives NMEA data to a PC. As a first try I put this USB in the RPI running pypilot (MicroUSB port), but it doesn't work. Anyone tried this?
How would the best possibility be to get the SEatalkNG to NMEA0183 and into pypilot?
Currently I am only running pypilot, so no OpenCPN, but I guess this would be an option.
Edit: Is the microUSB port usable for this? Or should I go via some other serial connection? Somewhere Sean stated you could go from an NMEA0183 network and a USB to serial converter to the pypilot...
Thanks for tips.
//Fabian
HI again,
this is what I got:
tc@box:~$ dmesg | tail
[ 2397.012416] usb 1-1: new full-speed USB device number 4 using dwc_otg
[ 2397.012752] Indeed it is in host mode hprt0 = 00021501
[ 2397.248187] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
[ 2397.248202] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2397.248209] usb 1-1: Product: FT232R USB UART
[ 2397.248216] usb 1-1: Manufacturer: FTDI
[ 2397.248222] usb 1-1: SerialNumber: A601SDDE
[ 2397.251468] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[ 2397.251682] usb 1-1: Detected FT232RL
[ 2397.252784] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
tc@box:~$
I guess it is just some definition that has to be changed?
The nmea test tool on the PC reads wind data, true and apparent. RAW data coming from the converter in wind mode:
$SDMDA,,I,,B,,C,9.8,C,,,,,,T,7.5,M,5.7,N,2.9,M*44
$WIMWV,7.5,R,2.9,M,A*29
$WIVWR,7.5,R,5.7,N,2.9,M,10.5,K*68
$WIMWD,,T,7.5,M,5.7,N,2.9,M*7F
$SDMDA,,I,,B,,C,9.8,C,,,,,,T,7.5,M,5.7,N,2.9,M*44
$WIMWV,7.5,R,2.9,M,A*29
$WIVWR,7.5,R,5.7,N,2.9,M,10.5,K*68
$WIMWD,,T,10.0,M,5.9,N,3.0,M*4A
$SDMDA,,I,,B,,C,9.8,C,,,,,,T,10.0,M,5.9,N,3.0,M*71
$WIMWV,10.0,R,3.0,M,A*12
$WIVWR,10.0,R,5.9,N,3.0,M,10.9,K*51
$WIMWD,,T,10.0,M,5.9,N,3.0,M*4A
$SDMDA,,I,,B,,C,9.8,C,,,,,,T,10.0,M,5.9,N,3.0,M*71
$WIMWV,10.0,R,3.0,M,A*12
$WIVWR,10.0,R,5.9,N,3.0,M,10.9,K*51
$WIMWD,,T,10.0,M,5.9,N,3.0,M*4A
Thanks!
//Fabian
I looks like your adaptor is recognized and a device is set up:
[ 2397.252784] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
That means your adaptor shows up as /dev/ttyUSB0, and you can set its baudrate with stty -F /dev/ttyUSB0 38400.
Then you can verify you get data by typing cat /dev/ttyUSB0.
If that is all right, I should ask the question that should have been asked before: why do you say "but it doesn't work"? What you should see is that the option 'Wind' is added to the dropdown in the pypilot user interface 1).
If you get data, and the option wind is not shown, then it is time to stop pypilot (sudo sv stop pypilot), run pypilot at the prompt, and share the output of it.
1) NOTE: this applies to the OpenCPN plugin and the Openplotter interface; the web interface always shows all options, but if you select wind and there is not wind data, it flicks back to compass.
Hi, thanks a lot for you quick replies. Really awesome!
@Ironman, yes, not working meant I don't get the W on the display and can't choose wind mode.
That's what I did today:
- look for serial_prots -> not existing
- Try to cat ttyUSB0 -> device busy
- down pypilot
- cat ttyUSB0 -> no output
- up pypilot
- telnet 20220 -> all NMEA sentences, incl. MWV
- Check pypilot -> wind mode available.
So, I basically only restarted pypilot without restarting tinypilot. I've turned tinypilot and the instruments off and on a couple of times and wind mode keep beeing available, so it seems to work.
Thanks for your help!
//Fabian