2022-05-24, 04:15 PM
if I knew a better expected behavior I could implement it.
For example, editing pypilot.conf while pypilot is running, could trigger a reload of the file. One issue is the actual settings in ram pypilot is using only gets stored to disk (pypilot.conf) every few minute from changes. Another issue would be mangling the file in which case pypilot could reject the changes, and overwrite them with the old settings, but depending on the text editor this could be considered confusing without better warning..
So if you can describe a better behavior than it has currently it would be interesting to make, but I am afraid it could actually create new situations that are more confusing than what is possible now.
Another way to "edit" the config at runtime is with pypilot_client. For example:
pypilot_client servo.max_current=5
you could have several per line, eg:
pypilot_client ap.heading_command=180 ap.enabled=True servo.amp_hours=0
For example, editing pypilot.conf while pypilot is running, could trigger a reload of the file. One issue is the actual settings in ram pypilot is using only gets stored to disk (pypilot.conf) every few minute from changes. Another issue would be mangling the file in which case pypilot could reject the changes, and overwrite them with the old settings, but depending on the text editor this could be considered confusing without better warning..
So if you can describe a better behavior than it has currently it would be interesting to make, but I am afraid it could actually create new situations that are more confusing than what is possible now.
Another way to "edit" the config at runtime is with pypilot_client. For example:
pypilot_client servo.max_current=5
you could have several per line, eg:
pypilot_client ap.heading_command=180 ap.enabled=True servo.amp_hours=0