Hi Nadeem,

Please consider the scenario that I choose to open Optinest via Polyboard, right at this stage we now close Optinest.
How do I reopen Optinest exactly at this stage with all the panels sorted out as per different materials used and their properties are in place. (without going back to Polyboard)

In my mind, your only option here is to make sure that you select File>Save in OptiNest to save this data. The only other way to properly re-open this is to export again through PolyBoard. That is why I would recommend OptiNest 3, as this is no longer the limitation with greater importation options and an automatic .nst file saved when you export from PolyBoard.

Finally, how will Optinest 3 help me out here, that will be better than version 2 that we use today?

OptiNest 3 has further improvements such as:

• .nst native file format for OptiNest from PolyBoard
• Multi-material nesting
• CSV/DXF component import (for manually changing dxf’s after PolyBoard export)
• Improved labelling options and capabilities
• G-Code export (for appropriate machines, with a custom made PP)
• Material library sharing with PolyBoard

Best regards, Isaac

Hello Nadeem,

Thanks for the detail, that helps a lot. Let me answer the command-line question directly and also point you to the route that will save you the most trouble.

First, an important clarification on where the data lives. When PolyBoard exports through an OptiNest post-processor, the material, edge treatment, grain, toolings and label/reference fields are all carried inside the layered DXF files and through to OptiNest. OptiNest reads that information according to its DXF import settings under Tools > Options > DXF parts import. So the “metadata” you are re-entering by hand is normally pulled straight from the DXFs, provided those import options are configured to match PolyBoard’s layer names.

The command line itself. I am no expert on working with command lines, although this is my understanding on the matter. You would need to test this alongside your set-up. OptiNest 2 doesn’t take a report file as a direct argument (so passing pp_report.txt on its own won’t drive the import, that file is a human-readable report). It uses the documented switches. To reload your existing PolyBoard DXFs, per material folder, the form is:

OptiNest.exe /Piece:”ImportDxf=C:\PolyBoard\<Job>\<MaterialFolder>\*.dxf” /Piece:Mobility=180,0

Notes on that line:
– Use the full path to your actual OptiNest executable.
– The quotes around “ImportDxf=…” and the | separator for multiple files are required; the * wildcard works, so pointing at one material sub-folder pulls every part in it.
– Importing one material folder at a time keeps the parts sorted by material, matching PolyBoard’s folder structure.
– /Piece:Mobility=<rotation>,<reversal>: rotation 0 = none, 90, 180, or any other value = all rotations; reversal 0 = not allowed, any other value = the part may be reversed during nesting. Add /Stock=”Material Name” /c to define/create the stock, /Optimize to nest, and /Result:ExportDxf=<folder> to write the nested DXFs.

My recommendation:

My honest recommendation is to update to OptiNest 3. OptiNest 3 will allow you to improve this process through one of the following two methods:

1. Save you OptiNest files from the PolyBoard PP as a single .nst file. This is a native OptiNest file that will contain all of your DXF components and their data, making this easier to manage rather then needing to import all pieces and data seperately.

2. If you need to continue using separate DXF components, OptiNest 3 also has the ability to import both DXF’s and a CSV at the same time. This means that each of your DXF’s will be imported, and additional data will be reference from your PolyBoard PP report.

All of this is explained in further detail through the following link:

OptiNest 3 information

Regards, Isaac

Nadeem, 

I have sent you an email with additional information. If you have any further questions, please ask them via this forum thread.

Regards, Isaac