Topics created by bubblevisor

@jay_s_uk Good point! Certainly works in DWC 3.5.0-rc1. I'll add it to that guide. I'll check with @chrishamm when it was added.

Edit: He says 3.5, so I think I'll wait until 3.5 is actually released before adding it to the docs.

5a7e8ebf-1508-412d-8b4b-e0743f345bbd-image.png

Ian

@bubblevisor maybe bossa the board. Who knows what changes fysetc have made to that beta version

@bubblevisor there are a number of discussions here due to the fact that the Smart Effector implements a fast acting strain gauge rather than the HX711/HX717 based ones that act slow and require higher loads.

@bubblevisor it doesn't matter which GND pin on the Duet you use for this purpose.

@bubblevisor said in Induction probe false triggering:

Do you mean I need to fully define M558 in the bed.g as well as in config.g? such as M558 K0 P5 C"^zprobe.in" H10 F1000 T6000 A20 S0.01

No, not the full M558, but you would need to include the K0 or K1 in addition to the parameter you wanted to change.

@bubblevisor I guess you are connecting the PanelDue using the ribbon cable? It is mentioned in a couple of places that the PanelDue_SD connector shares pins with the IO_0 header. I've added it in a couple of other places, to try and make it clearer.

IO_0 can be used for endstops, Z probes, filament monitors etc. so long as no PanelDue is connected.

Ian

A 5v active buzzer pulls 30mA. Would this be ok to run directly off the GPIO? I'm worried its too much! buz.JPG

@bubblevisor I thought about focused cooling at one point. Using compressed air (from an air compressor) and a solenoid seemed like it would be worth a try. If you already have a compressor its pretty simple from there.

@bubblevisor thanks for the tip!

Have you tried tuning it yet? What values did it produce?

It's probable that you'll get differences in behaviour when tuning from cold and from a warmer ambient.

In a normal use case, what would the environmental conditions be? Running from cold, or already being warm?

What wattage is the heater?

Also take a look here: https://forum.duet3d.com/topic/22729/automating-sequenced-prints-and-repetitions

3.4 final.

@bubblevisor said in Cannot update Duet 3 mini 5 to 3.3 firmware:

"no tool selected error".

Sounds like you need to select a tool. commonly this would be done in a few places to ensure one is selected when needed. Add T0 to the end of config.g to have the first tool selected at startup, and then add a T0 to your slicer start gcode to make sure one is selected for the start of the print. It may also be a good idea to create a start.g file in the system folder and add a T0 there as well.

@bubblevisor said in Defining Bed mesh probe points to avoid neodymium magnets:

@fcwilt Thanks for the info. Could you explain how you would "edit out" specific problem probe points?

This is what I have in the config currently M557 X21:216 Y28:200 P4 . But I would like to adjust the position of a few of the points.

Hi,

Sorry I wasn't clear.

You could view the height map in the DWC and make note of any points they were clearly incorrect and likely the result of the probe reading being influenced by the magnets.

By noting the XY position of the point you could edit the height map .CSV file and assign a Z value to that point that made sense based on the Z values of the points around it.

Frederick

@gixxerfast Brilliant!! I didn't notice the jumpers!!

@bubblevisor , to build the Y harness in @dc42's post, you can use these connectors which match your existing stepper connectors.

https://forum.duet3d.com/topic/23461/anybody-wants-a-stepper-motor-analyzer/122?_=1635001020231 (should land at my Oct 16, 2021, 1:04 PM post there)

@bubblevisor the official recommendation would be to use a PT100 daughterboard and use a PT100 sensor for one of the temperatures you need to monitor.

It may work "OK" using one of the analog inputs on the IO headers however the accuracy will be worse, and it may be nosier than using a proper temperature input, because the temperature inputs are referenced against analog ground and analog VDD and we measure those voltages to improve accuracy. That might be ok for the chamber heater.

On the mini 5+ you will need to use io3.in:
https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Hardware_overview#Section_IO_port_pin_capabilities
as that is the only IO pin that is analog capable.

Also, unlike the temperature inputs, that are pulled up to VDDANA with 2k2, the IO input is pulled up to EXT3.3V with 27k so a temperature setup string needs to take that into account.

This might work for a 100K thermistor
M308 P"io3.in" Y"thermistor" T100000 Bnnnn R27000

Where Bnnnn refers to the beta value of that thermistor.

The thermistor would then be connected between IO3.in and Gnd.

Note I have not tried this so don't know if it will work ok.

@bubblevisor said in Tool Length Switch:

I want the firmware to ignore any PINDA probe readings for Z offset.

Well the heightmap is created with the probe, so it's a list of values showing the relative difference in height compared to the z0 point established by that probe. As long as your probe Z0 point and the switch Z0 point agree, you don't have an issue. Does that make sense?

@bubblevisor said in Tool Length Switch:

I have now changed the way I home Z using only the tool switch. I am also defining the two sensors via M558 K command. Seems to be working....

If it's working, that's the important thing. Can you also share your homing files?