@Phaedrux haha, fair enough.

I have solved my issue, finally! I will give a quick rundown of my findings here, with the hope it helps someone in the future.

Basic issue: the servo motors controlling my delta printer towers were not moving correctly. These motors have external drivers that I am controlling using the Duet Expansion Breakout Board. This includes no movement, stuttering movement, incorrect distances, and incorrect speeds.

Solution: I believe all of these steps were necessary, but if I could go back and do it again I would definitely try the timing adjustments first.

1. Use 5V logic by connecting the PUL+, DIR+ and ENA+ for all three tower servo motors to the +5V pin on the H6_PMW header of the Duet Expansion Breakout Board.
2. Use 'R1' to invert the enable signal (although this may be accomplished by switching the ENA+ and ENA- wires).
3. Increase timing values. The tricky part here is that the values stated in the servo motor manual did not work! I had to increase the values well above what they stated was necessary. More details below:

Based on these figures, I believed that setting the timing to T3:3:6:6 using the M569 command would be sufficient. HOWEVER, after testing I found that the minimum values I can use are T4:4:10:6 meaning a 4 microsecond step pulse width, 4 microsecond step pulse interval, 10 microsecond direction setup time and 6 microsecond direction hold time. To be safe, my final values are as follows:

M569 P5 S1 R1 T5:5:12:6 ; physical drive 5 goes forwards (x-tower), enable signal inversion, timing:3,3,6,6
M569 P6 S1 R1 T5:5:12:6 ; physical drive 6 goes forwards (y-tower), enable signal inversion, timing:3,3,6,6
M569 P7 S1 R1 T5:5:12:6 ; physical drive 7 goes forwards (z-tower), enable signal inversion, timing:3,3,6,6

@bearer Thank you very much for your informative response. I will take all points into consideration and look around for Duet2 Wifi boards, which I would then pair with an expansion breakout board.
The excellent documentation and forum support are major reasons I'm looking at Duet3D products, so your quick response is a +1 there!

