To allow an engineering tool access to a slave at all times, it is switched onto the bus as a class 2 master and must explicitly establish a connection with the slave. Several master class 2 can establish a MS2 connection at the same time to the same slave. The connection has not to be planned in advance, but for this purpose, further SAPs are reserved on the master and slave:
SAP: service access points of master
SAP |
Name |
Meaning |
50 (0x32) |
MS2 |
Acyclic class 2 master |
SAP: service access points of DP slave
SAP |
Name |
Data unit from master to slave |
Data unit from slave to master |
≤ 48 (0x30) |
Communication |
DS_xxx_REQ, MS2_Abort_REQ |
DS_xxx_RES |
49 (0x31) |
Resource Manager |
MS2_Initiate_REQ |
Resource_Manager_REQ |
A connection is explicitly established with a DPV1_Initiate and closed again with am DPV1_Abort. For a connection to be established, the following services and telegrams must be transmitted:
DPV1_Initiate: at SAP = 49 (resource manager)
0x57 |
Reserved 3 bytes |
Send timeout |
Features supported |
Profile features supported |
Profile ident number |
Add_Addr Param |
A poll cycle at SAP = 49 with response data:
0x56 |
Server_SAP |
Min Send Timeout |
If the resource manager has no more free SAPs, it reports this at the FDL layer with RS (= no resource available). The master begins with a number of poll cycles at the new SAP = Server_SAP until a response is given or until the Min_Send_Timeout has expired.
0x57 |
Max_Len_ Data_Unit |
Features supported |
Profil features supported |
Profile ident number |
Add_Addr Param |
A negative response:
0xD7 |
Error_Decode |
Error_Code1 |
Error_Code2 |
If the response is positive, payload data can now be exchanged.
Sequence of telegrams for the establishement of a MS2 relation