The challenge was in serializing the data from robodk. The ARCS software uses something called python "pickling" to effectively pack and unpack data from a given program without losing its structure. I assume Chris did this so you can call programs from inside other programs (great function!). I just had to add a pickling element to robodk's example processor so ARCS can actually read a file and then adjust all the text output so it matches the ARCS format. I'll put it on github once I've had time to refined things more and add some comments.

That sounds reasonable. I think managing the flow of pellets to the extruder head while keeping everything light enough for the arm might be a little tricky but I think its totally possible. Have you built an arm yet? On the RoboDK end simulation/ adding a tool to the arm works well but exporting an actual toolpath without collisions/singularities is still pretty challenging. If you feel like could build out some more functionality in RoboDK it would be great to work together. I have basic functionality in that I can send J and L moves with fixed speeds but some work needs to be done establishing a starting/homing routine so robodk sends the machine to the right place. It may actually be easier to use COMPAS Fab in GH/python from ETH Zurich but building out the robot's ROS profile is a little beyond me right now.

Hi Austen, I've made an improved post processor for RoboDK that deals with serializing the output so it can be opened by ARCS/the AR2 platform. Happy to share and talk about it. I think I'm close to something with real toolpathing capability. What are you hoping to do?

Hi @Chris Annin I've now done some work on a robodk post for the AR3. I am outputting the properly formatted text (I think...the image of text is of the path in the video), but I'm unsure how to package it for loading into the AR2/ARCS program. When I try the file just gets overwritten. Any suggestions? I have the simulation in Robodk working through Rhino/Grasshopper for more complex toolpaths which is kind of fun but I can't seem to get the code into the interface to send to the machine.

Turns out my display resolution was such that the AR2 interface was cut off at the bottom.... I now see the manual entry function! Will update on this grasshopper/python input shortly.

Resolved. Looks like I pinched the endstop a little too much with the set screws that secured it, leading to inconsistent behavior. Thanks Chris for calling that out as a potential issue in the manual. Replaced the endstop, reset arduino sketch motor directions and UI settings to default and now it works. All systems are go!