command_util.py

[tmcolby 2]

Is there any sort of documentation on this?  Besides the minimal information that lives in the forums.

 

I would rather not spend my time sifting through the source code to determine what I can and cannot do with the utility.  I am particularly interested in how to use the "exec" command.  Also, a different but similar issue, the swagger docs do not seem to be up to date.  For example printer/led is documented, but not printer/led/brightness.  

 

Thanks for any help here..

 

for some additional context:  I do now see if I first "select" a mode, and then do "exec self." and hit tab, I can see a list of exposed functions.

 

I am interested in the printer's self.startProcedure method.  It takes "key" and "parameters" as arguments.

 

Currently, through the API, there is no way to set the loaded material.  I can set it using the command_util.py however.  I am building a smart dry box for my filament.  Since my filament will not be loaded on the stock reel holder where the NFC antenna is, I wanted to hack my UM3 by programatically assigning the material that will be loaded.  I also want to programatically initiate the load, unload, and change material wizards (I am pretty sure this can be done with exec printer self.startProcedure('SOME_PROCEDURE"..... ) but I need help with what the proper 'key' and 'parameters' are.

 

I found a list of procedures defined in the um3.json file in griffin/machines/ folder.

[nallath 1,118]

comand_util.py is a debug script, so mostly meant for our convenience. This also means that it has a horrible outward facing interface, which assumes that you know how the internal system actually works.

 

That being said; The internal system uses a pretty complicated system of procedures. As things can and will go wrong, it can occasionally be convenient to trigger specific procedures (or parts there of). That's what the startProcedure does.

 

All that being said; You're right on account of having to trigger those procedures to do what you want. If you want a full list of the procedures, you can find those on the machine, located at /usr/share/griffin/griffin/machines/um3.json

 

[tmcolby 2]

Thanks nallath.

Would you, or one of your team members, be willing to share what the proper arguments are needed for a couple of the procedures?  I want to run "LOAD | CHANGE | SELECT_MATERIAL_WIZARD" for instance.  What does the 'parameters' look like to fire off these procedures?  If you cant share, I will keep poking around and figure it out.

 

I would think it would be safe enough to expose any of the "wizard" procedures on the API.  If you can initiate something from the front panel, you should be able to initiate the same from  the API.  I would love to see this knitted into the API.  Happy to contribute too.

Edited September 11, 2018 by tmcolby

[tmcolby 2]

looks like this did the trick...

exec self.startProcedure("LOAD_MATERIAL_WIZARD", parameters={"wizard_type":"load"})

 

Edited September 11, 2018 by tmcolby