Topics created by darookee

The print just finished. It occasionally clicked and clacked a bit, I tried loosening the screw a bit more, but that does not do anything. But I guess it's not a Duet problem. Thanks for the help! 😄

Yes I think getting rid of springs can help. Play around with probing speeds too. Too slow and you don't get a trigger, too fast and you lose accuracy. Sorry for not picking up this one earlier I've been away travelling.

Thanks!

I had the M29 without the filename and thought that was the reason for it not working so I changed it, as the RepRap-Wiki also shows the example with the filename.

Well, that is interesting. It seems to be fixed for me, too. I added a call to '/rr_disconnect' in the script that pulls the printer status and it looks like the problem is solved. Thanks!

No, there is no second browser connected.
Btw: I do not even have power fail saves enabled!

Just installed the new 1.20beta and it looks like it is fixed. I get this response.

Manual corrections required: 0.00 turn up (0.00mm) 1.04 turn down (0.52mm) 0.26 turn up (-0.13mm) 0.60 turn down (0.30mm)

Thanks!

Edit: But I still can't access the 'probed points' view under 'machine control' 😐

The dead time measurement is the least accurate part of the PID tuning process. The value you get seems to vary somewhat with the M303 S parameter you use, which isn't right. So I'm looking at an improved way of measuring it in the next release.

Reducing the dead time further may help, but if you go too low then the temperature will oscillate. You can adjust it while you are printing, if you don't mind the possibility of ruining the print if it does oscillate..

I can see the value in setting based on existing conditions (like increase temp by X) - this is effectively a relative mode for temperature and other settings that we apply this to.

Adding to the M500 settings that are saved would also be useful (but of course adds to the potential confusion, which is why i wanted to just edit the config.g always)

We are continuing to more closer to a general language for programming using gcodes….a friend of mine compared it to the development of shader languages in GPUs into general purpose programming languages.

Ian Rommies issue is that the Effector tilt causes the probe to trigger at differing height around the bed and unfortunately this negates the use of the Bed Comp anyway and the prob will be just the same with a BLTouch.

I think DJ's Piezo idea will do away with that error as it uses the Nozzle tip itself as the probe point.

I wonder how difficult it would be to use Strain gauges on a

CB material or even better a Carbon Fibre effector with a set of Hayden's rod's?

Doug

Thanks for the tip toward troubleshooting these issues. I'll let you know how my progress goes (hopefully it will get better since hearing this tip)

Jonathan l

I tried reslicing the model from the slic3r file with S3D and now the Web Interface correctly display 0.18 for the first layer. And it seems that it is also correct, the nozzle does not scape on the bed… So it seems it is a problem with slic3r?

Yes, it was nice with autolevelling and all that, but I since repurposed all the electronics of my Wanhao into a Hypercube. Only needed the appropriately sized extrusions… 🙂

It worked alright, it heated up, so I won't be worried. Thanks for the answers! 🙂

Hey I have sent you an email.