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
Connecting NMEA Wind data from NASA Clipper
#1
Hi,
I have a problem connecting my NASA Clipper Tactical Wind System (NMEA 0183) to my OpenPlotter setup:
OpenPlotter: 0.17.1
Raspberry Pi 3
Connected devices in this test:
- GPS G-Star
- Cabled Ethernet
- Keyboard/Mouse/screen
- USB RS422/485 CAN Stick connected to NASA Wind System bought from Sailoog
- 1W temp sensor/GPIO relay board/Float sensor

Compass/SPI sensors is disabled since i saw in another post that this may interfere

I have connected the Wind System and the green light is blinking nicely

Here is the problem: When i run Autosetup (of USB Connections), i can see the NMEA sentences (the auto setup is inserted below) and it reports "found NMEA0183 on /dev/ttyUSB0 with baudrate 4800", but it never creates an auto-name so that i can "Add individual name to serial port" in the USB manager ...never creates anything selectable like it does when i add GPS etc.

Most often it hangs during the autosetup process but continues if i disconnect the USB/422 adapter.

Any thoughts?


/M
-------
Auto setup detects hardware. Please make sure that all devices are turned on.



search for tty devices
found: /dev/ttyS0 internal   3f215040.serial  
found: /dev/ttyUSB1 067b 2303  1-1.2:1.0 PL2303 Serial Port Prolific Technology, Inc.
found: /dev/ttyUSB0 1a86 7523  1-1.3:1.0 HL-340 USB-Serial adapter QinHeng Electronics

sort tty devices

check if we have to switch from dev to port
test  ['', '067b', '2303', '', '1-1.2:1.0', 'dev', 'ttyUSB', '/dev/ttyUSB1', 'PL2303 Serial Port', 'Prolific Technology, Inc.', 0]
test  ['', '1a86', '7523', '', '1-1.3:1.0', 'dev', 'ttyUSB', '/dev/ttyUSB0', 'HL-340 USB-Serial adapter', 'QinHeng Electronics', 0]
test  ['', 'internal', '', '', '3f215040.serial', 'dev', 'ttyS0', '/dev/ttyS0', '', '', 0]

search for NMEA0183 in tty devices

search NMEA0183 on /dev/ttyUSB1 with baudrate 4800
    Vc&vcFcVv$GPGSA,A,3,25,29,31,02,12,14,06,32,,,,,1.9,1.2,1.5*3
    $GPRMC,144034.000,A,5728.2680,N,01205.5684,E,0.00,334.93,140418,,,A*6
    $GPGGA,144035.000,5728.2680,N,01205.5684,E,1,08,1.2,9.7,M,40.1,M,,0000*5
    $GPGSA,A,3,25,29,31,02,12,14,06,32,,,,,1.9,1.2,1.5*3
    $GPRMC,144035.000,A,5728.2680,N,01205.5684,E,0.00,334.93,140418,,,A*6
found NMEA0183 on /dev/ttyUSB1 with baudrate 4800
search NMEA0183 on /dev/ttyUSB0 with baudrate 4800
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
    $WIMWV,358,R,0,N,A*2
found NMEA0183 on /dev/ttyUSB0 with baudrate 4800

create an autoname for found NMEA0183 devices
    $GPGSA,A,3,25,29,31,02,12,14,06,32,,,,,1.9,1.2,1.5*30
    $GPRMC,144038.000,A,5728.2680,N,01205.5684,E,0.00,334.93,140418,,,A*6F
.
.
.
.
.

    $GPRMC,144046.000,A,5728.2680,N,01205.5684,E,0.00,334.93,140418,,,A*66
    $GPGGA,144047.000,5728.2680,N,01205.5684,E,1,08,1.2,9.8,M,40.1,M,,0000*5C
    $GPGSA,A,3,25,29,31,02,12,14,06,32,,,,,1.9,1.2,1.5*30
    $GPRMC,144047.000,A,5728.2680,N,01205.5684,E,0.00,334.93,140418,,,A*67
    $GPGGA,144048.000,5728.2680,N,01205.5684,E,1,08,1.2,9.8,M,40.1,M,,0000*53
    $GPGSA,A,3,25,29,31,02,12,14,06,32,,,,,1.9,1.2,1.5*30
created the name: ttyOP_GP
  Reply
#2
thats strange ..
the guys are busy working on the next release and looks like they are addressing this .
https://github.com/sailoog/openplotter/c...4c5fad0dbb
mare liberum
  Reply
#3
(04-15-2018, 07:29 AM)jim321 Wrote: thats strange ..
the guys are busy working on the next release and looks like they are addressing this .
https://github.com/sailoog/openplotter/c...4c5fad0dbb

