I could use some help

fcwilt

@mac

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time)
G91               ; relative positioning
G1 H2 Z5 F3600    ; lift Z relative to current position
G1 H1 Z-245 F1800 ; move Z down until the endstop is triggered
G92 Z0            ; set Z position to axis minimum (you may want to adjust this)

; Uncomment the following lines to lift Z after probing
;G91              ; relative positioning
;G1 Z5 F60        ; lift Z relative to current position
;G90              ; absolute positioning

I don't get it, mac.

I give you code to try and you end up with something rather different.

I really do know what I am doing.

Frederick

A Former User

@fcwilt I don't know how that happened, honestly. I absolutely don't remember seeing that in your code, or copying anything that looks like into my code.

Frankenstein's Cinderella, that's all I can suggest.

This extraordinarily long thread has the code you suggested in it. It was the first code you provided to me. I know where it is. So I will go and get it, and put it in the homez.g again.

Now we will see what happens.

A Former User

@fcwilt @droftarts @alankilian

G91               ; relative movements
G1 H1 Z-250 F3600 ; fast move toward Z endstop
G1 Z10            ; backup off a bit
G1 H1 Z-15 F360   ; slow move toward Z endstop
 
G90               ; absolute movements
G1 Z10 F3600      ; move to 10mm off the bed to allow X and Y movements

This is the correct homez.g @fcwilt provided. I have no idea where that other code came from.

fcwilt

@mac said in I could use some help:

@fcwilt @droftarts @alankilian

G91               ; relative movements
G1 H1 Z-250 F3600 ; fast move toward Z endstop
G1 Z10            ; backup off a bit
G1 H1 Z-15 F360   ; slow move toward Z endstop
 
G90               ; absolute movements
G1 Z10 F3600      ; move to 10mm off the bed to allow X and Y movements

This is the correct homez.g @fcwilt provided. I have no idea where that other code came from.

You been drinking?

Anyway, have you changed the rotation of the Y stepper so the jogging operations move it in the right direction?

I'm still anxious to verify that the S setting is the problem there.

Frederick

A Former User

@fcwilt I'm going to work on that now.

Mac

A Former User

@droftarts @fcwilt @alankilian

In the config.g now:

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

Our change:

M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes forwards

A Former User

@alankilian @droftarts @fcwilt

On the X-axis, the printhead's chattering up a storm. When I 119 it, this is what I get:

6/27/2022, 4:18:07 PM	M119
Endstops - X: not stopped, Y: not stopped, Z: no endstop, Z probe: not stopped

A Former User

@Mac

; Endstops
M574 X2 S1 P"!^io5.in"        ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in
M574 Y2 S1 P"!^io6.in"        ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in

; Z-Probe
M950 S0 C"io3.out"                                 ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T3600     ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X15.875 Y0.625 Z2.5             ; set Z probe trigger value, offset and trigger height
M557 X5:190 Y5:215 S10                         ; define mesh grid

I guess the X-motors toast.

6/27/2022, 4:13:45 PM	G28 X
Warning: Driver 0.0 warning: phase B may be disconnected

fcwilt

@mac

It's more likely just a bad connection.

Did you get a chance to change the rotation of the Y axis and then test jogging?

Frederick

A Former User

@fcwilt

; Endstops
M574 X2 S1 P"!^io5.in"              ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in
M574 Y2 S1 P"!^io6.in"		     ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in
M574 Z2 S1 P"!^io2.in"		     ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin !^io2.in

I pulled the connector off of Driver_0, and put a short length of wire in the first two holes, then the second two holes. When I turned the X-motor, both phases resisted my efforts. So the phases are both there, but I guess that doesn't mean much?

