The kind of input for geometry they're expecting is pretty basic CAD shapes.
Biesse controllers are pretty strange coming from a G Code world. It's probably too late on a Friday night to be continuing to look into this, but from what I can find it looks like most 3rd party posts for BiesseWorks put all the geometry into a ROUT macro. Let me know if you need a guniea pig to test anything. Thanks so much for your work on creating this post! I've tried digging into the post config myself but I have to admit I'm a little out of my depth there.
I've also attached a page of the BiesseWorks manual that helps explain the logic of the Z levels. "Outside Cut Corrected" is a modified CIX that I exported out of BiesseWorks after copying the geometry to a "ROUT" macro instead. "Outside Cut" is the original CIX generated by your post. I've linked below to a Google Drive folder with a few files. EnRoute exports CIX files with the geometry inside of a ROUT macro. I have also found out the same code that gives the processor a hard time while in a "GEO" macro does just fine in a "ROUT" macro instead. Notice that the plunge move is included in the line segment as the Z start value of the line segment. What BiesseWorks is expecting, however, is something like this: The current post writes each step in sequence (keep in mind that to the best of my knowledge, the X and Y values here are absolute, and the Z values are relative to the previous point): Say for example we want to start at 0,0,-10, plunge to 0,0,5, and then move to 0,20,5. Here's the biggest thing I've learned: when defining points within the "GEO" macro, BiesseWorks doesn't accept sequential points that have the same X and Y values but a differing Z value. Getting HSM to be able to output code to our Biesses would be incredible. If you have any questions or want me to test something out on our machines let me know. Hopefully you'll find what I've learned useful. I've been testing this post for the past few days and I haven't been super successful getting it to work, but I've learned a ton about what BiesseWorks is expecting to get from a CIX. Not the easiest machines to understand coming from a G code world. I've worked in a shop that uses Biesse machine for nearly a year and I'm still learning the quirks of their crazy programming.