Hi Les,
I have only just started to experiment with this option, when I load up the jet or full report it crashes Sheetcam, I am using V6.03.
I have added the job file in case there is anything wrong there.
Many thanks
Sean
Job Report Crashing
Job Report Crashing
- Attachments
-
- 85mm plate.job
- (19.88 KiB) Downloaded 129 times
Same here
I think I have the same problem as the OP in version 6.0.3 and 6.0.4 on Win 7 Pro 64 (maybe in prior versions too but I'm not sure). If I choose a full job report, SheetCAM crashes with certain jobs and doesn’t crash with others. If I choose a summery job report I've no problem with those particular jobs.
But I think I’m on to something. After the crash I reload SheetCAM and it asks me to load a backup. But the backup doesn’t load correctly because the tool selection for each operation is blank. This also happens when I save the job myself and load it in afterwards. I think SheetCAM crashes because it can’t find the selected tools when creating a full job report. In the summary job report there aren’t any tools mentioned and so it doesn’t crash. By the way, the jobs run perfectly on my CNC mill and I love SheetCAM.
But I think I’m on to something. After the crash I reload SheetCAM and it asks me to load a backup. But the backup doesn’t load correctly because the tool selection for each operation is blank. This also happens when I save the job myself and load it in afterwards. I think SheetCAM crashes because it can’t find the selected tools when creating a full job report. In the summary job report there aren’t any tools mentioned and so it doesn’t crash. By the way, the jobs run perfectly on my CNC mill and I love SheetCAM.
- Les Newell
- Site Admin
- Posts: 3665
- Joined: Thu May 11, 2006 8:12 pm
- Les Newell
- Site Admin
- Posts: 3665
- Joined: Thu May 11, 2006 8:12 pm
Wow, that took some finding. The fault is triggered by the name of your path rule: Shapes <20mm FR60%
The '%' in the name is causing the debug log to crash. If you change the name of that rule the report will work. In the mean time I will beat the offending piece of code into submission and get a new release out as soon as I can.
The '%' in the name is causing the debug log to crash. If you change the name of that rule the report will work. In the mean time I will beat the offending piece of code into submission and get a new release out as soon as I can.