PROFIBUS DP-Master

More documents

Recommendations

Info

The Application Interface 136/315 6.1.10 PROFIBUS_FSPMM_CMD_WRITE_REQ/CNF – V1 Class 1 Write Request This packet can be used to send a DP V1 Class 1 write request. It operates based on slot and index information. Explanations of the parameters of the request packet: 1) The parameter ulRemAdd = Rem_Add contains the station address of the slave responder. 2) The parameter ulSlot = Slot_Number is used in the destination device for addressing the desired data block slot (typically a module). 3) The parameter ulIndex = Index is used in the destination device for addressing the desired data block. 4) The parameter ulLength = Length indicates the number of bytes of the data block that has to be written. If the destination data block length is less than required then the reply will contain an error message. If the data block length is greater or equal than the required length, the reply contains the number of bytes, which have been written. The PROFIBUS DP-Slave may answer with an error response if the data access is not allowed. The field abData contains the data block, which has to be written and consists of the number of octets indicated in the length of the request. For more information refer to section 5.3.1 ”Cyclic Data Transfer”. Note: The three variables bErrorDecode , bErrorCode1 and bErrorCode2 of the confirmation packet are only present in case of error TLR_E_PROFIBUS_FSPMM_MSAC1_NRS, otherwise they are missing. Packet Structure Reference typedef struct PROFIBUS_FSPMM_WRITE_REQ_Ttag { TLR_UINT32 ulRemAdd; TLR_UINT32 ulSlot; TLR_UINT32 ulIndex; TLR_UINT8 abData[PROFIBUS_FSPM_MAX_IO_DATA_LEN]; }PROFIBUS_FSPMM_WRITE_REQ_T; typedef struct PROFIBUS_FSPMM_PACKET_WRITE_REQ_Ttag { TLR_PACKET_HEADER_T tHead; PROFIBUS_FSPMM_WRITE_REQ_T tData; }PROFIBUS_FSPMM_PACKET_WRITE_REQ_T; PROFIBUS DP-Master | DOC061001API12EN | Revision 12 | English | 2010-12 | Released | Public © Hilscher, 2006-2010
The Application Interface 137/315 Packet Description structure PROFIBUS_FSPMM_PACKET_WRITE_REQ_T Type: Request Area Variable Type Value / Range Description Head structure TLR_PACKET_HEADER_T ulDest UINT32 0x20/ FSPMM_QUE Destination queue handle ulSrc UINT32 0 ... 2 32 -1 Source queue handle ulDestId UINT32 ulFSPMM0Id Destination end point identifier, specifying the final receiver of the packet within the destination process. Set to 0 for the Initialization Packet ulSrcId UINT32 ulAPMS0Id Source end point identifier, specifying the origin of the packet inside the source process ulLen UINT32 12 + PROFIBUS_FS PM_MAX_IO_D ATA_LEN 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 section 7.1 Error Codes of the FSPMM-Task ulCmd UINT32 0x2212 PROFIBUS_FSPMM_CMD_WRITE_REQ_T - Command Data ulExt UINT32 0 Extension not in use, set to zero for compatibility reasons ulRout UINT32 x Routing, do not change structure PROFIBUS_FSPMM_WRITE_REQ_T ulRemAdd UINT32 0 ... 125 Slave address ulSlot UINT32 0 ... 254 Slot ulIndex UINT32 0 ... 254 Index abData UINT8[] Write data Table 74: PROFIBUS_FSPMM_CMD_WRITE_REQ– V1 Class 1 Write Request 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 115 and 116: The Application Interface 115/315 P
Page 135: The Application Interface 135/315 P
Page 147 and 148: The Application Interface 147/315 W
Page 151 and 152: The Application Interface 151/315 T
Page 153 and 154: The Application Interface 153/315 u
Page 171 and 172: The Application Interface 171/315 T
Page 187 and 188:
The Application Interface 187/315 P
Page 189 and 190:
Page 191 and 192:
The Application Interface 191/315 6
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:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
The Application Interface 241/315 A
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
The Application Interface 253/315 F
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
The Application Interface 263/315 F
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
The Application Interface 289/315 a
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
The Application Interface 305/315 t
Page 307 and 308:
Status/Error codes overview 307/315
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315:
Contact 315/315 8 Contact Headquart
show all

PROFIBUS DP-Master

Create successful ePaper yourself

Delete template?

Save as template?