Is the print-mode.gcode exactly the same as in Firmware 4.2.19?

[lilalinux]

Hi,

the last time I printed the calibration, after running print-mode.gcode, the prints didn't stick nicely to the build plate anymore (could well be coincidence). However, after upgrading the firmware to 4.2.19 everything prints fine again.

Is there another way to reset the gcode apart from using the print-mode.gcode or reinstalling the firmware? Is print-mode.gcode still up-to-date with 4.2.19?

Thank you

[X3msnake]

yes it is

that was a coincidence. printmode and testmode only change what it need and nothing more

besides the firmware does not change what could cause your issue. did you by chance cancelled a print before it finished?

usually powering cycling the machine solves this.

if not a eeprom reset can be done, get defaults.gcode zip from Photonsters.org firmware archive

the eeprom cleans all saved values and restores the pribter to factory presets.

you will have to re-set the machine zero

No dia sexta-feira, 23 de agosto de 2019, lilalinux < notifications@github.com> escreveu:

Hi,

the last time I printed the calibration, after running print-mode.gcode, the prints didn't stick nicely to the build plate anymore (could well be coincidence). However, after upgrading the firmware to 4.2.19 everything prints fine again.

Is there another way to reset the gcode apart from using the print-mode.gcode or reinstalling the firmware? Is print-mode.gcode still up-to-date with 4.2.19?

Thank you

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/altLab/photon-resin-calibration/issues/15?email_source=notifications&email_token=ACUR56UOBTHAUXMTCDV73KLQGA6PJA5CNFSM4IPC3J72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHDYMKQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ACUR56R5TUUFRSW3YBCPUPDQGA6PJANCNFSM4IPC3J7Q .

-- Com os melhores cumprimentos, Vinicius Silva

[lilalinux]

Thank you very much for the fast reply. The (calibration-) print itself wasn't cancelled, it completed successfully.

However, there were multiple "memory errors" with the USB-Stick (though the stick works fine in production)

Is the gcode idempotent, i.e. can the print-mode.gcode simply be re-run if it was somehow interrupted?

rgds

[X3msnake]

yes

you can also run the defaults.gcode from fw archives anytime just remember to set zero if you do without commenting out the first parameter that clears eeprom

when there are usb failures the eeprom sometimes gets corrupted. printing defaults.gcode fixes most problems.

i have seen machines that lost the z axis movement come to life with a simple eeprom reset.

this tells me the stepper driver settings are getting mangled for some reason on some machines.

this is a random thing so far, may happen one and never again may happen more

No dia sábado, 24 de agosto de 2019, lilalinux notifications@github.com escreveu:

Thank you very much for the fast reply. The (calibration-) print itself wasn't cancelled, it completed successfully.

However, there were multiple "memory errors" with the USB-Stick (though the stick works fine in production)

Is the gcode idempotent, i.e. can the print-mode.gcode simply be re-run if it was somehow interrupted?

rgds

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/altLab/photon-resin-calibration/issues/15?email_source=notifications&email_token=ACUR56UQXVXMHQU2I2B5YHTQGDVW5A5CNFSM4IPC3J72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5B3QBY#issuecomment-524531719, or mute the thread https://github.com/notifications/unsubscribe-auth/ACUR56VQRSCTPW2HNOXD46LQGDVW5ANCNFSM4IPC3J7Q .

-- Com os melhores cumprimentos, Vinicius Silva