@Erikalon and @hans-martijn : your reports are conflicting... Please double check your modifications... Did you do all the steps including the 'sudo filetool.sh -b' step (without this one the changes to /opt/bootlocal.sh are not persistent and will revert back on reboot)
Can I have the logs on boot (from /var/log/pypilot/current) when it does not connect to pypilot server ?
@Erikalon : regarding "running the pypilot services remotely" I think this has something to do with the fact that you can run the pypilot services on tinypilot, but still run some utilities (like the scope, or the calibration etc) on OP, and those utilities will run locally while talking to the remote tinypilot. You can do this by specifying the IP address of the tinypilot as an argument to the tool: like in
Finally, regarding "changing mode buttons doesn't work on the web control" this is probably for Sean...
Can I have the logs on boot (from /var/log/pypilot/current) when it does not connect to pypilot server ?
@Erikalon : regarding "running the pypilot services remotely" I think this has something to do with the fact that you can run the pypilot services on tinypilot, but still run some utilities (like the scope, or the calibration etc) on OP, and those utilities will run locally while talking to the remote tinypilot. You can do this by specifying the IP address of the tinypilot as an argument to the tool: like in
Code:
pypilot_calibration 192.168.14.1
pypilot_scope 192.168.14.1Finally, regarding "changing mode buttons doesn't work on the web control" this is probably for Sean...