I guess that's why I got the warnings when running the temp auto calibration!

12:06:43M98 P0:/macros/test white F100
G32 bed probe heights: -0.205 -0.200 -0.200 -0.200 -0.203 -0.203 -0.203 -0.200 -0.200 -0.198 -0.200 -0.198 -0.200 -0.200 -0.203 -0.203 -0.200 -0.198 -0.203 -0.200 -0.200 -0.200 -0.205 -0.200 -0.203 -0.200 -0.200 -0.203 -0.200 -0.200 -0.200 -0.200, mean -0

Which facility are you using to set the laser PWM: E values on the G1 commands, or M3 commands between the G1 commands?

Either way, you first need to make the E1 heater output (heater 2) available as a GPIO pin by sending M307 H2 A-1 C-1 D-1. After that:

If you are using E values on the G1 commands, send M571 P2 If you are using M3 commands, send your M452 P2 command after that.

never mind I had a brain fart. Common sense would tell you to look at the coordinates on the dam marker dot and it tells you exactly where it was.

@stavrosgmtl:

That works on the duet?

Yes.

My recommendation is to print a grid pattern, then adjust the rod length to get straight lines and uniform spacing as far as possible. Then use M579 to correct any scaling.

I think some other delta printer firmwares do apply acceleration, jerk and speed limits to the carriages, not the Cartesian coordinates. It's not clear which is best, it depends on what you are trying to avoid by setting the limits. With the segmentation-free algorithm used in RRF, it's easier to apply them to Cartesian coordinates.

Thanks dc42

Try using Mike's page to figure out what you are doing wrong.
But be careful the board he is using is not the latest and the Johnsl board is connected to different pins than required on the Duet Wifi.

http://www.sublimelayers.com/2016/01/fsr-auto-calibration-setup-for-duet.html

I don't know what I'm doing and I was able to figure it out using that.

I have just updated the links.

Ok I have checked the resistance at room temperature and 200 degrees both seem pretty close with 200 degrees showing 450 ohms.
Also now getting a reading of 186 degrees when set at 200 degrees with my handheld temp probe using thermal paste and in the position suggested by Martin.
I have just tried another print that was printed at 190 before upgrading. I started the print at 215 degrees and gradually lowered the temperature until the extruder started skipping at 205 degrees. Retraction has also been reduced to 0.8mm to avoid hot plastic being drawn back into the cold area of the nozzel.
Looks like I will need to print at higher temps than before.

Arthur

Thanks! I was hoping some G or M codes would exists. Got love the duet firmware

There is currently no GCode to turn an individual tool off.

To set the active temperature of tool 0 to 200C, use G10 P0 S200.

M116 with no parameters will wait for all tools, bed and chamber heaters to reach their assigned temperatures.

Hmmm, I have SAM4E8E active, but duetNG in the variants folder is slashed. Only duet is non-slashed. Maybe its another bug, hopefully in just the display of the folders.

Some suggestions:

don't use M280 commands explicitly to deploy and retract the probe anywhere except in deployprobe.g and retractprobe.g. if you need to deploy or retract the probe explicitly, use M401 and M402 instead. That way the firmware can track whether the probe is deployed or not.

probe deployment is handled automatically in firmware 1.19 and later. So you don't normally need to use M401 and M402 anyway, except perhaps in bed.g to deploy and retract the probe just once instead of at every probe point

in your homez.g file and Z homing section of homeall.g, use a G30 command not a G1 S1 Z command

if mode 5 isn't working, this suggests that the output voltage of the Z probe is too low

if it is trying to exceed the bounds of the Y axis, this suggests that your M208 settings for the Y axis are not correct.

HTH David

thank you

Problem found: rod length was incorrect. The config-override contained an incorrect length (+8%). Since I use 6 factor calibration this value isn't adjusted. It was probably a side effect of a 7 or 9 factor calibration experiment.

What I learned: On a delta, if both you x and y are off by the same amount but your z calibration is fine. Take a look at the L parameter of the command M665 in BOTH config and config-override.

2.24 is when ir probe gets triggered, this value i have in config.g also..

Can it be config-overide.g that make this problem?..

Start to think i have forgotten something when i make files.

I suspect the problem lies in your homedelta.g file.