@bearer Just purchased a Duet 2 WIFI, Duet Expansion Board, and PanelDue 7i through reseller Filastruder. Looking forward to the huge upgrade from my MKS SGEN board (and I'll be using the correct logic level now haha). Excited to be a part of the Duet3D family!

@dc42 Yes, that is what I thought as well.

Do you have any idea why timing is so far off? Like I mentioned above, I successfully tested these motors with the same power supplies and a MKS SGEN controller board with timings of 3:3:6:6. The MKS SGEN board provided 3.3V logic, so if anything I would have assumed it would need more time to activate the opto-isolators due to the underpowered signal.

One concern I have is these motors are supposed to run at a maximum pulse frequency of 250 kHz. Is there a way for me to set that for the Duet board?

@droftarts Good to know, thanks. Here is what I get:

M569 P5
Drive 5 runs forwards, active high enable, timing 5.3:5.3:12.8:6.4us

@Phaedrux haha, fair enough.

I have solved my issue, finally! I will give a quick rundown of my findings here, with the hope it helps someone in the future.

Basic issue: the servo motors controlling my delta printer towers were not moving correctly. These motors have external drivers that I am controlling using the Duet Expansion Breakout Board. This includes no movement, stuttering movement, incorrect distances, and incorrect speeds.

Solution: I believe all of these steps were necessary, but if I could go back and do it again I would definitely try the timing adjustments first.

1. Use 5V logic by connecting the PUL+, DIR+ and ENA+ for all three tower servo motors to the +5V pin on the H6_PMW header of the Duet Expansion Breakout Board.
2. Use 'R1' to invert the enable signal (although this may be accomplished by switching the ENA+ and ENA- wires).
3. Increase timing values. The tricky part here is that the values stated in the servo motor manual did not work! I had to increase the values well above what they stated was necessary. More details below:

Based on these figures, I believed that setting the timing to T3:3:6:6 using the M569 command would be sufficient. HOWEVER, after testing I found that the minimum values I can use are T4:4:10:6 meaning a 4 microsecond step pulse width, 4 microsecond step pulse interval, 10 microsecond direction setup time and 6 microsecond direction hold time. To be safe, my final values are as follows:

M569 P5 S1 R1 T5:5:12:6 ; physical drive 5 goes forwards (x-tower), enable signal inversion, timing:3,3,6,6
M569 P6 S1 R1 T5:5:12:6 ; physical drive 6 goes forwards (y-tower), enable signal inversion, timing:3,3,6,6
M569 P7 S1 R1 T5:5:12:6 ; physical drive 7 goes forwards (z-tower), enable signal inversion, timing:3,3,6,6

@Phaedrux Am I correct in understanding that M569 P5 S1 R1 T3:3:6:6 will set motor 5 to forward, driver to active HIGH, pulse width to 3 us, step pulse interval to 3 us, direction setup time to 6 us, and direction hold time to 6 us?

@polbofree Have you tried auto calibration? https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Auto_calibration

Small dimensional errors like you have are likely an issue with your delta parameters (M665). If you are fairly sure your rod length (L) parameter is correct try to adjust your delta radius (R) parameter. If this parameter is incorrect (could be due to using a different effector configuration (i.e. ball spacing at carriage/effector changes)), you will have dimensional errors.

Post your config.g file, please.

I have rewired the servo cables following your guide so that PUL+, DIR+ and ENA+ for all three tower servo motors connect to the +5V pin on the H6_PMW header, while PUL-, DIR-, and ENA- are still connected to the respective pins on the E2, E3, and E4 headers. This changes seems to have fixed my first problem, so I can now move in the negative z-direction after homing. It also seems to have fixed the 'struggling' motion I noted in the above post. Woohoo!

HOWEVER, movement still does not work properly! Here's what happens:

G28 ; home
G90 ; absolute
G1 Z0 ; try to go down to bed
This should be a ~640 mm movement, but only goes about 270 mm. The towers do each seem to move in sync for the same distance. The tool position numbers react appropriately, and for this case show a position of 0,0,0, which is correct for my command but not what happens.

G1 Z100;
G91 ; relative

G1 Z100 ; all carriages move up ~43 mm (no difference observed using a ruler)
G1 Z-100 ; all carriages move down X ~44 mm, Y ~44mm, and Z~45mm

Next I tried going up 100 mm and then down 100 mm five times. End positions were: X +5 mm, Y +5 mm, Z +18 mm the starting position.

Next I tried going up 100 mm and then down 100 mm ten times. End positions were: X +8 mm, Y +8 mm, Z +34 mm the starting position.

For the final repeatability test, I repeated this 5 times and noted the different in end position:
G28
G90
G1 Z100
End position varied by about 1mm, both above and below the average position.

My conclusion from this inconsistent motion is that I must be missing steps (open to other suggestions of course). A few thoughts/questions:

1. In the servo motor manual, it says maximum communication speed is 250,000 Hz. Could the duet board be sending more commands per unit time than the servo's driver can handle?
2. How does setting a microstepping mode (M350) affect external drivers? Could interpolation cause any issues?
3. My timing could be off. This seems likely, except that I am using the same timing values that I successfully tested these motors with the MKS SGEN controller board. Copied from the servo manual:
   t1: ENA must be ahead of DIR by at least 5μ s. Usually, ENA+ and ENA- are NC
   (not connected).
   t2: DIR must be ahead of PUL active edge by 6μ s to ensure correct direction;
   t3: Pulse width not less than 2.5μ s;
   t4: Low level width not less than 2.5μ s.

At this point, I'm fairly stumped as to what to try next. Any thoughts or suggestions are highly appreciated!

@Phaedrux Thank you for linking the individual tower testing page. I tested all towers and endstops individually (problem not solved) and here are my results:

G28 to home - moves slowly to each endstop and reacts correctly by immediately stopping the correct motor for each respective endstop, moves down, and then does a second successful pass.
G91 to set to relative movement
G1 H2 X-10 - nothing happens
G1 H2 Y-10 - nothing happens
G1 H2 Z-10 - nothing happens
G1 H2 X1 - X carriage moves up approx. 1mm
G1 H2 Y1 - Y carriage moves up approx. 1mm
G1 H2 Z1 - Z carriage moves up approx. 1mm

*turn off power to motors and manually moved all carriages down to give myself room to test

G1 H2 X-10 - nothing happens
G1 H2 Y-10 - nothing happens
G1 H2 Z-10 - nothing happens

G1 H2 X10 - X carriage moves up approx. 6 mm
G1 H2 Y10 - Y carriage moves up approx. 6 mm
G1 H2 Z10 - Z carriage moves up approx. 8 mm

G1 H2 X-100 - now I'm getting strange behavior where the carriages will move down but seem to struggle (as if under mechanical resistance) and move at variable speed
G1 H2 Y-100 - now I'm getting strange behavior where the carriages will move down but seem to struggle (as if under mechanical resistance) and move at variable speed
G1 H2 Z-100 - now I'm getting strange behavior where the carriages will move down but seem to struggle (as if under mechanical resistance) and move at variable speed

The above moves don't seem to be repeatable and go variable distances all the while speeding up and slowing down and seeming to barely be able to turn under all of the mechanical resistance of my stare?

G28 - again works as it should (although maybe too slowly?). Also, I should note the negative z-direction move during homing before the second pass doesn't seem to struggle like negative z-direction moves noted above.

G1 H2 X-10 - nothing happens
G1 H2 Y-10 - nothing happens
G1 H2 Z-10 - nothing happens
G1 H2 X1 - X carriage moves up approx. 1mm
G1 H2 Y1 - Y carriage moves up approx. 1mm
G1 H2 Z1 - Z carriage moves up approx. 1mm

And so on.....

Okay so at this point I have a few ideas.

1. after homing there seems to be a software endstop type effect because the motors won't move down using the 'G1 H2' or 'G1'
2. based on the strange movement, 'struggling' to turn motion, and incorrect move distances there could be issues with timing or logic levels sent to the servo motor's external drivers.
   The second point is what I will focus on next. For my current set-up, I am using the Duet Expansion Breakout Board to communicate with the servo motors at a 3.3V logic level (communication at this level has worked in the past using an MKS SGEN 32-bit controller board). The servo motors are JMC integrated AC servo motors iHSV57-30-18-36-01-BY V604 and their manual/TDS is Servo Motor User Manual.pdf (also attached to my previous post). To be honest, I don't understand the difference between differential vs. non-differential(?) signals so maybe that is playing a role. My motors do have ENA-,ENA+, DIR_,DIR+, STEP- and STEP+ pins, so I'm guessing it is correct to attached them to the Duet Expansion Breakout Board with it's differential 3.6V signals. HOWEVER, the servo manual does specific 5V logic is needed to control the optically-isolated driver pins (again, in the past I got away with 3.3V using the MKS SGEN board). So, I will try changing to 5V logic following the instructions here: https://duet3d.dozuki.com/Wiki/Duet_Expansion_Breakout_Board#Section_Notes

My apologies for the very long post. If it is poor etiquette to post something this long please let me know.

Best wishes,
Joshua

I realize I forgot to add the firmware version.
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-02-11

@Phaedrux Attached below are my config.g and homedelta.g files, along with the servo motor TDS.

config.g
homedelta.g
Servo Motor User Manual.pdf

Some additional information about the behavior after homing:

1. I turned off power to the servo motors so I can turn them manually
2. I lowered all carriages by a hundred mm or so
3. I turn power back on to the servo motors
4. I press -50 z-direction a few times (so it thinks the carriages are sufficiently below the endstops)
5. The X and Y carriages move down a few mm each
6. I then press +50 z-direction and get the following behavior: X carriage goes up ~17mm, Y carriage goes up ~21mm, and Z carriage goes up ~20mm. This behavior seems to be repeatable, i.e. if I press +50 z-direction again each carriage moves up the same respective distance again (as far as I can tell with quick ruler measurements).
7. I then press -50 z-direction: the Z carriage doesn't move and the X and Y carriages move a few mm down and then won't go further.

Based on successfully using these motors in the past, 200steps/mm should be correct and the step-pulse timing I set should be correct too.

Thank you again for any help!!!

Hello all,

I have a custom delta printer running on servo motors with integrated drivers. I'm using a Duet 2 Wifi with a Duet Expansion Breakout Board. I used the RRF Config Tool to set up my system for the first time tonight and I'm running into some strange behavior after homing.

Homing works as expected. All three carriages move at the same rate and each stop once they hit their respective endstop switch, move down a few mm, do a second pass, and then are supposed to all move down the same distance of 50mm (I set this value to exaggerate the effect I was seeing). However, instead of all moving down 50mm, the X and Y towers move down about 10mm and the Z tower moves down about 2-3mm. If I use the DWC buttons to move in the negative z-direction, the X and Y towers move down a few mm but the Z tower doesn't budge. BUT, if I move in the positive z-direction, movement is as expected with all three towers moving up at the same rate (I have limited space here because the Z carriage only moved a few mm down from the endstop switch). Also, the position value changes when I do movement command, like the printer thinks it successfully completed the movement.

It seems like a software endstop type problem is keeping the Z carriage from moving down after homing. It is a similar type of inhibited movement that I've seen deltas do when you try to move outside the set boundaries. Looking at my config.g file, the only axis limit set is:

; Axis Limits
M208 Z0 S1 ; set minimum Z

I apologize for the lengthy and probably confusing post, but I would really appreciate any help. I'd be happy to provide any additional information, too.

Best,
Joshua

@bearer Just purchased a Duet 2 WIFI, Duet Expansion Board, and PanelDue 7i through reseller Filastruder. Looking forward to the huge upgrade from my MKS SGEN board (and I'll be using the correct logic level now haha). Excited to be a part of the Duet3D family!