Setup Sheet Data gathering

[Eskondedo]

Hello all,

   I am currently trying to build our setup sheets in Powermill so we can do away with having to cut/paste into Excel and hand type alot of information into a workbook.  I am rather new to HTML formatting but I seem to have a decent handle on it using the provided documentation and the forums.  Somethings I'm not seeing however is how to gather data from fields NOT showing on the documents.

   For example I would like the User defined settings to populate the setup sheets.  Here I can setup multiple material types, designer names, etc...  But I cannot seem to find anything on how this can be done.  Another thing I would like to populate is the Machine Tool information into the setup sheets.  I have a half-wit workaround as of now but the command to select the machine tool in the individual NCProgram shows up as

EDIT PAR "entity('ncprogram','ncprogramname').ParametersAutoUpdate" 0 EDIT PAR"entity('ncprogram','ncprogramname').MachineTool" "KernMicroGraphite"

I cannot for the life of me work around the ncprograme name being specific.  I tried using ; but no good.

Another thing is my company requires certain logos and text on every paper we produce and the image files im referencing only show up as black boxes.  It seems I've scoured the web for HTML reference material but without the ${______} format, images just will not produce. I've tried the <img src=variant, ive tried saving images directly into where the sheets are being created and to no avail.

I know this is alot to ask in one thread but any help woud be appreciated.  Anything we can do to streamline means less time fat fingering paperwork, we all know that time =$

Thanks,

[danmic7JH66]

I was experimenting with setupsheets like you and I found it was just easier to export out the information I wanted to track on the setup sheet with a macro and then import it into excel with another macro. No html required just a little Visual Basic knowledge. That's at least what I would suggest and I can post some examples if you are interested in going that route.

[LasseFred]

I'm working on a macro that does.
But it's not finished you can get what I have.

[Eskondedo]

Unfortunately I cannot download things like the .rar file you attached ( security protocols and all ) Can you copy paste it here so I can try it that way?

[TK.421]

is your service subscription? i've been playing around with the shared views instead of setup sheets. I like them a lot. still waiting for a couple bugs to be fixed in the app, but you can see everything in a web browser. kind of neat if you want to push your company to "go green" and "do their part" to "save the environment" so you guys aren't "wasting paper" and "using all the printer ink"

[Eskondedo]

Because of our security we cannot go subscription right now, our CAD policys prevent our boxes from connecting to the internet. I dont know about the shared views but im trying to get the setup sheets to show all pertainant information to the HTML so the members on the floor can see it saved with the projects.  Long term yes we would be paperless.  Its gonna take some time but we will get there.

[5axes]

You can also import the informations directly in Excel without using  a macro and wihout intermediat file format. Just via the Vba . Sample excel file : 

https://forums.autodesk.com/t5/powermill-forum/get-the-tool-list-of-a-pmill-project-directly-in-exce...

[rui_rita]

Hi @Eskondedo 

machinetool -> {ncprogram.MachineTool.MachineName}

user parameters ( tool example ) {tool.userparameters.MyParameter}

image example

<td class="center" rowspan="3"><img src="c:/dcam/config/setupsheet/CompanyLogoII.jpg"></td>

I think that covers everything, let me know if you need more help

[Eskondedo]

Machine Tool is selected

Here you can see a Machine Tool is selected in the NCprogram but the output via HTML with the provided code did not produce anything.  Also I tried your <td class="center" rowspan="3"><img src="c:/dcam/config/setupsheet/CompanyLogoII.jpg"></td> but with my image and directory and still got nothing.

[rui_rita]

Hi @Eskondedo 

can you please attach your html and style.css 

[Eskondedo]

My IT restrictions prevent me from uploading files so I can paste them here if that works?

[Eskondedo]

Check_Sheet.html <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9" />

${project.CompanyLogo}

CNC Programmers Checklist / CNC Programming Department Standards and Rules
Project Number:			${project.Name}
Checksheet created:			${project.date}
Cam System Used:			Delcam
Material:			{project.Material}
Machine:			${Project.PartName}			Circle Type of Prog:		Rough	Semi	Fin	Patch
Programmed by:			${project.Programmer}			Checked by:

CNC Program checklist procedure:

1. The CNC Programming Department Standards and Rules section of this checklist should be reviewed before starting any program. This section contains information that will need to be used and follower thought the programming process.
2. The Programmer will use this list to check the final project, and as a guide for following CVI Programming department standards and Programming rules.
3. Before releasing the NC packet for manufacturing, the Programmer will review and complete this check list. The Programmer will initial the "Programmed by:" check box.
4. This checklist will then be given to a programming peer or supervisor for a final review.
5. A programming peer or supervisor will verify and initial the "Checked by:" box.
6. A completed check list will be added to the project paperwork packet to be given to the manufacturing floor.

