@chownki
I had some similar error messages on my Duet 2 Wifi months ago.
All was working fine and suddenly some phases may be disconnected.

To make it short, in my case the connection of the stepper was weak.
I checked it a couple of times and I thought the connections is fine, but when looking in detail, the crimping on the cable was not perfect and I could pull the cable out of the contact shoe.

To be 100% save I soldered the cable to the connector shoe and this error message did not appear again.
So shame on my crimping style.

You may check with a complete new cable on your driver giving the error message.

@chownki
I had some similar error messages on my Duet 2 Wifi months ago.
All was working fine and suddenly some phases may be disconnected.

To make it short, in my case the connection of the stepper was weak.
I checked it a couple of times and I thought the connections is fine, but when looking in detail, the crimping on the cable was not perfect and I could pull the cable out of the contact shoe.

To be 100% save I soldered the cable to the connector shoe and this error message did not appear again.
So shame on my crimping style.

You may check with a complete new cable on your driver giving the error message.

I got the parameter B1 example from duet3d.dozuki. It might be a worth to change the B1 parameter to B0 in the toubleshooting doku for BL-Touch.

Modify your M558 and G31. The BLTouch behaviour is controlled by the M558 and G31 commands in config.g. Here is what an ideal set of commands should look like.  


M558 P9 F100 H5 R0.2 T6000 A5 B1 


This sets probe type 9 for BLTouch, 100mm/min probe speed, 5mm dive height, 0.2 second pause time before probe move, 100mm/s travel moves between probe points, probe up to 5 times , or until 2 consecutive probe results match, and disable heaters during a probe move to limit interference. G31 P25 X10 Y10 Z2 Sets the trigger sensitivity to 25, the X Y and Z values should be measured to match your setup.

@DC42
David you are fast and you are right.
Thanks for your helpfull advice.

I had the M558 with B1 parameter (got is from setup example for BL-Touch) and wasn't aware of the impact of the B1 parameter.
Keeping the heater on as default is the better choice. Not sure if the homing will be that much more accurate with heaters switched off. Would need to check this.

With heaters off during homing I run into undertemperture issue with no extruding because of low temperture when the printhead was located very high over the bed. This is solved now.

Bug or feature ?

Temperture is dopping during a long time consuming move / home all .

I'm running a Duet Wifi 1.01 board and ugraded some weeks ago to RRF3.
I noticed that the heater seems to be not heating if a time consuming move is made.

In detail :
I heat up the bed to 50 degrees and the extruder to 200 degrees and than I do homing all.
During the move to home all axes the heater seems to be not heating, the time for homing was aprox. 2 min 30 sec and the extruder temperature drops from 200 to ~140 degrees. (see screenshot below ) when all the moves for homing are completed the temperature is rasing again to targeted 200 degrees.
(I see this temperture drop on the long time z-axis movement, not sure about the x and y axis)

In addtition, If the duet is heating up to the target temperature e.g. from 20 degrees to 200 degrees, I can not do printhead moves until temperture is reached (not always, I don't know what makes the difference here) .

It looks like moves and heating can not be done in parallel, not sure if this behavior comes from the duet firmware or from the web firmware.

I just noticed it on RRF 3.01 RC4 and RC5.

Solved on the extrusion multiplier issue.
The problem was in front of the PC

I had mixed T0 with drive 2 some time in the past and I need to change the extrusion multiplier for Extrusion 2 .
When doing this, also the displayed extrusion length changes in the expected way.

Completly my fault.

Closed

Regards
Pumlux

Hi all,

I'm facing since some days a strange problem and can not find how to fix it.
I noticed that suddenly from one print to the next print my setup seems to be not correct any more. The walls are not touching together and the hole print
object it not strong enough. It is more visible when the print contains retraction. The gap is minimal and I tried to fix it by increasing extrusion multiplier but this seems to have minimal to no effect.

To test this I print 2 lines
0.8 x 100 x 0.4 mm
1.6 x 100 x 0.4 mm

I tried with extrusion multiplier of 20% , 100% and with 400 % and the drive display in the webgui says always 38.4 mm.
I messured the thickness of each line printed with a caliper and they had been all 0.3 mm.

For me it looks like I can not influence the extrusion multiplier at all.

For my setup, just some small details.

Selfbuild printer MendelMax like with Duet Wifi and Titan Extruder using about 60 cm of bowden between coldend and hotend (e3D Chimera) with filament cooling.
I printed with 83 °C bed and 185 °C Hotend.
Firmware 1.18.1

I did not retry to reload the firmware yet.

Did someone had a similar issue or a tip for me ?

Regards
Pumlux

Hi Strips,

did you check your wiring for the y-stepper ?

I had a similar issue , one with the also the y-stepper and one somewhere with the power supply setup.
After I crimpt the cable with new connectors, my issues disappeared completly.
I used already a good crimping tool, but it looked like I worked not good enough on the first time.

Just from my expierence.

Regards
Pumlux

Looks like the link in the first post ist broken.

I did not see a default gateway in the list. Wouldn't this be requirred for accessing from different network , aka port forwarding from public Internet / VPN ?

Regards
Andreas

Did anyone had success to access the Duet Wifi from the internet ?

Let me describe again what the goal to achieve is.

Access the Duet wifi (having a private IP address) via the public IP internet over a router.
Normaly this requires a port forwarding rule on the router, something like
forward (external IP port) (Duet wifi external) to (ip of Duet Wifi) port 80
e.g. take 2000 as external IP port and the duet wifi ip address as 192.160.0.100

This would allow you to access your Duet Wifi over the internet .
With the duet 0.8.5 this works perfectly, with the duet wifi the connection can not be established.

The explanation from W3DRK sounds resaonable, but makes me unhappy

@ tomasf
I think this depends on where your VPN tunnel terminates and what kind of IP address your VPN network card gets assigned. As long as this ip address is in the same subnett as the Duet Wifi is, the explanation from W3DRK is still valid for your and his statement.