@axiom You don't need to call filament-error.g; it will get called when there is a filament error. See the 'Events' page I linked. You can run it to test it with M98, I suppose. As to what it contains, that's up to you. If you don't need it to do more than pause, you probably don't need it. If you need it to move to a specific place, retract filament etc, copy the contents of the pause.g macro and add/change to get it to do what you want. You can use conditional Gcode and query the Object Model if you want it to automatically change to a different tool and continue, though I don't have an example of that code to hand.

Ian

@axiom

Try these
M18

M17

You can pass one or more axes as a parameter

@T3P3Tony Thanks! Yeah, I think I've been coming to that conclusion too. Might also go for the height adjustable pebble wiper in case I modify my tools in the future. Somehow I feel this is gonna be more than a Saturday afternoon tinker...

Have you done the static and dynamic test of the probe to verify it's working first?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

Probe already triggered may mean the input pin needs to be inverted, or the probe wiring is incorrect, or the probe has a fault, or that it's actually already in a triggered state. You'd need to provide a lot more information to determine which it could be.

@axiom said in height tolerances heating bed:

When leveling bed, error messages appear regularly.

What error messages?

@axiom said in control screen shows a temperature range of -273.1 degrees:

@deckingman Wow, thank you so much, it was so easy!
I have a volcano hot end
https://www.3djake.de/e3d/supervolcano-upgrade-kit-300-mm?sai=7419
Can I also enter 285 or 400 degrees as the maximum temperature, or does the board reach its limits?
And can I also set the standby temperature for the heating bed myself...I didn't find it in the documentation for unger Bedheater standby.

You can set pretty much any temperature you like. It's not a question of if the board will reach a limit, but rather will the hot end? If the hot end fails to reach the set temperature, this will result in a fault condition and the board will turn the heater off.

As for setting a standby temperature for the bed, you could in theory but it wouldn't be wise. The reason for having standby and active temperatures is mostly for machines which have multiple tools. In this situation, when you change from one tool to another, it's better to keep the unused tools warm as it will save time when it is next used. But with a single tool, there isn't really a use case for using standby temperatures and it's generally safer to turn it off when not in use. The same applies to the bed. You can of course use any active temperature you like. This is what I do on my pre-print macro. I start by setting the bed temperature to around 40 Deg C then wait. Once it reaches 40, I then set it to 60 (or whatever value I need for the filament) but in this case, I don't wait. While the bed is heating to the higher temperature, I then home the printer and set the hot end to the active temperature. Then finally I wait for both the heaters to attain their set point temperatures by using M116.

@Nxt-1

Well drawn explanation of the piezo sensitivity!

Sorry for necroing this thread, but your drawing inspired me to design a program that can generate a point cloud for probing, that avoids the points near the towers and prefers the points near the underbed piezo's.

Sadly it's made in Grasshopper so I can't share it as a script or executable, but maybe this could be inspiring to someone.

I just finished my DIY Delta printer today and I noticed that the probing wasn't that great across the bed so I wanted to see if I could fix that somehow. Assuming my bed is flat enough, I came up with this, where the colored circles are the piezo locations:

Example with lines drawn:
9c8f3237-91f5-41e9-8df4-8e158ddf8a8a-image.png

Outermost points culled and I tweaked the amount of points a little bit (and the point data is rounded to whole numbers):
f7aad29a-4642-4322-953f-6f08c6cd600d-image.png

And this is the output point list that can now manually turned into a list for the reiterative probing sequence for example (with the point data rounded to two decimals):
4d5e58f3-fc33-4f0a-b941-af7d6e556de2-image.png

This data can be changed on the fly, so I can see what the probing pattern will look like live without having to first run a script, it's live:
https://youtu.be/0ofXqwViaMc

I hope this could serve as an inspiration to someone and if you have ideas of a good type of point distribution I'd love to hear your ideas.

I have yet to try out this set of points but it's kinda late now so I'll do that tomorrow when I'm sharp and present again.

