Stepper definition Z motors

fcwilt

I've re-arranged the M569 commands by board address.

You have P1.0 and P1.1 appearing twice.

M569 P0.0 S1                                                                            	; Z1	 physical drive 0.0 goes forwards
M569 P0.1 S1                                                                            	; Z2	 physical drive 0.1 goes forwards
M569 P0.2 S1                                                                            	; Z3	 physical drive 0.2 goes forwards
M569 P0.3 S1                                                                            	; Kext1	 physical drive 0.3 goes forwards
M569 P0.4 S1                                                                            	; Kext2	 physical drive 0.4 goes forwards
M569 P0.5 S1                                                                            	; Z4	 physical drive 0.5 goes forwards

M569 P1.0 S1	; Y	 physical drive 1.0 goes forwards
M569 P1.0 S1                                                                            	; DEXT3	 physical drive 1.0 goes forwards
M569 P1.1 S1	; X	 physical drive 1.1 goes forwards
M569 P1.1 S1                                                                            	; DEXT2	 physical drive 1.1 goes forwards
M569 P1.2 S1                                                                            	; DEXT1	 physical drive 1.2 goes forwards

M569 P2.2 S1                                                                            	; Kext3	 physical drive 2.2 goes forwards

M569 P3.0 S1                                                                            	; V	 physical drive 3.0 goes forwards
M569 P3.1 S1                                                                            	; U	 physical drive 3.1 goes forwards
M569 P3.2 S1                                                                            	; Kext4	 physical drive 3.2 goes forwards

ahwitmer

Thank you for the effort. I'm going to look at it tonight.

ahwitmer

@fcwilt
Yes you are right indeed. Don't fully understand why the mistake got in there because that part was programmed via the config tool. My X and Y are connected to board 2
Indeed the end stop needs to be connected to the same board as the stepper.
By changing the stepper drivers to board 2, the endstops are connected to the same board.

Although it was incorrectly specified, changing the board number did not change the situation.

fcwilt

@ahwitmer Did you fix the M584?

M584 X2.1:3.1 Y2.0:3.0 Z0.0:0.1:0.2:0.5 U3.1 V3.0 E1.2:1.1:1.0:2.2:3.2:0.3:0.4 P5

Or is that intentional?

Frederick

ahwitmer

@fcwilt
No that is indeed intentional. It is a double gantry CoreXY. This means that X and U as well as Y and V move in the same direction when printing.

Harald

ahwitmer

@Veti @fcwilt
Veti it is a double gantry CoreXYUV
It is the intention to move the pairs X/U and Y/V simultaneously for now,

How do you mean Z does not allow for multiple values?
Do I understand correctly that I have to remove the multiple Z values for the commands M92, M566, M203, M201 and M906 ? Even when they are connected to their own drivers ?

Indeed you are right, just tested it, after removing the extraneous data at the Z-steppers do correctly show the correct amperage.

Part 1 solved

The extruders are not yet recognised.
Also get errors on microstepping

Thanks so far!

fcwilt

Hi,

From the DWC console execute M350 by itself.

If that doesn't reveal the problem try commenting out the M350 in config.g and re-boot.

Then from the DWC console execute M350 with one drive at a time to see if you can find what is causing the error.

My printer is a Cartesian with these commands:
- M584 X0 Y1:2 Z5 E3
- M350 X16 Y16 Z16 E16 I1

If I enter M350 X0 I get a driver 0 error.

If I enter M350 Y0 I get a driver 1 error and a driver 2 error.

if I enter M350 Z0 I get a driver 5 error.

All those driver numbers in the errors match with the driver numbers in M584.

Also check config-override.g for a M350 command.

Frederick

ahwitmer

@fcwilt
Your advice works out. It had to do with the Z parameters. I was using Z:16:16:16:16
After changing it to Z:16, the error message is not shown anymore!

My Extruder steppers still do not shown amperage yet.

Harald

fcwilt

@fcwilt said in Stepper definition Z motors:

Your M906 has semi-colon where it should be a colon. That of course means everything after the semi-colon is considered a comment.

M906 X3200 Y3200 Z2240:2240:2240:2240 U3200 V3200 E1360:1360:1360 ; 1360:1360:1360:1360 I30

Frederick

Veti

@ahwitmer said in Stepper definition Z motors:

How do you mean Z does not allow for multiple values?

Z0.0:0.1:0.2:0.5

this is not allowed. z only take 1 values for all

this applies to M92 M566 M203 M201 M906

ahwitmer

@Veti Indeed, followed up your advise and that works out fine. Thanks!

@Veti @fcwilt

And the story continues:

My set-up
Mainboard 4 z-steppers (Nema 23, 2.8 Ampere)
Expboard 0: 3 extruders
Expboard 1: X and Y stepper (nema 23, 4 Ampere)
Exp board2: U and V stepper (Nema 23, 4 ampere)

