I don't understand why this is happening
-
There is no hot end endstop, but you may have a Z probe. It is configured using M558, not M574.
If the hot end stops above the bed when you try to run auto calibration, that suggests that that least the H parameter in your M665 command is a long way out. See https://duet3d.com/wiki/Calibrating_a_delta_printer#Setting_up_your_initial_delta_parameters.
-
Ok Z Probe certainly covers the way it operates and the function it carries.
Thanks. I should be able to move on with the Calibration link
Tim -
Hi:
When I click the auto bed level, the effecter will drop to about 40mm away from the bed and go through the motions.
I get a message saying that the Z probe has already been triggered which it will be since it is closed on the print head.Does it stop at that height because it is already closed?
Do I have to rewire the probe? It is set to open when the probe touches the bed.
-
Sorry
My Bad.
Missed the M564 S0 in configuring the Z Probe -
Ok
I was able to get down to the bed and determine the trigger height on the Z probe which is 0.2 It is repeatable.
I did an M500 to save this information.If I home from the bed, the effector will stop before the endstops are reached. If I home again, it will home properly
If I initiate the autobed level, the effector will stop and complete it's various points around the bed while it is still 72mm above the bed. At each probe point, it will report that the Z Probe is already triggered.
I am obviously still missing (not grasping) something in this process.
Thanks
TimConfig.g
[[language]] ; Configuration file for Duet WiFi (firmware version 1.17 to 1.19) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool on Sun Jan 07 2018 13:38:34 GMT-0500 (Eastern Standard Time) ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P2 ; Set firmware compatibility to look like Marlin ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration. M665 R85 L218 B85 H306.5 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; Put your endstop adjustments here, or let auto calibration find them M208 Z-0.7 S0 ; Set minimum Z ; Endstops M574 X2 Y2 Z2 S1 ; Set active low endstops M558 P4 X0 Y0 Z0 H10 F120 T2400 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds G31 P600 X11 Y0 Z0.2 ; Set Z probe trigger value, offset and trigger height M557 R85 S20 ; Define mesh grid ; Drives M569 P0 S0 ; Drive 0 goes forwards M569 P1 S0 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation M92 X80 Y80 Z80 E663 ; Set steps per mm M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min) M203 X18000 Y18000 Z18000 E1200 ; Set maximum speeds (mm/min) M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Heaters M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0Bed.g
[[language]] ; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool on Sun Jan 07 2018 13:38:34 GMT-0500 (Eastern Standard Time) M561 ; clear any bed transform ; Probe the bed at 6 peripheral and 3 halfway points, and perform 6-factor auto compensation ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g. G30 P0 X0 Y84.2 H0 Z-99999 G30 P1 X66.01 Y38.11 H0 Z-99999 G30 P2 X66.01 Y-38.11 H0 Z-99999 G30 P3 X0 Y-84.2 H0 Z-99999 G30 P4 X-73.61 Y-42.5 H0 Z-99999 G30 P5 X-73.61 Y42.5 H0 Z-99999 G30 P6 X0 Y41.05 H0 Z-99999 G30 P7 X29.84 Y-17.23 H0 Z-99999 G30 P8 X-36.81 Y-21.25 H0 Z-99999 G30 P9 X0 Y0 H0 Z-99999 S6 ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed) -
If I home from the bed, the effector will stop before the endstops are reached. If I home again, it will home properly
#5 at https://duet3d.com/wiki/Common_problems_and_their_solutions.
If I initiate the autobed level, the effector will stop and complete it's various points around the bed while it is still 72mm above the bed. At each probe point, it will report that the Z Probe is already triggered.
Test your Z probe. For a switch type Z probe, the Z probe reading in DWC should be 1000 when the probe is triggered, and 0 when it is not. If yours is the other way round, then if possible use the NC switch contacts instead of the NO contacts. If you can't do that, add I1 to your M558 command.
-
Thanks very much. I will follow through on #5
Changing the M558 should be straight forward. I read 1000I have a bigger problem however. My new DuetWifi Card arrived today and the setup was going along just fine until I tried to connect both printers at the same time. They started off with one connecting, and when I went through the part that calls for Y A Terminal, it took the information, but when I rebooted, it would not connect. Now my other one sn't connecting either and neith is showing on Angry IP Scanner.
I will try one at a time via the USB direct. Did I read a caution somewhere that said there was something I had to do before I added a second card on the network. Something other than a different IP?
Thanks
Tim -
The note about having more than one Duet on the network only applies to using the Duet 06 or 085, or the Duet Ethernet with firmware older then 1.19. You had to configure them to use different MAC addresses.
-
Is there a workaround for not being able to read the SD card on the DuetWifi? My new board that arrived yesterday is giving me an "error 1 accessing SD card" message when I try to read the card from the DuetWifi board using the DuetDisplay.
The message at the top of the display screen says Files on card 1 <_>
I can read / write / copy etc to the little card when it is inserted in an adapter on my PC
-
I seem to have recovered the original DuetWifi. I will go after the step #5 that you identified above.
-
To be clear, my new DuetWifi is installed in the original cartesian printer and is unable to read the SD card.
My original DuetWifi is installed in my new Delta which is my original reason for seeking help
Thanks
Tim -
Hi
Firstly, thanks for the |1. That is certainly activating the probing activity. The probes are failing (not triggered) during the process since the process is starting 76mm above the print bed.I understand there is a max height which I believe is in the M665 early in the process. Measured from the bed to the end stop metal tab (when level) is 548mm. Everything I have read (ie the setup documentation) says I should set this at about 300 and indicates it will be adjusted later.
Should I not take the 76mm out of the measured total 548mm height to determine that the actual height setting for M665 is 472mm?
I also have a distance of 55mm (aprx) between the tip of the nozzle and the actuator on the switch for the probe. It doesn't appear that I need to input that number anywhere. Is that correct?
-
set the hight in the M665 to be 5mm greater then the distance from the nozzle to the bed when it is homed and adjust the Dive Hight in the M558 h param to something like 20 then it should work for you and once you've got the initial config params you can reduce the Dive hight to whatever you feel comfortable with mine is normally 5 but you can go lower if you want to shave a few seconds of the cal time
-
I understand there is a max height which I believe is in the M665 early in the process. Measured from the bed to the end stop metal tab (when level) is 548mm. Everything I have read (ie the setup documentation) says I should set this at about 300 and indicates it will be adjusted later.
No, you need to set it to be approximately right. See https://duet3d.com/wiki/Calibrating_a_delta_printer#Setting_up_your_initial_delta_parameters.
I also have a distance of 55mm (aprx) between the tip of the nozzle and the actuator on the switch for the probe. It doesn't appear that I need to input that number anywhere. Is that correct?
If you mean that the switch triggers when the nozzle is 55mm above the bed, that is the Z probe trigger height and it needs to be entered as the Z parameter in the G31 command.
-
Hi,
No, the switch doesn't trigger unless it actually touches something which is at .2 as indicated. What I'm saying is that 55mm needs to be travelled before the switch will be triggered.
What about my question on the new card that isn't reading the SD? Is there any way to get to the board and enter the data without reading the info off the card, or is there some way to test the card, or is there anything I can do to activate it from within firmware via the USB?
If you are pointing to the info on M665,
"H = height of the nozzle above the bed when all three carriages are just high enough to trigger the endstop switches. Measure it as best you can, to within about 5mm. Calibration will adjust it."I read that as the start print height since it is .2mm
M666 is about adjusting the end stops.
I don't see how this applies to my question
-
Sorry
Frustrated and didn't understand why you sent me back to the same reference again since it says H is the height of the nozzle above the bed. I'm trying to establish the height setting that I need to use so that the effector does not stop 76mm above the bed.I have spent a huge amount of time trying different numbers in the H setting of M665 and I can't seem to find the "right" number that will allow the autodeltaconfig on the wifi interface page to take over and finalize the settings. I have been working steady on that since the first time you pointed me to that section of the configuration documentation
I home the printer and that's fine. M114 tells me that Z is 295.
I try autodeltacalibration and the effector stops 76mm above the bed. Now that I have added the |1, the printer goes through the motions of thinking that it is lowering the hot end to press the nozzle against the bed. It moves down 10mm for each point and fails because the nozzle never touches the bed.
I use M564 S0 to allow myself to move down to the actual bed, and then set the Z value to 0 using G92 Z0
Unfortunately. if I try to use G30 S-1 to probe the bed, the probe does not trigger (probe value does not switch from 3xx to 1xxx) and I have to reset the printer.
Since I added the |1 in the M558, do I not need to somehow set the port for the E0 end stop to active high ?
-
its I1 (capital i) not |1 as you wrote above?
-
Really?
Thanks! Boy, that wasted a bunch of time…..........
I shall make the change and see what happens
-
I try autodeltacalibration and the effector stops 76mm above the bed.
I use M564 S0 to allow myself to move down to the actual bed, and then set the Z value to 0 using G92 Z0
M558 P1 H10 F120 T2400
G30 S-1 - does not stop Probe value 311
Need to Home All twice
I try autodeltacalibration and the effector stops 76mm above the bed.
All probes show message that Z probe already triggered. Probe Value 688I use M564 S0 to allow myself to move down to the actual bed, and then set the Z value to 0 using G92 Z0
G30 S-1
M558 P1 H10 F120 T2400 I1
No Movement. Message says Z Probe Already Triggered
Do I have to physically rewire the Z-Probe end switch?
-
I don't know anything about Deltas so this is probably way off the mark but in your config.g you have the probe trigger value set to 600 so that'll be why it says triggered when the value is 688. So setting the probe trigger value (G31) higher might help. I'd guess the thing to do would be to see what the probe value is when it's just clear of the bed and again when it's just touching the bed and set the trigger value somewhere in between. Dunno, just a guess. If this sounds like a load of crap, please ignore it as Deltas "ain't my thing".
