I could use some help

A Former User

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time)
G91                                 ; relative positioning
G1 H2 Z5 F3600          ; lift Z relative to current position
G90                                   ; absolute positioning
G1 X47 Y21 F3600      ; go to first probe point
G30                                  ; home Z by probing the bed

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

A Former User

@droftarts after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.

droftarts

@mac Fixed your Gcode posts. You selected the 'list' format (three dots vertically next to three lines) rather than the 'code' format (like </>). You can also edit your posts to fix them; click the three blue vertical dots on the right of a post, next to the upvote/downvote buttons, and select edit.

Ian

fcwilt

@mac said in I could use some help:

after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.

The symptoms you describe do suggest a stepper wiring issue.

Frederick

droftarts

@mac said in I could use some help:

@droftarts after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.

... though usually if a phase was disconnected you would get an error. It's possible that the DWC jog buttons are just trying to move the axis too fast. Try sending something like G1 X10 F100 for a short, slow move. This should move the X axis 10mm at 100mm/min, so take 6 seconds.

The default for the jog buttons is 6000mm/min, or 100mm/sec. If you want to change this, it's in System > Machine specific > General tab, under 'Machine specific > Feedrate for move buttons'.

Ian

A Former User

@droftarts Since my bed on the Y axis was behaving, I decided to change the X-motor's rotation to REVERSED also. When I tested it, that didn't go well the first time. I thought because I reversed the green and white endstop connector at the same time, that may have had something to do with the print head's back-and-forth behavior.

So I left the X-motor reversed, and changed the endstop wiring back. Now, GRN is white, and i05.in is green. Because of that, the x-motor's behaving. It appears that it's limited movement to the left (where the endstop is), has to do with where the board thinks the left of the bed is.

Can you tell me, once again, HOW to tell my board where the LEFT ENDSTOP for the X-AXIS is?

I'll assume that the process is the same for the Y and Z axis, and go from there?

Mac

A Former User

@droftarts Because the X, Y, and Z motors are seem to be happy being reversed, my assumption is A) the wiring to the main connectors is backwards, and B) I need to change the EXTRUDER motor to REVERSED as well?

A Former User

@droftarts So, I just switched to Console, and there's this message: 6/26/2022, 8:23.46 AM / Event / G28 X (new line) Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected

Lovely. That means the Y-axis motor has failed, right?

Mac

A Former User

@droftarts false alarm, the Y motor's working, but it's stopping way short of the front of the printer. So it's doing what the X motor is doing. There's a clue in that, I think.

A Former User

@droftarts okay, final update for today. I homed Y. It went all the way to the right (as far as it thinks it can go, I gather), and started coming down. When I looked at it head-on, I saw that the BLTouch was off the board (to the right). So, I turned the machine off.

Mac

fcwilt

@mac said in I could use some help:

Can you tell me, once again, HOW to tell my board where the LEFT ENDSTOP for the X-AXIS is?

The only thing you can do, with the current firmware, is to specify that the endstop is at the low end or the high end of the axis.

When you execute a G1 H1 move and the endstop sensor is activated the logical position of that axis is set to the axis min or max, as defined by the M208 values for that axis.

If the endstop is declared to be at the low end of the axis the min value is used.

If the endstop is declared to be at the high end of the axis the max value is used.

If, because of the actual location of the endstop sensor, the resulting logical position is not correct you have these options:

adjust the position of the endstop sensor so it matches the M208 min or max value depending on the endstop being at the low or high end of the axis
adjust the min or max value in M208 so it matches the position of the endstop sensor, again depending on the endstop being at the low or high end of the axis
adjust the logical position to match the physical position using the needed combination of G1 moves and G92 setting of the logical position.F

Frederick

A Former User

@fcwilt yep, that’s what it gets down too. I’m going to change the setting to what they were in the beginning: Low, instead of high, using RRF, and see how that goes.

fcwilt

@mac said in I could use some help:

@fcwilt yep, that’s what it gets down too. I’m going to change the setting to what they were in the beginning: Low, instead of high, using RRF, and see how that goes.

