@aGlance Server Configuration Example

The following scenario deals with the configuration of the IDX @aGlance gateway to interface between an OPC system and an @aGlance-only system:

 

images\Image2.jpg

 

In this case, five slots/tag values need to be passed through the gateway from an OPC Server, OPC_CON1 to an @aGlance client. These tags, on the OPC server, are CONTROL1.APV, CONTROL2.APV, CONTROL3.DESC, CONTROL4.APV and CONTROL5.APV. These tags are represented on the gateway by SLOT_1, SLOT_2, SLOT_3, SLOT_4 and SLOT_5. SLOT_1 and SLOT_2 are BIT values, SLOT_3 is a STRING value, SLOT_4 is a FLOAT value and SLOT_5 is an INTEGER value.

In this case, since only a single @aGlance server is required, no special @aGlance client module and connection considerations need to be taken into account (referring primarily to @aGlance runtime restrictions which force the use of multiple IDX services when using multiple @aGlance client/servers).

Configuration

·      Configure the Service

·      Configure the DMs

·      Configure the Slots

·      Configure the Slot Actions

·      Start the service

·      Test the solution