PROFIBUS DP-Master

More documents

Recommendations

Info

The Application Interface 280/315 Packet Structure Reference typedef struct PROFIBUS_DL_DLSAP_ACTIVATE_RESPONDER_CNF_Ttag { TLR_UINT8 bSrcSAPIdx; /* Source Service Access Point to be activated */ TLR_UINT8 bAcc; /* access protection to specify if all stations or individual station may access */ } PROFIBUS_DL_DLSAP_ACTIVATE_RESPONDER_CNF_T; /* Request-Packet for SAP responder activation */ typedef struct PROFIBUS_DL_PACKET_DLSAP_ACTIVATE_RESPONDER_CNF_Ttag { TLR_PACKET_HEADER_T tHead; PROFIBUS_DL_DLSAP_ACTIVATE_RESPONDER_CNF_T tData; /* Packet Data Unit */ } PROFIBUS_DL_PACKET_DLSAP_ACTIVATE_RESPONDER_CNF_T; Packet Description structure PROFIBUS_DL_PACKET_DLSAP_ACTIVATE_RESPONDER_CNF_T Type: Confirmation Area Variable Type Value / Range Description Head Data structure TLR_PACKET_HEADER_T ulDest UINT32 Destination queue handle, unchanged ulSrc UINT32 Source queue handle, unchanged ulDestId UINT32 ulAPM0Id Destination end point identifier, unchanged ulSrcId UINT32 ulDL0Id Source end point identifier, unchanged ulLen UINT32 2 Packet data length in bytes ulId UINT32 0 ... 2 32 -1 Packet identification as unique number generated by the Source process of the packet ulSta UINT32 See chapter 6.5 Packets for Configuration during running system. ulCmd UINT32 0x123 PROFIBUS_DL_CMD_DLSAP_ACTIVATE_RESPONDER _CNF - Command ulExt UINT32 0 Extension, unchanged ulRout UINT32 × Routing, do not change structure PROFIBUS_DL_DLSAP_ACTIVATE_RESPONDER_CNF_T bSrcSAPIdx UINT8 0-63. 64 = NIL SAP Source Service Access Point to be activated bAcc UINT8 0-126,255 access protection to specify if all stations or individual station may access Table 172: PROFIBUS_DL_CMD_DLSAP_ACTIVATE_RESPONDER_CNF – Confirmation of Activate a SAP for Responder Functionality PROFIBUS DP-Master | DOC061001API12EN | Revision 12 | English | 2010-12 | Released | Public © Hilscher, 2006-2010
The Application Interface 281/315 6.3.13 PROFIBUS_DL_CMD_DLSAP_DEACTIVATE_REQ/CNF - Deactivate an SAP for Request This service is used to deactivate a local service access point which has previously been defined either with the • “PROFIBUS_DL_CMD_DLSAP_ACTIVATE_REQ/CNF - Activate an SAP for Request” packet described in section 6.3.11 or with the • “PROFIBUS_DL_CMD_DLSAP_DEACTIVATE_REQ/CNF - Deactivate an SAP for Request” packet described in section 6.3.12. Only the numerical value assigned with the SAP or the RSAP to be deactivated needs to be specified. Packet Structure Reference /* Request-Packet for SAP deactivation */ typedef struct PROFIBUS_DL_DLSAP_DEACTIVATE_REQ_Ttag { TLR_UINT8 bSrcSAPIdx; /* Source Service Access Point to be activated */ } PROFIBUS_DL_DLSAP_DEACTIVATE_REQ_T; typedef struct PROFIBUS_DL_PACKET_DLSAP_DEACTIVATE_REQ_Ttag { TLR_PACKET_HEADER_T tHead; PROFIBUS_DL_DLSAP_DEACTIVATE_REQ_T tData; } PROFIBUS_DL_PACKET_DLSAP_DEACTIVATE_REQ_T; PROFIBUS DP-Master | DOC061001API12EN | Revision 12 | English | 2010-12 | Released | Public © Hilscher, 2006-2010
Page 1 and 2:
Protocol API PROFIBUS DP-Master V2.
Page 3 and 4:
3/315 Rev Date Name Revisions 11 20
Page 5 and 6:
5/315 5.3.3 Configuration of Inputs
Page 7 and 8:
List of Figures 7/315 Figure 1: The
Page 9 and 10:
9/315 Table 62: PROFIBUS_FSPMM_CMD_
Page 11 and 12:
Introduction 11/315 Table 178: PROF
Page 13 and 14:
Introduction 13/315 1.5 Specificati
Page 15 and 16:
Introduction 15/315 1.6 Terms, Abbr
Page 17 and 18:
Introduction 17/315 1.8.3 Exclusion
Page 19 and 20:
Fundamentals 19/315 2.2 Accessing t
Page 21 and 22:
Fundamentals 21/315 2.3.2 Using Sou
Page 23 and 24:
Fundamentals 23/315 Example This ex
Page 25 and 26:
Fundamentals 25/315 3) You can find
Page 27 and 28:
Fundamentals 27/315 2.4.2 Applicati
Page 29 and 30:
Dual-Port-Memory 29/315 3.1.1 Input
Page 31 and 32:
Dual-Port-Memory 31/315 3.2.1 Gener
Page 33 and 34:
Dual-Port-Memory 33/315 Extension T
Page 35 and 36:
Dual-Port-Memory 35/315 3.3 Status
Page 37 and 38:
Dual-Port-Memory 37/315 Common Stat
Page 39 and 40:
Dual-Port-Memory 39/315 Communicati
Page 41 and 42:
Dual-Port-Memory 41/315 3.3.1.2 Mas
Page 43 and 44:
Dual-Port-Memory 43/315 3.3.2 Exten
Page 45 and 46:
Dual-Port-Memory 45/315 Extended St
Page 47 and 48:
Dual-Port-Memory 47/315 • bErr_Re
Page 49 and 50:
Dual-Port-Memory 49/315 abSl_state
Page 51 and 52:
Dual-Port-Memory 51/315 bErr_Event
Page 53 and 54:
Dual-Port-Memory 53/315 3.4 Control
Page 55 and 56:
Getting started / Configuration 55/
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Overview 73/315 5 Overview 5.1 Prof
Page 75 and 76:
Overview 75/315 5.3 Functionality o
Page 77 and 78:
Overview 77/315 5.3.2 Acyclic Data
Page 79 and 80:
Overview 79/315 5.3.3 Configuration
Page 81 and 82:
Overview 81/315 This format is call
Page 83 and 84:
Overview 83/315 5.3.4.3 Conditions
Page 85 and 86:
Overview 85/315 5.3.5.1 Diagnostic
Page 87 and 88:
Overview 87/315 This bit is reserve
Page 89 and 90:
Overview 89/315 The following bytes
Page 91 and 92:
Overview 91/315 The third byte cont
Page 93 and 94:
Overview 93/315 5.4.4 Basic Service
Page 95 and 96:
Overview 95/315 5.4.8 Initializatio
Page 97 and 98:
Overview 97/315 5.4.10 Requirements
Page 99 and 100:
Overview 99/315 5.5.1 Data Transfer
Page 101 and 102:
Overview 101/315 The following pack
Page 103 and 104:
Overview 103/315 management service
Page 105 and 106:
Overview 105/315 o Finally, the fir
Page 107 and 108:
Overview 107/315 The following figu
Page 109 and 110:
The Application Interface 109/315 6
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
The Application Interface 115/315 P
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
The Application Interface 147/315 W
Page 149 and 150:
Page 151 and 152:
The Application Interface 151/315 T
Page 153 and 154:
The Application Interface 153/315 u
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
The Application Interface 171/315 T
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
The Application Interface 199/315
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230: The Application Interface 229/315 P
Page 231 and 232: The Application Interface 231/315 6
Page 241 and 242: The Application Interface 241/315 A
Page 253 and 254: The Application Interface 253/315 F
Page 263 and 264: The Application Interface 263/315 F
Page 279: The Application Interface 279/315 5
Page 289 and 290: The Application Interface 289/315 a
Page 305 and 306: The Application Interface 305/315 t
Page 307 and 308: Status/Error codes overview 307/315
Page 315: Contact 315/315 8 Contact Headquart
show all

PROFIBUS DP-Master

Create successful ePaper yourself

Delete template?

Save as template?