Posts made by Phaedrux

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

You'd need a heatsink fan with RPM monitoring to be able to tell when it's not running. Once you have that reported, you can use conditional gcode and daemon.g to take an action if the rpm drops during a print.

First, you'll need to change the line endings in YAT so we can see multiple lines.

Second, the command to forget networks is M588 S"*"

Also, sending M552 by itself will give some information as well.

Take a look here: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m573-report-heater-pwm

And you can set the frequency in the M950 that defines the heater.

You probably have Cura set to absolute extrusion and your end gcode has a retraction in relative extrusion which is causing the extruder to move to a very early absolute position.

The solution is to either add a switch to relative extrusion mode before your retraction in your end gcode, or better yet, switch Cura to use relative extrusion. Search the settings bar.

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Sorry for the inconvenience.

Can you send M587 by itself and see what it reports?

How are you trying to define the IP address currently?

Over wifi you can set the Duet address when setting up the SSID you connect to with M587

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m587-add-wifi-host-network-to-remembered-list-or-list-remembered-networks

Inn.nn.nn.nn (optional) IP address to use when connected to this network. If zero or not specified then an IP address will be acquired via DHCP.

The only change to M226 between 3.1.1 and 3.4.1 I can find is in 3.3

M25, M226 and M601 all accept a P0 parameter, which causes pause.g not to be run. M24 accepts a P0 parameter, which causes resume.g not to be run. Caution: in RRF 3.4 this is likely to be replaced by a P"filename" parameter.

Though that doesn't seem to be captured in the gcode wiki for those gcodes.

If you're under a deadline I implore you to seek an extension under the grounds of safety.

@tryptamine said in Tuning a hugely overpowered heater:

Is there any constructive, solution-related stuff that could help me?

I promise you this is the most constructive solution.

Can you share the gcode file being printed? Or at least a section of it that shows the M226

Please send M122 and M98 P"config.g" in the gcode console and post the results. You can also send M557 by itself to see what it reports as it's grid settings.

When exactly do you get the No valid points error? Those grid values are only called upon when sending G29 S0 to do a mesh compensation grid.

@dubdub said in Issues with bed probing and leveling independent Z drivers:

G29 X44.1 Y6.4 Z2.35 ; set Z probe offset

This isnt a valid command in your bed.g. Perhaps you wanted to use G31?

Post your config.g

Yes it's likely U3 that has failed.

@dubdub said in Issues with bed probing and leveling independent Z drivers:

Or must the sequence be:
G1 X(180-probeXoffest) Y(180-probeYoffset)
G30

This would be correct for homing.

@tryptamine said in Tuning a hugely overpowered heater:

I am trying to get to work a 12V heating cartridge on a 24V system.

Stop now. Just don't.

@tryptamine said in Tuning a hugely overpowered heater:

Exchanging one is a huuuge pain. So I must get this working.

The pain of melting or burning your printer or worse will be greater.

So you are saying that the print will pause, but the paneldue still shows that it is active, and instead of a resume button, you have a pause button on the panel?

The steps needed to do a DHCP reservation will depend on your wireless router. You'd need to check your manual.

If that proves impossible, you could try setting the IP address in the config.g but you risk using an IP address that your wireless router could give to another device, causing a conflict. You'd need to determine the IP address range being used by the router and pick an address outside of that range.

See here for manually setting the IP for the Duet.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m552-set-ip-address-enabledisable-network-interface

Please only create a single post for your issue.

Wired or wireless?

Are you manually defining the IP address on the Duet, or are you letting the router assign an IP address via DHCP?

DHCP leases may have expired and it got a new address. If this is the case, it's best to setup a DHCP reservation on your router so that the Duet is always assigned the same address. This is preferred to manually forcing an IP address on the Duet, since then you have to avoid IP conflicts yourself.

@dubdub said in Issues with bed probing and leveling independent Z drivers:

G30 X180 Y180

This is not a valid G30 command. In order to probe at a point, you must send a separate G1 X Y command first to position the probe before using G30 to probe at that point.

It's a little different when using the define points like you have here:

G30 P0 X20 Y180 Z-99999                       ; probe near left lead screw
G30 P1 X330 Y180 Z-99999 S2                   ; prober near right lead screw and calibrate two motors

Check out M600 instead

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m600-filament-change-pause

I believe Modix has support for RRF3 now and should be able to provide you with more details and config changes required.

Sounds like a regulator is blown.

With vin connected does anything get hot to the touch?
Can you see any visible signs of damage on any of the smaller chips?
Photos?

Boogie Down!