Topics created by KP0005

The different banding in the top and bottom half of each tower segment is (I think) because the move direction flips midway.

That's all I got so far. @oliof

@derBruchpilotPro and @KP0005 thanks for confirming the fix

@dc42 yes I think this is the issue.
I thought I also encountered it on beta 4 but it is possible the firmware didn't flash back to the previous version correctly.

@KP0005 in those menu files, which field doesn't update unless you force the page to refresh? I didn't see a field that expanded the time to HH:MM:SS.

I created https://github.com/Duet3D/RepRapFirmware/issues/913.

dc42 created this issue in Duet3D/RepRapFirmware closed 12864 'value' menu items using object model expressions don't update #913

@KP0005 update, on 3.5.0 beta 4 "value" does accept strings.

There's still one issue - the filenames are generally too long to be shown in their entirety. It wpuld be nice if the firmware supported multiline text or maybe horizontally scrolling things that are too long, but that's more wishlist territory.

Thanks for the reassurances 😃

In the meantime, I'll try to continue using the board and report any issues I can find.

@Matej101 I expect it will appear again, if you didn't find any reason. Maybe a loose connection or a thermal effect. Please tell if it reappears. And if it reappears, you should make a M122 directly after appearing, maybe you can analyze something then.

This is now fixed in the 3.01 source code and in the firmware binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

Thanks, I got the readout now! Now to just solve the little problem of it always being zero 🙂

This is on a Maestro so no DSF. RRF 3.01-RC06, DWC 2.11
Steps to reproduce:

configure and connect a filament sensor - M591 D0 P2 C"e0_stop" S1 try to start a print while no filament is inserted print does not start, display (12864) flashes, DWC console says "operation cancelled"

The 0.9degree stepper has arrived and with it the hiss is (mostly) gone! There is still a faint grinding noise at standstill but it's almost as quiet as the old motor was in Stealthchop mode! I still plan to look around for MK3 owners to borrow motors from for testing, until than the conclusion seems to be one of the following:

I got unlucky and received a bad batch of motors, or my motors simply wore out (the printer is three years old after all) Prusa and Ultimachine have managed to cook up some black magic stabiliser for the Einsy

@dc42 Thanks, I'll be looking forward than!

so you are looking for the c parameter. and that register is not only spreadcycle
see
https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC220x_TMC2224_datasheet_Rev1.09.pdf
page 29.

Alright, I wired up the 24V PSU and it seems to have solved my problem at least partially. The motor no longer loses torque in the range where I want to operate it. The vibration problem didn't completely go away but it now starts at a higher speed and it isn't as bad. Thanks for the help!

It's OK, I can wait. Unfortunately, the bed is neither flat nor stably curved. The PCB traces which are also the bed's heating element are on one side which causes a bit of flex due to thermal expansion.

I resolved the issue with the retailer, consider this solved. Thank you for all the assistance @T3P3Tony!