-
Notifications
You must be signed in to change notification settings - Fork 14
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
ST1 via ShipModul, GUI shows "No Pilot" but AP does go into 'Auto' #21
Comments
There should be a response from the AP which is then parsed in https://github.com/SignalK/nmea0183-signalk/blob/master/hooks/proprietary/PSMDST.js into Signal K. You have an active 0183 connection to the shipmodul unit? |
Ahh, that explains something for me: that webapp is not available to me in the AppStore. I assumed the webapp SignalK-autopilot is what was needed for this. |
I tested the module with the two linked nmea0183 usb units linked in the readme, and not with the GPIO unit. But I no longer have any way of testing the seatalk 1 parts. And I only tested with an ST2000+. There may be differences in the solutions. The more you can diagnose, the better we can help |
To rule out any possible WiFi problems I have now connected the ShipModul via USB, but see no difference. |
@EdKok Hi I have the same problem and configuration. ST1 Autopilot over a multiplex shipmodul. I see for ca. 2 seconds the autopilot data on the Plugin interface and then the no pilot response. The autopilot reacts to PUT commands but I'm not able to get a response. For now, I'm using node-red PUT module to access the autopilot and set the SK values separately, which is not a good solution. Where are you able to solve the problem? |
@inspirity I have stopped trying and built this instead: https://github.com/AK-Homberger/Seatalk-Autopilot-Remote-Control |
@EdKok Thank you for your info. I will dive deeper into the signal plugin because I'm convinced there is a solution. Worst case, I will write my plugin for it. |
Good luck and pls keep us posted. A PR would be great! I can test if you want. |
@EdKok What firmware version of the Miniplex are you using? I had somewhat similar issues and found that at somepoint ShipModul updated the Miniplex PSMDST sentence to include a new column which is either R or C indicating receiving from or sending to SeaTalk. To handle this, I created a PR into this plugin as well as the https://github.com/SignalK/nmea0183-signalk. I also found that the Miniplex only sends the PSMDST message for sentences that it does not convert to some other message type. To get it to send all SeaTalk datagrams as a PSMDST message you have to uncheck the Raw SeaTalk option then change the input to a NMEA input at 4800 baud, then re-check the Raw SeaTalk option. |
@jprotzman can you share screenshots of the configuration of your miniplex? I have all components, but not working. Thanks |
@jandroamc Attached is my current Miniplex config export changed to .txt since GitHub does not allow .ini attachments. I am using firmware 3.6.3. Also, I found that in the 3.14.0 firmware, I never received the PSMDST messages from the Miniplex like I should have. I reached out to the creator who said he found a bug in that code causing these messages to not work. I did not hear if that had been resolved and I see the latest version is still 3.14.0. I have just continued with 3.6.3 because it does everything I need. |
Thanks @jprotzman I prefer keep updated all the system. With the 3.16.2 I see the PSMDST messages. And I can write with the MPX Config the sentence: "PSMDST,C,86,11,01,FE" and works fine. But the plugin still not working... |
@jandroamc I agree with staying with the newest firmware. I had only avoided it because it had some issues. I spoke with Miendert Sprang (the creator of Miniplex) about this issue a few days ago. He let me know that he had resolved it and make the update available. As for you issue, I have two open PRs that have not been added to the core code. Without making these changes manually on your install, this will continue to not work. If you complete the same code changes that I have done in these PRs, it should start working correctly. I can confirm that it is working for me. |
@jprotzman can you help me to do the changes manually? thanks |
@jandroamc This PR SignalK/nmea0183-signalk#234 has been merged into the normal branch so you can just install the latest version to get that part working. For the PR into this plugin, you will have to modify the file raymarinest.js. You will find this code at line 74 and 74 of that file In between these lines, add this |
Thanks @jprotzman . I'm trying to send from node red the sentence in nmea 0183: |
Situation:
RaspBerry with SignalK -- WiFi -- ShipModul -- ST1 to RayMarine ST7000+
Problem:
The buttons in the GUI do put the AP into 'Auto' and back to 'Standby' but the display only shows "No Pilot". And the four steering-buttons do not work at all.
I noticed the plugin sends $PSMDST which is "Proprietary ShipModul", so I was hoping this plugin supports the ShipModul. That is also what is in the plugin's readme.
Using this $PSMDST is why my AP goes into 'Auto' just fine, but why does the GUI stay on "No Pilot"? I guess it is waiting for the status? How should that sentence look like? Or what else do I need to configure to get the status updated?
The text was updated successfully, but these errors were encountered: