2023-03-15, 02:43 PM
(This post was last modified: 2023-03-15, 02:45 PM by seandepagnier.)
Stelian,
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.
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.
python inotify is used now because you can now edit the pypilot.conf file while pypilot is running to change settings.
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.
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.
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.
python inotify is used now because you can now edit the pypilot.conf file while pypilot is running to change settings.
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.