Hi Les,
I am having trouble loading a .DXF drawing from my plugin, job files load just fine. here is the latest plugin and the test program, .job file and .DXF file.
-James
Problem with scLoadDrawing
-
Les Newell
- Site Admin
- Posts: 3667
- Joined: Thu May 11, 2006 8:12 pm
Problem with scLoadDrawing
Hi James,
As far as I can tell your app isn't calling scLoadDrawing at all. When I
run SheetCAMVBInterfaceTest.exe, SheetCam starts up then after a couple
of minutes I get a message box saying SheetCAMVBInterfaceTest can't find
SheetCam.
Try rebuilding the library file. The next release will include
debugging messages to let you know when functions are called by a dll.
In SheetCam.ini, add the following value to the [preferences] section:
ShowDebug = 1
This will tell SheetCam to show the debug window.
Here is some data on the job file format. You will have to refer to a
job file to make any sense of it. Most values are optional. If they
don't exist then default values will be used.
Tool section
[Tooln] where n is a tool index. Note the number is the index in the
tool table and must be sequential, starting at 0.
Most of the values in this section are pretty self explanatory
Type. Tool type. One of the following:
0=TOOL_TYPE_PARALLEL (mill/router)
1=TOOL_TYPE_DRILL
2=TOOL_TYPE_V
3=TOOL_TYPE_PLASMA
4=TOOL_TYPE_CODE (g-code)
5=TOOL_TYPE_TAPMATIC
6=TOOL_TYPE_RIGIDTAP,
TextData. Used for code snippet 'tool'
Tool change
[ToolChange]
X,Y,Z are toolchange positions
UseX,Y,Z. If these are not zero then the relevant toolchange positions
are used
Code Code run after a toolchange
BeforeCode Code run before a toolchange
NoMove. If this is non-zero the first move before a toolchange is suppressed
[Misc]
Count. This is the number of parts, 1 if there is only one part. This is
not optional. See the [Partn] section below
FileVersion=1. Should always be 1. This line is not optional.
Dimensions of the material
[Work]
These values are pretty self explanatory. If this section is missing
then the current work dimensions are used
Dimensions of the machine
[Table]
These values are pretty self explanatory. If this section is missing
then the current machine dimensions are used
ToolTime. This is the toolchange time - used to estimate job time
RapidSpeed. Rapid speed - used to estimate job time
[Part n] part number. n must be sequential and start at 0. Count in the
[Misc] section above specifies how many parts are in the job.
Most values are pretty obvious.
CopyOf. -1 for a part or the part number for a duplicate. Use a valid
part number or Bad Things (TM) will happen...
HRef,VRef. If non-zero the part is horizontally or vertically reflected.
[Part nProcessx] n is the part number, x is the process number. x must
be sequential, starting at 0. Note: Process sections are not used for
duplicates.
Function. Process function. One of the following numbers:
0 = PROCESS_INOFFSET
1 = PROCESS_OUTOFFSET
2 = PROCESS_FOLLOW (no offset)
3 = PROCESS_PLASMAIN
4 = PROCESS_PLASMAOUT
5 = PROCESS_PLASMAFOLLOW (no offset)
6 = PROCESS_SPIRALPOCKET
7 = PROCESS_GCODE
8 = PROCESS_VARIABLE
9 = PROCESS_DRILL
10 = PROCESS_ZIGZAGPOCKET
11 = PROCESS_TAP
Tool. Tool number. This is the tool number..
Increment. Z increment
TextData. Used by G-code process and variable process to store text data
Lead in, Lead out. lead size
Lead in type, Lead out type
One of the following
0=LEAD_NONE
1=LEAD_ARC
2 = LEAD_TANGENT
3=LEAD_PERP
CodeSnip. Used by G-code process. Indicates a code snippet
Les
As far as I can tell your app isn't calling scLoadDrawing at all. When I
run SheetCAMVBInterfaceTest.exe, SheetCam starts up then after a couple
of minutes I get a message box saying SheetCAMVBInterfaceTest can't find
SheetCam.
Try rebuilding the library file. The next release will include
debugging messages to let you know when functions are called by a dll.
In SheetCam.ini, add the following value to the [preferences] section:
ShowDebug = 1
This will tell SheetCam to show the debug window.
Here is some data on the job file format. You will have to refer to a
job file to make any sense of it. Most values are optional. If they
don't exist then default values will be used.
Tool section
[Tooln] where n is a tool index. Note the number is the index in the
tool table and must be sequential, starting at 0.
Most of the values in this section are pretty self explanatory
Type. Tool type. One of the following:
0=TOOL_TYPE_PARALLEL (mill/router)
1=TOOL_TYPE_DRILL
2=TOOL_TYPE_V
3=TOOL_TYPE_PLASMA
4=TOOL_TYPE_CODE (g-code)
5=TOOL_TYPE_TAPMATIC
6=TOOL_TYPE_RIGIDTAP,
TextData. Used for code snippet 'tool'
Tool change
[ToolChange]
X,Y,Z are toolchange positions
UseX,Y,Z. If these are not zero then the relevant toolchange positions
are used
Code Code run after a toolchange
BeforeCode Code run before a toolchange
NoMove. If this is non-zero the first move before a toolchange is suppressed
[Misc]
Count. This is the number of parts, 1 if there is only one part. This is
not optional. See the [Partn] section below
FileVersion=1. Should always be 1. This line is not optional.
Dimensions of the material
[Work]
These values are pretty self explanatory. If this section is missing
then the current work dimensions are used
Dimensions of the machine
[Table]
These values are pretty self explanatory. If this section is missing
then the current machine dimensions are used
ToolTime. This is the toolchange time - used to estimate job time
RapidSpeed. Rapid speed - used to estimate job time
[Part n] part number. n must be sequential and start at 0. Count in the
[Misc] section above specifies how many parts are in the job.
Most values are pretty obvious.
CopyOf. -1 for a part or the part number for a duplicate. Use a valid
part number or Bad Things (TM) will happen...
HRef,VRef. If non-zero the part is horizontally or vertically reflected.
[Part nProcessx] n is the part number, x is the process number. x must
be sequential, starting at 0. Note: Process sections are not used for
duplicates.
Function. Process function. One of the following numbers:
0 = PROCESS_INOFFSET
1 = PROCESS_OUTOFFSET
2 = PROCESS_FOLLOW (no offset)
3 = PROCESS_PLASMAIN
4 = PROCESS_PLASMAOUT
5 = PROCESS_PLASMAFOLLOW (no offset)
6 = PROCESS_SPIRALPOCKET
7 = PROCESS_GCODE
8 = PROCESS_VARIABLE
9 = PROCESS_DRILL
10 = PROCESS_ZIGZAGPOCKET
11 = PROCESS_TAP
Tool. Tool number. This is the tool number..
Increment. Z increment
TextData. Used by G-code process and variable process to store text data
Lead in, Lead out. lead size
Lead in type, Lead out type
One of the following
0=LEAD_NONE
1=LEAD_ARC
2 = LEAD_TANGENT
3=LEAD_PERP
CodeSnip. Used by G-code process. Indicates a code snippet
Les
I am having trouble loading a .DXF drawing from my plugin, job files load just fine. here is the latest plugin and the test program, .job file and .DXF file.
-
jemmyell
Thanks for the .JOB file info
Hi Les,
That error message you are getting from the test VB app indicates that my new plugin is NOT getting loaded by SheetCam. I have issues trying to launch SheetCam after starting up my COM object, so I simply wait until two named events are available after launching SheetCam from VB IF I don't see those events as already available. The timeout was SUPPOSED to be 15 seconds, but I believe that I used a Sleep(5000) instead of a Sleep(500) for each loop of the wait.
If I could get around the 256K posting limit I would provide my debug builds also which have many debug messages.
-James
That error message you are getting from the test VB app indicates that my new plugin is NOT getting loaded by SheetCam. I have issues trying to launch SheetCam after starting up my COM object, so I simply wait until two named events are available after launching SheetCam from VB IF I don't see those events as already available. The timeout was SUPPOSED to be 15 seconds, but I believe that I used a Sleep(5000) instead of a Sleep(500) for each loop of the wait.
If I could get around the 256K posting limit I would provide my debug builds also which have many debug messages.
-James