@gloomyandy posted

[[ Both the 5160 and 2209 were a pain to tune with the 0.9 steppers. I started out with 2209s and managed to get them working pretty well. ]]

But this is in Stealthchop mode ONLY 100% of the time ... utilizing print speeds < 100 mm/s and non print travel moves < 200 mm/s right ? Probably fine for MOST cartesians but not the OPS - travel moves over 200 mm/s are doable as are much faster print moves.

Operating in stealthchop for several of us is just not a solution - especially on a Voron 2.4 - purpose built to far exceed Stealthchop limitations.

The issue we're fighting isnt Homing sensitivity and the PITA that that is- we've gotten past that - we're now missing steps during print moves < 100 mm/s in Spreadcycle. Thats a very serious issue for a 3d print and the FW - somewhere. This post is far beyond mere inconvenience, its now to the point of the Duet 3 Mini 5+ viability as a useable board.

@t3p3tony - any potential ideas to help get this resolved. If not - pretty sure I'll just send my Mini 5+ back in for a refund to Filastruder.

Someone needs to put some type of effort also into getting Trinamic engaged to help sort these issues its across the spectrum with several other boards - at least with those one can swap out drivers.

Never thought Id be sending back a Duet in order to get a china board ... for different drivers.

@gloomyandy ... Yes - we do have some test cases setup.

I have 2 Duet2 wifi's running various LDO .9* and 1.8* steppers
I have a voron 2.4 build in the works that will possibly be fitted with a Mini 5_ Duet 3 w/ Pi4

We also have a test Caribou 320 with Mini 5+ - w/ LDO .9* steppers on X / Y / E [ OP's machine ]

Another Bear with linear rails w/ Mini 5+ - w/ LIN .9* steppers on X Y E - working ins spreadcycle but skipping steps and klunking on higher than 180 mm/s moves

Then a Voron 2.4 w/ full sized main board duet and .9* OMC Stepper online on all axis

Then another Voron 2.4 with SKR and 2209's and 1.8* LDO Motors

So lots of things being compared ... This with this exhibits that or none of this etc ..

Thru the process of elimination its seems to be either LDO .9* motors or RRF3 FW.

@droftarts said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@SputnikOC3d please don’t quote a whole long post that you’re not actually referring to, it makes the thread very long and harder to navigate.

Ian

You got it champ ... I'll work on better forum reply posting etiquette ...

Patience of a saint on display here ... I think its high time to seriously consider a new board with a different driver type. Since Duet 2 would be going backwards - revision' ly ... the 6HC seems a proper choice for the customer - having dealt with So Much effort to make this work. Personally, thats where Id be at this point.

As an update: Ive just gotten the X Tilt / Z-Leadscrew setup working now, and I think this was 90% of my issue! Ive run 4 prints now using the x tilt correction before each print and Ive NOT needed to babystep in with PLA [ only filament tested so far ] .... Amazing! At most it may need .02 / .04 tweek to be PERF.

@bearer said in PanelDueFirmware 3.2.4 released:

@SputnikOC3d said in PanelDueFirmware 3.2.4 released:

but it cant seem to connect to the duet on rrf 3.2-beta4

if you upgraded from before 3.1 check out the release notes https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310

Found another thread / post where you identified the issue :

Ive got no M575 P1 S1 B57600

Think thats the issue ?

TY ...

@jackatom74

Im using Matterhackers [ they are just down the street from me ] 1.75 Aqua PetG Pro

Thanks guys ... yeah I just punted and dl'd 3 main files [ as I dont use PanelDue ] and - installed ...

Guessed on the order... just did the main baords fw 1st then, wifiserver then DWC file.

@SputnikOC3d

Solved it - missing vital COM line in config.g

M575 P1 S1 B57600

Release notes people ... READ them

@zapta cult of Voron ... lol ABS Mafia

Patience of a saint on display here ... I think its high time to seriously consider a new board with a different driver type. Since Duet 2 would be going backwards - revision' ly ... the 6HC seems a proper choice for the customer - having dealt with So Much effort to make this work. Personally, thats where Id be at this point.

@oc_geek said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@dc42 said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@oc_geek, if you print with mesh bed compensation turned off then standstill current reduction will kick in on the Z axis.

Can you hold your finger on the Z driver chips while the machine is printing with bed compensation enabled? If you can't because they are too hot, then you probably need better cooling or lower current.

there are 1000(s) Voron 2 out there (made at spec) and none have these issues... perhaps those use different hw though...

very few of them on Duet 5+ - MOST on dual skr's - locked in stealthchop

@carcamerarig said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

was stopping in the middle of the rail without the sensor beeng actually triggered... i had to power off twice to get it back to normal....

Sensitivity in homing files too low or motor current reductions in homing files - too low

• false stallguard like trigger appears - no ?

Youre on a voron with no stallguard useage - is the new fw youre usingor the config.g used have it on ?

@droftarts - any chance of elaborating on the mods and changes and focus of how to sort this ?

What did we discover was happening that was corrected ?

@argo - No Bang Bang ?

@dc42 - prior to the config.g file you see posted above - the OP was running with the driver set into SpreadCycle by the D parameter. He is on a prusa style bedslinger [ Caribou 3d ]

Stealthchop was only utilized during homing for stallguard as machine has no mechanical endstops. Its then forced into Spreadcycle. The issues is just as pervasive in Forced Spreadcycle as it is in stealthchop.

OP produced M112 prior to home / after home / and during print - the diag tool told us it was in spreadcycle mode before homing / in stealthchop during and immediately after homing op's / and then in Spreadcycle mode during print.

Not sure if we screwed something up with parameters and settings but - we couldnt find the issue.

@argo said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

I'm using 1.8 LDO motors with my Mini 5+. No bonging, no issues. Prints 24/7 at the moment.

... but locked into StealthChop 100% of the time - at reduced travel speed moves and reduced print speeds below what the OP's machine was designed to operate at.

Important to be concise.

The mini 5+ duet and the .9* motors were supposed to be an upgrade in performance [ speed and print resolution ] over the Einsy and 1.8* LDO steppers.

Any type of an update on this issue ? TMC have any input and perhaps narrow down the testing options ?

@dc42 - et al ... I have also given the motor #s of the users involved here to my contact at LDO motors for him to give to his engineering team to review and to compare their motors to their competitors that are both working and not working as well - to see if they have some insight that might help us all resolve.

Not sure if that task will bear fruit - and not holding my breath - but hopeful.