Topics created by joeko

@joeko Yes, a number of Duet users are using the ERCF or the Prusa MMU. Take a look at some of the threads listed here:
https://forum.duet3d.com/search/?term=ERCF&in=titlesposts
https://forum.duet3d.com/search?term=MMU&in=titlesposts

Ian

i got it.
i had to change the connector to the oposite. wrong cable

@joeko

Thanks for the explanation.

Frederick

@dc42 said in Heater fault on heated bed ...rising to slow. since beta7:

@joeko please try the 3.4.0beta7+2 build of RRF at https://www.dropbox.com/sh/5ubjszy9fmlvzwu/AAAeOMGP-Yi-Gn9LZwQoPfita?dl=0 that I linked to in the other thread.

the link is for beta3.47+1 and not +2
i cant find beta 3.47+2

thank you 🙂

and again, first while

sudo apt-get install duetsoftwareframework

i got errormessage that no connection to the board is possible (of course) and the sbc hangs and i had to cut the power, power on and modify the json and install new.

i talk the most time with me 🙂 but it is also for other user
now i got the install without errormessage and install the stable firmware is possible. plugin i dont try further until a new stable firmware will arrive.
after

sudo apt-get install duetsoftwareframework

i modifeyed the config.json to the correct gpio pins. than i deinstalled it again, reboot and installed it again and now....all fine also with installing the stable firmware. plugins i dont have tried because also with the raspberry and manuel installing like in the guide it was not possible (and all needed services was running also appamor) in standalone it tried it with the latest beta and all was fine

@joeko @dc42 That's a known limitation of v3.3. v3.4 will print echo messages and code replies instantly like rrf does.

@dc42 said in Heater 0 appears to be over-powered.:

@joek the warning is coming from the M307 command in config.g. That M307 command should be removed because you have the correct one in config-override.g, which was saved there when you ran M500. Or you can copy the one from config-override.g to config.g.

i had to copy it from the config-override to config. remove or a ; at the beginning of the line in the config was not enough

i suppose i got it.
it is an makerbot switch and it has to be connected as an makerbot switch with all 3 wires

@joeko glad you found the problem!

@phaedrux said in reduce printarea while printing ?:

There is a DWC plugin that displays the currently loaded gcode file as a 3D object. You can choose can cancel from there.

Check your DWC plugins (3.2.2 and beyond)

the 3d viewer ?
hmm, after every start of the board i have to start this plugin manually, with my other duet3 it start from it self.

i replaced the clone to an genuine duet3 mini5+. fan + heater etc run well now. also power supply is stable now

@joeko

Yes, that is right.

Connect the power supply positive output to the LED strip positive. Connect the LED strip negative to the FAN- pin Connect the power-supply negative output to the Duet power supply negative output if they are two different supplies. Make sure your LED power supply voltage is not too high for the type of Duet board you are using.

@alankilian said in bed sensor always in minus:

@joeko said in bed sensor always in minus:

M308 S0 P"bedtemp" Y"thermistor" T10000 B3950

This should be T100000 not T10000.

yes 🙂
this solved it. thx 🙂

perfect, that fixed this 🙂

@Phaedrux said in Stealthchop on z axis with 3 z motors ?:

Do you mean from this thread?
https://forum.duet3d.com/topic/21296/resonance-spreadcycle-and-stealthchop/19?_=1613410278985

The tuning procedure only needs to be a small movement for the drivers to auto tune themselves. The data sheet says a normal homing procedure should suffice.

yes also this thread.
but i think i was wrong and the tuning on the 3 z motors is succesfully.
i was confused about the pwmGradAuto 0 stays on 0 but other parameters is changing

ok, maybe a option in future firmware