Topics created by dgrat

@dgrat The warping is more likely due to the different thermal expansion characteristics of the spring steel vs the (presumably aluminium) bed, rather than a temperature gradient across the bed. You could limit the rate of heating by reducing the PWM value but that might limit the maximum temperature than you can obtain. Alternatively, you could heat the bed in (say) 10 deg C stages with a pause in between each stage.

This is very vague. Can you give some more detail?

Do you think it makes sense to check encoding in the firmware and reject the file to avoid UB.

@oliof
I'll check that

@dgrat said in Maybe Bug: Redoing height maps add sometimes random offsets:

Thanks all for gcode and explanation

Always glad to help if I can. If I cannot help I try very hard to not make things worse. 😉

Frederick

@dgrat I found the issue. I forgot to set the X/Y offset of my sensor. It was correcting for the wrong spot..

@T3P3Tony , I use klipper on my modified BigBox printer. Compensation can be done for both X and Y axis' . The result on my printer, with two lightweight carriages in an IDEX configuration, is pretty amazing (I can watch ringing ripples disappear when using their test pattern). Also, there are multiple algorithms that are available now for the resonance compensation, so I think Dmitri's work will be a great resource for development!

@dgrat the CNC build I’m working on now is based on a Duet3. Pretty excited to start making chips!

Good to hear that the fallback to USB flashing with Bossa worked. Something may have gotten out of sync. The main reason for updating to 3.0 first is to ensure that the IAP files are present from that release. Perhaps something was out of sync, corrupted, or missing.

You have the correct M574 endstop configuration for those endstop switches, see https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Makerbot_Mechanical_Endstop_v1_Num_2.

Independent homing of dual axis motors should be working. If you are in doubt, you can check it by triggering one of the endstop switches early; but if you do that, take precautions against damaging the machine due to running just one of the axis motors, for example by reducing the motor currents.

zprobe.in+zprobe.mod works fine. I must have missed that in the docu. I usually use the effector with the sensitivity 8:247 and double tip each point.
I get the best consistency with this setting. Down site is that the fans must be off during calibration. In the new firmware a lot of stuff changed. Took me a while to move settings. Good thing is that you have to do it just once.

Thanks for sharing that design. It's on my list to print.

Loose pulley, check that the bed is mounted fixed

@dc42
Okay I flashed the firmware with avrdude. Seems to work now.

@dc42 seems like effector may still work after swapping the fuse, but my effector also has no probe indicator led as illustrated in the docu. Is this for self soldering or are the other two leds intended to glow (which they don't)? I also tested resistors R11, R13 and R14 and they seem more or less fine. But there is still no changing Probe signal as in the beginning.

IMG_20191018_184449.jpg

c0de5170-f57d-47dd-ac78-fe89812ec560-grafik.png

My Fluke sais I have a phase resistance of A) 1.8-1.9 Ohm and B) 2.0 Ohm.

Why not just home Z with the BLTouch to begin with?

Ok that makes sense. I was wondering why this was in the spread sheet and now I know.

Thanks

41a06f09-1ac4-4347-b1c6-37292b7dc6b2-image.png

G30 with a P parameter is intended for auto calibration and similar operations performed when the printer has already been homed. So it starts probing from the dive height (M558 H parameter). Whereas G30 without a P parameter is intended for operations such as initial Z homing and measuring the Z probe trigger height, so it starts probing from the current height.