-
Notifications
You must be signed in to change notification settings - Fork 7
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
signalk-calypso-ultrasonic plugin not turning on compass option #1
Comments
Hi Ken,
Unfortunately, I don’t have an Ultrasonic to test on at the moment, but I can have a look. Could you raise an issue on the Github page so I can track it?
Fabian
… On 19 Jun 2020, at 04:12, KenHawes ***@***.***> wrote:
Hi,
I am using the calypso-ultrasonic-portable plugin with with a raspberry pi4 running buster os with openplotter on the signalk node server.
The server scans, connects and returns data with my ULTRASONIC, it adjusts the select data rate accordingly, ie 1, 4, or 8 Hz (so it is writing to the ULTRASONIC to adjust the options) however, I cannot get it to turn the Compass ON by selecting “1” in the plugin options.
I have written a rudimentary python script with no error correction using bluepy (I am not a programmer by any means) to connect to and write to the ULTRASONIC in a terminal window outside of the signal node server and it does turn ON the Compass so the ULTRASONIC is working fine.
Can you offer any suggestions as to how to fix this and has anybody else had difficulty?
Also the connection to the ULTRASONIC in the plugin only seems to run for several minutes then drops out, it works continuously from the terminal.
Regards
Ken Hawes
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA6CQNE2OGJAV22M2R5MODRXLCSLANCNFSM4OCKD6FA>.
|
Hi Fabian, Just to confirm, when I run your standalone.js script it DOES turn the Compass ON however, that script returns the data in a terminal window, not in the signalk server. The reason I need the Compass magnetic heading data is because I have a rotating mast and need to offset the Calypso magnetic heading against the boat magnetic heading to calculate the mast rotation and as a result the apparent wind direction. Ken |
Hi Fabian, First of all many thanks for your efforts! Your work and opensource mindset is much appreciated! I bought my ULTRASONIC PORTABLE a couple of months ago and I would love to make use of it via my onboard Signalk server installed on an RPI3B+. Unfortunately though, I did not manage to succeed as I'm experiencing the same issues as Ken has described. Additionally to what Ken described, the Bluetooth connection with the ULTRASONIC is somewhat stable at 1Hz (hours) but not stable at all above an update baud rate of 1Hz (minutes). Furthermore, I have installed the RUUVI Tag plugin for signalk as well and I noticed that I'm not able to connect to both the ULTRASONIC PORTABLE and a single RUUVI tag at the same time while Noble informs that 5 simultaneous connections on a LINUX distribution is supported. The RUUVI Tag plugin works great if I disable the ULTRASONIC plugin. Did not test multiple RUUVI tags though, I only have one for the fridge. I'm no programmer in any means (I can search copy and paste though) and learning Linux, Multiple Bluetooth connections, Ruuvi tags, NodeJS, SignalK, InfluxDB, Grafana or in other words the whole shebang. So I'm not sure if it's worth sharing but during my online research regarding multiple Bluetooth connections I came across the suggestion to lower the UART baud rate for greater stability of the onboard Bluetooth adapter of the Raspberry PI (https://blog.ruuvi.com/rpi-gateway-6e4a5b676510). p.s. I did not install my ULTRASONIC in the mast yet and live in Utrecht (boat in Lelystad) so we could figure out something if that helps? Alex |
Hi,
I am using the calypso-ultrasonic-portable plugin with with a raspberry pi4 running buster os with openplotter on the signalk node server.
The server scans, connects and returns data with my ULTRASONIC, it adjusts the select data rate accordingly, ie 1, 4, or 8 Hz (so it is writing to the ULTRASONIC to adjust the options) however, I cannot get it to turn the Compass ON by selecting “1” in the plugin options.
I have written a rudimentary python script with no error correction using bluepy (I am not a programmer by any means) to connect to and write to the ULTRASONIC in a terminal window outside of the signal node server and it does turn ON the Compass so the ULTRASONIC is working fine.
Can you offer any suggestions as to how to fix this and has anybody else had difficulty?
Also the connection to the ULTRASONIC in the plugin only seems to run for several minutes then drops out, it works continuously from the terminal.
Regards
Ken Hawes
The text was updated successfully, but these errors were encountered: