2024-08-08, 11:03 PM
(2024-08-04, 03:35 PM)Pantera Wrote:(2024-07-09, 02:48 PM)opaezosu Wrote: Thanks, yes I did try that, but no luck this time, it used to work. Do you happen to have a link to the optocoupler you are using?
I am suspicious of a sw update that happened a couple of weeks ago when I connected the boat's pi to the internet.
Either that or the optocoupler acting up. I'll try reading directly from the gpio next time I'm in the boat to see if there is some activity in there.
Best
(2024-07-08, 04:46 PM)Pantera Wrote:(2024-07-08, 03:08 PM)opaezosu Wrote: I was at the boat during the weekend, and for the first time I could not get the seatalk working at all: the led on the optocoupler blinking as always when the instruments are on, but this time SK did not read any of the data. I tried restarting the gpiod service several times, nothing, restarting sk also nothing. I tried manually setting the gpio hi/lo (it has worked before) to trigger the data acquisition, no luck this time. So I'm in a worse place now of what I was a week before. Cable connections did not change.
Any thoughts?
I have detected that if I re-start pigpiod it starts working
In the terminal type: sudo systemctl restart pigpiod
good luck!
You are right, I also updated and re'starting gpio stoped working.
The optocoupler im using is the most recomended one. This is the link
https://es.aliexpress.com/item/100500324...pt=glo2esp
Cheers. Let me know if you can solve it!
Ok, I got it working for quite some time last time I was on the boat. What I did was to ground the output signal pin momentarily (from output pin to GND pin) and magically the data started flowing. After a restart I had to do this again. I do not understand electronics very well, but we may have to do something to the input GPIO to drain it, otherwise it may remain high for too long, perhaps adding resistor somewhere. I am using GPIO 17 by the way. If someone here could please explain why this is happening, it will be really appreciated.
Best