Half of the video was chopped off the back side of it. I don’t know why.
Part 2 can be found here, altho its processing still https://youtu.be/0o4PsJxOzbw
Hi MooseJuice
I just remembered a past article and posted a link to it the other day.
There was a glitch in the one released at that time.
The firmware that was addressed was released within a week, and you can try downgrading with the older firmware around that time.
This is the next version of the firmware that was first released to support the new 8/20mm module.
Sorry I don’t remember which version.
I think it is worth a try.
From your video it does not appear to be controller damage.
I would guess that the most suspicious thing is the firmware.
Blockmodule,
Thanks for the suggestions. I had played around with a few different firmwares and the issue is now gone!
Do you have any suggestions on reasonable speed settings on the new modules?
default printing speed trying 5000 mm/min, xy travel 5000 mm/min, I am not sure what to try on Z so im going to keep it on 1000 mm/min for now,
Acceleration speeds I am not sure so i am trying 3500 for xy
MooseJuice
Others may have trouble with the same content as you.
Please share your problem-solving content and procedures.
What was the cause of the problem…
acceleration, etc. I will check the Ultimaker Cura settings when I get home and get back to you.
The problem was related to firmware like you suggested.
In reality I think what shook it loose was a M502 factory reset then reinstalling the firmware.
The new modules were not being used properly by the firmware on the controller so I think that the factory reset corrected the firmware to see the right modules maybe.
The modules are also quieter now than they were and smoother. So i think the controller was using the wrong PID tuning values (from the old modules).
I spent a lot of time taking the modules apart and doing all kinds of testing, but people should start with a factory reset if they have this problem.
The exact steps I took were to download the latest firmware on my USB drive, load up Luban and push the factory reset macro (M502 followed by M500), then on the machine use the USB drive to reinstall the latest firmware and the problem is gone
Above here I have several videos I posted during the troubleshooting that I went thru with guidance from support and just testing things, but all of it was resolved with a simple factory reset 
3 Likes