2020-10-30, 04:03 PM
Thanks for the feedback.
This if true some servo settings, like rudder calibration, slew speeds max current and a few others are stored on the motor controller's eeprom. This way the motor specific settings are not lost if you upgrade, and if you have two motor controllers and two motors you could use the backup one with different settings. Hopefully this option doesn't matter for most users.
(2020-10-29, 07:34 PM)xfactor99 Wrote: So back from sailing.maybe it was "servo.use_eeprom" option?
Installing the new immage was just swapping SD-Cards. So also if needed easy to swap back.
My old tinypilot was 0.12 with OP1.2 and the corresponding plugin at the navegation pi3b+ at the nav desk.
I have done arround 1000 NM in the courrent year verry happy and no problems.
So today I used also a headles PI4 with OP2 and the newest pypilot plugin 0.22.5 witch will go to replace the one at the nav desk if the testing is a sucess.
So after booting I edid the pypilot.conf to my proven gains and servo settings. Also I changed a line with somethiing
hat.eprom=true into false. (I guess i have no hat and no eprom but not shure about ;-) )
This if true some servo settings, like rudder calibration, slew speeds max current and a few others are stored on the motor controller's eeprom. This way the motor specific settings are not lost if you upgrade, and if you have two motor controllers and two motors you could use the backup one with different settings. Hopefully this option doesn't matter for most users.
Quote:I tested all wifi connection types, Master, Managed with fixed IP, Managed with dhcp. ---- all worked fineSo the signalk is working ok for wind once you granted permissions?
I had a problem with signal-k connection wich I worked arround by setting into signal-k an TCP output to get winddata into pypilot and in to OPENCPN an TCP input to get roll and pitch to the PI4.
Later I found that er was an connection request for singnal-k at the security options wich I had to allow and to gant read and write permissions. So my foult an I remooved the TCP connections.
Quote:The LCD display and keys at the helm worked right away just had to flip the display adjust the port and Std keys as they were inverted. That was easy done by the webapp. ----- GREATSwitching the rate to 20hz from 10hz will probably not affect performance unless the autopilot is working pretty hard.
As there was verry few wind I just motored. Stearing in compass mode was good and as epected. I could not notice any diference in this conditiones .....
Quote:I like the wind display with 180 Stb/Port and the underline too see witch side.I will optimize this in the future. It also looks different on the new screen which is higher resolution.
So here a few and mor cosmetic observations:
In the LCD the wind underline is thicker on the upper number (actual wind) then at the lower numer (wind to steer).
I like more the slim line as it dit not touch tbe number and it is thatfor more visible.
Quote:In the Pypilot Plugin when the wind ist from Port, every time you make a change ther coms the 360 figuere before the -180 is displayed. I think ist an output befor recalculation. Also der is no sign for wind from stb. it would be nice to have -90 and 90- ... a minus in front and minus behind for wind from port.I'll look at this also. How was the wind display in the webapp?
Quote:Tacking is not working, it beginns and than the AP disengages.Ok, I didn't expect tacking to really work, it never really did
Quote:When it comes to remote control, I have keys at the helm, Pypilot Plugin at the Nav-Desk and Mobile Phone/Tablet for any remote needes, with webapp or VNC-Viewer to the PI at the Nav-Desk.I want to support much more in learning pilots and of course tacking and jibing, but it's taking a while.
So I dont need more RF/Wifi remotes .... but I understand that others like them.
Conclusion of the day:
I will stay with Tinypilot 0.25 image from 27.10.2020 an now change the OP1.2 at the nav with PI4 OP2
Wishlist: Tacking/Jibing and selflearning ..... but I also can live without