Problems with Duet 3 Mini 5+ WiFi

fcwilt

@unforgivenll said in Problems with Duet 3 Mini 5+ WiFi:

@fcwilt Okay, that seemed to do it. Thank you. It worked on that network before. I have another printer on the guest network connected and it is working correctly for 2 years now.

But were you trying to connect to the printer from another "guest"?

Frederick

Unforgivenll

@fcwilt I had the original board connected on the guest ssid/network and with the exception of the wifi module not working properly it connected fine. I have a second printer on the same network.

Unforgivenll

@fcwilt I'm not sure what happened but it looks like even though the router showed as connected on that SSID, it wasn't working. I double checked after my last reply to you and the other printer couldn't connect either. Figures it was something simple. Sorry to bug you. Thank you for everything. I really appreciate it.

fcwilt

@unforgivenll

Glad to be of help when I can.

A typical WiFi "guest" setup is for guests to your home who want Internet access but you don't want them to have access to your network.

It generally provides a dedicated DHCP server to handout IP addresses to the guests and it prevents one guest from seeing another.

Frederick

Unforgivenll

@fcwilt I understand. The only reason I set it up that way is because it wasn't working initially. I should have tried the main network first. I am having another issue with the new Moons motors I just received. I've tried every possible combination in the wiring and keep getting an out of phase error. Any idea what I'm doing wrong?

MS17HD4P4065.pdf

Phaedrux

Have you identified the phase pairs?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting#identifying-the-stepper-motor-phases

Unforgivenll

@phaedrux Yes I have.

Phaedrux

And do your pairs match what they show in the data sheet?

Unforgivenll

@phaedrux Yes they do.

Phaedrux

And how are they connected to the Duet?

When do you get the out of phase errors?

Does that happen on every driver?

Unforgivenll

@phaedrux I get the error when I try to home it. Tried different drivers and different motors. The error comes up when I press home. After a second the motor turns in the correct direction and after about 20 seconds or so it stutters.

Phaedrux

Can you share your config file?

And it happens to every driver and with different motors? The scope of the problem keeps creeping.

Can you also post your homing files if that's when the problem happens?

Unforgivenll

@phaedrux It does happen on X an Y. I cannot test Z yet as it isn't homed (Still testing before everything is permanently placed.).

homez.g homey.g homex.g homeall.g config.g

Phaedrux

If you want to test movement on an unhomed axis use G1 H2 Z10 for instance.

Unforgivenll

@phaedrux Is that why I'm getting an error?

Phaedrux

Do you have motors connected to all of the drivers when you test?

What is the exact error you're getting?

Phaedrux

I see you have sensorless homing set for X and Y. Do you have endstop switches as well? That can simplify things during initial setup.

Unforgivenll

@phaedrux I have senseless homing set in the config but not calibrated. 8 don't have any endstop switches.

Unforgivenll

@unforgivenll G1 H2 X10 makes the motor lock up and whine.

Phaedrux

Ok, so sensorless homing is going to take some configuring to get working. I would suggest that you put that off until you've done some more testing and commissioning.

You can also force the axis to be homed by sending G92 X0 Y0 Z0 for example which would make the firmware think that the current position is at the low end for each axis. This can be useful for testing.

Basically we need to test movement without homing (or sensorless homing in this case)

The same can be done by using G1 H2 commands to ignore the homed state and just move the motor.

Do you get the errors when trying those means of moving the motor?