Topics created by duetlover

use this one to calibrate, it is specifically made for core xy calibration
https://www.thingiverse.com/thing:4018438

interesting, thanks !

I found the problem... finally a hardware issue !

@duetlover

Are you sure that's the correct thermistor for your bed? Also looking at my config.g set up via the online config tool it appears your missing a commands.

M308 S0 P"temp0" Y"thermistor" A"Keenovo Bed" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C

@duetlover there's a plugin under general which allows you to browse the whole object model

Yes that could work. What is the device you are wanting to control with the SSR? Does it make more sense to control it as a heater?

S1/S0 also works for on off.

@sebkritikel, if you are running 3.2beta3.2 then I recommend you upgrade to 3.2-RC2 anyway.

Thank you, I will check this !

If you're using x16 microstepping you should enable interpolation for the quiet and smooth motor operation. Not much reason to use anything but x16 with interpolation on the Duet Wifi.

You'd have to post your config.g and homing files and slicer start gcode otherwise we're just guessing.

Output of a M122 would tell us your board and firmware version too which would be helpful.

@sylvain said in RRF3 : connecting a servo to duex.fan7:

M280 P9 S80

Thanks, it works !

@duetlover
There isn’t a lot of examples. I just cobbled this together for a temperature tower. It needs to use some Constants from the slicer and variables. I have not been able to get the Latest RRF 3.X working well yet. So, I don’t have variables yet, but hear is a Script that worked for me on layer change for the temperature tower:
;
if move.axes[2].machinePosition > 1.3 && move.axes[2].machinePosition < 1.4
echo "machinePosition=", move.axes[2].machinePosition
echo "Setting tempreture to: 240"
M104 S240
elif move.axes[2].machinePosition > 11.0 && move.axes[2].machinePosition < 11.2
echo "machinePosition=", move.axes[2].machinePosition
echo "Setting tempreture to: 245"
M104 S245
elif move.axes[2].machinePosition = 21.0 && move.axes[2].machinePosition < 21.2
echo "machinePosition=", move.axes[2].machinePosition
echo "Setting tempreture to: 250"
M104 S250
elif move.axes[2].machinePosition = 31.0 && move.axes[2].machinePosition < 31.2
echo "machinePosition=", move.axes[2].machinePosition
echo "Setting tempreture to: 255"
M104 S255
;
Sorry, keeps losing the indents

What is your usage case?
If you're not FDM printing, but instead trying to control an external device via the relay (like say a welder), you could probably set the machine up in laser mode.
See M542
https://duet3d.dozuki.com/Wiki/Gcode#Section_M452_Select_Laser_Printer_Mode

In order to not be limited by max Z speed movement I choose to do :

G1 R2 X0 Y0 F21000
G1 R2 Z0 F1500

Best regards

Thanks for your help !

@JoergS5

In fact I have in config.g:

G10 P2 X-9.0 Y39.5 Z-4.8

And I believe that the x movement is 9mm (when I look on web dashboard, I calculate a 9mm x movement)

Although it doesn't say it implicitly in the wiki for M25, it makes perfect sense that it finishes at least the move it is currently on before pausing.
The printer has a limited scope of where it is at any moment.
Instead it knows where it started and where it's going.
If you pause in the middle of a G1 X0 to G1 X200 move, your resume point is most easily going to be one of those two points.
You wouldn't want the first one as that's already been printed so the best compromise is to finish the line and have a clean start point.
I would not be surprised if RRF is smarter and can in fact store a midpoint and recalculate the current move, but I wouldn't be disappointed if it didn't.

@dc42 I'm an idiot. You literally said that above and I somehow read past it. My apologies.