Yup, but now need to create the Recube Wand.
- - - - - - - - - -
And other thing stop working after downgrade to V2.00 is the Print over USB, the cura Slicer Send the filer do everything, but the printer didnt print.
Yup, but now need to create the Recube Wand.
- - - - - - - - - -
And other thing stop working after downgrade to V2.00 is the Print over USB, the cura Slicer Send the filer do everything, but the printer didnt print.
That is some really good information with regard to the hack and v2.00 of CubePro.
Let me know if you need some help with the recube wand.
This is curious.
I've been doing some thinking on this wondering why this is the first direct tie and one previous report of an unresolved 'heater failure'.
Is it possible that the heater protocol in F/W was corrupted in the F/W file swap to load the modified F/W?
Have you undone the upgrade and tried again? I only say this because of these two isolated occurrences reported to date.
Conversation here got me wondering - LINK
Just to make sure, I use a CubePro Trio and I did an update to V2.02 Original and the chamber heater crashes. After that I tried to downgrade to V2.0 but nothing changed. (Just im thinking that maybe its just the firmware after all.... but the other smell and the existing problem after donwgrade speaks for a defect.) Will check the next few days to see what happened to my heater, but so far I have bypassed the error message with a hair dryer to heat up the print chamber.
So will report back the next few days on what was damaged. I would recommend to keep this thread active and we should link all heating problems related to this thread here.
It is probably a MOV on the heater control module. Seen that picture before. But the factory 2.02 upgrade was fine, I still run it. I honestly think that settings go out of bounds for the heater when the hack is interrupted. This makes for repeatable errors. In this case, the component that fries is an over-voltage protection device.
How far into the routine does the system go before it complains?
Probably when the function is being confirmed by firmware.