(2023-03-15, 02:43 PM)seandepagnier Wrote: So sorry I didnt get enough time to extensively test the tinycore 13 and I decided to make one last release on the tinycore 9 system.
No problem !
(2023-03-15, 02:43 PM)seandepagnier Wrote: After I have a final stable image, I will move to tinycore 13, but some strange issues have been mentioned here and I havent had time to do any long-term testing so. One issue (for example) is about the motor controller not communicating after a few hours... Not sure the exact issue there but it was reported, but maybe only hardware too.
Well, all the reported issues were about missing python modules. This has been corrected since and will be in the image I plan to release shortly. As for the issue about the motor controller, this needs further debugging indeed, but the problem could be anywhere: the image, of course, but also the hardware, or pypilot itself...
(2023-03-15, 02:43 PM)seandepagnier Wrote: python inotify is used now because you can now edit the pypilot.conf file while pypilot is running to change settings.
Right, I see it now, but this in only in your "unstable" branch.
Speaking of which, something is strange in the pypilot git repo embedded in the image: does this correspond to the "unstable" branch ? In this case it has diverged from the "unstable" branch on github.... Or did you merge part of the "unstable" changesets back into master, and fergot to push to the master on github ?
(2023-03-15, 02:43 PM)seandepagnier Wrote: I would hold off on an update image until I have a stable image (more testing and feedback) If you want to merge changes it would only make it easier, I would do this. There are changes to the boot scripts (in mydata.tgz) as well.
My image is based on the "stable" "master" pypilot branch. I will look at the boot scripts changes, thanks for the heads-up !
Anyway, without releasing a newer image I don't think we will get more testing because I don't think there are many users updating the git and rebuilding pypilot.tcz inside the image...