



This system configuration illustrates the testing of two resources
in a remote device named DEV1
. The test panel shown at
left is located in the local device instance named DEV_TESTER
. The
local resource DEV_TESTER.RES1
provides the HMI for testing of the FB_ADD_REAL
instance AD
in the remote resource DEV1.RES1
, while
the local resource DEV_TESTER.RES2
provides the HMI for testing of the E_CTU
instance CTR
in the remote resource DEV1.RES2
.
See Annex B.2 of the Compliance
Profile for a listing of the request/response transactions
resulting from launching
the remote DEV1
device
, followed by launching
the system configuration.



