SM-Applications Modules & Motion Processors User Guide 87
Issue Number: 4
Safety
Information
Introduction Installation
Getting
Started
Parameters
DPL
Programming
Communications
Freeze and
Marker
CTSync
Inter-option
Synchronization
Diagnostics
Migration
Guide
Quick
Reference
Index
SCHEDULEEVENT
This function block is used to schedule an EVENT task. The arguments are:
• Slot number
Specifies which slot to schedule the event task in. Currently only 0 is allowed here
which means the local slot.
•Task ID
Range 0-3 to specify which EVENT task to trigger
• Reason
A user defined reason. Must be a value of 34 or higher. This value can be accessed
in the EVENT task by looking at parameter Pr 90.12-Pr 90.15.
CTNETDIAGNOSTICS
This is only available on Second Processors with CTNet. Please see the Features
section on pages 8 & 9 to see if CTNet is available on your Second Processor.
This returns diagnostic information for CTNet. Refer to on-line help. This replaces the
special variables such as NOFMESSAGES that was used on the UD70 product.
This command takes no input and returns 10 outputs. The table below details the
outputs and the equivalent UD70 variable.
BACKGROUND {
... some code
// Schedule local event1 task with reason code of 45.
a% = SCHEDULEEVENT(0, 1, 45)
... some more code
}
EVENT1 {
IF #90.13 = 45 THEN
// task scheduled from DPL
ENDIF
}
Table 7-6 CTNetDiagnostics Output Values
Output Value UD70 Variable
1 Total number of messages handled by this node NOFMESSAGES
2 Number of cyclic data overruns NOFOVERRUNS
3 Lost RX messages NOFLOSTMESSAGES
4 Number of retries NOFRETRIES
5 Number of recons NOFRECONS
6 Number of excessive NAKs NOFEXENAKS
7 Duplicate sync NOFDUPSYNCS
8 Number of locally generated recons NOFMYRECONS
9 Number of non-cyclic messages NOFNONCYCLICMESSAGES
10 Number of lost routing messages N/A
To Next Page
Loading...
Need help?
General