We are putting a lot of hope as always in the next version but it is good, i just hope that they are aware of this behavior so that the catch these issues too  ...  anything i should do? I mean, if i was at my work i would report a JIRA, a bug.

It /is/ a very strange behavior. Somebody mentioned that NASA instruments still run NMEA0183 V1, unbalanced and without checksum... but i can find no information verifying that.
As long as i can see the messages in auto-setup i should be on safe ground reception-wise but then how to make these messages show up iin signal K ...have no idea.

/M
  Reply
#4
I run the older Nasamarine NMEA wind instrument. 

I have seen what you are speaking about, and with persistence am able to get it working, though I can't remember specifically how. Try configuring manually, rebooting, moving off of a tab and back again to see if what you saved stayed there... and other favorite superstitious rituals. Smile

There's nothing specific to this instrument you need to do.


On my wish list has been a way to reset "dead ahead" by entering in an offset amount in software, so that this adjustment could be made more easily singlehanded or at dockside. I'm not certain how universal this little inconvenience is to wind instruments.
  Reply
#5
(04-15-2018, 04:24 PM)Saqqara Wrote: I run the older Nasamarine NMEA wind instrument. 

I have seen what you are speaking about, and with persistence am able to get it working, though I can't remember specifically how. Try configuring manually, rebooting, moving off of a tab and back again to see if what you saved stayed there... and other favorite superstitious rituals. Smile

There's nothing specific to this instrument you need to do.


On my wish list has been a way to reset "dead ahead" by entering in an offset amount in software, so that this adjustment could be made more easily singlehanded or at dockside. I'm not certain how universal this little inconvenience is to wind instruments.

Thanks Saqqara,

Well, if it's only persistence that is needed, then I'm almost done...
Knowing that someone else has succeeded is a fantastic motivator!

I also see that there is a lot of not only persistent but smart people in this forum so i hope that i can get some help, saving my persistence for another day.
Any ideas and hints welcome.

... Is it not possible to just add a few lines directly in the config files in the /dev/ directory like edit the ttyHUB2 file

@Jim, i read through the material on the github autoconfig you gave but see no reference to solving my problem. Lots of GPS and N2K stuff though, but i guess they are not finished yet

Well, here in Sweden we are getting our boats ready for the water ... yessssss!

BR/M
  Reply
#6
Saqqara,
Like i said, it is good to have an understanding of what it should look like in a working setup with the NASA system, so i wonder if you could take some screenshots of your "USB Manager" and "NMEA 0183"  tabs? 
If possible could you also give me a hint of how the physical connections are done: The setup i am having has the NASA Clipper tactical wind system with the wired NMEA0183 masttop unit connected to the Sailoog RS422/USB adapter. The output from the NMEA masttop unit is only three cables. V+. NMEA and Earth(=v-) so it is not apparent how to connect this to an RS422 which is balanced. anyway, i hav the green light blinking nicely and the NMEA MWV's visible in the Auto setup so something must be working
BR/M
  Reply
#7
if its an older nmea standard others have used different serial adapters to receive results.
http://forum.openmarine.net/showthread.php?tid=1003

Didier B did a good write-up pdf.

http://forum.openmarine.net/attachment.php?aid=253
mare liberum
  Reply
#8
(04-16-2018, 09:10 AM)jim321 Wrote: if its an older nmea standard others have used different serial adapters to receive results.
http://forum.openmarine.net/showthread.php?tid=1003

Hi, 

Yes i have seen that thread and tried his approach, even built the cable but unfortunately to no joy...nothing showed in the auosetup like the MWV's I get with my current setup

/Micael
  Reply
#9
the dev's only post about once a week don't give up yet...
mare liberum
  Reply
#10
(04-16-2018, 05:24 AM)Smartell Wrote: Saqqara,
Like i said, it is good to have an understanding of what it should look like in a working setup with the NASA system, so i wonder if you could take some screenshots of your "USB Manager" and "NMEA 0183"  tabs? 
If possible could you also give me a hint of how the physical connections are done: The setup i am having has the NASA Clipper tactical wind system with the wired NMEA0183 masttop unit connected to the Sailoog RS422/USB adapter. The output from the NMEA masttop unit is only three cables. V+. NMEA and Earth(=v-) so it is not apparent how to connect this to an RS422 which is balanced. anyway, i hav the green light blinking nicely and the NMEA MWV's visible in the Auto setup so something must be working
BR/M
Your hardware is fine if you see the data scroll by. It just isn't keeping the settings.

I haven't had any boat time in weeks but will try to get you specifics some evening this week.

Sent from my Moto G (5) Plus using Tapatalk
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)