-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nexus network connection (WSI Box) #7
Comments
In your fdxprotocol.rst file it is written : I think it means 1 stop bit because there is always 1 start bit ... Have you some more informations about parity type ? |
Expedition has this documented:
I'll clean up the |
Thanks |
@ygageot I have also a WSI box and am interested in listening to it. Have you made any progress? |
I made yesterday a first try to connect my Mac to Nexus network
On the boat
I have a WSI box (pack 4)
I have my Mac (Sierra)
I have a serial cable for RS-485 (Cf. link)
For easy access, I connect my cable to White and Yellow plugs in parallel behind the Sea Data instrument and first I have errors on the instruments.
I switched the 2 cables (White=DataB=TDX- Yellow=DataA=TDX+ ) and then no error and my cable RDX led detect traffic.
I run a small nodejs program to capture traffic and dump it in your Fdxread dump format.
I seems to work but with many long sentences...
In parallel, I read and snap the basic values : AWA,AWS,BSP,RSI,DPT,BAT,TMP,hPA
I configured with 8-N-1 serial definition (1 start bit, 8 data bits, 1 stop bit, No parity) and 9600 bds.
At home
I see that the sentences are not good, too longs and first bytes not good.
Next week I will test more because I will have more time.
I will try parity changes and will check also with programs fdxread and serial2dump.
The text was updated successfully, but these errors were encountered: