(2020-08-25, 05:48 AM)Cari20 Wrote: If anybody can guide me to the location of the files on sk server and which solution will be more suitable I can try making the changes, test and report the final solution.https://github.com/SignalK/signalk-serve...seatalk.js, but I see there was already a bug report opened and resolved.
(2020-09-03, 09:51 PM)Cari20 Wrote: I can publish the details of my flow in the next few days if you're intrested.Yes please, or PM me, because we might be going off-topic.
I've been experimenting this weekend.
Because I'm not near my boat at the moment, I programmed an Arduino to send out Seatalk.
It's based on the SeatalkTest program here, but I didn't use the 9-bit versions of HardwareSerial from there.
Instead I used those posted by Nick Gammon here.
Finally I had to update the Arduino script to use the correct serial.begin and serial.write9bit lines, as described in the example code in the same post by Nick Gammon.
When I use STALK_read.py with these settings:
Code:
gpio= 17 # Define gpio where the SeaTalk1 (yellow wire) is sensed
invert = 1 # Define if input signal shall be inverted 0 => not inverted, 1 => Inverted
pud = 2 # define if using internal RPi pull up/down 0 => No, 1= Pull down, 2=Pull up
I can see the seatalk sentences roll in, and comparing them to Thomas Knauf's website, I think they are correct:
Code:
pi@GuldenDraak:~/STALK_read $ sudo python STALK_read.py
$STALK,
$STALK,24,02,00,00,00
$STALK,00,02,40,fc,00
$STALK,20,01,42,00
$STALK,89,b2,0a,00,20
$STALK,10,01,00,78
$STALK,11,01,09,05
$STALK,24,02,00,00,00
$STALK,00,02,40,ff,00
$STALK,20,01,3f
$STALK,89,b2,0a,00,20
$STALK,10,01,00,78
However, SignalK with below settings doesn't seem to receive a thing:
There's no option to set the pull up/down resistor, so I assume it will default to a pull up for that pin?
I also tried copying the STALK messages I get with STALK_read.py in the data fiddler and it says it's invalid.
So is there something wrong with the datagrams, or SignalK?