arthurwolf
commented
8 years ago Hey.
You shouldn't worry about timeouts. The code should wait to get an "ok" before sending another gcode, and waiting too long is a bug. For long commands ( like heat-and-wait and pid tuning ), the plan is to actually have fabrica "do" those itself, via special screens. Taking the job away from smoothie, and doing the work and displaying it's status directly withing fabrica.
Cheers.
not sure what the best way to deal with lack of gcode response is. with the default jquery timeout, it resent the command twice when homing Z from 100mm on my i3. perhaps the simplest way is to have the timeout be configurable considering all the kinds of machines smoothie is used for. the set of commands for some machines will expect very little delay (like lasers) and some commands will have long delays (like heat-and-wait on printers).