This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2023 beta image
#51
I will look into signalk in the next few days. Sorry for the delay.
Reply
#52
I pushed a change that hopefully fixes the signalk access request. It is strange but seems that if a token expires and a particular client requests access again the signalk server just replies "completed" It may actually be a bug on the signalk server but at least now pypilot will change the uid and request access again.

https://github.com/pypilot/pypilot/commi...c76b108075
Reply
#53
I have now "Tinypilot_beta_2024_03_09" installed on Raspberry pi Zero 2 W and Open Plotter on Raspberry pi 4B. Connection to "Pypilot" plugin in OpenCPN works fine. But i miss connection to signalK and dit not get any wind data to "Tinypilot".
I have attached configuration in OpenCPN.
   

Get following message in pypilot log:
2024-02-11_14:24:57.47875 signalk error requesting access Expected object or value
2024-02-11_14:24:58.05519 signalk zeroconf service add openplotter._http._tcp.local. _http._tcp.local.
2024-02-11_14:24:58.91721 signalk server found 192.168.50.101:3000


I dont get any "Access Requests" in SignalK.
All this works fine with the previouse versions of Tinypilot images, but with them my jlx12864 display dont work. 
Reply
#54
Could you try:
https://drive.google.com/file/d/1xYzzJ83...sp=sharing

and post the log. It should give better debugging information even though I could not find the exact error.
Reply
#55
I try with Your new version, and attached here is log file.


.txt   beta_2024_03_12_pypilot.txt (Size: 4.68 KB / Downloads: 21)

Then thinking about Your question about "bug" in SignalK and rember that i have some old images for RPi4B (Openplotter).
So i tested with this older version "Openplotter" and it works Smile with the beta version of Tinypilot.

In my new version it is SignalK v.2.6.1  (No connection from beta tinypilot)
In my old version it is SignalK v.1.46.3 (Access request and then connection to/from beta tinypilot)
Reply
#56
Hello Sean,
I have installed your very last version. It's working fine, the connection with my Raspi 3B by SignalK is OK, but I am still running an old version after numerous attempt to update SignalK to v.2.6.1 leading OpenPlotter to crash.
Thanks a lot for your work on the french version. All is good now.
A little issue for me, I don't succeed to reinstall the wired link by eth0 with OpenPlotter that I get correctly with the version 0.49. I will dig a little bit more to understand, that's probably a mistake on my side.
Eric
Reply
#57
Oh, you are wiring ethernet into tinypilot?? This is not officially supported (yet) but I could certainly get to it.

Once I switch over to tinycore 13, it would make more sense at this supports pi 4/5 and zero 2 etc.

I will look into the more recent signalk server, it seems that must be the issue, thanks for clarifying the version.
Reply
#58
Thanks for your reply. Finally I succeed to connect eth0. I have made a mistake in my procedure. But with this wired connection SignalK doesn't transfer the data to OpenPlotter. Not a problem for me, I got the data in OpenCPN through TCP on OPCPN and I have suppressed Pypilot on SignalK.
Reply
#59
hmm, I wonder if pypilot is not detecting signalk using mdns from the ethernet link for some reason?
Reply
#60
Hello Sean, I would need some more help. I was quite sure to have solved the question of connection by eth0. My solution, elaborated with the help of Stelian, was as following:
- load the file net-usb-4.9.22-picore.tcz on repo.tinycorelinux.net/9.x/armv6/tcz/net-usb-4.9.22-piCore.tcz
- paste net-usb-4.9.22-picore.tcz in the folder /mnt/mmcblk0p2/tce/
- create the file "onboot.lst" dans /mnt/mmcblk0p/optional/ :
cd /mnt/mmcblk0p2/optional/
sudo touch onboot.lst
- edit onboot.lst:
sudo nano onboot.lst
- add the following line:
net-usb-KERNEL.tcz
ctrl o, ctrl x, filetool.sh -b
- execute:
tce-load -i net-usb-KERNEL.tcz
- edit bootlocal.sh to configure eth0 connection:
sudo nano /opt/bootlocal.sh
- insert the following sentence after networking start, line 137
ifconfig eth0 10.10.10.11 up
ctrl o, ctrl x, filetool.sh -b

That was working fine with the previous versions but I don't succeed with this last one. The command ifconfig -a show that eth0 is not there. I succeed to activate eth0 after launching of Tinypilot entering manually the following command with the console :
tce-load -i net-usb-KERNEL.tcz
ifconfig eth0 10.10.10.11 up

I have make some other trials, insert tce-load -i net-usb-KERNEL.tcz before ifconfig eth0 10.10.10.11 up in bootlocal.sh, place these commands at the end of the file, add sleep 8 between both but no change.

To summarize I need the way to obtain automatically during the launching the result given by my manual action.

Concerning SignalK behavior is correct if I give the same IP to wlan0 and eth0. By this way, the access is granted to this IP and the link is maintained once I disable the wifi.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)