It is very unlikely that the firmware would brick the UMO...
The only possibility is that you generated a fimware for UMO while having an UMO+ or the opposite.
If you give me the md5 checksum of the firmware you flashed, I will have a look at the parameters used by the builder and check if any weird setting was used. (I am not a Windows person, but there are free tools on Windows to compute the md5 hash, alternatively you can use an online service like http://onlinemd5.com/ )
I managed to get the original firmware back on it in the end, it needed the thermocouple sensor installed to start up apparently. This has posed another problem - I have a new e3d V6 installed, which uses a thermistor rather than a thermocouple. I installed a 4.7k resistor on the r23 pads, attached the thermistor to signal and ground of the temperature plug and changed the firmware to the relevant thermistor. This was causing the ultimaker to not start, however. The only solution I could find was to plug the thermocouple board back in, but that meant the temperature was not read. Any solutions to this? Board is version 1.5.6
Recommended Posts
amedee 349
It is very unlikely that the firmware would brick the UMO...
The only possibility is that you generated a fimware for UMO while having an UMO+ or the opposite.
If you give me the md5 checksum of the firmware you flashed, I will have a look at the parameters used by the builder and check if any weird setting was used. (I am not a Windows person, but there are free tools on Windows to compute the md5 hash, alternatively you can use an online service like http://onlinemd5.com/ )
Link to post
Share on other sites