@aGlance Client Configuration Examples
The following scenario deals with the configuration of the IDX @aGlance gateway to interface between an @aGlance-only system and an OPC system.
In this case, five slots/tag values need to be passed through the gateway from an @aGlance server, AAG_SERV1, to an OPC client system. These tags, on the @aGlance server, are VALUE1.APV, VALUE2.APV, VALUE3.DESC, VALUE4.APV and VALUE5.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. Additional specifications include:
· For process purposes, all tags must be polled at 1 second intervals.
· A backup @aGlance server is available, AAG_SERVBAK. If the main server stops responding for 10 seconds, the gateway client should switch to the backup server.
In this case, since only a single @aGlance server connection 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).