Programming Department Standards and Rules									Yes	No	N/A
1. Are all toolpath origins in the same location?
2. Has each toolpaths Machine Axis Controls been set to: Orientation Vector Fixed Direction Components 0-0-1?
3. Do the cutting tools have the appropriate labels based on the length of the heat shrink?
4. Have the Feeds and Speeds been checked?
5. Does your documentation provide pickup locations clearly?
6. Is the pallet oriented correctly?
7. Has each toolpath been simulated in Powermill with no less than a 5mm collision distance?
8. Has a qualified member checked and approved posted code?

TMD.076 Rev.02

Style.css /* Start documentation header comment PowerMILL Setup Sheets: default cascading style sheet ============================================================================= COPYRIGHT 2005 DELCAM PLC., BIRMINGHAM, ENGLAND. ============================================================================= History. DICC Who When What ===== === ======== ========================================================== 55767 SPD 26/04/05 Written, based on work done by AW. 55886 SPD 28/04/05 Formatting for error message, a4page and index classes. 55941 SPD 09/05/05 Improve the appearance of printed output. 56175 SPD 20/05/05 Formatting for regeneration link, and browser controls. 56285 SPD 02/06/05 Added VML stuff, and no_print_breaks class for . 56775 SPD 05/07/05 Changes to the image classes. 56844 SPD 11/07/05 Added vspace class, for improved print layout. 57697 SPD 14/09/05 Added a comment about US Letter paper. 59645 SPD 05/02/06 Word wrapping now done here; no longer hard-coded. 60056 SPD 03/03/06 Added the wrapped class for spans. 60450 SPD 24/03/06 Made snapshot image widths automatic. 60637 SPD 05/04/06 Snapshot image display tweaks. 65030 SPD 08/03/07 Updated the colour scheme for PowerMILL 8.0. 66999 MH 20/08/07 Use page-break-after for a4page 111512 MOM 03/04/14 Adjust snapshot image size, and remove borders 111727 MOM 15/04/14 Adjustments for IE9 emulation, and some other visual tweaks for web and print. 112626 MOM 29/05/14 Tables have a fixed width so that they don't exceed their parent's width if cells contains long strings. ============================================================================= End documentation header comment */ /* GENERAL FORMATTING: */ body { left: 0.0cm; top: 0.0cm; width: auto; height: auto; margin: 0.0cm; padding: 0.0cm; text-align: left; font-family: sans-serif; font-size: 12px; color: #000000; background: #ffffff; } /* A span in which the text is allowed to wrap: used for entity names. */ span.wrapped { word-break: break-all; /* N.B. This is a proposed extension to the CSS standard! */ } /* Unvisited links */ a:link { color: #e10000; /* A bright red. */ } /* Visited links */ a:visited { color: #1173b4; /* PowerMILL blue. */ } /* User hovers */ a:hover { color: #000000; /* black */ background: #80ff80; /* A bright green --- like highlighter pen. */ } /* Active links */ a:active { color: #1173b4; /* PowerMILL blue. */ } /* * A4 is 21.0cm x 29.7cm, the margins are... * Top: 1.5cm * Right: 2.0cm * Bottom: 2.5cm * Left: 2.0cm * This leaves 17cm x 25.7cm for the content * * US Letter paper is 21.59cm x 27.94cm. There is no need for a separate CSS * class --- the following settings can be used, resulting in the following * margins when printed on US Letter paper... * * Top: 2.0cm * Right: 2.59cm * Bottom: 0.74cm * Left: 2.0cm * */ div.a4page { page-break-after: always; page-break-inside: avoid; width: 21.59cm; height: 27.9cm; margin-top: 2.0cm; margin-left: 0.5cm; padding: 0.1cm; border: solid 1px #eeeeee; /* Very faint border, to mark edge of printable region of page. */ } /* Formatting for the navigation frame. */ div.index { width: 90%; height: auto; margin-left: 5%; margin-right: 5%; margin-top: 1.0cm; padding: 0.0cm; border: solid 1px #eeeeee; } @page { size: 21.0cm 29.7cm portrait; /* a4 paper. */ margin-left: 0.5cm; margin-top: 0.5cm; } @media print { body { width: 21cm; } div.a4page { margin: 0.0cm; } } div.vspace { width: auto; height: 6cm; } footer { text-align: right; vertical-align: bottom; padding-top: 300px; } /* TABLE-SPECIFIC FORMATTING: */ table { cellspacing: 2px; width: 100%; table-layout: fixed; page-break-inside: avoid; } thead { display: table-header-group; } th { background: #dddddd; color: #000000; padding: 0px 4px; text-align: left; border: solid 1px #cccccc; font-size: 12px; word-wrap: break-word; } td { margin: 10px; padding-top: 1px; padding-bottom: 1px; padding-left: 4px; padding-right: 4px; border: solid 1px #cccccc; font-size: 12px; word-wrap: break-word; } td.text { margin: 10px; padding-top: 1px; padding-bottom: 1px; padding-left: 4px; padding-right: 4px; border: solid 1px #cccccc; font-size: 12px; word-wrap: break-word; } td.hidden-cell { visibility. hidden; border-style: none; } td.pot_number { margin: 10px; padding-top: 1px; padding-bottom: 1px; padding-left: 4px; padding-right: 4px; border: solid 1px #cccccc; font-size: 12px; word-wrap: break-word; } /* White text in a coloured box. */ td.title { background: #1173b4; /* PowerMILL blue. */ color: #ffffff; border-style: none; font-weight: bold; font-size: 17px; } tr.summary { background: #eeeeee; font-size: 12px; } tr.full_summary { background: #cccccc; color: #000000; padding-top: 0px; padding-bottom: 0px; padding-right: 4px; padding-left: 4px; text-align: left; border: solid 1px #aaaaaa; font-weight: bold; font-size: 12px; font-family: sans-serif; border: solid 1px #aaaaaa; } /* ERROR MESSAGE FORMATTING: */ div.error { color: #ff0000; /* red */ font-weight: bold; font-size: 17px; text-align: center; width: 16.8cm; height: auto; padding-top: 1.0cm; padding-right: 0.0cm; padding-bottom: 1.0cm; padding-left: 0.0cm; margin: 2px; border: solid 1px #cccccc; } #regen_link { text-decoration: underline; cursor: hand; } /* FORMATTING FOR THE BROWSER CONTROLS: */ table.browser_controls { font-weight: bold; color: #000000; background: #ffffff; margin-top: 10px; margin-bottom: 10px; border-style: none; text-align: center; } #back_button { background: #cccccc; border-width: 2px; border-style: outset; width: 100px; } #forward_button { background: #cccccc; border-width: 2px; border-style: outset; width: 100px; } /* This "pads out" the right-hand side of the table containing the browser contols. */ #dummy_button { background: #ffffff; border-style: none; width: auto; } /* IMAGE STUFF */ /* This is used to force images to be centered. */ div.center { text-align: center; } img.tool_image { width: 178px; height: 250px; border: solid 1px #eeeeee; } img.snapshot_image { display: block; margin-left: auto; margin-right: auto; page-break-inside: avoid; width: auto; height: auto; /* Based on the a4page & body classes to make it fits within an A4 page */ } img.logo_image { width: 100%; height: auto; } /* Microsoft VML stuff, for the automatically-generated PowerMILL tool image. */ v\:* { behavior: url(#default#VML); }

[rui_rita]

can you send by email or do it from home?

[Eskondedo]

So through an arduous amount of trial and error I managed to produce the HTML sheets that I want.  Now the next problem is that when my macro is running I need individual setup sheets to output with seperate Summary.html files based on a number of variable.  The logic to accomplish this is complete but when I try to change the Summary.html path per NC program it sets this globally and changes all the NC programs.  I cannot seem to find away do do this within the base UI of powermill is there some kind of work around to this?  Id rather not have to post individual NC programs one at a time and change it prior to posting each one.  I'd like this to be as automated as possible.  I've attached a photo of the route that I am talking about and a sample of the macro that I am using.  The callout per NC program  and Root NCP is the exact same that I can tell.  I hope I explained this correctly.

//Setup Sheet selection
EXPLORER SELECT NCProgram ; NEW
FORM NCSETUPSHEETS
SETUPSHEETS TEMPLATE ENABLE NCPROGRAM_HEADER
SETUPSHEETS TEMPLATE ENABLE NCPROGRAM_SUMMARY
EDIT NCPROGRAM PREFERENCES SETUPSHEETS SUMMARY FILEOPEN
"N:\DelCam_CVI\Powermill TEST Setup Sheets\Summary.html"
SETUPSHEETS TEMPLATE DISABLE PROJECT_HEADER
SETUPSHEETS TEMPLATE ENABLE PROJECT_SUMMARY
EDIT NCPROGRAM PREFERENCES SETUPSHEETS PROJECT_SUMMARY FILEOPEN
"N:\DelCam_CVI\Powermill TEST Setup Sheets\Project_Summary.html"
NCSETUPSHEETS ACCEPT

[Anonymous]

Something like that? Customized as I wanted.