Topics created by Schild0r

@schild0r
I wouldn't use M957 as it's for debugging as you say.
I see no problem with calling the macros for filament-error or load.g from your trigger.
I seem to remember DWC 3.4 allows a filament change to the same filament now, but you can always identify the load.g you want to run with
move.extruders[state.currentTool].filament

@dc42 said in Object cancellation: cancel global features:

Would it really make sense to cancel all non-object items at once?

No of course not all at once, this is why I thought it was maybe possible to count and list non-object items the same way as object items so there would for example the following list

Object 0: "cube"
Object 1: "cylinder"
(non) object -1: purge towers, etc. Everything that the slicer gemerates and does not label as object
(non) object -2 to -99: e.g. custom gcode sequences that are explicitly labeled via M486 S(-2 to - 99) that the user may want to leave out at some point, and that are not printing moves. The negative numbers only make sure that these custom features can be used regardless of the number of printing objects (for which the slicer/firmware would automatically generate only positive numbers).

You could of course also label these custom features with M486 S999999 or so because you are realistically not printing a million objects but I am not sure if there would be some implications for that (like the requirement for continuous numbers so the firmware would create "null" placeholders for everything between the last object number that is actually in the gcode and 999999) EDIT: this seems to be the case but only up to 40 objects

@phaedrux Oneplus 8 Pro (doesn't matter if I run it at FHD or 4k) on chrome and brave. DWC 3.3.0

@Schild0r Just out of curiosity, why did you set your tpwmthrs, thigh, and tcoolthrs to 0? Shouldn't these values be set to a feed rate you'll use for printing?

@dc42 Any chance of having trigger events that can be used to execute macros immediately before power off and immediately after power on so we could unhook & rehook the toolboard automatically?

Here's my answer, but it's based on me only knowing one way to "read" a user input - the M291 command. Someone else might have a better method.

M291 posts a message and the user has two response options, "OK" and "Cancel". According to the M291 wiki page, if the users responds "OK", execution continues, but if they respond "Cancel", it "cancels the operation in progress".

I use the M291 in the following way:

global response = "Cancel" ;set the variable to the default Value. M291 P"To keep the default, select "Cancel" R"To change the default to the new value, select OK" S3 ; use the box title and the message to describe the two options. set global. response = "OK"

I put these lines in their own macro. If the user responds OK, the last line is executed and the global variable becomes the OK value. If they select Cancel, the macro exits without executing the last mine and the "Cancel value is used.

Someone may know better what "operation in progress" means and maybe this could be written in an if statement in the code.

A good FW wishlist item would be new M291 parameters to specify the words on the buttons, and have the response stored in the object model so you could read the response directly.

@rjenkinsgb ah I did not know that. I thought a OTG adapter would be something like a crossover ethernet cable. And with that one it doesn't matter which device sits on either end as long as there is a crossover (and even this isn't always necessary nowadays).

I will try it then with the otg Adapter on the phone and a standard micro b cable in the duet and report back.

EDIT: works

Now I only need to find wiring that fits my space constraints 😉

I would suggest that you should use a citrus oil based glue remover to detach the heater from the plate and replace the 3M adhesive with a high temp RTV silicone instead.

https://www.amazon.ca/Permatex-81878-Copper-Silicone-Gasket/dp/B01LZ7WZAT/ref=sr_1_39?keywords=rtv+silicone&qid=1637961534&sr=8-39

Or have you already used RTV silicone? As you do mention it for attaching the sensor.

I would attach the fuse to the heater pad itself.

@alankilian I think have my machine wired up properly, with all the metal parts being continuous with PE so the RCD would trip before you get electrocuted in case of a faulty insulation on the primary/AC side (components might get damaged but you wouldn't get hurt)
Also PE is continuous with the secondary/DC 0V so if I have a faulty insulation on the DC side of things, the PSUs would error out due to their short circuit protection.
The "mixed cable" actually was the idea of an electrical engineer (German guy with quite some experience) so I didn't think much of it...

My solution for now if anyone is interested

if state.status == "off" M81 elif state.status == "busy" ; state can't be idle because controller is busy running this macro M400 ; wait for all movement to stop if heat.heaters[1].current < fans[1].thermostatic.lowTemperature ; check for all tool based thermostatic fans to be off M80 else M291 R"Prohibited" P"PSU toggle is only allowed in standby or idle state! Wait for cooldown of hotend." else M291 R"Prohibited" P"PSU toggle is only allowed in standby or idle state!"

@schild0r, on Duet 3 MB6HC the un-calibrated errors can be quite large. Typically, TEMP0, TEMP1 and TEMP2 have significant error at low temperatures only, and different TEMP3 has significant error at high temperatures only.

Not directly. Only Duet3 hardware supports direct drive of dotstar or neopixel.

With Duet 2, you'd have to drive a pin that switched a controller that, in turn, drove the LEDs.