Technical data

Technology functions
CPU 317T: Technology Functions
6-178 A5E00251798-03
Output parameters
Parameter Data type Start value Description
Done BOOL FALSE TRUE: Cam segments were deleted
Busy BOOL FALSE TRUE: Command is busy
Error BOOL FALSE
TRUE: Command initiation
with error.
The command is not executed;
the cause is found in the ErrorID.
FALSE: Command initiation
without error
ErrorID WORD 0
ErrorID of output parameter Error.
Warning
The deletion of cam disks with many interpolation points or polynom
ials may take a
relatively long time. Other technology objects can not accept any new commands
within this period of time. This also applies to MC_Stop commands ! Note that you
can not cancel commands without defined termination ("MC_MoveVelocity", for
example) within this time.
If the monitoring time for command execution is set too short in S7T Config, a
deletion may lead to a time-out and, thus, to a STOP of the Technology CPU.
MC_CamClear - ErrorIDs
ErrorID Error message Description / to correct or avoid error
0000 No error
8001 Internal fault Faulty or inconsistent project / software.
8005 Command canceled because of
input buffer overflow
The rate at which the user program outputs commands to
the technology is too high.
8007 An internal error has occurred at the
job interface
Due to an internal problem in the S7 system, commands
can not be accepted.
Check the consistency of your project data, then download
all system data to the module again.
8044 Task not supported by the
technology object
Send a command to a cam, for example.
8045 Illegal command with current status • The cam is in use.
• An MC_CamSectorAdd is busy adding interpolation
points to a cam disk.
(the cause can only apply to firmware version V3.0.x of
the integrated technology.)
804C Command output rate too high The command output rate with the same instance DB was
higher than the command interface was able to accept.
The second command is rejected in order not to violate
consistency the first.
For high command output rates, always use a separate
instance DB, or send the command again. Please note,
that although the first accepted command may be busy,
you may not be able to monitor it at the status outputs.