Quantcast
Channel: Reprap Forum - Firmware - Marlin
Viewing all articles
Browse latest Browse all 2831

Dual Z axis will move together, but will not home together (no replies)

$
0
0
Originally posted this to the marlin bugfix, but they locked the post and said that is would be better way to get support for a user issue from the forum. So I'm here.

Below is the original post, which I hope has enough details to be useful.
### Did you test the latest `bugfix-2.1.x` code?

No, but I will test it now! //acutally tried using the 2.1.1 configuration release files from btt, and copying over to the latest version of 2.1 bugfix. Can't count the number of items I have errors on, so my copy/paste skills must be horrible somewhere in the 3000 lines of code. Those are attached as configuration-mega.zip. not sure what version they are supposed to work with, and get the config files are newer, please upgrade marlin or .... so tried manually copying pasting....with horrible results. more errors than I can count, and deleting sections to remove errors just cause more. those are only include to show what a working file specifically designed is supposed to look like. they were not part of any successful build I've been able to compile.

### Bug Description

Likely in the wrong place, but at my wits end, would appreciate any help on what obvious error I'm creating for myself.
I simply cannot fathom what part of the code I've missed to force both z axis to home in unison.

[FIRMWARE.CUR.inverted.stops.to.NO.from.zip](https://github.com/MarlinFirmware/Marlin/files/9701493/FIRMWARE.CUR.inverted.stops.to.NO.from.zip)


### Bug Timeline

_No response_

### Expected behavior

E expect both z to home and trigger on end-stop

### Actual behavior

Only the left axis moves on the home command when using pronterface, had inverted endstop triggers originally causing some issues, but have verified both z axis are not triggered via m123

### Steps to Reproduce

1. compiled based on the attached files
2. load build onto sd card
3. successful flash of new file
4. testing results in second z running correcty on move command, but home command simply does not move second z motor.


SENDING:M119
Reporting endstop status
x_min: open
y_min: open
z_min: open //have tested both z and physically verified triggered versus untriggered, this allowed me to correct from NC to NO flag. All anycubic triggers are NO.
z2_min: open //have tested both z and physically verified triggered versus untriggered, this allowed me to correct from NC to NO flag. All anycubic triggers are NO.
z_probe: TRIGGERED //I don't have a z probe, so no idea what this is reading
filament: open
### Version of Marlin Firmware

2.0.9.3

### Printer model

Anycubic Mega

### Electronics

SKR3

### Add-ons

No addons

### Bed Leveling

No Bed Leveling

### Your Slicer

Cura

### Host Software

Pronterface

### Don't forget to include

- [X] A ZIP file containing your `Configuration.h` and `Configuration_adv.h`.
[Configuration-Mega.zip](https://github.com/MarlinFirmware/Marlin/files/9701602/Configuration-Mega.zip)

### Additional information & file uploads

I really do apologize if this is in the wrong forum, I'm completely lost. just grasping for straws. Feel free to delete and tell me what simple step I'm missing if this is not actually an error. First time compiling Marlin. Worked my way through a dozen other errors before getting a good compile, so this build has no errors on compile.

Have also tried copying BTT recommended profile for 2.1.1 to the latest 2.1 bug-fix, and cannot count the amount of errors I've tried to re-create from the pre-configured file from BTT. so just trying to get anything to work here.

it's been mentioned that the z axis should be a simple command. but noticed my code is shaded as inactive for defining the z stop:

// For Z set the number of stepper drivers
//
#define NUM_Z_STEPPER_DRIVERS 4 // (1-4) Z options change based on how many // have tried from 2 to 4 drivers, and the below code still shows inactive.

#if NUM_Z_STEPPER_DRIVERS > 1
// Enable if Z motor direction signals are the opposite of Z1
//#define INVERT_Z2_VS_Z_DIR
//#define INVERT_Z3_VS_Z_DIR
//#define INVERT_Z4_VS_Z_DIR

#define Z_MULTI_ENDSTOPS
#if ENABLED(Z_MULTI_ENDSTOPS)
#define Z2_USE_ENDSTOP _ZMAX_ // from here down it shows the code as being inactive no matter how many stepper drivers I try to select. so the zmax endstop is not actually defining?
#define Z2_ENDSTOP_ADJUSTMENT 0
#if NUM_Z_STEPPER_DRIVERS >= 3
#define Z3_USE_ENDSTOP _YMAX_
#define Z3_ENDSTOP_ADJUSTMENT 0
#endif
#if NUM_Z_STEPPER_DRIVERS >= 4
#define Z4_USE_ENDSTOP _ZMAX_
#define Z4_ENDSTOP_ADJUSTMENT 0
#endif

Viewing all articles
Browse latest Browse all 2831

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>