@dc42 @droftarts Thank you again very much! Our device had a current draw of 100 mA only, and based on your advices we were now able to start using OUT 4-6 for our 24V devices. What a great feeling, thank you for excellent support!
Best posts made by HeidiH
-
RE: How to read state of servo/output/input pins
Latest posts made by HeidiH
-
RE: Possibility to abort self-written macro
@droftarts Hi Ian, yes, I understand completely and definitely want to do as it is easier for you. And thank you, now I got the idea that I just copy-paste inside those marks, simple :). Now the code is as it is as I have used it with Duet.
-
RE: Possibility to abort self-written macro
@droftarts Hi, thanks, I modified my code now. I don't know if those > and >> were necessary to see the indentations, but I added them anyway.
-
RE: Possibility to abort self-written macro
@droftarts Hi, I have been testing the above ideas further using a macro, in which I have a repeatable beep-sound, which I should be possible to end if the stop macro is activated.
The code, consisting of 5 beep sounds, is as written below:
if !exists(global.abortMacro) global abortMacro = false ; var Toisto = 0 ;loop while var.Toisto < 5 echo global.abortMacro if global.abortMacro = false echo global.abortMacro M300 G4 S2 set var.Toisto = var.Toisto +1 ;iterations echo var.Toisto echo global.abortMacro if global.abortMacro = true abort "Aborted"
Then, I have Abort_activation macro, in which I change the global variable abortMacro to true:
set global.abortMacro = true
However, it seems that my Abort_activation macro does not have an effect on the ongoing beep-sound macro, when it is running. Like the beep-sound macro would check the state of the abortMacro global variable? However, my Abort_Activation macro works when used without the running beep-sound macro, as I have seen from the console.
Would I need to have some kind of break in my while loop to be able to see the changes in the global variable state during the repeatable process of beep sounds?
BR; Heidi
-
RE: Possibility to abort self-written macro
@droftarts Thank you for your edit. I tested my files and the macro file, which I am running and am willing to abort, does still not respond to another macro (called Abort X), in which I activate the global variable of the configuration file with global.abortX=true. I don't get any warnings, still. As a result, the macro is still running.
Have I understood correctly that it is possible to abort the running macro (called X), just by including inside of it the commands
if global.abortXabort"0:macros/X"
BR; Heidi
-
RE: Possibility to abort self-written macro
@dc42
Please, find below the above macros with indentations:In config.g
global abortX=false
In the macro file, named X, I should be able to abort when needed:
set global.abortX=false M42 P6 S255 ; output is generated G4 S10 if global.abortX abort"0:macros/X"
In the Abort X-macro activation macro I have:
set global.abortX=true
-
RE: Possibility to abort self-written macro
@dc42 Thank you for your advise and my apologies for the delayed response.
I need to allow canceling a few different macros, which I could name as X, Y, and Z. I tested this with single, but for some reason didn't get the abort to work but the macro, which I was intended to abort with another macro but it the executed macro did not stop working. Here is how I modified your above code:
In config.g
global abortX=falseIn the macro, which I should be able to abort when needed:
set global.abortX=false
M42 P6 S255 ; output is generated
if global.abortX
abort"0:macros/X"In the abort macro I have:
set global.abortX=trueWhy does not my abort macro affect the macro that I would like to abort?
-
RE: Pt100 Offset adjustment with M308 command
@dc42 @T3P3Tony @Phaedrux Thank you all for your help.
I had tried to modify the formula that was given for the M308, which Phaedrux instructed but I didn't understand it sufficiently to get it working. However, based on instructions on T3P3Tony I now got the point better and am now able to make the required modifications.
I would like to double check, that dc42 meant that my 3.5.0-rc.3 firmware version is not the latest release? I checked the version from https://github.com/Duet3D/RepRapFirmware/releases and it seems that this should be the latest?
-
Pt100 Offset adjustment with M308 command
Hi,
I would have a question related to the offset value of my Pt100 sensors, attached on Duet 3 MB6HC 3.5.0-rc.3 firmware. I have +1C deg offset value in my sensor from which I would like to get rid off. Also, I have some small noise, which increases at high temperatures to approx. 1C variance between the target.
With the gcode instructions it is said that I should add Uu, Vv. I assume that I should place U-1 (for offset removal), but this didn't make any change to my temperature reading. Also, does this V (slope adjustment parameter) affect the noise?
I did not find an example on how to write the M308 command with those Uu and Vv, so it would be great to have instruction on that.
Br, Heidi
-
RE: How to read state of servo/output/input pins
@dc42 Yes, great. it is that. We solved the issue by using a semiconductor relay allowing to provide external trigger for our Duet 3 board input, in which we chose the active-to-inactive stage change. Thanks again!
-
Possibility to abort self-written macro
Hi,
I would be great to have a chance to abort a macro, which I have written for Duet 3 MB6HC (firmware 3.5.0-rc.3). How could I do that?
BR, Heidi