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

GoremanX

GoremanX

Works perfect... now I just need to move the camera off-system. Apparently while the Duet is printing (in SBC mode), the SPI bus on the attached pi gets too busy to handle the HQ camera feed and all the captured photos get messed up

Phaedrux

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

Apparently while the Duet is printing (in SBC mode), the SPI bus on the attached pi gets too busy to handle the HQ camera feed and all the captured photos get messed up

Interesting. Pi cam module?

GoremanX

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

Interesting. Pi cam module?

Yeah it's a genuine Raspberry Pi HQ camera. It works fine as long as the Duet isn't printing, but as soon as it starts printing, the photos end up with very random wide magenta bands all the way across and weird lines of noise. At the end of the print everything returns to normal. So I was gonna build a separate camera using the same HQ module and a Pi Zero W

Phaedrux

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

a separate camera using the same HQ module and a Pi Zero W

I do the same with MotionOS and it works quite well.

Greg_the_maker

Hello,

I'm a complete idiot when it comes to programming and I am finding the instructions a little vague. I feel I need some assistance please

The Installation is as follows.

Download.

Does this mean git clone? That's what I did anyway.

Rename to just execonmcode

Rename what? There are a load of .go files in the directory, do I rename one of those?

chmod etc

The rest of the install I can manage. I think.

Thank you for your time.

PCR

look some pots up. I made a video about this @Greg_the_maker

Greg_the_maker

What is it i need to be looking for?

PCR

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

made a little videos how to install it. Mainly for my own reference later

How to install and test

How to make it as a systemservice

Here you go

Greg_the_maker

thank you

wilriker

@Greg_the_maker Thanks for pointing that out. I will point the download instructions towards the GitHub Releases page. For there it should be clear what is meant by renaming also.

Greg_the_maker

Is tehre a way to get terminal messages displayed in the console?

For example I need to see a list of usb devices with lsusb, is it possible to have that list returned as an M117 message or similar?

wilriker

@Greg_the_maker In theory this is possible. Right now successful execution will discard the application output and error in execution results in an error being sent to DCS what failed (e.g. file not found but still not the output of the application).

I could add that but I am not sure how it will deal with line-breaks.

Greg_the_maker

@wilriker Ahh ok. was just a thought. would be a nice feature to have though

wilriker

@Greg_the_maker I have to correct myself. In case of an error it will indeed return the output of stdout and stderr combined as an error message. But since we are in short-lived world things can be changed quickly and thus:

Release v5.1.2

This release adds a new flag -returnOutput to be able to send the collected output of a successful run back to DCS. Prior this was only the case if the execution of the command failed.
Note that this cannot be combined with -execAsync.

Download

As usual get it from GitHub Releases page.

Greg_the_maker

@wilriker Fantastic! Works exactly as desired. Have my upvote!

oozeBot

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

wilriker

@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.

oozeBot

@wilriker Thanks. So the return is echo'ed in DWC, correct? Could the return value be evaluated within conditional gCode?

garethky

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

@wilriker Thanks. So the return is echo'ed in DWC, correct? Could the return value be evaluated within conditional gCode?

I was thinking about this today. Currently there are no variables so there is nothing to write the result back to. (there is a result int from the last code but it can't contain other data types) I think we might have to wait for variables and then we could write the value back to a global.

When that happens... it should be possible to set up an MCode that stores and retrieves values from a file on the SD card. So we could do what M500 does but with key/value semantics of M409:

M7500 K"some.key" V"The value"
M7500 K"some.other.key" V0.05

and then get them back in a global with:

M7500 K"some.key"
echo {global.M7500_value}    ; or whatever you want to name it!

and stored on disk as JSON:

"some": {
    "key": "The Value"
    "other": {
        "key": 0.05
    }
}