FIRMWARE RE-WRITING  

Re: FIRMWARE RE-WRITING

Anybody can describe in simple terms steps of how to disseminate the firmware hex file

That's most likely impossible.
Usual procedure is to take source code of the firmware, make required changes and build (compile) new firmware .hex file. Source code of Prusa's firmware should be available on Github. No offense, but if you don't know exactly how to do it, then don't do it.

Re: FIRMWARE RE-WRITING

Hi David,
many thanks for your reply. I am nt offended in any way and admit I am not much knowledgable in this stuff. I am in mech eng but have an idea of the stuff. Bsically, I need to activate the Z axis overtravel to avoid the printer digging the nozzle in the bed. I want to edit the firmware really but unless I have the raw data which was used to compile the firmawre with, I can`t do that. so my best option was to edit the firmware I have. I cannot understand how the developers obmitted such an important requirement and felt it is irrelevant, when the printer is controlled by a sensor which is prone to malfunction with the heat of the bed....

Re: FIRMWARE RE-WRITING

What idea do you exactly have? How do you want to deal with z-endstop failure?

Re: FIRMWARE RE-WRITING

Basically, I want to activate the Z-minus endstop to fit an endstop microswitch....

// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_MIN_ENDSTOP_INVERTING = false; // set to true to invert...
const bool Y_MIN_ENDSTOP_INVERTING = true; // set to true to invert...
const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert...
const bool X_MAX_ENDSTOP_INVERTING = true; // set to true to invert...
const bool Y_MAX_ENDSTOP_INVERTING = false; // set to true to invert..
const bool Z_MAX_ENDSTOP_INVERTING = false; // set to true to invert...
//#define DISABLE_MAX_ENDSTOPS
//#define DISABLE_MIN_ENDSTOPS

this is possible....
i wish to look into the to possibly find a way to activate another microswitch activated by filament which has finished and pause the process and activate the pause print function...
that would be great...

i do not know if there is anywhere on some site the uncompiled firmware which I can modify and then compile...

Re: FIRMWARE RE-WRITING

Maybe here?
https://github.com/prusa3d/Prusa-Firmware/tree/MK2/Firmware

Re: FIRMWARE RE-WRITING

Basically, I want to activate the Z-minus endstop to fit an endstop microswitch....

// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_MIN_ENDSTOP_INVERTING = false; // set to true to invert...
const bool Y_MIN_ENDSTOP_INVERTING = true; // set to true to invert...
const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert...
const bool X_MAX_ENDSTOP_INVERTING = true; // set to true to invert...
const bool Y_MAX_ENDSTOP_INVERTING = false; // set to true to invert..
const bool Z_MAX_ENDSTOP_INVERTING = false; // set to true to invert...
//#define DISABLE_MAX_ENDSTOPS
//#define DISABLE_MIN_ENDSTOPS

Hi Tonio,

you can easy change the PINDA to a micro switch in the firmware, BUT doing that you loose the mesh bed leveling which is one of the nice things of the Prusa i3 MK2/s.
I think what you want, is to have the PINDA AND a micro switch as a hard stop to prevent the nozzle digging in your bed if the PINDA fails. That will need some coding to get both working together.

this is possible....
i wish to look into the to possibly find a way to activate another microswitch activated by filament which has finished and pause the process and activate the pause print function...
that would be great...

i do not know if there is anywhere on some site the uncompiled firmware which I can modify and then compile...

If you are looking for a filament runout sensor firmware checkout my github https://github.com/3d-gussner/Prusa-Firmware/releases
Please read at least the last two Pre-releases to know who to connect and use the new features.

Waldemar

Re: FIRMWARE RE-WRITING

I looked up what gert1 wrote and followed all.
I managed to install theAdruino software and all additions and have all operational,
However I need the raw source code for the software I run on my machine, The 3d printer I have is with the multicolor upgrade MK2S.
I realize that the software is on the Github site, There is the firmware itself of the prusa MK2S and there is the RAW source code.
I sincerely do not have any proof that the source code posted there by prusa is the correct one which will produce the proper firmware....

this is the link-
https://github.com/prusa3d/Prusa-Firmware/releases

some of the files are marked as pre-release and I do not know if these are the correct ones to produce the firmware or just experiments and
send the machine to oblivion....

I need the latest 4 color firmware in raw condition to do this....

many thanks for everybodys help.
Tonio