Processor to Processor Communications Driver

This driver is for communication of system variables between RTI processors for a multi-processor environment. Comms between two RTI processors is the only supported mode (and is the only tested mode) of operation. String, Integer and Flag variables can be automatically communicated from an XPn to another XPn by configuring each desired variable in ID during programming. The receiving XPn will map variables to its internal driver variables labeled Integer 1, Integer 2, ... String 1, String 2, ... and Flag 1, Flag 2, ... SO, YOU MUST KEEP TRACK OF WHICH SOURCE VARIABLE IS CONNECTED TO WHICH DESTINATION VARIABLE. Sorry but current limitations in ID do not allow you to change driver variable names at design time.

Dynamic Naming

If you used this driver before and are updating it you will ask yourself "What happened to all of my string, integer and flag configuration parameters!?"

Answer: They are still there but you need to open the String Names, Integer Names and Flag Names configuration categories and give names to each of the variables you are receiving from the other Processor. Then you will see these names and the default names on each of these variables. NAME YOUR VARIABLES.

RS-232 Connection

The RS-232 connection between XP processors can use a Cat-5 cable with special terminations. A null modem is required therefore you must swap the Rx and Tx pins between processors.

Serial Port is the two-way port you connected to this XP processor.

TCP or UDP Connection

The TCP or UDP connection between XP processors uses standard Ethernet networking and requires no special or additional cabling. You must be connected either directly between processors with a crossover cable or via a network router or switch. Currently UDP is the only protocol that works between XP processors.

UDP Remote Address is the IP Address of the other XP processor. For example: 192.168.1.100.

UDP Port is the TCP port address for sending/receiving data to the other XP processor. For example: 40600

Strings, Flags, Integers

These variables are for mapping this XP processor's driver and system variables to the partner XP processor through a copy of this driver on the partner XP processor. For example, Integer 1 can map Current Temperature from a room Thermostat to Integer 1 on the partner XP processor. The partner XP processor can then display XP2XP Driver Integer 1 on a remote as Current Temperature for that room. A system Flag on this XP processor can be transfered to the partner XP processor for use in macros on the partner processor.

In other words, the state of String, Flag and Integer variables will be automatically maintained from this processor to the partner processor. (And vice versa for the partner processor's configured variables.)

Macros

You can select system Macros that the partner processor can execute directly. The macros will be mapped to Macro 1, Macro 2, etc. on the partner processor. So on the partner processor, when you call the Execute System Macro function, it will call the mapped macro on this processor. This will tie up the partner processor XP2XP driver for the duration of the macro. Please do not execute long macros. Instead, trigger them with a Driver Event as described next...

System Driver Events

This driver provides system events that you can setup on the Events tab of the XPn processor in Integration Designer. These events can be triggered as normally on this processor or by calling the Trigger Driver Event on the partner XPn processor. This is the preferred method of calling macros on the partner processor because the driver can just trigger the event and the XP processor will take over from there.

Macro and Event Commands

Execute System Macro

Call this function to execute a (short) macro on the partner XPn processor. There must be a configured and properly created system macro on the partner processor to execute or else nothing will happen.

Trigger Driver Event

Call this function to trigger a system event on the partner XPn processor. There must be a configured and properly created event on the partner processor to execute or else nothing will happen. Use this method to invoke longer or complex macros on the partner processor!