@col_clucks said in Duet 3 mini 5+ unresponsive after axis crashed:

The status LED flashes slowly in all modes.

See https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Wiring#Section_LED_indications

By slowly do you mean "Flashing steadily, about half a second off and half a second on" (normal operation), or "Fading from bright to dim and then back again" (USB bootloader activated)?

Ian

@sindarius

Exactly, as it is now a restart is needed.

@charlesmc said in Confused on G-code header:

@fcwilt That's a good suggestion - will implement!

Just remember that each slicer generates code based on the "G-code Flavor" setting and other settingsundefined such as extruder/bed temps.

On some slicers you can complete prevent any code from being generated, on others you can control it to some degree and on others you can use a feature which allows you to make "automatic edits" to the generated code.

And each slicer may generate code before and after the M98 call to your code.

If you ever try this approach and have problem just let me know.

Frederick

@engikeneer Thanks

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt - heres a solution for Super Slicer ...

https://github.com/supermerill/SuperSlicer/issues/425#issuecomment-913036749

found the setting [ if it were a snake it have bit me ]

superslicersolution.png

I like that. Every slicer ought to have that option rather than having to figure which other settings will stop the generation of this or that bit of code.

Good work.

Frederick

Apparently you didn't read the NOTES BEFORE YOU START section.

Check that you have downloaded the correct firmware before installing it. See section below regarding which files are needed for each board.

You'd want this one by the way

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/DuetMaestroFirmware.bin

And you'll also want to update the DWC files in the /www folder on the SD card since you're doing this manually.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/DuetWebControl-SD.zip

Extract that zip file into the /www folder replacing the contents that are already there.

Once you have updated and connected to DWC, you should verify that the firmware and DWC were updated.

Then to ensure you have all the correct files in place you should upload this zip file to the system tab. This would be the normal way to update when you still have a network connection to DWC active.

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

@phaedrux

Thank you very much !!
Did update paneldue firmwere , looks that it work perfect,
THANKS,

@signpostman it literally is as simple as adding S2 to the end of your M671 line (replacing the S1 if you have it). You'll have probably put your M671 command in your config.g file, but might be in your bed.g file instead as @tecno suggests

looks like it actually solved my issue, thank you !

Good morning,

@PHAEDRUX yes I have looked at that link, but I can't quite understand how the tagging is done, nor do I know how to enable it from DWC, I was trying to do it with simple examples to see if I was able to understand how they work.

@dc42, if I am using S3D, using the processes as labelling would be useful for what I want to do now, do you have any practical example, so I can analyse it and understand it?

@MARTINNYHC if you have any example I would like to see it.

Best regards, and thanks

@dc42 Thanks! Commenting M203 really did solve the issue. I thought I did something wrong with my sensorless homing setup.

@aitor said in Question on global variables:

How much free memory is recommended for a good performance?

When "never used RAM" runs out, the machine is in danger of resetting with an Out Of Memory fault if you do something that needs more RAM. So aim to have a few kb spare after you have done a print. Performance is not affected by the amount of free RAM as long as it hasn't run out.

@flobler thanks for confirming this. I'm sorry it took a while to resolve.

Thanks everyone for your input!
I think I got it.
I removed the Z-Probe pin, and it now works completely.
4734c54a-89d9-47e9-8183-dace09afcd7c-image.png

@dc42 thank you I got it working. For those who might come later in this post here is my config for reference :

M584 X0.0 Y0.1 Z0.2 A0.3 C0.4 E0.5 U1.0 ; set drive mapping M669 K0 X1:0:0:0:0:0 Y0:1:0:0:0:0 Z0:0:1:0:0:0 ; set kinematics parameters M669 K0 U0:0:0:1:0:0 A0:0:0:0:1:0 C0:0:0:0:-1:1 ; set kinematics parameters

@leckietech

How many more are you planning on adding? You could use the daughterboard expansions to add up to 4 more PT100/k type thermocouples and should be a lot easier than creating the network you’re describing.

I did power measurement and you are right about this, the power consumption reduced when regulating the temperature so it's an acceptable value. Thanks !

@dc42 oh duh! It totally slipped my mind. Thank you!

@phaedrux I started adding items back one at a time. It looks like the PT1000 (thermistor and probe) and the BLTouch no longer work but everything else does. My guess is that one of the two could be the cause of the issue that I was having.
Thanks for the help everyone!