Posts made by Dave Parry

@dc42 David,
Got it working.
in the end I did a auto calibrate and that sorted it. Should have tried that first.
Anyway thanks for help.

@dc42 Hi David, thanks for the reply, sorry for delay but been busy and not able to check your recommendations,
1 Yes I have 501 at the end of the config.g
2 the bed temp is stable, but will check again.
Will give it a bit longer to stabilise.
If the tips dont work, I think I will reload the software.
I did have a problem at the end of a print when the panel duo suddenly went haywire and had garbage on the screen. I had to reload its software, so maybe the Duet was also corrupted in some way.
What I have noticed is that the calibration is always at -1.05 after homing.

I'm trying to calibrate my mini kossel, using the Duet3D guide.
I get through it all ok, but if I home the carriage and re-do the calibration its always out, ususlly X=0 is too high. I've tried sending M500 before homing no difference.
How can I get it to keep its calibration?

@droftarts Thanks, That sorted it. Although it does seem to exceed 500 normally, I have set it to 490 and it works fine

I have a duet 2 board and a dc mini height sensor.
I have not used it in a little while but now I'm getting Height sensor problems when I try to calibtrate it, if I send either G30 S1 or use auto calibration it, although the red light comes on, the carriage doesnt stop and hits the bed and I have to use emergency stop.
My config.g is
M558 P1 C"zprobe.in" H8 F120 T2400
G31 P500 X-0 Y-0 Z2.16;
I do also get z probe display info on the screen. 6 or 7 when far away and 500 when near the bed.
how do I get it working?
My software is
Duet Web Control 3.4.5

@Phaedrux Thanks, thats what I did, But would'nt open in anything.
Have managed to import the step files into inventor and then save those as STL's. Just printing them now. Fingers crossed.
The V1 files also wouldnt open, but there is a link above that worked, but my magnet is 2mm so I think it's V2

I am trying to print this redesigned housing, but I cannot get open the V2 stl files. Have tried simplify3D, cura and mesh maker. I think the source may be corrupted. Does anyone have working versions of them?

Thanks for reply, but have sorted this out. Must have been something in the config.g but no idea what. I found a older saved config.g which has cured the problem.

I have calibrated my mini kossel delta, which has a ir mini sensor.
all is good until I try to do a mesh calibration G29.
it starts ok but at the same point every time I get a message
"G29
Error: Probe already triggered before probing move started"
on watching the probe info it starts out at about 4 or 5 untriggered and 470 to about 520 triggered. When the error occurs it jumps to 900 + for a fraction of a second. It doesnt happen any other time, but it stops the mesh calibration.

@dave-parry No Its back giving the error.
What commands do I need to reduce the sensitivity?
at the moment I have

M591 D0 P3 C"e0_stop" S1 ; filament monitor connected to E0_stop
M591 D0 ; display filament sensor parameters for extruder drive 0

@dave-parry That seems to have cured it. Increased current to 1000mA.
Guess its the slight extra force required to push it through the sensor.

@dave-parry No Its still happening. The motor current is set to 750mA which is the nominal current rating. Should |I increase it slightly?

@dc42 No cant hear any skipping, will try the pressure.

@dc42 Thanks David. Yes thats the error I get (couldnt remember the wording). I'm using a bondtech extruder, would increasing the pressure help?

I keep getting random sensor errors since using PLA. It didnt happen on petg. It pauses with the message
If I cancel the message and resume it may complete or I may get the same thing again.
I'm using
M591 D0 P3 C"e0_stop" S1 ; filament monitor connected to E0_stop
M591 D0 ; display filament sensor parameters for extruder drive 0
in my config.g file and sending m591 d0 gives
Duet3D rotating magnet filament monitor v3 on pin e0stop, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check printing moves every 3.0mm, version 3, mag 131 agc 58, measured sensitivity 31.06mm/rev, min 85% max 118% over 24.8mm
I assume widening the sensitivty may resolve this but what do I put into my config file?

Well it Paused the print and saved the resume state, so I guess thats a "solved" thank god ( and You).

@dave-parry Ok have changed the M591 in config.sys to the second M591 in your list
m591 D0 P3 C"e0_stop" S1 and it seems to have done the trick....
Havent tried it yet with running out of filament will try that now. Also console says no calibration data, do I need to do this, cant see anything on the dozuki that mentions it.
Anyway thank you very much for your patience. Promise next time I take the print bed off will change the cable round so the colours are correct....

@alankilian No sorry Alan, I meant I put the Gcode commands in manually and it reports V3. If I power on/off it goes back to no sensor. It does however display extruder drive 0 data in the status window. If I feed some filament it increments the correct amount.

@dave-parry Have rechecked the commands and I now get this
m591 D0
Duet3D rotating magnet filament monitor v3 on pin e0stop, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check printing moves every 3.0mm, version 3, mag 133 agc 60, no calibration data

So it is V3

@dave-parry Restarted it and it's now homing