[DSF Extension] Exec On MCode (was: Shutdown SBC)

oozeBot

@wilriker - just adding in that I'm experiencing the same thing on 3.3rc2.. I was able to capture it from a console when running below.

Do you know if the issue has been found and is being corrected in 3.3rc3? Any interim builds out there floating around I could download to get past this issue?

Thanks

Phaedrux

@oozebot said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

Any interim builds out there floating around I could download to get past this issue?

You could test with this build but be aware there are other potential issues.

https://www.dropbox.com/sh/1bblsmpe8m6kb0p/AAD4J_9-uEEnr-Rvh3OjlXyZa?dl=0

wilriker

@CrazyCreator @oozeBot I can confirm that this bug will be fixed with DSF v3.3-rc3.

wilriker

@oozebot said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

Any interim builds out there floating around I could download to get past this issue?

There are no interim builds of DSF available. You would have to build it yourself from sources. What @Phaedrux posted was "only" preliminary builds of RRF 3.3-rc3.

CrazyCreator

With the new release 3.3RC3 it works

Now I have to put the code for power off the shelly-pm in my shutdownsbc.service

next adventure for me

CrazyCreator

@crazycreator

here I am ... can someone help me again?

After the update, execonmode now works wonderfully.

But unfortunately I can't start the web call to switch the shelly off.

Unfortunately i can't really work with the console. So it would be nice if someone could take me by the hand and show me the right way so that I know what I can try or test where.

So I want to achieve the following:

when a certain MCode is called, my Shelly 1PM should be switched off.
This would work in my case with the following command:
http://192.168.1.47/relay/0?turn=off

If I enter this line in a browser (of course only at home in my own network) the Shelly switches off.

My goal is now to achieve this via Execonmcode.

please help me

oozeBot

@crazycreator this should probably be it’s own thread.. but you’ll need to code a shell script to accomplish this. Here is something similar I did for Wemo. Maybe you can take some hints from it.

https://forum.duet3d.com/topic/18989/script-to-control-wemos-from-gcode-using-dsf

CrazyCreator

@oozebot
I answered you there once

CthulhuLabs

Is execonmcode blocking? Meaning if I make an M1999 Mcode which executes a command that takes a moment will my Duet pause till the script is finished?

EDIT: Found my own answer.

Phaedrux

@cthulhulabs said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

EDIT: Found my own answer.

What's the answer?

wilriker

@phaedrux said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

What's the answer?

The answer is that it depends on whether or not you use the -execAsync flag when starting execonmcode. If you do it won't block and if you omit it it will wait until the command has finished.

oozeBot

@wilriker said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

@oozeBot said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

@wilriker Could you please provide a simple example of using the -returnOutput flag? Thanks

Simple example:
execonmode -mCode 7777 -command "whoami" -returnOutput
will not just confirm successful completion of the command but as part of this return the output of whoami (that returns the user execonmcode is started as, so probably root) so you can see it e.g. in DWC.

Digging this back up.. Does anyone know if it is possible to assign the -returnOutput to a variable?

T3P3Tony

@wilriker @Falcounet

Just replying here to point to the python version:
https://forum.duet3d.com/topic/29783/execonmcode-v0-1