5 — VEHICLE CONTROL LANGUAGE (VCL)
Curtis Model 1351 – December 2018
pg. 88
Emergency Message Monitoring
Emergency messages are collected by the CAN master (when enabled) and placed into an indexed buffer.
Messages can be retrieved by the NODE ID or the depth of the buffer can be retrieved and messages
pulled out one-by-one.
The buffer is 16 emergency messages deep.
When a “code” is retrieved from the buffer, its data is placed into pre-defined global VCL variables
and the message is pulled from the stack. The user can then check for the next message until the index
returned is null (valueless).
function
Enable_Emergency_Message_Monitor()
Starts Emergency Message
monitoring.
Disable_ Emergency_Message_Monitor()
Disable will clear out ALL
nodes from the monitoring list.
syntax
Enable_Emergency_Message_Monitor(Port)
Disable_ Emergency_Message_Monitor(Port)
arguments:
Port_1 = CAN1
The primary CAN port, pins 3 & 4
Port_2 = CAN2
The secondary CAN port, pins 5 & 6
returns:
0 =
did not execute.
1 =
successfully executed
reported errors:
function
Setup_Emergency Message_Monitor()
Monitor a Node for Emergency
messages
Place this Node ID into the list of devices that will be monitored for Emergency
messages.
syntax
Setup_Emergency Message_Monitor(Port, Node_ID)
arguments:
Port_1 = CAN1
The primary CAN port, pins 3 & 4
Port_2 = CAN2
The secondary CAN port, pins 5 & 6
Node_ID
The Slave Node ID
returns:
reported errors:
