![]() ![]() Like all things when you start digging you find oddities, like where is the active extruder tag, token or place name whatever it's called, or how can you control a Robox with the state of that Custom Command panel, and the Machine Control Interface, which frankly is a mess, so as bad as some of the UI details are in AutoMaker, there are others that are worse.Īssuming the gcode is OK, the best way for most of you use this software is to save your files to disk and use the Automaker Preferences tab, and drop files into the Transfer and Execute Code box, and at least you can stop everything and use the normal AutoMaker macros to Abort etc. I've had email discussions about a few things, and they don't seem to be on the same wavelength, re Robox firmware requirements, and what it expects to see, and they are developing a Dual Material version, because they have a Robox in their development office. ![]() There is one at layer 2, but I've got around it, with a post process, which isn't ideal. ![]() They will say not, but you have to look at the gcode generated, compare it to what a Robox expects and go over it for bugs. ![]() As far as I know this is the same as the one we tested recently.this is 3rd party software so damage resulting from it’s use to produce gcode to run on Robox must be at your own and others, there is definitely some risk with this too. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |