@fatalis22 said in Set z endstop as a trigger.:

The truth is that this is the best, the ease and speed of making a home with the endstop along with the compensation and the mapping of the sensor. 😁

Great! My first convert!

😉

Frederick

@engikeneer Thank you a lot !

I guess it's solved by now since I didn't know that it will get solved basically by making "PID autotune" since as I was used to Marlin there it is a bit different.

Thank you a lot once more and take care! 🙂

@paulhew Thanks, but i have seen that.
But i could not found the triggers in the OM!

Wow I was approaching this totally the wrong way...

All I have to do, as per your recommandations, is to set in relative mode, and add 100 to Z...

I was WAYYYYYYY overthinking this...

Thanks guys

In SBC mode too from 3.3beta3.

@t3p3tony
can I also send variables with M118 or 'strings-only'?

Just a sidenote: I read about SD-card stuff yesterday and I thought 'all' relevant M-codes are M20-M32.
Now I see M929 is also related to SD-card, but there was no_word about it in the other M-codes. (playing hide and seek?)
OTOH, there are M33-M35 currently not used by RRF. Why not put the M929 function there?

@sinned6915 yes, you do. 3.2.2 for it. The object model also changes somewhat between 3.1.1 and 3.2.2 so I suggest upgrading anyway

That's correct, the M98 P parameter is not included, on the grounds that it's not normally of interest because you know what file you are running.

In the meantime I tested the macros a bit more and had to adjust the math. Now every tool has it's own ooze-countdown.
ooze_compensation.txt

It also looks like, there's no math allowed in 'echo {expression}'?
Also I have to add a local variable and calculate things before using the result in 'G1 E{expression}'

@sinned6915 3.2 I believe

@dc42 said in Macro to call heaight map based on bed temp:

As an alternative to using M116 to wait for the temperature to settle and then testing heat.heaters[0].current, you could test heat.heaters[0].active which will be the commanded temperature.

That is certainly true in the case of the Macro to load the height naps and it would mean you don't have to worry about whether M116 releases before reaching the target temperature.
ergo. It's a cleaner implementation using .active
I just figured if you get that much bed variation to need this in the first place then you're going to have to wait sometime.

@owend
If I had to integrate a Daemon.g into a very timing-related program such as RRF, I'd not run the whole Daemon at once, but would squeeze it between my already running program line by line. (or the shortest possible code snipped)
That way you can set a waiting time with G4 S20 in Daemon.g, while the real print-routine goes on.

That would work well, unless there is a line that calls another sub-program in a subprogram. M190 P0 R{heat.heaters[0].active -1} is such a line. It calls the 'math' routine with (-1) while being in the subroutine of M190.

It's just wild guessing, but maybe there is a limitted level of subroutines for Daemon.g?

@o_lampe said in Do variables need to be freed?:

@owend
👍
Then the 12864 LCD only eats Duet2 memory, because it's not natively supported, as it is by Maestro?

The 12864 LCD eats memory on any Duet now, however the Maestro has more free memory available to start with.

@roken22 maybe use a magnet on each syringe and an hall sensor on the "extruder". That will allow also for adusting the switching distance without mechanical parts.

@mendelevium
In my opinion you can try use M400 or M116 between the temp settings. Although M109 already waits for temp to be reached. It might not differ between T0 and T1 (just guessing)

@Phaedrux thank you very much

My Toolchange script now Cools down
the Old tool before Selecting the New One (tpre, tpost)

the tpost code:

if heat.heaters[1].current > 100 && move.axes[0].homed = true G1 X-5 F15000 while heat.heaters[1].current <= heat.heaters[1].active G1 X-13 F1000 G4 S2 G1 X-5 if heat.heaters[1].current >= heat.heaters[1].active break G1 X-13 F1000 G4 S2 G1 X-5 G1 X-13 G4 S2 G1 X-5 G1 X-13 G4 S2 G1 X-5 G1 X-13 G4 S2 G1 X-5 G1 X-13 G4 S2 G1 X-5 M116 G1 X-13 G4 S2 G1 X-5

is there a Variable that equals to M116 => i want to wipe till the new tool is ready,
but i found no boolean in the object browser for it.

on the Paneldue i sometimes get the Message
M4 command is not supported in machine mode FFF.

But i have no M4 Command in it?!

I'm glad I started learning IDEX printing on a fun project where it doesn't matter when things go wrong.
Running a testfile I paused the print and changed tool. The tfree macro worked as expected, but after hitting resume both axes were moving for a moment. I guess the print queue wasn't empty?
OTOH, when I send T0 or T1 without pausing, everything works. I know there is a M400 wait until printbuffer clear, but where do I put it?

@dc42
I used the configurator tool to generate my config.g. When I defined the tools without fan the configurator adds a "F-1" to M563.
But RRF3.3b2 doesn't accept that and throws an error, when running M98 "Pconfig.g".
Something like "expecting a numeric expression after 'F' param"

Maybe I' m the first noticing that, otherwise ignore it...

; Tools M563 P0 S"X-Axis" F-1 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"U-Axis" F-1 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"XU-Copy" F-1 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C

@OwenD said in Reading Input Pin States for Conditional GCode:

A persons name must be represented with a capital letter.

But if case sensitive names had been the norm from the far past that "rule" you mention would not exist.

I reject your rejection. 😉

Frederick

@hmortensen said in Cannot access gpin in code:

Have you tried copying the value from the object browser?
In the screenshot it seems to be capital letter I in gpIn and your echo command is all lower case.

Good catch - you must have sharp eyes.

For some reason things are case-sensitive and the lower case letter was the problem.

Thanks much.

Frederick