Duet3 Homing failed

Hammad

@phaedrux Yes, I followed the instructions in the documentation. I've tried from many different PCs and cables. The board gets detected but the writing process doesn't finish. I even left it over night and it stayed at 34%. I tried older versions of the Firmware and it doesnt get beyond 34% for some weird reason.

dc42

@hammad when and where did you purchase the Duet? Which country are you in?

Hammad

@dc42 From Dold Mechatronik in Germany.

Hammad

@hammad said in Duet3 Homing failed:

@dc42 From Dold Mechatronik in Germany.

I received the board like a month ago.

Hammad

@hammad @Phaedrux @dc42 The firmware writing worked. The issue was the powered USB hub. After uploading the firmware to the board the 5V and 3.3V LEDS stopped working.

Hammad

@dc42 I upgraded the Firmware of the Duet3 to 3.4. When the board is only connected to 24 V externally the 5V and the 3.3V LED aren't on. When I connect the micro USB to my PC it works again (the 24 V isn't connected to avoid a ground loop). now I did the trick where I tell the board through YAT that it homed and tried to move the axis and it didn't work. What am I doing wrong?

jay_s_uk

@hammad if the 5v and 3.3v lights aren't on when powered by 24v, the onboard 5v converter has died

Hammad

@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.

jay_s_uk

@hammad good question. its typically the result of a short in wiring. what were you doing with it prior to the bossa issues? could it have occurred during removal from the printer (assuming you did that for bossa purposes)? if not, whats plugged into it?

Hammad

@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.

Hammad

@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

@hammad one for @Phaedrux or @dc42 to comment on then. in the mean time use it with USB power applied

dc42

@jay_s_uk said in Duet3 Homing failed:

@hammad if the 5v and 3.3v lights aren't on when powered by 24v, the onboard 5v converter has died

Or else the jumper to enable the on-board 5V regulator is not int the correct position. @Hammad, please check it against the wiring diagram.

jay_s_uk

@dc42 forgot about that! Good shout

Hammad

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

Hammad

@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?

Phaedrux

@hammad said in Duet3 Homing failed:

Can you suggest a solution to this problem?

I'll ask again:

Have you been able to get the motors to move at all? You can force the axis to report as homed without moving at all by sending G92 X100 Y100 Z10 and then carefully testing movement by sending G1 X1 F100

Hammad

@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.

Phaedrux

I am confused by your response. Is homing working or not?

Can you give a more detailed restatement of the current problem situation?

Perhaps it would even be a good idea to start a new thread since this one has gone on for quite some time and we've gone through a number of things.

deckingman

@hammad Are you saying that the homing status changes from "unhomed" to homed but the motors don't move? If so, then it means that the homing switch is triggered at the start of the move. The usual cause of that is either the configuration does not match the physical NO/NC of the switch, or there is a wiring fault.