I receive the following error messages when importing a drill file created with OrCAD X PCB Editor 2023 or from OrCAD X Presto 2023:
////////////////////////////////////////////// Import Log ////////////////////////////////////////////// Start time: 06/03/24 12:17:23 File: power_distribution_board-1-2.drl . Created NC Tool 1, #1 Diameter 0.0350 Created NC Tool 2, #2 Diameter 0.0460 Created NC Tool 3, #3 Diameter 0.0550 Created NC Tool 4, #4 Diameter 0.1700 FATAL: Unable to display Invalid Tool #: 5 (File Byte Location: 757) FATAL: Unable to parse NC. (M00) FATAL: Unable to parse NC. (File Byte Location: 757) FATAL: Unable to parse NC file at byte: 0 power_distribution_board-1-2.drl FATAL: Translation Failed. . Finish time: 06/03/24 12:17:23 Start time: 06/03/24 12:17:23 File: power_distribution_board-1-2.drl . Created NC Tool 1, #1 Diameter 0.0350 Created NC Tool 2, #2 Diameter 0.0460 Created NC Tool 3, #3 Diameter 0.0550 Created NC Tool 4, #4 Diameter 0.1700 FATAL: Unable to display Invalid Tool #: 5 (File Byte Location: 757) FATAL: Unable to parse NC. (M00) FATAL: Unable to parse NC. (File Byte Location: 757) FATAL: Unable to parse NC file at byte: 0 power_distribution_board-1-2.drl FATAL: Translation Failed. . Finish time: 06/03/24 12:17:23
Count: Hits=18
I am a bit at a loss why it is trying to create a fifth tool. I looked at the file in a hex file viewer at the offset specified in the error message and I do not see anything unusual.
I have tried regenerating to file several times, but still the error persists.
The drill file and the nc parameter file are attached.
Regards..
Thanks again for providing a sample file.
Last month we made an update to compensate for recent OrCAD X (generated Drill files) - which uses the command M00 (to imply that the tool number is being incremented - instead of using the Tool Change command). Alternatively, M00 is considered as the "end of file" (for other PCB CAD tools). Typically most Drill files assign the tool change command T01,T02 , T#...
FAB3000 automatically detects what CAD tool the Drill file was generated from - and make any necessary updates to import the Drill files (as intended). We created an alternative solution to prevent incrementing the additional tool# - with OrCAD X generated drill files. The update of FAB3000 will be available tomorrow, and I'll send you the download link when it's available.
The importer has been updated (as mentioned in my previous reply), and here's a screen capture:
I receive the following error messages when importing a drill file created with OrCAD X PCB Editor 2023 or from OrCAD X Presto 2023:
//////////////////////////////////////////////
Import Log
//////////////////////////////////////////////
Start time: 06/03/24 12:17:23
File: power_distribution_board-1-2.drl
.
Created NC Tool 1, #1 Diameter 0.0350
Created NC Tool 2, #2 Diameter 0.0460
Created NC Tool 3, #3 Diameter 0.0550
Created NC Tool 4, #4 Diameter 0.1700
FATAL: Unable to display Invalid Tool #: 5 (File Byte Location: 757)
FATAL: Unable to parse NC. (M00)
FATAL: Unable to parse NC. (File Byte Location: 757)
FATAL: Unable to parse NC file at byte: 0 power_distribution_board-1-2.drl
FATAL: Translation Failed.
.
Finish time: 06/03/24 12:17:23
Start time: 06/03/24 12:17:23
File: power_distribution_board-1-2.drl
.
Created NC Tool 1, #1 Diameter 0.0350
Created NC Tool 2, #2 Diameter 0.0460
Created NC Tool 3, #3 Diameter 0.0550
Created NC Tool 4, #4 Diameter 0.1700
FATAL: Unable to display Invalid Tool #: 5 (File Byte Location: 757)
FATAL: Unable to parse NC. (M00)
FATAL: Unable to parse NC. (File Byte Location: 757)
FATAL: Unable to parse NC file at byte: 0 power_distribution_board-1-2.drl
FATAL: Translation Failed.
.
Finish time: 06/03/24 12:17:23
Count: Hits=18
I am a bit at a loss why it is trying to create a fifth tool. I looked at the file in a hex file viewer at the offset specified in the error message and I do not see anything unusual.
I have tried regenerating to file several times, but still the error persists.
The drill file and the nc parameter file are attached.
Regards..
0 Votes
0 Comments
Login or Sign up to post a comment