OpenMarine

Full Version: Openplotter 3 64 bit - No Seatalk1, GPIO app unavailable.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I have Openplotter 3, 64bit, Rasberry pi running. OpenCPN, SignalK work, gps data is read via usb into SignalK and arrives in OpenCPN. 
Now I am trying to attach Seatalk1 devices via optocoupler on GPIO4. Successfully created connection in SignalK, selected GPIO4 and inverted.
I can see optocoupler receives data (led mainly on but sometimes dimmed). SignalK server does not receive any data. With or without logging enabled, the systemlog fills with Python *source code* lines from pigpio.py line 1062 (I repeat: source is logged, not output or errors). Log says something about Nonetype has no sendall

Now my questions:
- All youtube films and documentation point to using GPIO app to enable SignalK functionality. But in Settings (V3.4.4) all Raspberry Pi apps except Network and Pypilot are grey and cannot be installed. Why?
- I get a feeling (but NOTHING in documentation) that GPIO may no longer be needed and Seatalk1 might be enabled by default. Please confirm?
- I tried installing GPIO from deb directly from github but this fails with a variety of errors. Any pointers?
- Any help available to solve this puzzle?

Thanks in advance!
- GPIO app for OpenPlotter 3 is in the TODO list. This is the roadmap: https://forum.openmarine.net/showthread.php?tid=3878
- It is not possible to enable Seatalk1 by default in SK without using the GPIO because Seatalk devices are not compatible with normal serial devices (short explanation) and you always need a piece of hardware to translate.
- Do not try to install GPIO app for openplotter 2 in openplotter 3, it will never work.

Being said this, you are right Seatalk1 by GPIO is broken in Signal K. I pushed a fix for python3 to SK but they asked for a backwards fix (also for python2) but I have not time for that right now: https://github.com/SignalK/signalk-server/pull/1455
I will do it for sure when working on GPIO app for OpenPlotter 3.

hopefully the puzzle is solved Smile
Moving this thread from bugs forum to "How do I...?"
(2022-10-06, 10:58 AM)Sailoog Wrote: [ -> ]- GPIO app for OpenPlotter 3 is in the TODO list. This is the roadmap: https://forum.openmarine.net/showthread.php?tid=3878
- It is not possible to enable Seatalk1 by default in SK without using the GPIO because Seatalk devices are not compatible with normal serial devices (short explanation) and you always need a piece of hardware to translate.
- Do not try to install GPIO app for openplotter 2 in openplotter 3, it will never work.

Being said this, you are right Seatalk1 by GPIO is broken in Signal K. I pushed a fix for python3 to SK but they asked for a backwards fix (also for python2) but I have not time for that right now: https://github.com/SignalK/signalk-server/pull/1455
I will do it for sure when working on GPIO app for OpenPlotter 3.

hopefully the puzzle is solved Smile

Thanks for the quick reply Sailoog!

I did read the todo list, but I had to confirm that I still need the GPIO app. My assumption looking at source code was that V3.x software enables GPIO4 as a default.

I think I have the right hardware, I have seatalk1 data connected via an optocoupler to GPIO4 as I said. Rest of the solution would be software, no?

>>I pushed a fix for python3 see https://github.com/SignalK/signalk-server/pull/1455
Can I install this on my system as it is now? Or would I still need the new GPIO then?

>>I will do it for sure when working on GPIO app for OpenPlotter 3.
I see no date in the roadmap. When do you think this will happen?

Last question: To which release/image should I downgrade to make Seatalk1 work? Would you advise downgrade or wait?

Thanks!
repeat question: To which release/image should I downgrade to make Seatalk1 work? Would you advise downgrade or wait?

I would really appreciate a short answer.
OpenPlotter GPIO v3 is published with some features already tested. Seatalk1 feature will work soon, see details here: https://forum.openmarine.net/showthread.php?tid=4347
For the life of me, i can’t get Signalk to pick up on any Seatalk1 signal i give it.

The wiring seems to be working fine (led dims briefly on the optocoupler), Signalk has the correct settings (tried every possible combo as well), the software seems to have updated the PR1455 from december ( i checked the code in the package)…

Have people already gotten Seatalk1 to work with OP3 and the 3.2.26(beta)version of the GPIO app?
Yes, a lot of systems are already working.
Could you show the circuit you are using?
(2023-04-15, 11:26 AM)Sailoog Wrote: [ -> ]Yes, a lot of systems are already working.
Could you show the circuit you are using?

I followed the youtube tutorial and based on your positive reply dug a little deeper. 

I built a testsetup at home and guess what, it works fine! I did get it to work on the boat briefly but after a reboot things went silent again never to resurrect again.

Only difference between home and boat is the length of the wires, and my thought is that i made a mistake on the boat by placing the 4700 resistor far away from the optocoupler (~3 meters).

Sadly I can’t test this hypothesis for at least a few weeks since my calendar doesn’t allow for a lot of boat time.

Will for sure follow up here…
put it near the optokopler - or like the canbus use 2 x (10k) at both ends of your loooong bus.
Pages: 1 2