[Solved] V2Calibration gcode temperature modification
Hello all.
Since I was not able to find this topic on this forum, I have a question:
(Q) 1: Can I modify the temperature values in the V2Calibration.gcode for other values - i.e. 240 and 75 - for using PET-based filaments? Or, is the V2Calibration.gcode read by the machine firmware and it needs the base/preset values of 210 and 55?
(Q) 2: Can I use software such as Notepad++ to edit the V2Calibration.gcode (and save it), without any issues? Or do I need to use something else?
It is a PITA to keep changing filaments from PETG (or ABS) to PLA to run the V2 Calibration, as I use nozzle cleaning filament to purge the previous filament each and every time, as I really want to make sure I am using the full effective properties of a given filament and not some residuals of a previous one with different properties - first-layer critical.
Thank you.
Assembled MK2.
Re: V2Calibration gcode temperature modification
I have changed the extruder and bed temps in the calibration gcode myself. As I'm a "command line" kind of guy I use VIM but any text (not word processor) editor should work fine. I would save the changed gcode to a different file name.
Bill
Bill W
"Even old dogs can learn new tricks!"
Re: [Solved] V2Calibration gcode temperature modification
I have changed the extruder and bed temps in the calibration gcode myself. As I'm a "command line" kind of guy I use VIM but any text (not word processor) editor should work fine. I would save the changed gcode to a different file name.
Bill
Thanks for taking the time to answer Bill.
So that means that the firmware just looks at whether the (nozzle) Z height has been calibrated/adjusted, not what file (name) has been used - i.e. FlyingPinkElephants.gcode to calibrate.
Assembled MK2.
Re: [Solved] V2Calibration gcode temperature modification
Hi
I use Notepad++ to edit the GCode files all the time. It's no problem, just ensure that you save the file before closing the program.
Changing temps is very easy, as is adding M600 for colour change; don't try to amend other things though as you could end up with a disaster.
File name is irrelevant. The thing with V2Calibration is the M87 which sets the "Calibrated" flag in the firmware.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: [Solved] V2Calibration gcode temperature modification
Hi
I use Notepad++ to edit the GCode files all the time. It's no problem, just ensure that you save the file before closing the program.
Changing temps is very easy, as is adding M600 for colour change; don't try to amend other things though as you could end up with a disaster.
File name is irrelevant. The thing with V2Calibration is the M87 which sets the "Calibrated" flag in the firmware.
Peter
Thank you Peter for letting me know about the M87 and M600; I did manage to successfully create and execute a PETG_V2Calibration.gcode as it was a hassle changing back to PLA, every time I wanted to run the V2 routine.
Assembled MK2.