Tinchus last edited by Tinchus
Hello. Y have this situation:
When printer is not printing, there are times I manually switch the tool (Y have 2 tools). When that happens, the firmware follows the steps, 1 of them is to set the stand by temperature of 1 of the tools. That is OK of course if the printer is printing, but if there is no printing I will end up with one tool being hot, and I can forget it... so I added this to my TFREE0.g file, these lines checks the status of the printer, and if status is idle, then it sets the stand by temperature of the tool 0 to 0 degrees.
This is my objective by it is not working. Can someone tell me what Im doing wrong?
The lines are TFREE0.G
(indent here) M568 R0 S0
If the printer is idle, why is a standby temperature greater than zero set?
Perhaps it would suffice to simply set the standby temps to zero in the end gcode section so that when the print completes the standby temp is zeroed out. Do the same in cancel.g.
Schild0r last edited by
When your printer is running tfree.g it is not idle but busy (with running the tfree.g macro). Had the same problem when writing my power toggle macro.
Haven't found an elegant solution to this though... Instead I had to query if the printer is 'busy' but that all heaters are off and so on. If someone knows a way to query the state the printer had before the macro was triggered, please tag me
cosmowave last edited by cosmowave
@phaedrux because I have set main temp and stand by temperatures in the filamento lead routine.
Setting stand by temperature on the end gcode works of course, but then when starting a print you would need to set that temperature again. From where you would do that? not in start gcode. Best way I have found to do this is to just set up the temperatures in the filament load routine, actually I think I read that advise in your wiki.
@cosmowave this works! Good TIP
@tinchus said in checking STATUS:
From where you would do that? not in start gcode. Best way I have found to do this is to just set up the temperatures in the filament load routine, actually I think I read that advise in your wiki.
If you're switching to an entirely separate config folder for filament management you could have a custom start.g in there with the standby temps for that filament. Start.g gets run right before the sliced gcode file.
@phaedrux How do I get a custom start.g file? O knew I can have a custom config.g wich is inside each filament folder, but how do I set a custom start.g file for each filament?