Hi All,
Thanks for your replies. I took the carriages and packed them with lithium grease for bearings. I used sewing machine oil for the linear rails. The problem has been reduced. At least, I don't hear the weird sound. Now I am doing my autocalibration.

I will post the auto calibration results in a separate thread.

In short, lubricate both the rails and carriages even if they come from high-quality vendors. It helped a lot.

Regards,
Vasan

Got it in one. Thanks yet again dc42.

I've added the F parameter to the M42 command in 1.19beta7, which I intend to release tonight or tomorrow. Like the I parameter, it isn't remembered for M42 (unlike in M106).

DWC does indeed give you a window into the printer operation, however it lets you customise that window. There are some aspects that you would not want to store server side. For example, you might choose a fast polling rate when using a PC next to the printer, and a slower rate when using a mobile device.

I use m226

Just to finish this of by saying I ordered the pt100 daughter board (hopefully nothing is amiss with that system). I tried H7 but when I enabled it as my second tool numbered 99, in tool definitions the DWC was now displaying 7 tools of which 4 (h2-h5) showed 1970 deg C and 2 (h6 and H7) error with or without a thermistor attached, the two working ones are handily bed and h1. So thanks for the advice but yes it seems as though something is amiss with the adc system though thankfully not the heaters, motors or anything else.

@npm1:
If you can mount it, go with the piezo system from Precision Piezo (DJDemonD).
Till recently I had a FSR system under the bed and it was good to probe with the nozzle. But the piezo is better.

Might want to send him an email through the forum as his PM notifications seem to have problems.

https://www.duet3d.com/forum/thread.php?id=1569#p14784

Lol sounds nice. My printer is literally made from a recycled swingset into a prusa i3 style printer. usually it works perfectly fine and have had zero issues, until this week when it seems everything wanted to die all at once…

Here is a controller that works great but I think the Duet Wifi/Ethernet would be even better. G codes and description of what they do.

https://planet-cnc.com/wp-content/uploads/2016/03/CNCUSBController.pdf

Welcome!

To see what you need to do, go to https://duet3d.com/wiki/Duet_Wiki and look at section "Getting started with the Duet WiFi". There is also a Quick Start Guide on that page.

The main steps are:

1. Make any necessary changes to your wiring harness to suit the Duet. In particular, the endstop connections and the Z probe connections will almost certainly be different. See the Hardware and Wiring section of that wiki page.

2. Get connected via WiFi. See the Getting connected to the Duet WiFi link.

3. Generate config.g and homing files for your printer. See the links in section Firmware configuration (Duet Ethernet & Duet WiFi).

HTH David

I'm glad you figured it out. My guess is that your bed.g file had a row of zeros at the start because y=0 was not accessible to the probe, and that row of zeros was confusing DWC.

Christian hasn't built a .bin version of DWC 1.16 because that release is targeted ad the forthcoming 1.19 firmware release.

Done, I know its taken a while, https://www.thingiverse.com/thing:2388496 including a link to a youtube video.

Great! Looking forward to it 🙂

@FrankNPrinter:

some slicers have a setting to make the tip go back over the part while doing a retract, this may help prevent the blobs if they are being caused by retracts.

In Slic3R it's called "Avoid crossing perimeters" and you are right to point out that it might help.

This is a known issue with this forum software, I will look into it when I get a chance (but the hardware dev work and other stuff around that is really busy right now!)

@dc42:

If all the LEDs went off including the blue one, then the power to the Duet kept failing. Possibly causes include:

Bad power in connection. Check that the VIN terminal block screws are tight. Something drawing more that 30A shortly after power up. But I would expect you to see signs of charring if anything on the Duet was doing this. A fault in the PSU causing its overload protection to trigger falsely.

Hello Mr. David,
Your suggestions are all right, in fact these are the first things I thought and controlled, unfortunately I find nothing unusual and then, as I wrote before, I launched a test print and everything worked well.
So I guess there's no log, right? If I enable debugging in the firmware what happens?
Do you completely exclude a possible bug under certain conditions?
Are you aware of the slight anomalies with the web interface?

Thank you anyway for support
Dommy

I thank you sir.

I haven't used M98 before
I just looked it up the wiki
Not sure why it worked before for you but not now
The wiki says the default path is /sys and some firmware will look into /macros
So probably RRF skips /macros