Topics created by fractalengineer

@fractalengineer as a test please try a fresh DuetPi bookworm build on the SD card on the pi. Don't modify it other than to setup your printer.

Well how uncanny is that, that was totally it; adding M83 at the start of my stop.g fixed it

Lol so the printer wasn't frozen it was just trying to get back to absolute extruder position -3mm

Thank you very much; very odd that Cura adds that M82 before the end of the print I don't recall it ever doing that or being an issue before

Cheers!

@chrishamm resolved in b4, thank you 👌

@chrishamm interesting; perhaps there might be some delay issue?

The power supply goes as follow:

24V PSU ------- Duet 3
\______________ 5V DC/DC PSU ________ Rpi 3B+

With the 5V Rpi jumper removed as follows:

5V enable ON,
Duet --> SBC OFF
SBC --> Duet OFF

Perhaps the rpi power up a fraction of a second too late as powers through the additional 5V DC/DC converter?

That might also explain why it would start up fine after a repower; perhaps thanks to some residual juice in that 5V PSU?

Could disabling the 5V Enable jumper and jump SBC --> Duet be worth trying?

@fractalengineer download the files from the system tab in DWC, set up the new SD card and then upload the files

@fractalengineer I think you will find that the Pi plus screen draw rather more than 1.2A. The Duet 5V rail may well be at 5V but the voltage at the Pi may be somewhat less because of the voltage drop in the ribbon cable.

You could try running 5V and ground wires from one of the IO port connectors on the Duet to the Pi USB power input.

@fractalengineer you can only use the 'set' command to set your own global and local variables. Use M106 commands to change the fan speed.

@rjenkinsgb Yep that worked; should have read further I would have found my answer in the doc hehe

Thank you!

@fractalengineer said in RRF3.2 M303 Warning: heater behaviour not consistent:

What do you mean about setting a pwm freq of 10 for the bed heater; is it to be easier on the SSR?

RRF3 does not automatically lower PWM depending on the output. See here

that's a bit ghetto

oh yeah man, Ghetto should be my printer's name by now.

@dc42 said in Temperature chart scale up to 2000c after updating to RRF3.2?:

If you enable logging at the start of config.g using M929, they should already be logged.

Ah, I had missed this possibility (probably did not get that far when studying the gcode-list...). Sounds like this would be a good recommendation for people trying to debug their configuration setup.

@fractalengineer said in Duet3 + SBC apt-get update to 3.2 RC2 but not release?:

Aw man I looked everywhere on the github release notes but missed the post here, thanks.

I've updated the github notes to include that detail for users updating from a test version.

So for folks trying to understand how tpwmthrs is calculated, and especially how to convert it to mm/s...

12,000,000 / (256 * tpwmthrs) = steps / second You need steps per mm from M92... be careful with units... Then multiply mm/step * step/second

Using evan38109's config as an example:

M350 X32 Y32 Z32 E32 I1 ; configure microstepping with interpolation M92 X{400 / (18 * 2) * 32} Y{400 / (18 * 2) * 32} Z6400.00 E1674.00 ; set steps per mm

They're using 32 microstep units, and M92 gives microsteps per mm.

400 / (18 * 2) * 32 = 355.55 microsteps / mm 355.55 / 32 = 11.11 steps / mm

So for 40 tpwmthrs...

(1 mm / 11.11 steps) * (12,000,000 / (256 * 40)) = 105.5mm/s

The 12,000,000 comes from the clock frequency, tpwmthrs is in units of clock period Check out the datasheet: https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2160A-datasheet_Rev1.06.pdf

Do note I've not tried if say IO1.out can be used as a digital input but they would have none of the input protection IO1.in has in hardware - and it would be down to the firmware to allow IO1.out to be configured as an input.

And using IO1.in as an output would probably also be less than ideal; it would only be possible to get it down to about 1v not 0v.

But hopefully you meant you could use IO1.out independent of IO1.in which i hope to be true.

@blt3dp Yep depending on your printing accuracy you may have reading inconsistencies due to variation in the slots sizes.

Hence why I'm setting readng over 50mm; that's the distance it takes it to make one revolution, averaging out this variation.

There are plenty of plastic molded wheels you could use to get more consistent slots, if you redesigned the shaft and possibly the housing to fit

I was also thinking of laser cutting the wheel in acrylic for instance

I'm glad it's sorted. I recommend you change your M558 line to this:

M558 P9 C"^io7.in" H5 R1 F120 T6000 A5 S0.02 B1 ; Define the bltouch input on io7.in

(not the ^ before io7.in) in case you ever replace the BLTouch by a more recent version.

RRF 3.01-RC11, DWC 2.1.6 and DSF 2.1.3 are now available. If the hotend heater still disappears after installing that version, please start a new thread about it.

@fractalengineer said in Duet 3 Slow Hotend Heatup, can't even run PID tuning:

That board is smarter than it looks

😀

@fractalengineer said in Duet 3 - Bed on OUT0 not firing up SSR?:

I wouldn't think the gnd side needs to be jumped too as it should be shared right?

had to check the schematic to be sure, but yes, shared ground.
4e08c45c-08ce-4ab1-8ee7-378aaf990039-image.png

@bearer @Phaedrux

I have solved the issue by installing the unstable version (DSF Version: 2.1.3) of Duet Software Framework on Raspberry Pi. and also reverting back to RC11

The guide links to the stable version of the DSF and latest version of the reprap firmware which, at least in my case is not compatible and will lead to the "DCS is unavailable" Error.

cheers Max