UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
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
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.
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
Recommended Posts
nallath 1,123
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
Link to post
Share on other sites
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 by tmcolbyLink to post
Share on other sites