I found the error... 2 1XD Boards had the same address and it was causing the whole problem. Thanks for the support!

@jay_s_uk Thank you for the idea. Ill let you know in few minutes if this actually works.

I found the error... 2 1XD Boards had the same address and it was causing the whole problem. Thanks for the support!

@dc42 @deckingman @jay_s_uk @Phaedrux this is the link to the new thread.

new thread

Hello experts,

I am having a problem with my setup.

The setup is a Duet3 6HC with 3 1XD modules that are connected to stepper motors from Nanotec. Link to the Motors:

Nanotec Stepper Motors

I'm still getting no response from the motors even after upgrading the firmware to 3.4 to solve the issue with 1XD modules. To check the motors I used an Arduino Uno with grbl and the motors moved. I still can't figure out why the motors won't respond to the Duet3 setup. I checked the wiring and every bit of the documentation. Any idea what could be the problem?

I also tried forcing the axis to report as homed and the motors still won't move. The coordinates on the touchscreen (Panel 7) change when I try to move the axis but the motors aren't moving at all.

Extra info:
The limit switches are in NC setup.
There will be no heated bed or fans in this printer
The Mainboard will not use Ethernet.

thanks for the support!

@deckingman The Homing status changed to the coordinates I entered with G92 X100 Y100 Z10. The Touchscreen showed X 100 Y 100 and Z 10. When I try to move the motors using the Touchscreen they don't move at all but the coordinates on the screen change. The wiring isn't the issue. I checked everything and it was built to be normally closed as recommended by the documentation. I'm going to start a new thread to make it easier for everyone to follow. I need to get this to work for a big project. I already ordered many boards for the other printers lol. I'll post a link to the new thread in a bit.

@phaedrux It does home. I can see the coordinates on the Touchscreen. The Motors don't move at all. I tried moving the Motor with an external driver and it worked. Just to make sure that the Motors aren't the issue here.

@dc42 @Phaedrux I'm still facing the original Problem with the Motors. The Board doesn't home or move the Motors. I reconfigured the RepRap firmware and still nothing. I bought the 1XD Modules to be able to use the motors I mentioned in my reply at the beginning. Can you suggest a solution to this problem?

@dc42 Thank you so much. This was actually the Problem.

@jay_s_uk I only have the CAN cables and the 24V cables. nothing else. The motors are connected to the 1XD Modules.

@jay_s_uk I didn't remove the board from the housing. I just got the board and 3 1XD Modules for a big 3D printer. The board arrived like a month ago. The issue with BOSSA was just an issue because I misunderstood the Firmware process. I erased the Firmware by bridging the erase on the board. There is no wiring issues and everything is built according to the documentation.

@jay_s_uk why would it die after a firmware update? while updating the firmware i only used the USB port as a source. When the update was done i unplugged the USB cable and used the 24V external source.