Mainboard: 12 V supply
Expansion boards: 24 V supply

Switch to 24 Volt was done in a later moment after I purchased several 12 Volt other elements. Have insufficient space to install another 24V power supply.

Commissioning
Okay now my Z-steppers provide the correct amperage when issuing M906.
Commissioning the Z motors is done by first disabling the endstop requirement by
M564 S0 H0
Pushing the buttons on the machine movement tab should move the motors.

Result
Out of the 4, only two Z-steppers react on the commands to move.

Both motors move irregularly.
For one of the motors, once it starts stepping it will continue stepping, but it decides itself if it takes the required direction, sometimes it is up, some times it is down or it just stutters at the down command.
The other motor hardly turns and also changes its mind regularly to up or down stuttering.
In addition, the first motor is not activated after the step-cycle is finished, that is okay.
The second motor however remains kept energized. I did not realize it until I found that the motor got quite hot and even the power cable became warm.

I have a continuous readout of voltage (both 12 V and 24V) and that one is keeping stable during this excercize.

Changing the mainboard from 12 V to 24 V will likely change the issue of the warm cable. Nevertheless keeping it energised is never the intention. I have to reset the board to get it de-energised.

What would be the reason behind iregular stepping?
Why is one motor kept energised?

PS I did not yet switch cables to find out if the cables are crimped (in)correctly.

Harald

fcwilt

Hi,

If it were me I would comment out the existing stepper configuration commands (M92 M203 M201 M566 M906 M350) and create a test set for one Z stepper at a time.

Then I would verify that each one works on it's on - thus checking the stepper, the wiring and the power).

Divide and Conquer.

Frederick

Phaedrux

@ahwitmer said in Stepper definition Z motors:

What would be the reason behind iregular stepping?
Why is one motor kept energised?
PS I did not yet switch cables to find out if the cables are crimped (in)correctly.

Definitely check your wiring and ensure you have the motor phases correctly paired.

https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

ahwitmer

@Phaedrux @fcwilt @Veti

The pairing of phases is verified again and shown to be connected correctly for all motors connected to the mainboard.
Still the steppers sometimes go up and sometimes go down.

Only wondering if there is a difference between

A1 A2 B1 B2 and A2 A1 B1 B2

fcwilt

@ahwitmer said in Stepper definition Z motors:

@Phaedrux @fcwilt @Veti

The pairing of phases is verified again and shown to be connected correctly for all motors connected to the mainboard.
Still the steppers sometimes go up and sometimes go down.

There appears to be a timing problem related to the expansion boards that deals with this issue.

https://forum.duet3d.com/topic/21326/just-another-bug-with-3hc

Frederick

ahwitmer

@fcwilt I'm going to take a look at it, thank you..... I'll be back

ahwitmer

@fcwilt @Phaedrux @Veti
Have been busy for some time with other pressing issues.

Last weekend I adopted the advise of fcwilt I modified the Config.g file using only one Z-motor (on mainboard driver 0). Then using an extra motor I tried to get it stepping.
It turned out that the cabling and crimping was the main origin of the problems.

One cable had to high AWG. That made the stepper squeek and respond differently on commands and got it quite warm.
I checked, recrimped all wires, now I have 4 working cables for the steppers.
Next I tested every driver connection to the mainboard.

Now I have three drivers working however the last one (driver 1 on mainboard) did not react to any stepping request. When requesting a large step, the system returns an error message.

Exchanging the cables did not have any effect. The cables are now working like a charm except on driver 1.

I have been careful with the motors not to rotate them when connected to the board.

This has all been done on 3.2. After my finding I decided to install 3.2.2 for the mainboard and the expansion boards. But helas no improvement. The other drivers still perform correctly. Driver 0.1 keeps on having issues....

Did I fry my driver in some way?

Phaedrux

@ahwitmer said in Stepper definition Z motors:

Did I fry my driver in some way?

Anything is possible, but let's eliminate cabling first since that's the most likely issue. Is there anything visibly different about that driver header? Is the crimp making good contact?

ahwitmer

@Phaedrux
I have 4 cables for the 4 motors,
I'm using driver 0.0 0.1 0.2 and 0.5
Modified my config.g so that I test driver by driver with any of the 4 cables
In total I test 16 times with a stepper. Every driver with any of the 4 cables.

Testing all cables on 0.0 0.2 and 0.5 and rotating/testing all 4 cables work perfectly in
Connecting any of the 4 cables to 0.1 results in the same error as shown above.

Because of this I conclude the cables are okay.

The connector on the motherboard looks very similar to the other connectors.
Nothing special there.

Phaedrux

Thanks for the clarity on your testing. Before we conclude the driver is failed, can you share your current config.g? Just in case.