@oliof of course it is .
many industrial motion systems use h bot . startasys used hbot in their printers . it all depends how rigid your design is .

i would control each bed from different out , each with own thermistor .

I think , at some point open source becomes pointless .
And , i think RRF already reached that stage .

Lets take marlin for example (i didn't use RRF at its early stages) , i remember the days when i tweaked the code to add sensors / change thermistor tables and other settings and felt like a superman .

Or the days when some of us tweaked android phones with custom firmware builds .

It was fun and all , but today at this stage , i never touched RRF source code and never tweaked it .
Same for my android phone , last time i had a phone with an open bootloader was about 10 years ago .

After years of development , the software grows so big , complicated and feature packed that it becomes a real pita / needless to touch it .
So whats the point of the software to be open source at this stage ?
its only relevant to about 0.001% of total userbase , probably less.

print 2 cylinders (like you did in your images) while one is twice in diameter .
compare the pitch distance on both cylinders .
if its the same - you have problem with your leadscrews , probably one of them bent .

if the pitch is different for the larger cylinder then you have temp / extruder issue .

@deckingman said in Poor print quality with RRF3 - especially 3.2.2.:

How do you explain the print to print variability when nothing changes between prints - not even the filament?

firmware also didn't change between those prints .

i'm not saying the firmware is perfect . I'm just starting with duet3 and i can say that so far with all the various (minor) issues i had , the diagnostics (m122) was pretty much useless in my case .
i also didn't like the default homing files , which mark axis as homed even if i dont have a sensor attached to the board (no sensor = NO = HOMED...) . this could potentially cause damage as i'm using large high current motors .

back to topic ,
your print has no layer shifts , so i guess the problem is extrusion related .

if i were you , the first thing i would change is the filament . if you didn't print for 19 months , i guess that pla is more then 19 months old . pla degrades over time and its the easiest thing to change .that curling is good indication of degraded filament (if temps were ok).

next i would test extrusion / retraction (including firmware )
for example extrude 11mm and retract 1mm 10 times , measure if total is 100 . do this with various feed rates until you reach approx 1.5x your max printing feed rate.
if you think its something related to multi axis/ stepper movement then you can add movements during this test .

your test print is pretty large , i would use something smaller for tests , even benchy would be better .

this guy is doing great analysis of this issue
https://www.youtube.com/watch?v=dL6u0UwPJOQ

it looks like he also thinks (like me) that this comes from direct drive dual gear extruders . i'm waiting for the next vid to see his conclusion .

currently my only running machine is a modified prusa mk2 . still using marlin .
if i'm using retraction , its easy to tune the seam to be a bulge or a void . invisible seam is impossible .
i dont see how its not tunable with rrf , same way it is with marlin .
i will try to connect it to duet board and compare.

maybe try M303 H2 P0.5 S220

tmc2660 on duet 2 is connected with series sense resistor on the output H bridge .
if you're lucky , you burned only the sense resistor .
check it with multimeter , R33 and R35 near the z axis driver IC .
while testing the z axis driver , did you place jumpers back on the second z motor connector ?

i set very conservative acceleration and jerk setting in the profile i sent you (i thought you are limited to 20mm/s from your original profile) . in S3d those values are under post processing script , as this 150$ software didn't add simple acceleration and jerk settings

i also think you should move away from s3d as they are going nowhere it seems .
for easy transition you can try ideamaker .

as much as i hate S3D as a company , i still find it useful for multi process and sequential printing .other then that , prusaslicer , ideamaker and cura , all of them much better now .

for low voltage high current dc powered bed you can also use external high power mosfet with a heatsink . usually will be cheaper then ssr .

@T3P3Tony thanks allot.
i'll contact local distributor tomorrow to check if they don't have the never ver. for sure .if not i'll contact you.

@T3P3Tony
i wanted to buy from the duet site as i see the never ver. of the 6hc board is in stock there. Local retailer has only older versions .

i know its an old topic but i'm also trying to log in to duet shop with same issue as op .
do i need to create different account ?
(forgot password button does nothing)

@T3P3Tony
i can read data sent on the network via external software (while it is connected to industrial dnet controller) from yaskawa that is used to configure the driver and connects to a laptop via usb. it also allows to monitor real time torque , rpm etc .

my current roadblock is the handshake . i can set the baud rate (max is 500k and not 1mb like duet) and address on the driver , but i need a network scanner , or "master" to make the handshake .

hello guys.
i have a complete set of servo motor ,encoder and driver from yaskawa - servopack sigma 3 series . more details here:
https://www.yaskawa.com/products/motion/sigma-5-servo-products

is there any chance to "map" the servo drive on duet(3) ? i know duet is can fd and its a bit different to dnet .
i want to use the motor as a spindle , and need only simple control , like set rpm and spin . i can read the data that is sent to the unit to make it spin , but so far i'm unsuccessful with somehow connecting the unit to a dnet "master" .i tried searching if anybody done this with arduino without success .

any other suggestions for devicenet control (on the cheap) are welcome .

did you try with R value in m307 at 0.001?
also , maybe your heater never reaches the target temp .

i liked the slicer , it used to be the best one around .
the company is awful though .
they didn't touch v4 for years , not even bug fixes .
they delete posts on their forum and now they want 50$ for an upgrade .
I'll pass.

with such high current on mains i think its also important to buy ssr with zero cross trigger type.

Definitely could be. I double checked with an IR thermometer and got ~5°c off the printer's reading (which is good for an unknown emissivity, I'd say...). Can't find my multimeter's thermocouple at the moment but I will double check it.
However I think there is a possibility that the readings are accurate and the cause for the different behavior might be:

• High temperature inside the chamber (4 of the 6 walls are double aluminum panels with an air gap between them for better insulation, and the remaining doors are thick glass panels)
• Reflective aluminum walls bouncing the IR radiation from the oversized bed back to part to be absorbed.

i suggest you measure the bed temp with a thermocouple + multimeter . some of the parts look completely melted (way higher then 100c) . my chamber temp is higher then 50c , its around 60 .at work i have stratasys printer thats prints abs with 90c chamber and nothing like that is happening .
your bed is huge , maybe the heat is uneven . also its worth checking the nozzle temp with external measurement