Camsoft error

[KARD]

Has anyone had a Camsoft Error: Run Time error '5'.
Invalid Procedure call or Argument

I get this error when trying to Mid Program Start in the MDI Editor window. This error causes my camsoft program to shutdown every time I get it.

[Karl_T]

Are you using the MIDPROGRAM command to pick your start line out?


MIDPROGRAM
This command is similar to CYCLESTART except it will prompt the user for an N block number to begin at. There will be a prompted option to either run the program up to this point with the axis locked to pick up tool offsets, fixture offsets, tool changes and M codes or begin the program immediately at this block number and provide the option of entering in extra G, X, Y, Z, F, S, T and M codes as needed to do a midprogram start. This command contains three optional parameters. The first optional parameter is used for providing an N block to resume cutting at. If omitted or is zero, a prompt will appear asking the N block to begin at. The second optional parameter is for inserting extra G code before the cut begins. If omitted, a prompt will appear asking for the extra G code. The third optional parameter is MOUSEPICK, which allows the user to go to the midprogram start window and graphically pick a position with their mouse or touchscreen as to where they want to start midway through the program. This parameter only works in wireframe mode.The MOUSEPICK option is not recommended for use with TOOLCOMP or SMARTPATH. If you have TOOLCOMP or SMARTPATH in use, then you may use either the MIDPROGRAM command without MOUSEPICK or the MDI window to restart midway through the part program.
EXAMPLE: MIDPROGRAM 100;G90 F300 S1000 M03
MIDPROGRAM MOUSEPICK

[Karl_T]

QUESTION 193
How can we better control the MIDPROGRAM restart feature?

The MIDPROGRAM command has these options:

(1) Parameter to enter the extra G&M codes or axes positions you need before a restart begins.

(2) Option to read quickly through the G code program from the beginning to automatically pick up tool changes and M codes for such items as Spindle On, Laser On or Flame On plus read tool, part and fixture offsets. It will then ask you to press Cycle Start when you are ready.

(3) CNC Professional even has a MOUSEPICK option to graphically select the restart position with the mouse pointer even midway along a long move.

(4) If you want more control over what happens before the restart, then take a look at the following example. Let's say you need to suppress the M codes from triggering a tool or spindle gear change while the program is scanning quickly in memory to pick up all the previous axes positions and offsets. Then, just before you get the prompt to press Cycle Start, you want all the M codes to resume normal actions plus turn on the Spindle, Laser or Flame. Keep in mind that you can add the commands you need before the program scans in memory and also just before Cycle Start is pressed. In this example we will suppress all M code functions while scanning and then re-activate the M codes plus turn on the spindle.

SUSPEND MCODE 'Suppress all M code functions
SUSPEND RESPOND 'Suppress all I/O relays
MIDPROGRAM MOUSEPICK 'Execute graphically restart
-----M100


SAY PRESS CYCLE START 'Talk out of the speakers to operator
MESSAGE Press CYCLE START when Ready
RESUME 'Re-activate M codes and I/O relays
[SPINDLE ON] 'Spindle ON Macro
CYCLESTART
-----M199

[HuFlungDung]

I'm running an older version 14.6 CNC professional, but I think it works alright from within the MDI window for me.

What I might suggest is to make sure that you have properly ended all motion commands that might be in the command buffer. To check this hit ESC before you open the MDI window. If all motion commands have been terminated, you should see a dialog about shutting down the program. You can hit cancel if this is the case.

However, if you see the other dialog come up with 3 choices about aborting the current move, etc, then that means the command buffer is still active. Terminate the current move is what you should do.

Then open the MDI window and try the midprogram restart.

I don't know what else. I actually made a button for my GUI that is dedicated to 'abort program'. Basically, this does what an M30 does for ending the current program, and sets everything back to readiness for a new run at the program. I felt that the ESC button method was not capable of a real clean abort under all circumstances. Of course, I have lots of logic flags that need to be kept track of.