EDIT: [SOLVED]
- My Setup Sheet button wasn't linked to a .cps file; to link the button, follow the instructions outlined on NexGenCam's blog - Selecting the Default Setup Sheet.
- Please also see Scott's response below for using the powerful post processor menu
- A handy post processor file is tool-list.cps!
Thanks!
--------------------------------------------------------------------
I receive the following error message. My setup, problem description, and troubleshooting are listed below. Please advise!
My setup:
- HSMXpress 2016 R2.40513
- I am using locally stored tool libraries (copied over from my company's network drive)
- Solidworks 2016 x64 SP3.0
- Solidworks PDM 2016
- I have ownership of the assembly in which I'm making toolpaths
- I cannot provide my part files publicly
- Message was edited by Chris Kearney: I have removed the test files I used because responders seemed to think the test files were at issue. Those files allow generation of Setup Sheets, but our files opened through PDM don't. While I appreciate the effort, please read the entire post before responding. Thank you!
Problem:
- In HSMXpress CAM, I'd select my toolpaths, click the Setup Sheet icon, and select the folder to save the setup sheet file into. That's when I receive the message "Failed to generate setup sheet for operation(s)."
Questions I've asked myself thus far:
- Is there something wrong with the tool definition?
- Made a new part and saved it locally
- Used the same tool (from the same tool library as my assembly)
- Generated similar toolpaths
- Clicked Setup Sheet
- Setup Sheet was produced and opened automatically in browser
- Conclusion: Probably nothing wrong with my tools/libraries. Maybe it's file-related or network-related.
- Does it matter that I'm working in an assembly?
- Made an assembly of 2 parts
- Used the same tool (from the same tool library as my assembly)
- Generated similar toolpaths
- Clicked Setup Sheet
- Setup Sheet was produced and opened automatically in browser
- Conclusion: Assembly filetype or multiple parts are not the problem. Maybe network-related.
- Are my coworkers having the same issue?
- Yes. Their own investigations have yielded the same results - sadness.
- Conclusion: Problem not unique to my computer or installations.
Speculations:
- Our network implementation of PDM or HSMXpress is/are corrupted
- Some attribute or setting in PDM is set wrong
- There might be a work-around if I delve into how Setup Sheets are generated at the code level
- Haven't explored this yet
Any advice would be greatly appreciated!
Thank you,
Chris
Hi Chris,
The best place to ask HSMXpress questions is over on the HSM forum, you should get a better response time than here. Thanks to Michael Lord for letting me know this was here though.
I've downloaded your sample files and successfully generated setup sheets from them. I'm curious if you've tried generating the setup sheet using the following method?
Please let me know how you get on.
Cheers
Scott Moyse