Above is a change I made. The listing for the Z-endstop disappeared, I guess (I don't know). So I re-entered it, saved the config, and there it is now.

6/27/2022, 4:50:03 PM	M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
6/27/2022, 4:50:01 PM	M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
6/27/2022, 4:49:54 PM	M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
6/27/2022, 4:44:54 PM	Connection established
6/27/2022, 4:44:48 PM	Connection interrupted, attempting to reconnect...
HTTP request timed out
6/27/2022, 4:44:36 PM	Upload of config.g successful after 0s
6/27/2022, 4:40:53 PM	M119
Endstops - X: not stopped, Y: not stopped, Z: no endstop, Z probe: not stopped

You can see by the entries in the Console that the Z-endstop is now present (again). On the lowest line you can see that there was "no endstop" previously.

Mac

fcwilt

@mac

Good, glad to hear the Z endstop is back.

As I recall (or maybe I'm wrong) that you had some problems getting good crimps?

Can you verify that the connector that plugs onto the Duet has good crimps for each wire?

Does the stepper have a connector mounted on it for plugging in a cable OR are the wires part of the stepper?

Also, can you please change the rotation of the Y stepper in config.g and see if the Y jogging now works as it should?

Thanks.

Frederick

A Former User

@fcwilt said in I could use some help:

@mac

Good, glad to hear the Z endstop is back.

As I recall (or maybe I'm wrong) that you had some problems getting good crimps?

I ordered the large crimps for the two large connectors on the board because I destroyed the 5 they sent. All is well there.

Can you verify that the connector that plugs onto the Duet has good crimps for each write?

You mean wire, I checked both phases, so the wire between the motor and the connector is good, both phases were present.

Does the stepper have a connector mounted on it for plugging in a cable OR are the wires part of the stepper?

Yes, it has a 6-pin socket.

Also, can you please change the rotation of the Y stepper in config.g and see if the Y jogging now works as it should?

I posted that change above. Please scroll up to it.

I’ll try to home Y, and let you know if my edit accomplishes anything.

Thanks.

Frederick

fcwilt

@mac said in I could use some help:

I ordered the large crimps for the two large connectors on the board because I destroyed the 5 they sent. All is well there.

Good

You mean wire, I checked both phases, so the wire between the motor and the connect is good, both phases were present.

Did you wiggle the wires while you checked looking for an intermittent connection?

Yes, it has a socket.

I have to purchase cables for that type as I don't have the parts to make such cables.

I posted that change above. Please scroll up to it.

I did miss it.

What happened when you tried jogging Y? Did it now go in the right direction?

Frederick

A Former User

@fcwilt good news, the Y-axis / bed slowly started to move towards the back, where the end-stop is, then came to a stop about 40mm before it.

I tried jogging the bed Y+10 > and it went forwards. <Y-10 sent the bed towards the rear of the printer.

So the edit I made:

M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes forwards

worked!

fcwilt

@mac said in I could use some help:

@fcwilt good news, the Y-axis / bed slowly started to move towards the back, where the end-stop is, then came to a stop about 40mm before it.

I tried jogging the bed Y+10 > and it went forwards. <Y-10 second the bed towards the rear of the printer.

So the edit I made:
M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes forwards
worked!

OK you are making good progress.

Now to test for the second thing I think is wrong.

I need you to devise a way to measure if the Y axis moves the distance you tell it to when jogging.

For example if you clicked the button that jogs Y 10mm (either direction is fine) five times did the bed actually move 50mm.

It is essential that we get all axes to move the distance they are commanded to move. This is step one of that process.

Frederick

A Former User

@alankilian @droftarts @fcwilt

Here's the latest challenge:

6/27/2022, 5:26:40 PM	G28 Z
Error: G0/G1: insufficient axes homed

I got that report when I used Z to home the print head. It did it, but very slowly , with the motor making a horrible high-pitched sound as it moved about 40 mm.

The BLTouch never tried to probe the bed coming up underneath it.

The print head is about 5mm above the bed, and the X-axis is slightly less than 2mm above the Z-endstop.

fcwilt

@mac said in I could use some help:

@alankilian @droftarts @fcwilt

Here's the latest challenge:
6/27/2022, 5:26:40 PM	G28 Z
Error: G0/G1: insufficient axes homed
I got that report when I used Z to home the print head. It did it, but the motor made a horrible high-pitched sound as it moved down about 40 mm. The BLTouch never tried to probe the bed coming up underneath it.

The print head is about 5mm above the bed, and the X-axis is slightly less than 2mm above the Z-endstop.

It sounds like you are trying to home using the other code that homed with the Z probe, rather than my code which homed with the Z endstop.

BUT...

We have to verify what I think is wrong with the Y axis.

If I am correct in my thinking the problem likely affects X and Z and it plays a role in what you are seeing.

Frederick

A Former User

@fcwilt Well, now that you've delivered a real CLIFF-HANGER, proceed!

For the record, I unplugged both ends of the X-motor cable and tested all of the wires for continuity. All of them, including the wires to the end-stop passed the test.

Interestingly, on the X endstop, on the other side of it, I can see the the information: (can't discern)A 125 250V (weird horizontal line) 10T85. The markings are, left to right, 1, 3, 2.

On the other side: (the red wheel is up on the left), the casing says NC (far left) NO (center), and O (right side).

The GREEN WIRE is in the middle, it is connected to the NO post on this side, and it is numbered 3 on the other side.

The WHITE WIRE is on the RIGHT (below the end of the metal arm), it is labeled O on this side, and 1 on the other.

Hope that information helps.

A Former User

@mac

fcwilt

@mac said in I could use some help:

On the other side: (the red wheel is up on the left), the casing says NC (far left) NO (center), and O (right side).

That O is actually a C for COMMON. The NC is for NORMALLY CLOSED. The NO is for NORMALLY OPEN.

The GREEN WIRE is in the middle, it is connected to the NO post on this side, and it is numbered 3 on the other side.
The WHITE WIRE is on the RIGHT (below the end of the metal arm), it is labeled O on this side, and 1 on the other.

Which is perfectly consistent with how we had to set the M574 commands.
...

I really want to get your printer up and running so would you please find a way to measure the Y axis movement and verify that is moves the distance you command it to move.

We cannot move forward until we have verified the Y axis is moving as it should in regards to distance.

That likely will tell us what needs to be done to rectify homing problems with all of the axes.

Please.

Frederick