@dwarren5684 said in Erratic behavior, skipped steps:

Normally if I wait a while (10s) the motors will start working

Boot up can take a few seconds. 10 seconds from power on isn't unusual I think.

Thanks for your reply. It's little bit complexe for me but i nothing is unpossible !

@CrashWidget As above but actually, you'll find that overall heat up time will be drastically reduced (improved) if you move the thermistor - (ideally fit it into hole in the edge off the plate, close to the upper surface). The reason being that when the sensor is close to the heating element, there is a rapid rise in temperature at that point. The heating algorithm will "see" that high temperature and turn the heater off. Then there will be delay for it to cool before the heater turns on again. That on-off-on cycle repeats until the plate eventually reaches print temperature. If you move the sensor as I suggest, then you won't get that on-off-on cycle - the heater will simply turn fully on until the temperature gets close to the set point when the PWM will start.

@resam said in Object Cancellation M486:

I read somewhere that the Duet2 is memory-limited and therefore only 10 parts are remembered - I have 12 on my current build plate. Lucky me.

In RRF 3.2.x it's 20 parts on Duet 2, 32 parts on Duet 3. In fact on Duet 2 it can count up to 32 objects, but it can't provide their dimensions beyond the first 20, and it will only provide the names of up to 20 objects.

I've made a note to check M486 C. It should respond with "Object N cancelled" if successful. Currently it returns nothing if the command fails, but I'll change that in RRF 3.3 to report why it failed.

Excellent. Thanks again.

You can use this method to identify the motor phases to ensure correct wiring.

https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

most likely he forgot to update the duet web control

That's a relief. 🙂

@dc42 in my case it could also be pet hamster related... 😅

@OwenD Thanks ! 🙂 Your solution is awesome !

Post your config and tool files?

Also update to 3.2.2, including the tool boards.

SBC or standalone mode?

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

@AlVo94

No problem at all, glad you're up and running.

Instead of S255 please try S1.

Post your full config.g as well if that doesn't work.

@simonJ Follow the 'getting connected' guide, specifically here: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7?lang=en#s9

Usually, I find it more reliable to turn off WiFi with M552 S-1, then turn it on in idle mode with M552 S0 before adding SSID, if there's no existing WiFi connection. Then send M552 S1 to enable WiFi.

Ian

@Saurabh said in Using FAN Pin as a GPIO in Duet 3:

Solved the issue, GPIO pin is working when a device is connected to that. Earlier I was checking output on out4 using a multimeter and it was showing almost 0V. Any idea how to detect this pwm signal on out4 using a multimeter or scope?

Connect a pullup resistor between the OUT- pin and the adjacent positive supply pin.

I have sent the warranty contact formular a few days ago, has it arrived? I didn't get a confirmation email yet or any other reply.

@TomasL said in Multiple problems:

Now, I got it working so far.
It seems that the IR-probe stopped to work though.
Well a minor problem.

Please start a new thread if you need help with that.

@Phaedrux Well it seems to have worked this time. I might have used the wrong settings when i used the config tool. It does say this:

Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 3 idle and 25 tuning cycles in 2864 seconds. This heater needs the following M307 command:
M307 H0 R0.322 C440.5 D3.78 S1.00 V24.1
Send M500 to save this command in config-override.g

No errors when heating the bed so can I assume that things are all fine then?

@Phaedrux I received my replacement board and now everything works properly. Thank you!