I could use some help
-
@mac said in I could use some help:
@fcwilt I got the code to appear like you did, with the black background.
You are making good progress!
Now with the endstops configured what we believe to be correct you can check their operation using the Object Model Browser.
You did get that up and running didn't you? I think I recall you did.
Or you can execute M119 from the DWC console and it will display the state of the endstops.
To verify their operation you have to find a way to hold them closed so you can execute the M119 and see what is reported.
And, of course, you want to execute M119 when they are not closed to see what is reported.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@fcwilt The Z Endstop is plugged into io_2 (right above i0_3, which is the BLTouch). The green wire is attached to GND (middle hole), and the white wire is attached to io2. in.
-
@fcwilt I have to go feed my daughter's horse. Back in twenty.
-
@mac said in I could use some help:
@fcwilt The Z Endstop is plugged into io_2 (right above i0_3, which is the BLTouch). The green wire is attached to GND (middle hole), and the white wire is attached to io2. in.
Then the command should be:
M574 Z1 S1 P"!io2.in" but using the ! character assumes you have connected the white wire to the NC connection on the endstop switch.
If you HAVE NOT connected the wire to the NC connection of the endstop switch DO NO include the ! character.
And then we need to us M119 to verify the operation of each endstop switch to be sure they are working and generating the correct states for closed and open.
Frederick
-
@fcwilt The WHITE WIRE is connected to the NO.
-
; Endstops M574 X1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !io5.in M574 Y1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !io6.in M574 Z1 S2 P"io2.in" ; configure Z-probe endstop for low end on Z -
@droftarts I LOVE doing that!
-
@mac said in I could use some help:
@droftarts I LOVE doing that!
OK now that we think the M574 commands are all correct you need to verify the endstop switches are all working.
So switch to the DWC Console and type in M119 and press the enter key.
Please post back what you see displayed as a result of the M119.
Frederick
-
@droftarts M119 reports: "X not stopped: Y not stopped, Z no endstop, Zprobe: not stopped
-
; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z600.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z200.00 E250.00 ; set accelerations (mm/s^2) M906 X600 Y600 Z600 E600 ; set motor currents (mA) M84 S0 -
@droftarts check out the existing M92 line.
-
@mac I think those M92 numbers should be halved.
Ian
-
@mac said in I could use some help:
@droftarts M119 reports: "X not stopped: Y not stopped, Z no endstop, Zprobe: not stopped
We are making progress.
After you edited the config.g file and updated the M574 command for the Z endstop did you re-boot your printer to cause the changes to the config.g file to take effect?
The M119 reported no Z endstop so I am thinking the changes you posted were not applied by re-boot.
Frederick
-
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X40.00 Y40.00 Z2000.00 E420.00 ; set steps per mm -
@droftarts I've been saving and rebooting after each change (after the last few changes, but not the first two).
-
@mac said in I could use some help:
@droftarts check out the existing M92 line.
Hi mac.
It seems you may have missed the post I made about the benefit of placing the M92 command before the M350 command.
There is no downside to doing so and it allows you to make changes to the M350 command, if you wish to experiment, without having to change the M92 command, once the M92 command is correct for 16x micro-stepping.
Frederick
-
@mac said in I could use some help:
@droftarts I've been saving and rebooting after each change (after the last few changes, but not the first two).
I see the problem with the M574 for the Z endstop.
The command has an S2 when it should be S1.
Edit and re-boot, then execute M119 again.
We are close to getting homing working.
Frederick
-
@fcwilt I'm still considering your M92 edit (moving it to ABOVE the M350 line). Can I simply copy and paste? Will the form renumber itself?
-
@mac said in I could use some help:
@fcwilt I'm still considering your M92 edit (moving it to ABOVE the M350 line). Can I simply copy and paste? Will the form renumber itself?
Yes, you can cut-and-paste a line of code with no problems.
Frederick
-
; Endstops M574 X1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !io5.in M574 Y1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !io6.in M574 Z1 S1 P"io2.in" ; configure Z-probe endstop for low end on Z