It's not guess work.

You know where the endstop is mounted, either at the min end of the axis, in which case the endstop setting is low, or at the max end of the axis, in which case the endstop settings it high.

And you can make a simple change like what via the DWC Gcode editor.

I believe you are encountering what some folks do when the use the configuration tool. It generates a complete set of files, which may or may not be correct. Folks install the files and hit homeall - and it doesn't work because of a wiring problem, bad part or configuration error.

The procedures I described for determining the max travel of an axis are part of checking the behavior of the printer step by step. And fixing each problem as you find one.

When I build a printer I take a very methodical, and perhaps boring, approach. One thing I will do is wire up one stepper at a time and verify it is working. Once all steppers are verified then I will move on the the endstop sensors. Again wiring up one at a time and verify it is working.

Frederick

A Former User

@fcwilt I think your's is a wonderful approach. Here's where I am at the moment.

In I/O Mapping, under Z-Probe, the Input Pin appears to be losing the (not assigned) assignment (not assigned). I can see that the BLTouch is bright red. I guess I'll have to pull the connector off the board to get that fixed. (I took your advice, and reinstalled my Z-axis end stop.)

On the Motors page of RRF: X is Forwards, Y is Forwards, Z is Backwards, and EO is Forwards now. I've been experimenting with hi and low endstop settings to see if I could get the Y-axis to behave. It's not happening so far.

On the Endstops page of RRF: X, Y, and Z are SWITCH, Low, High, Low. I have Y on High because I'm still trying to figure out what the settings should be. The range of Y seems to be only the front half of the printer (if that makes sense).

On the same page, No Z Probe is the choice.

On the Heaters Page I've gone back to Bang-Bang. I'm trying to get the printer to work by keeping it simple. The Heated Bed is set for a max of 33 degrees celcius. The Nozzle is set for 100 degrees celcius. The sensors are 4092's.

On the Fan page, Fan0 is full on, no thermostatic control, and Fan1 is the same.

Honestly, I don't understand the Tools page. What should I be trying to accomplish there?

I've turned off all display choices, so I guess this is a headless setup. I'm feeling a bit headless as well.

But I feel like I'm making some progress.

Mac

A Former User

@fcwilt no progress, I think. I did change the y-axis endstop connector. It goes to i/06, so white wire to i/0 6_in, and green wire to GND, just like the X endstop connector next to it.

Home All: raises the x-rail, moves the bed towards the front, Z doesn't bring the z-rail down to the bed?
Home X: raises, moves the printhead to the right, and lowers the print head back again.
Home Y: raises the x-rail, and moves the bed forwards at the same time.
Home Z: raises the z-rail, turns the top fan for the print head on full speed, and that's it.

fcwilt

@mac said in I could use some help:

@fcwilt no progress, I think. I did change the y-axis endstop connector. It goes to i/06, so white wire to i/0 6_in, and green wire to GND, just like the X endstop connector next to it.

Home All: raises the x-rail, moves the bed towards the front, Z doesn't bring the z-rail down to the bed?
Home X: raises, moves the printhead to the right, and lowers the print head back again.
Home Y: raises the x-rail, and moves the bed forwards at the same time.
Home Z: raises the z-rail, turns the top fan for the print head on full speed, and that's it.

What you are trying to do is sort of what I talked about, testing "high level" things like "homing" before verifying that all the individual bits and pieces are working.

Think back to those "instructions" I suggested you try to verify that each axis was working (moving in the correct directions) and determine the max travel for each axis.

Were you able to complete those?

Frederick

A Former User

@droftarts my bad, sorry about that.

A Former User

@fcwilt no, sadly, I was not.

I've made 3 videos of what's going on with my printer. The third one is almost on youtube.

For what good it will do.

Mac

A Former User

@droftarts @fcwilt

link text

I am trying. We have a language problem obviously. But I’m serious about getting my printer working. Your help has been very appreciated.

I’ll take these videos down when my printer's working as good as the XVico was.

Mac

A Former User

@droftarts @fcwilt

link text

The End.