More MasterCAM setup sheet data variables?

[The_Machine]

I plan on using MCfSW.

In HSMWorks during runtime, the setup sheet program would pull every Custom Property assigned to the solidworks file which the toolpaths are applied to which made it very easy to store and propagate revision information, stock material information, grain direction, etc to the setup sheet and the setup sheet was ready to go. 

I'm looking to do the same with MasterCAM (particularly MCfSW) so that I can incorporate it into our workflow. It's not immediately clear that I will be able to do that or how I would go about it. Storing this program revision and stock material and size data into the setup sheet dialog would be acceptable as an alternative to storing it in the Solidworks Custom Properties, but there aren't enough fields to accomplish this. (Note1, Note2, Note3) The Solidworks Custom Properties method would be preferred because it has a Custom Property Tab builder that allows the building of drop down boxes, radio boxes, etc to speed up the data entry process.

Any thoughts?

I am familiar with C# so that's not out of the question. I just don't understand how the information is pushed from the XML file and then to active reports. If I have to create a custom addin or macro that can generate a custom xml file that could work, but I don't know how to trigger active reports. Has anyone done this already? A starting point would be helpful.

[The_Machine]

I think I found it in the help. Going to export it and report back.

 

How do I pull information such as nc file name (NCFILE-SHORT) into the main setup sheet without creating a subreport? I see that in the xml file referenced by the report document (SSM.xml) NCFILE-SHORT is encapsulated under NCFILE tag. Can I just simply move it? Gonna do some trial and error but I suspect a lot of "Error"

[JParis]

Your reseller has a tutorial or you can download on the official Mastercam forum

https://users.mastercam.com/Default.aspx?siteId=13&ReturnUrl=%2FForum11.aspx

[The_Machine]

Using additional values described above worked but the data you enter in there isn't saved the next time you run it.  It would be an awful place to store program revision notes.

 

 

[The_Machine]

Are you implying that I shouldn't be asking for help here? I see that there isn't a forum category for support or help. 

I figured out how to reference a data field that's contained in another tag. 

The example .XML file (SSM.xml) contains root fields, and "sub" fields. NCFILE-SHORT for example is stored under the NCFILE tag. To access these fields without directly referencing the "recordset pattern" (EX: //NCFILE) you just simple format your DataField variable like this: "NCFILE/NCFILE-SHORT"

[crazy^millman]

8 minutes ago, The_Machine said:

Are you implying that I shouldn't be asking for help here? I see that there isn't a forum category for support or help. 

I figured out how to reference a data field that's contained in another tag. 

The example .XML file (SSM.xml) contains root fields, and "sub" fields. NCFILE-SHORT for example is stored under the NCFILE tag. To access these fields without directly referencing the "recordset pattern" (EX: //NCFILE) you just simple format your DataField variable like this: "NCFILE/NCFILE-SHORT"

No he was just trying to help you get documentation from the correct places is all.