When the printer driver (print3d) is still starting up the heatup command fails. Looks like the driver doesn't actually check the response. This will mostly happen when the driver is still searching for the right baudrate.
Failed (driver was still searching for the right baudrate) :
27-01 10:55:14 [IPC] command: [>>getProgress]
27-01 10:55:14 [CDH] received get progress command
27-01 10:55:14 [IPC] command: [<<ok]
27-01 10:55:14 [SRV] read 0 bytes from client with fd 5
27-01 10:55:14 [SRV] read 10 bytes from client with fd 5
27-01 10:55:14 [IPC] command: [>>heatup:s180]
27-01 10:55:14 [CDH] received heatup command with temperature 180
27-01 10:55:14 [MLD] sendCode(): M104 S180
27-01 10:55:14 [MLD] extractGCodeInfo()
27-01 10:55:14 [IPC] command: [<<ok]
27-01 10:55:15 [MLD] update temp()
27-01 10:55:15 [MLD] check temp 1/2
27-01 10:55:15 [MLD] sendCode(): M105
27-01 10:55:15 [MLD] extractGCodeInfo()
27-01 10:55:17 [MLD] update temp()
27-01 10:55:17 [SER] setSpeed(): 250000
27-01 10:55:17 [ABD] setState(): 2:idle > 2:idle
27-01 10:55:17 [SRV] read 4 bytes from client with fd 5
27-01 10:55:17 [IPC] command: [>>getState]
27-01 10:55:17 [CDH] received get state command
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:17 [SRV] read 0 bytes from client with fd 5
27-01 10:55:17 [SRV] read 10 bytes from client with fd 5
27-01 10:55:17 [IPC] command: [>>getTemperature:s1]
27-01 10:55:17 [CDH] received get temperature command with arg 1
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:17 [SRV] read 10 bytes from client with fd 5
27-01 10:55:17 [IPC] command: [>>getTemperature:s2]
27-01 10:55:17 [CDH] received get temperature command with arg 2
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:17 [SRV] read 10 bytes from client with fd 5
27-01 10:55:17 [IPC] command: [>>getTemperature:s3]
27-01 10:55:17 [CDH] received get temperature command with arg 3
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:17 [SRV] read 10 bytes from client with fd 5
27-01 10:55:17 [IPC] command: [>>getTemperature:s4]
27-01 10:55:17 [CDH] received get temperature command with arg 4
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:17 [SRV] read 4 bytes from client with fd 6
27-01 10:55:17 [IPC] command: [>>getProgress]
27-01 10:55:17 [CDH] received get progress command
27-01 10:55:17 [IPC] command: [<<ok]
27-01 10:55:18 [MLD] readCode(): 'start'
27-01 10:55:18 [MLD] readCode(): 'echo:PowerUp'
27-01 10:55:18 [MLD] readCode(): ' External Reset'
27-01 10:55:18 [MLD] readCode(): ' Brown out Reset'
When the printer driver (print3d) is still starting up the heatup command fails. Looks like the driver doesn't actually check the response. This will mostly happen when the driver is still searching for the right baudrate.
Failed (driver was still searching for the right baudrate) :
Success: