2019-09-16, 08:48 AM
Hi gypsylion,
thanks for your answer.
Seatalk: I have seen the work of Thomas Knauf. My Problem with seatalk is not the "hardware" side. I have adapt the seatlak to uart. Uart have also an inverted pegel. I get data on the Pi, but I do not find a way to read 9bit of seatalk data.
Theoreticly the sc16is752 can read 9 bit. But i have not find a way to configurate the linux driver for the sc16is752 I2c/Uart to 9bit.
NMEA0183: I used a max 3485. This use rs485/422. Also Real NMEA. The Problem is, the ST60 have no RS485 /422 or RS232 compatible format. The ST60 switch the - on/of.
Here you find a thread to this:
"The Raymarine output is a constant +11V on NMEA+ and NMEA- is floating and switches to ground for ON.
That will not work with any single ended input; all you are doing is applying a constant +11V to the NMEA IN." (http://www.ybw.com/forums/showthread.php...ost5179893)
thanks for your answer.
Seatalk: I have seen the work of Thomas Knauf. My Problem with seatalk is not the "hardware" side. I have adapt the seatlak to uart. Uart have also an inverted pegel. I get data on the Pi, but I do not find a way to read 9bit of seatalk data.
Theoreticly the sc16is752 can read 9 bit. But i have not find a way to configurate the linux driver for the sc16is752 I2c/Uart to 9bit.
NMEA0183: I used a max 3485. This use rs485/422. Also Real NMEA. The Problem is, the ST60 have no RS485 /422 or RS232 compatible format. The ST60 switch the - on/of.
Here you find a thread to this:
"The Raymarine output is a constant +11V on NMEA+ and NMEA- is floating and switches to ground for ON.
That will not work with any single ended input; all you are doing is applying a constant +11V to the NMEA IN." (http://www.ybw.com/forums/showthread.php...ost5179893)