Duet 3 Mini LED Question

JADoglio

I am installing a Duet 3 Mini 5+ in a Voron 2.4r2 build. I have never used LED's in my printers so I am a bit unclear on the connections.

It appears that I need to connect a 5V power in source to pin "pson". Is that correct?
As this pin shares resources with IO_4.OUT once I use this port I can't connect anything other devices to the IO-4 port? Please confirm

Do I also need to create a M950 command to define the port?
If that is true what would that M950 include?

I also need to connect the LED's to the Neopixel pins which appears to be named "NP_LED", however in the documentation of pin names in the Duet 3 Mini5+ table it does not appear so I would appreciate it if someone can confirm this?
Last, I need to define the LED's as a fan using M950 F3 C"NP_LED" and then they can be controlled using M150 commands?

If someone can fill in the blanks, or confirm/correct all of this it would be greatly appreciated.

dc42

@JADoglio currently you don't need to configure the LED port using M950, although this may change before the stable 3.5 release. That's why there isn't a pin name for the NPLED pin on the Neopixel connector.

The external 5V supply should be connected to the 5V_EXT_IN and GND pins of the 5V_EXT connector. Do not connect anything to the PSON pin of that connector, unless you are using it to turn an external power supply on/off.

You can use IO4.out if you have nothing connected to the PS_ON pin.

HTH David

JADoglio

config.g.txt @dc42 That helps. Thanks again. However, now I have another issue. I am trying to shakedown the Voron 2.4r2 I built. So far, I have confirmed the end stops are working, the bed heater is working, the z drives and all working properly and respond as expected when using the DWC dashboard controls. As you know this is a Core XY machine. And as it is my first Core XY I will admit I understand less than I would like about the kinematics. So here is where I could use some help, the A (X) B(Y) motors are behaving strangely. I attached a table showing the XY movement behavior using different M569 S parameters. I also included my config.g file. As the file is currently setup X and Y move as they should but using the DWC Dashboard controls the X axis seems to be assigned to the Y controller and the Y axis seems to be set to the X controller. Any ideas why this is happening and how to control it. I am amazed how promptly you respond people on these questions. Thanks again for your continued support and help.config.g.txt M569 Summary.xlsx

oliof

@JADoglio Please see Testing motor movement to identify how to fix the motor assignments so the printer moves the right way.

JADoglio

@oliof

Thanks, I figured it out. I was using M564 H0 and using DWC to check movements but somehow it was messing things up. When I stopped using it and went to the procedure you provided everything began to behave as it should.

JADoglio

This post is deleted!