PMS is the layer of the project for the PCP message handling channel. The PLC always acts as a client of PMS message handling and all the PCP devices connected on the bus act as servers.
Each device connected to the INTERBUS bus observes a profile. The profile defines the functions of the project, which are visible through communication.
The following table lists the PMS services of the TSX IBY 100 or TSX IBX 100 module.
|
Type of service
|
Service
|
Project access
|
|
Variable access
|
|
READ_VAR(ADDR(’r.m.0.pcp’),’PMS’, index, subindex, %MWk:4, %MWi:L)
|
|
|
WRITE_VAR(ADDR(’r.m.0.pcp’),’PMS’, index, subindex, %MWi:L, %MWk:4)
|
|
Device management
|
|
SEND_REQ(ADDR(’r.m.0.pcp’),16#31, MWi:L, %MWk:4, %MWj:L)
|
|
|
SEND_REQ(ADDR(’r.m.0.pcp’),16#0F, MWi:L, %MWk:4, %MWj:L)
|
|
Program management
|
|
SEND_REQ(ADDR(’r.m.0.pcp’),16#24, MWi:L, %MWk:4, %MWj:L)
|
|
|
SEND_REQ(ADDR(’r.m.0.pcp’),16#25, MWi:L, %MWk:4, %MWj:L)
|
The addressing of requests is performed by (ADDR('r.m.0.pcp') where
-
r.m corresponds to the rack and module,
-
0 corresponds to the channel,
-
pcp corresponds, in auto mode, to the physical order number of the PCP device of the Control Expert configuration + 1 (pcp ranges from 2 to 63).
Example of physical order number
In the INTERBUS configuration list, two devices support PCP message handling.
In this case, the number of the first PCP device will be as follows: 2 (= 1+1).
The number of the second PCP device will be: 3 (= 2+1)
If a request has to be sent, PMS messaging establishes a connection with the INTERBUS slave.
If the connection is successful, all the transactions towards the slave are executed. If it fails, all the requests towards the INTERBUS slave are refused.
On a project stop, the status of PMS messaging matches the configuration established on Control Expert.
Dialog boxes are used in Control Expert to help enter the READ_VAR and WRITE_VAR functions.
