Posts made by 3DTyro

Thanks- I found it after more searching. For those who follow this thread later, the correct command is "M564 H0", and adding it to the end of config.g worked for me.

I have a Duet Ethernet-controlled Powerspec I3 printer. It has been working well, until I upgraded it to 2.01 and DC42's latest DWC. Also fails with 1.22 of DWC in the same way.

The wiring didn't change, there were no mechanical changes, and the CONFIG.G file seems the same as before.

Th error message when I try to home the printer is: Error G0/G1 Insufficient axes homed" , which is of course what I'm trying to do...

Any ideas?

Agree with robm, DWC is really good, but adding the gcode visualization would be a great feature.

Based on DC42's experience with the Sannce camera, I bought 2 to test. I finally, after a little fiddling, got it to work just using the URL DC42 provided.

The port varies, as mine was different than DC42's example. I'm not sure if that's because the camera was on a different firmware revision, or if it is random. In any case, the app linked to showed not only the IP but the port as well.

I wasn't able to use the solution briangilbert suggested, though I am running Chrome, not FF.

Yep- that's it! The Z-probe display also shows numeric values with the paper test. Now to make a new mount…

Thanks!

No, it doesn't. What does that mean? And why doesn't the display show the values in the DWC?

I'm setting up a Duet Ethernet with the DC42 IR probe for Z probing on a Wanhao I3 Plus clone (Powerspec). The probe shows the expected 4 flashes on startup, but in the Duet web control display the value for the height level is always zero, instead of the expected values around 500 when the probe is near the bed.

I've set the correct M558 command G31 as follows in the config.G file:

M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P500 X34 Y0 Z2 ; Set Z probe trigger value, offset and trigger height
M557 X25:175 Y25:175 S20 ; Define mesh grid

The problem is that when trying to probe the bed height using the Auto Bed Compensation button, the nozzle drives about .250" into the top of the print surface, so obviously it can't be probing the bed correctly. It does seem to want to move around to the various check points, each time crashing the bed.

So what am I doing wrong? Should I comment out the mesh grid command- I thought that might be the result of a bed probe… Or is there another problem?