@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.

@zbeeble

Why should we be polite when discussing them ? They are very "impolite" putting it mildly.

Their poor behavior as listed above and other nefarious B.S. merits them to earn the honors of the maker community banning and disparaging them - at least as much as the ABS Mafia in the voron community has ex-communicated Slice Engineering for enforcing their legitimately files patents.

FYSETC - low quality junk. Do not recommend.

@chrishamm - bro ... HUGE info. Appreciated.

On a mission

p.s. - as if you couldnt tell by my post - my linux skills are trash, but learning

@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.

@fcwilt - awesome.

Ok so it is manageable. This further info posted from your start print macro is helpful. The conditional code - solves several concerns - wasnt thinking of that flexibility being availed in rrf3.x but its there now.

Yes T0 and M703 are the 1st two lines in my start macro, but Im sure it was my lack of passing temps for nozz and bed thru variables to the slicer somehow that cause it to emit junk gcode.

I did find a hack for the superslicer G10/M116 issue - and that is - it and prusa slicer will not emit "safeguard" gcode into the mix if you stuff a M104 / M190 at the front of your custom start.g in the slicer.

I switched over to M568 ... and neither slicer jived with that; hence it stuffed a G10 P0 S215 and a M116 - to safeguard me from myself.

2 am now ... lots to ponder and fix. off to bed for a short bit then back at it fresh in the a.m.

thanks again for all your help.

Voron 2.4
Duet 3 Mini 5+
1LC toolboard v.1.1
RRF 3.4.0-Beta4

;===================================
; Nozzle Heater
;===================================
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138        ; configure sensor 1 as Nozz Heater Therm on pin 121.temp0
M950 H1 C"121.out0" T1                                   ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 B0 S1.00                                         ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S285                                             ; set temperature limit for heater 1 to 285C

Previously well functioning machine. Had the magnet on the BL Touch drop the pin mid print in hot enclosure and caused havoc. I thought I smelled blue smoke but thought it might have been the hotend nozz dragging across the top of the prints infill. Was printing PC-CF at 270c when it all went south a few months ago. Just now getting things back to working.

Havent been to get to print or PID since the above failure ... now on all starts the HotEnd runs away to thermal max and beyond ... 400c the first time before i realized it was happening. Max temp is set at 285C

Ive ohm'd the installed heater at 14.3 [ 24v system and 40 heater cartridge AFAIK ]

Ive swapped out another heater cart too and it also goes straight to max temps and no control allowed at reboots.

Ive been running the machine for setup and fw/config.g tweaking without the Heater wires connected to the 1LC 121.out0.

Suspecting maybe blown mosfet on the 1LC now. Perhaps thats what caused all the issues with the BL Touch as well ??? [ noted some fw update notes that the 1LC's io0 pins are not acceptable for servo pins ? ]

How can I troubleshoot from here ?

@fcwilt

Just looked your post over better - I get it now - duoh!

So what I think youve outlined there is - I'd have a manual button/macro I can hit that will toggle on/off my load / unload scripts when I change a filament via dwc tool drop down option ...

Kinda slick actually - I like this.

@chrishamm said in cant connect to https://pkg.duet3d.com for update:

@SputnikOC3d It's just a stub at this point. First of all, you need to enable root plugin support in /opt/dsf/conf/config.json by changing RootPluginSupport from false to true. Then restart the SBC or just DCS by running sudo systemctl restart duetcontrolserver from a Linux terminal. Once done, you need to download the latest .deb packages from the stable/unstable package feeds (see the command line here for a list of the packages you need), compress them as dsf-update.zip, and upload it on the Files -> System page. After 2mins or so, DWC should report that the installation was successful. I don't think this way of updating is supported before v3.4, though.

Awesome - thank you ... running 3.4+ iirc - Need to fire up the beast and see where shes at ... Thanks again.

@chrishamm - where can I learn more about what this is about and how it works ? Im in SBC mode, but my printer is on a private lan in my shop and cannot easily get out to the internet to apt.get ...

@zapta said in Opinions on "FYSETC" ... politely, please.:

@notepad the examples above are of a 6HC. You dispute it using an older WI FI 2.

trying to have a honest discussion of the morality of these clone whores and the users hellbent on saving $35 at the cost of the originating ecosystem is futile. They will justify their savings with 500 differing variants of logic... all while knowing they are screwing the people who brought this whole thing to the forefront. Its sad.

Whats funny tho is listening to how theyve justified the cost savings in their minds with "How theyre actually improving the whole thing" with "competition" and "options" - utterly laughable.

@zbeeble

Why should we be polite when discussing them ? They are very "impolite" putting it mildly.

Their poor behavior as listed above and other nefarious B.S. merits them to earn the honors of the maker community banning and disparaging them - at least as much as the ABS Mafia in the voron community has ex-communicated Slice Engineering for enforcing their legitimately files patents.

FYSETC - low quality junk. Do not recommend.

@oc_geek

Just chiming in to add a +1 for me on this as well. Would be helpful.

@adamfilip

Howdy sir. My apologies - I didnt mean to come off like that, and perhaps my good willed intentions didnt come through in my post. for that I apologize. I know the last thing you need when struggling to get your printer working after hours of config and testing and struggles - is some clown on the interwebz giving you flack.

Didnt mean to be rude ... sorry if it came off that way. Was hoping to prevent you from spending $$$ unnecessarily. Thats all. Thought I saw some print tuning issues from your pics - perhaps I was mistaken.

Good luck with getting this sorted. Hope it gets worked out soon.

@adamfilip from the looks of the lower layers of this print - its slicer setting and print tuning - not the steppers fault. The poorly formed overhangs, the over extrusion in general. Not sure of the material being used or your slicer settings et al ... but the part of the print that didnt fail doesnt look like its coming off a well tuned printer - ready for a 53 hr challenging print task.

Not sure closed loop servos is the right solution ...

@oliof said in Tool Swaps Multiple Hotend PID tunes Trigger Height drama:

Since you manually swap out the tools, maybe using M505 to switch between configurations is an option

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m505-set-configuration-file-folder

TY sir ... however - thats a bit much work methinks for a mere 5 lines of code per hotend. Trying to sort some form of a singular - conditional macro like above sample posted .. but I cant sort what in the dwc interface would give me a suitable trigger event to tell such a macro what tool[0-3] was actually attached.

I have 4 macros now for each toolhead as a workaround Ive created that set

• trigger height for G31
• thermistor type
• M307 PID tune settings
• Max temps
• Tool A"name"

@mac pretty sure you could still use it - just use a browser vs. the Find My Duet "APP" - browser DWC is likely a better interface now too.

@fcwilt Thanks again Frederick ...

Was looking over your code and injecting snippets of it into my cfg.g file as applicable. However; I noticed then that perhaps your setup differs from mine in that you have a multi tool expansion board where all of your toolheads can be live - and communicating via canbus at the same time - and perhaps they even have separate part cooling and hotend fans on the toolheads ?

My setup is a bit different than that, in that I have to manually unwire the Heater and unplug the therm connector on my 1LC toolboard mounted on my 1 singular toolhead. So, having all these tools defined as live [ if you will ] in the cf.g.g seems like it will just throw endless gcode errors - as the fw will be looking for defined "stuff" that isnt connected ?

Also - my hotend heater is H1 .. in your tools section you have a heater defined as H0 - isnt that assignment used by your bed ? or when youre using toolheads like this - bed heater is no longer H0 ? Same issue for the fans assignment in M563 ...

OR ... does rrf not get bothered by that because its being done in M563 vs. M308 M950 gcode lines

... obvi Im kinda confused