Closed arneboon closed 9 years ago
print3d is not started correctly at boot
root@wifibox:~# ps | grep print3d
1038 root 1284 S {print3d-manager} /bin/sh /usr/libexec/print3d-manag
1040 root 1280 S inotifyd /usr/libexec/print3d-new-device.sh /dev n
1211 root 1284 S grep print3d
when running manually, it works:
root@wifibox:/usr/libexec# ls
print3d-manager.sh print3d-new-device.sh print3d-runner.sh
root@wifibox:/usr/libexec# ./print3d-new-device.sh
log is created in tmp:
root@wifibox:/tmp# ls print3d*
print3d-ttyUSB0
print3d-ttyUSB0.log
http://192.168.5.1/d3dapi/info/status:
{
data: {
bed: 0,
bed_target: 0,
buffered_lines: 0,
current_line: 0,
has_control: true,
hotend: 180,
hotend_target: 180,
state: "idle",
total_lines: 0
},
status: "success"
}
this was fixed by commit https://github.com/Doodle3D/print3d/commit/1f1e7a2c37f242a845b7d5888869de3b824d39ae
inotifyd only activates on changes, at boot the changed might be missed therefor run the command at least once at boot the script has a check to prevent opening a connection when there already is one present