Posts made by moosi

Hi,
I just smoked my 6HC v1.01 by accidentally connecting it to 48V.
Is there any experience of which components were damaged in the process? If only a few parts of the PWM buck converter are fried, I would try to replace them.
I've already ordered a new 1.02 board, but if I can recover the old one, it wouldn't be too bad.
I would really appreciate some tips.

@OwenD
thanks so much.
It is exactly what I was looking for.

Thanks @Phaedrux
maybe this place is better

Hi there,

I´m using G38.2 to probe toward a workpiece.
In the case of an error the message is displayed.
How can I react to an error? In my case I want to stop the program, and show a custom message.
Maybe I want to retry the probing move, but in the end I need to abort the gcode.
Is there a way with conditional gcode or so?

thanks for your help.

@dc42
thanks a lot. I will do so.

@dc42

It´s:
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.4-rc1
Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.0rc1 (2022-02-09)

I´m going to check the "slicer" time.

@dc42
thanks a lot for your reply.
Yes it does support time, but DWC is only showing percentage. M73 has apparently no impact on DWCs calculations. AFAIK it uses filament and byte positions as fallback but no M73.

Do I miss something?

Hi,
I would like to set the percentage via Gcode. I know M73 but according to the wiki it is not supported by RRF.
I could live with either the percentage or remaining time, but I have to set in the code.

Are there any ways of doing this?

thanks for your help

Hi,
can DWC show the remaining print time in minutes?

thanks
Moosi

Hi,
I´m want to communicate between duet3 and an arduino.
So far I can send messages to the arduino (M118 ) and receive them when sent via the serial port.

What I want to do now is to wait for a specific response after sending a message.
I created a vue button (v-btn) and used this code for the click event below.
What is the right way to do it?

async click() {
      if (!this.waitingForCode) {
        this.waitingForCode = true;
        try {
          await this.sendCode(`M118 P2 S"MyMessageToArduino" L0`);
        } catch (e) {
          console.log(e);
        }
	// How do I wait for a message sent back from the arduino? Let´s say I want to wait for G555 or any other message...
        this.waitingForCode = false;
      }
    },

thanks for your help
Moosi

@dc42
Ahh, that is great, thank you so much!

@achrn thanks so much!
I did´t realize that it works on .g files as well.

But the "G500.1.g" idea is still there.
Any thoughts on this. Maybe it is just me finding this helpful...

Hi,
I know we can create a new GCode command by putting a file like "G500.g" in the system directory.
This works like a charm, but could be extended a little bit, in my opinion.

It would be great, if we could use a second dot like "G500.1.g" because there is already the concept in the predefined Gcodes like "G59.3". That way we could define "G59.4" if there is a need to do so. Of course one needs to be careful if future updates collide with such changes, but this is always the case.

The second thing would be to pass parameters to this self defined commands.
let´s say I would write "G500.1 P1 S3 X100"
I could use the parameters inside the .g file like {P}, or {X} maybe with a "@" connotation like in batch files or so.

I would love it!

best wishes
Moosi

@dc42

Thanks, that was fast
It is working now. Not exactly as expected, but I think it is my fault and I need to dive deeper into the configs.

Hi,
I´m just playing around with the new version.
One thing I stmbled across is M558
How do I set up a second probe?

I tried:
M558 K1 P5 C"!e0stop" H5 F120 T300
M585 Z100 F600 P1 S0

but I get the error:
"M558 invalid z probe index"

I can change K1 and P1 to 0 and it works, so there might be a problem with additional probes?

thanks
Moosi