Unofficial Firmware Message
Hi all,
So after placing an unofficial firmware on the MK3, a message appears on the LCD display stating that the firmware version is not official and to use it at your own risk. You can press the button to accept the message. This message appears every time you attempt to connect a device to the printer. So if I wanted to connect Slic3r, S3D, Pronterface, etc... to the printer it will not allow it because when clicking connect, the printer will reboot to the LCD screen and not allow a connection.
Does anyone know if there is a way around this so I can connect my computer to the printer?
Re: Unofficial Firmware Message
Possibly by replacing the bootloader with a standard arduino one. I haven't read through the code, but that is likely where the check is being done.
Re: Unofficial Firmware Message
Possibly by replacing the bootloader with a standard arduino one. I haven't read through the code, but that is likely where the check is being done.
No.
This is done in Marlin_main.cpp by the show_fw_version_warnings() function. It is fed by whatever FW_DEV_VERSION is defined as in your configuration, and gets automatically adjusted by Prusa's build server when they do releases. You can compile this workaround yourself, but as a favor to Prusa Support please don't spread the .hex if you do. We've discussed this with a Prusa employee in another thread, and they are now aware of the issue this is causing. Here's hoping they come up with a workaround eventually.
My MK3 Parts: [Bowden] [New Shoes] [TPU Micro Springs]
Re: Unofficial Firmware Message
Possibly by replacing the bootloader with a standard arduino one. I haven't read through the code, but that is likely where the check is being done.
No.
This is done in Marlin_main.cpp by the show_fw_version_warnings() function. It is fed by whatever FW_DEV_VERSION is defined as in your configuration, and gets automatically adjusted by Prusa's build server when they do releases. You can compile this workaround yourself, but as a favor to Prusa Support please don't spread the .hex if you do. We've discussed this with a Prusa employee in another thread, and they are now aware of the issue this is causing. Here's hoping they come up with a workaround eventually.
Thanks. I read the other post concerning this issue. I will not be messing with the version stuff. Thank you.