!!&%!(!&
I was able to infer what the problem was by reading what dc45 wrote about the panel due in other posts.
Turns out someone mucked with my baud rate setting. !%^$!#@&^$
So for those who are having the same problem as i described above...
CHECK YOUR BAUD RATE SETTING It can't be higher then 57600.
and...
Be careful about bringing things to show at meet ups!!!
@andy-cohen The messages were from the homing scripts.
Just printed a perfect cal cube. Thanks for all your help and especially your patience. I'll be sure to do a shout out to you (well... your online handle at least) on the podcast. Without your help (and the others here) I do not think I would have figured it out.
I had the same problem. Turned out it was EMI. or RF noise. I switched from a T/c to a thermistor and the problem never reoccured.
Too bad the mesh compensation turned out to be such a total waste of time. It works better just to tweak the leveling knobs and just chuck the unnecessary complexity.
@bot Thanks, I got it. Lets hope the MOFSETS do not blow.
I’m still using v2.X of RRF. I’ve been experimenting with moving from Simplify3d (which has not been updated in years) to Prusaslicer. Trying the paint feature in the latest beta version. Each time I try to print the Duet board reboots during the print. I’ve swapped out the PS and put in a new power switch thinking I had a HW problem, but nowIm wondering if maybe the older version of RRF does not like the gcode coming from the latest Prusaslicer. Is this a good inference?
@oliof I see. Thank you. I looked at the Duetlapse docs. It does not do what I need. Octolapse does. It’s an easy trade off.
@phaedrux I figured it out...
Safari was uncompressing the file automatically and in the process must have omitted files. I turned that off and it worked fine. Yet another thing to watch out for.
Thanks for your help regardless.
I do mention you in the podcast...
@phaedrux I'm pretty sure that was the file I tried. I did it again from your link and got the exact same error message.
"Error: M997: Firmware binary "0:/firmware/Duet2CombinedFirmware.bin" is not valid for this electronics"
Its a Duet wifi 2.
Trying to update from 3.3 to 3.4 on my Duet wifi. I get...
"Error: M997: Firmware binary "0:/firmware/Duet2CombinedFirmware.bin" is not valid for this electronics"
Any ideas?
@phaedrux yup. The developer says its used for timing. Not sure, but I do know that I get really awesome vids using Octolapse.
https://www.youtube.com/watch?v=2pkGCpHOs0U
@andy-cohen Octoprint attaches all automatically and it works with zero issues.
However, Octolapse? Not. It comes back saying that my FW does not have the M114 command which Octolapse requires. AFAIK RRFW has the M114 command.
@oliof I see. Thank you. I looked at the Duetlapse docs. It does not do what I need. Octolapse does. It’s an easy trade off.
@oliof Using Octoprint limits RRF? How? Does it not call macros? If it’s real time control as in cancel or speed or pause that’s ok… so long as my macros are called such as on a toolchange.
I want to do Timelapse vids with Octolapse. Anybody here drive a Duet Wi-Fi with Octoprint? I assume connecting via the USB port.