Hello,
I installed the package. Roll, pitch, temperature and air pressure are transmitted.
GPS does not appear to be transmitting.
The app displays the following error message:
"The default OpenCPN connection is missing and is not getting data from signal K. Please create this connection in OpenCPN:
Network
Protocol: Signal K
Address: localhost
DataPort: 3000
Automatic server discovery: not
"
However, this connection is created and activated in OpenCPN.
Temperature and the other things are transmitted and displayed.
A connection has been created in SK, but no data seems to flow.
Greetings Jürgen
Translated with
www.DeepL.com/Translator (free version)
(2020-08-12, 02:11 PM)Luckbert Wrote: [ -> ]Hello,
I installed the package. Roll, pitch, temperature and air pressure are transmitted.
GPS does not appear to be transmitting.
The app displays the following error message:
"The default OpenCPN connection is missing and is not getting data from signal K. Please create this connection in OpenCPN:
Network
Protocol: Signal K
Address: localhost
DataPort: 3000
Automatic server discovery: not
"
However, this connection is created and activated in OpenCPN.
Temperature and the other things are transmitted and displayed.
A connection has been created in SK, but no data seems to flow.
Greetings Jürgen
Translated with www.DeepL.com/Translator (free version)
Be sure the connection in opencpn looks exactly like this:
Network
Protocol: Signal K
Address: localhost
DataPort: 3000
Automatic server discovery: not
pay attention to "Automatic server discovery: not"
is the hat detected in openplotter-serial app?
(2020-08-11, 08:08 PM)Rooco Wrote: [ -> ]Great that it works!!!
I think the driver for the MCS board is facing the same issue. I'm not sure if this is a bug in the new Raspberry Pi kernel or a feature. The problem is definitely caused by a fixed device numbering for TTY devices.
Regards,
Thomas
Again, when restarted today, the HAT is blocked ... luckily everything is still on the desk!
(2020-08-12, 07:59 PM)Max1947 Wrote: [ -> ] (2020-08-11, 08:08 PM)Rooco Wrote: [ -> ]Great that it works!!!
I think the driver for the MCS board is facing the same issue. I'm not sure if this is a bug in the new Raspberry Pi kernel or a feature. The problem is definitely caused by a fixed device numbering for TTY devices.
Regards,
Thomas
Again, when restarted today, the HAT is blocked ... luckily everything is still on the desk!
What does "blocked" mean? No access anymore?
You need to give more details otherwise it might be difficult to get the issue solved.
Have you changed your system configuration? Is only the HAT installed or other hardware as well?
It would be very unusual if the driver suddenly stopped working.
Please provide the output of dmesg.
(2020-08-12, 08:16 PM)Rooco Wrote: [ -> ] (2020-08-12, 07:59 PM)Max1947 Wrote: [ -> ] (2020-08-11, 08:08 PM)Rooco Wrote: [ -> ]Great that it works!!!
I think the driver for the MCS board is facing the same issue. I'm not sure if this is a bug in the new Raspberry Pi kernel or a feature. The problem is definitely caused by a fixed device numbering for TTY devices.
Regards,
Thomas
Again, when restarted today, the HAT is blocked ... luckily everything is still on the desk!
What does "blocked" mean? No access anymore?
You need to give more details otherwise it might be difficult to get the issue solved.
Have you changed your system configuration? Is only the HAT installed or other hardware as well?
It would be very unusual if the driver suddenly stopped working.
Please provide the output of dmesg.
No, I haven't changed anything. The same problem is reproduced:
https://i.imgur.com/V2sEpLd.png
https://i.imgur.com/FDpf96l.png
https://i.imgur.com/Jwct16Z.png
https://i.imgur.com/rD6w1ip.png
PI4 + Hat v1 + MCS
(2020-08-12, 09:10 PM)Max1947 Wrote: [ -> ]No, I haven't changed anything. The same problem is reproduced:
https://i.imgur.com/V2sEpLd.png
https://i.imgur.com/FDpf96l.png
https://i.imgur.com/Jwct16Z.png
https://i.imgur.com/rD6w1ip.png
PI4 + Hat v1 + MCS
I can't reproduce your issue. Tested tonight on several systems/configurations, multiple reboot cycles. Do you have the issue if MCS is not attached as well?
Let's do some debugging...
To get more debugging information, we need to load the driver with debug information enabled. This can be done using the following commands in a terminal.
We kill all processes that uses the driver (except "node", this automatically respawns):
~/moitessier/scripts/kill
Now we can list all processes that are still using the moitessier driver. Only "node" should be listed.
lsof /dev/moitessier.*
We kill "node" and immediately after that we need to unload the driver. You need to be very fast with the rmmod command, otherwise node will be started automatically again. Maybe you need to try several times.
pkill node
sudo rmmod moitessier
We load the driver with debugging information enabled. The specified module is used for the Pi 4 and the latest kernel version. If using a different Pi version, you need to use the proper module.
sudo insmod moitessier/modules/moitessier_5.4.51-v7l+.ko DEBUG_LEVEL=13
Store the kernel messages in a file and send it to me.
dmesg > dmesg.txt
We also might do a remote session via VNC or TeamViewer.
Regards,
Thomas
(2020-08-13, 07:51 AM)Rooco Wrote: [ -> ] (2020-08-12, 09:10 PM)Max1947 Wrote: [ -> ]No, I haven't changed anything. The same problem is reproduced:
https://i.imgur.com/V2sEpLd.png
https://i.imgur.com/FDpf96l.png
https://i.imgur.com/Jwct16Z.png
https://i.imgur.com/rD6w1ip.png
PI4 + Hat v1 + MCS
I can't reproduce your issue. Tested tonight on several systems/configurations, multiple reboot cycles. Do you have the issue if MCS is not attached as well?
Let's do some debugging...
To get more debugging information, we need to load the driver with debug information enabled. This can be done using the following commands in a terminal.
We kill all processes that uses the driver (except "node", this automatically respawns):
~/moitessier/scripts/kill
Now we can list all processes that are still using the moitessier driver. Only "node" should be listed.
lsof /dev/moitessier.*
We kill "node" and immediately after that we need to unload the driver. You need to be very fast with the rmmod command, otherwise node will be started automatically again. Maybe you need to try several times.
pkill node
sudo rmmod moitessier
We load the driver with debugging information enabled. The specified module is used for the Pi 4 and the latest kernel version. If using a different Pi version, you need to use the proper module.
sudo insmod moitessier/modules/moitessier_5.4.51-v7l+.ko DEBUG_LEVEL=13
Store the kernel messages in a file and send it to me.
dmesg > dmesg.txt
We also might do a remote session via VNC or TeamViewer.
Regards,
Thomas
Hi Thomas, I am attaching "dmesg.txt" as requested (what I was able to do with copy / paste). Can you use AnyDesk to connect with my computer? (
https://anydesk.com/en/downloads/linux). As you can see from the photo it becomes a hard job to disconnect the HAT (with the fear of ruining everything) however I will try to put it on Pi3 alone for other tests, maybe after you have connected with my desktop ... wait for news!
https://i.imgur.com/ZyXXuTh.jpg
https://i.imgur.com/1E31Z2J.png
(2020-08-11, 06:46 PM)Rooco Wrote: [ -> ]There is a package available for testing: https://get.rooco.tech/moitessier/buster...t_only.deb
Would be great if someone could test it and give feedback.
The package does not support all prior kernels, only 5.4.51 (with the latest kernel commit).
Package was tested with Pi 3, Pi 3+ and Pi 4.
Ok, Thomas, I reinstalled
https://get.rooco.tech/moitessier/buster...t_only.deb
and now everything works. I re-link the "dmesg" for a comparison. I just have to hope that when I turn the Pi back on it doesn't lose this update ...mysteries of electronics, hope!
Ok, with the latest kernel, everything is perfect! Also in MCS there are serial interfaces and Moitessier is fine! Thanks to Sailoog, Rooco and Thomas for the work done! Good wind and good mid-August!
https://i.imgur.com/7oHoji4.png
(2020-08-12, 07:29 PM)Sailoog Wrote: [ -> ] (2020-08-12, 02:11 PM)Luckbert Wrote: [ -> ]Hallo,
ich habe das Paket installiert. Roll, Pitch, Temperatur und Luftdruck werden übertragen.
GPS scheint nicht zu senden.
Die App zeigt die folgende Fehlermeldung an:
"Die Standard-OpenCPN-Verbindung fehlt und erhält keine Daten von Signal K. Bitte erstellen Sie diese Verbindung in OpenCPN:
Netzwerkprotokoll
: Signal K
Adresse: localhost
DataPort: 3000
Automatische Servererkennung: nicht
"
Allerdings Diese Verbindung wird in OpenCPN erstellt und aktiviert.
Die Temperatur und die anderen Dinge werden übertragen und angezeigt.
In SK wurde eine Verbindung hergestellt, aber es scheinen keine Daten zu fließen.
Grüße Jürgen
Übersetzt mit www.DeepL.com/Translator (kostenlose Version)
Stellen Sie sicher, dass die Verbindung in opencpn genau so aussieht:
Netzwerkprotokoll
: Signal K
Adresse: localhost
DataPort: 3000
Automatische Servererkennung: Beachten Sie
nicht "Automatische Servererkennung: nicht".
Wird der Hut in der openplotter-serial-App erkannt?
Code:
pi@openplotter:~/Downloads $ sudo dpkg -i moitessier_2.1.0_armhf_pi3_test_only.deb
(Reading database ... 101544 files and directories currently installed.)
Preparing to unpack moitessier_2.1.0_armhf_pi3_test_only.deb ...
Unpacking moitessier (2.1.0) over (2.1.0) ...
******************************************************************************************
Running post remove... (upgrade)
******************************************************************************************
******************************************************************************************
Nothing to do
******************************************************************************************
Setting up moitessier (2.1.0) ...
******************************************************************************************
Running post install...
******************************************************************************************
/etc/systemd/system/moitessier.shutdown.service
******************************************************************************************
File /etc/systemd/system/moitessier.shutdown.service deleted.
******************************************************************************************
[Unit]
Description=Moitessier Shutdown
[Service]
ExecStart=/home/pi/moitessier/scripts/system_shutdown
Restart=always
[Install]
WantedBy=multi-user.target
******************************************************************************************
Setting up interfaces...
******************************************************************************************
moitessier: setting up /etc/modules
i2c-dev
******************************************************************************************
Updating HAT firmware...
******************************************************************************************
******************************************************************************************
This script is used to flash the STM32 microcontroller on the Moitessier HAT.
One of the following options can be applied:
-r : Will load the latest firmware release from the remote repository https://github.com/mr-rooney/moitessier-firmware.git.
The firmware will be located in "./fw/application.binary".
-s : Specifies the firmware that should be used.
This option requires the path + filename as parameter
-f : Forces the Raspberry Pi to shutdown after firmware update. A shutdown + power cycle
is required only for virgin Moitessier HATs without any firmware.
Note: Options -s and -r must not be applied at the same time!!
******************************************************************************************
******************************************************************************************
Determining I2C GPIO device
******************************************************************************************
******************************************************************************************
I2C GPIO device: 3
******************************************************************************************
******************************************************************************************
The firmware file "application.binary" is used for the update
******************************************************************************************
******************************************************************************************
Terminating running processes...
******************************************************************************************
******************************************************************************************
"kplex" not running
******************************************************************************************
******************************************************************************************
"gpsd" not running
******************************************************************************************
******************************************************************************************
"opencpn" not running
******************************************************************************************
******************************************************************************************
"node" killed
******************************************************************************************
....................................
******************************************************************************************
Flashing firmware.
******************************************************************************************
stm32flash 0.5
http://stm32flash.sourceforge.net/
Using Parser : Raw BINARY
Warning: Not a tty: /dev/i2c-3
Error probing interface "serial_posix"
Interface i2c: addr 0x41
GPIO sequence start
setting gpio 18 to 1... OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 17 to 1... OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 0... OK
delay 100000 us
delay 100000 us
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1... OK
delay 100000 us
delay 100000 us
GPIO sequence end
size = 131072
Version : 0x10
Device ID : 0x0442 (STM32F030xC/F09xxx)
- RAM : Up to 32KiB (6144b reserved by bootloader)
- Flash : Up to 128KiB (size first sector: 2x2048)
- Option RAM : 16b
- System RAM : 8KiB
Write to memory
Erasing memory
Wrote and verified address 0x08020000 (100.00%) Done.
Starting execution at address 0x08000000... done.
GPIO sequence start
delay 100000 us
delay 100000 us
setting gpio 17 to 0... OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1... OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 0... OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1... OK
GPIO sequence end
******************************************************************************************
FIRMWARE UPDATE SUCCESSFULL!!!
******************************************************************************************
insmod: ERROR: could not insert module ./moitessier_5.4.51-v7+.ko: Invalid module format
******************************************************************************************
ERROR occured!!
Could not load "./moitessier_5.4.51-v7+.ko".
******************************************************************************************
******************************************************************************************
ERROR occured!!
You might try to install the package again.
******************************************************************************************
dpkg: error processing package moitessier (--install):
installed moitessier package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
moitessier
pi@openplotter:~/Downloads $
Hello, everyone,
Unfortunately I only got around to testing something today.
The error message was a typo "Localhost vs. Lokalhost"
Nevertheless, no GPS is transmitted. In the Serial APP the HUT is not recognized.
I have already copied the OS new to a USB stick several times.
Sometimes the HUT is recognized in the app and sometimes not. But my procedure is the same every time.
See the current error message.
A remote maintenance with VNC or Teamviewer is possible.
Greetings Jürgen