Just a small update on this reply, which I might turn into a post later on if anyone thinks it deserves its own post:

The results are in, initially it had quite a big deviation, but the second probing sequence was an immediate hit:
Calibrated 8 factors using 18 points, (mean, deviation) before (-0.009, 0.034) after (0.000, 0.022) Auto calibration successful, deviation 0.022mm

I also incorporated a point sorting algorithm. Before the point list was random, causing long travel times during probing, but now it's just moving from one point to the next closest point making this a painless probing sequence.

Ok, this has now been resolved (at least on one printer. Will test on the others once I have rewired them).

To fix the issue, had to update firmware and rewrite the stop.g and cancel.g files. Guessing issue was somewhere in the old firmware or in those configs.

Updated to RRF3.4.4 (Sorry, the printers were in storage for months).
Cleared all entries in stop.g and started over.
Then found it would throw the heater fault on cancel.g but is now fine on stop.g.
Cleared cancel.g, then rewrote it calling stop.g with a couple calls before and it works now too.

On another topic, also found on very rare occasions to be breaking contact on the connector, even with new wires, new molex connector crimped, and new senso with appropriate connector. I have found this can be averted by fixing the connectors so they are not free to move around. ...I need to revise my cable management.

I would suggest that you upgrade to 3.4.5 by uploading the full zip file release to the system tab in DWC.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

That will update everything including DWC.

After updating the firmware can you send M98 P"config.g" to check for any syntax errors?

For the PanelDue, what hardware version is it specifically? I have an old v2 panel and it still runs 3.4.x so unless you have a really ancient one I think you would be ok.

; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 R80 ; enable HTTP on Port80

I would simplify those to be M552 S1 and M586 P0 S1 since you're just listing the default values anyway.

; Z-Probe - BLTouch M950 H7 C"nil" ; Disable heaters h7 to free up pins

It's not necessary to use "nil" to free up a pin unless it's already been assigned previously. At startup, it won't have been bound to anything yet.

If this is a delta, your endstop configuration is incorrect.

; Endstops M574 X1 S1 P"xstop" ; X min active high endstop switch M574 Y1 S1 P"ystop" ; Y min active high endstop switch M574 Z1 S1 P"zstop" ; Z min active high endstop switch

You have them set as low end stops. But on a delta they are at the top.

X1 Y1 Z1 should be X2 Y2 Z2

Fixing that should negate the need to do a weird workaround.

If it wasn't connected before that would definitely explain the reduced range.

@jay_s_uk yes, indeed.

@axiom you need to have a look here:

https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

and here:
https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation

the functions you reference in your example "hasHeightHap()" etc are not meta gcode.

@axiom If you go to the status screen you will see the baby stepping button:
55f1aa37-77eb-4851-b977-f62c205bd7ce-image.png

Can you grab a photo of the mosfet? Sometimes they appear damaged.

Otherwise you can use a multimeter to check them. Though they are quite small, so you need to be careful with the probe tips.

https://www.youtube.com/watch?v=RkWy1EirEu8

If they are failed, they can be replaced. https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#fan-mosfet

They typically fail if the fan short circuits either through the wiring or internally to the fan. Does the fan still work when connected directly to voltage?

@gloomyandy
D3 makes no difference

7938dc71-d13b-45c8-9c42-6253cfe06312-image.png

Looks OK and familiar 😉

@DechAmim-0 the cable to the 12864 display carries the Reset signal, so close proximity of that cable to a stepper motor cable might perhaps cause a reset because of capacitive coupling.

@Zdenko said in Duet 3D in mind - Building ver.2 Pick and Place machine:

That sounds good, only thing is to use one BAT43 or BAT85 or even 1N4148 on the Output line of the sensor with the cathode "pointing" towards the sensor, simple.

That diode is recommended when connecting an NPN sensor to an older Duet 2 board. It is not needed when connecting to a Duet 3 board.

@Visionary no. That's how RRF2 used to home axis with more than 1 motor