I don't understand why this is happening
-
Post your bed.g please
-
Delta printers home to the top.
What happens if you use the Z jog buttons in DWC to jog the Z axis in the negative direction? It should move the effector toward the bed. After you have moved the effector down sufficiently, you can jog X and Y. You can't jog X and Y when the effector is right at the top.
-
Jogging Z by -10 won't execute because it wants to go up and it is homed so there is nowhere to go.
Bed.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) -
Jogging Z by -10 should move the effector down, not up. Are you sure that you have the carriages moving in the right direction? After sending G91, sending G1 S2 X10 should move the X carriage up 10mm, and G1 S2 Y-10 should move the X carriage down 10mm. Similarly for the Y and Z carriages.
-
Hi and thanks for staying on this with me.
From Pronterface
I have issued a G28 and the carriages are all up at the top with the limit switches tripped.
M114 returns X:0.00 Y:0.00 Z:295.004
M119 returns Endstops -X: not stopped Y: not stopped, Z: not stopped, Z probe: at min stopFrom DWC
G1 S2 Y-10 moves Y up
G1 S2 Y+10 moves Y down 10
G1 S2 X-10 moves X up 10
G1 S2 X+10 moves X down 10
G1 S2 Z-10 moves Z up 10
G1 S2 Z+10 moves Z down 10Wiring between Wifi port and Stepper Motor is verified that what I think is X is what is connected to X port
Right Front Vertical Extruded Axis is X
Left Front Vertical Extruded Axis is Y (1 Step Clockwise around Axis from X)
Read Extruded Axis is Z (2 Steps Clockwise around Axis from X). (1 Step CounterClockwise)Homeall from DWC moved X and Z up to engage limit switches (were only 10 or so away)
Homeall did not move Y all the way to limit switch. Moved up what looks like 10Limit Switches match Axis designations.
All switches Black wire on GND on Board - Outside pin on actual switch
All switches Red wire on STP on Board - Opposite Outside pin on actual switchTim
-
1. Your motors are all moving in reverse. Correct them by changing S0 to S1 or vice versa in your M569 P0, P1 and P2 commands.
2. It sounds that you are using the NC endstop switch contacts. The endstop LEDs on the Duet will be lit when the switches are not triggered, and off when they are triggered. This means that in your M574 command you need S1 not S0.
-
Hi
Well, that would explain why I was having so much trouble setting it up.I switched all the motors and M574
Homeall worked, but all carriages bounced out of closed
I tried to do the auto bed leveling and the hotend stopped about 50mm above the heat bed. There is a limit switch in the hot end that opens when the nozzle touches the bed. Should that one be S1?
-
M574 has only three endstops listed. Should I add another for the hot end endstop? It is wired to the E0 port beside X limit switch
-
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?
