Prosoft-technology MVI56E-LDM Bedienungsanleitung Seite 179
- Seite / 264
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
ControlLogix Platform ♦ "C" Programmable CIP API Functions
Linux Application Development Module Developer's Manual
ProSoft Technology, Inc. Page 173 of 264
March 12, 2014
OCXcip_MsgResponse
Syntax
int OCXcip_MsgResponse (OCXHANDLE apihandle,
DWORD msgHandle,
BYTE serviceCode,
BYTE * msgBuf,
WORD msgSize,
BYTE returnCode,
WORD extendederr);
Parameters
apihandle
apihandle returned by previous call to OCXcip_Open
msgHandle
Handle returned in OCXCIPSERVSTRUC
serviceCode
Message service code returned in OCXCIPSERVSTRUC
msgBuf
Pointer to buffer containing data to be sent with response (NULL
if none)
msgSize
Number of bytes of data to send with response (0 if none)
returnCode
Message return code (OCX_SUCCESS if no error)
extendederr
Extended error code (0 if none)
Description
OCXcip_MsgResponse is used by an application that needs to delay the response to
an unscheduled message received via the service_proc callback. The
service_proc callback is called sequentially and overlapping calls are not
supported. If the application needs to support overlapping messages (for
example, to maximize performance when there are multiple message sources),
then the response to the message can be deferred by returning
OCX_CIP_DEFER_RESPONSE in the service_proc callback. At a later time,
OCXcip_MsgResponse can be called to complete the message. For example, the
service_proc callback can queue the message for later processing by another
thread (or multiple threads).
Note: The service_proc callback must save any needed data passed to it in the
OCXCIPSERVSTRUC structure. This data is only valid in the context of the callback.
OCXcip_MsgResponse must be called after OCX_CIP_DEFER_RESPONSE is returned by
the callback. If OCXcip_MsgResponse is not called, communications resources will
not be freed and a memory leak will result.
If OCXcip_MsgResponse is not called within the message timeout, the message will
fail. The sender determines the message timeout.
msgHandle and serviceCode must match the corresponding values passed to the
service_proc callback in the OCXCIPSERVSTRUC structure.
Return Value
OCX_SUCCESS
Response was sent successfully
- MVI56E-LDM 1
- Your Feedback Please 2
- Warnings - MVI56E-LDM 2
- Contents 5
- 1 LDM Introduction 10
- In This Chapter 12
- 2.1 System Requirements 12
- 2.2 Package Contents - LDM 13
- 2.4.1 Setup Jumper - MVI56E 14
- telnetd file 20
- 2.8 Module Rescue 27
- 3 Development Environment 29
- 3.2 Using Eclipse 33
- 3.2.1 Building a Project 33
- python createimage.py 36
- 4.1 API Library - MVI56E 39
- 4.1.1 Header File 39
- 4.1.2 Sample Code 39
- 4.3 CIP API Functions 42
- 4.4 Backplane Device Driver 42
- 4.5 Sample Code 44
- 4.10 Sample Tutorials 51
- 4.11 Ethernet Sample 52
- 4.12 Serial Sample 55
- 4.13 Led_Sample 56
- 4.14 Backplane_Sample 57
- 4.15 Tag_Sample 59
- 4.16 Sample Applications 61
- 5 CIP API Functions 76
- OCXcip_Open 79
- OCXcip_OpenNB 80
- OCXcip_Close 83
- 5.2 Object Registration 85
- OCXcip_RegisterAssemblyObj 85
- OCXcip_UnregisterAssemblyObj 88
- OCXcip_RegisterFatalFaultRtn 90
- OCXcip_RegisterResetReqRtn 92
- 5.4 CIP Callback Functions 94
- 5.5 Connected Data Transfer 105
- OCXcip_WriteConnected 105
- OCXcip_ReadConnected 107
- OCXcip_ImmediateOutput 109
- OCXcip_WaitForRxData 111
- 5.6 Tag Access Functions 116
- OCXcip_AccessTagData 116
- OCXcip_CreateTagDbHandle 120
- OCXcip_DeleteTagDbHandle 121
- OCXcip_SetTagDbOptions 122
- OCXcip_BuildTagDb 125
- OCXcip_TestTagDbVer 127
- OCXcip_GetSymbolInfo 129
- OCXcip_GetStructInfo 132
- OCXcip_GetStructMbrInfo 135
- OCXcip_GetTagDbTagInfo 138
- OCXcip_AccessTagDataDb 141
- 5.7 Messaging 144
- OCXcip_GetDeviceIdObject 145
- OCXcip_GetDeviceICPObject 148
- OCXcip_GetDeviceIdStatus 151
- OCXcip_GetExDeviceObject 155
- OCXcip_GetWCTime 158
- OCXcip_SetWCTime 162
- OCXcip_GetWCTimeUTC 165
- OCXcip_SetWCTimeUTC 169
- 5.8 Miscellaneous Functions 172
- OCXcip_GetIdObject 173
- OCXcip_SetIdObject 175
- OCXcip_GetActiveNodeTable 177
- OCXcip_MsgResponse 179
- OCXcip_GetVersionInfo 182
- OCXcip_GetUserLED 184
- OCXcip_SetUserLED 186
- OCXcip_GetModuleStatus 188
- OCXcip_SetModuleStatus 190
- OCXcip_GetLED3 192
- OCXcip_SetLED3 194
- OCXcip_ErrorString 196
- OCXcip_SetDisplay 198
- OCXcip_GetDisplay 200
- OCXcip_GetSwitchPosition 202
- OCXcip_GetSerialConfig 204
- OCXcip_Sleep 207
- OCXcip_CalculateCRC 209
- OCXcip_SetModuleStatusWord 211
- OCXcip_GetModuleStatusWord 213
- 6 Cable Connections 215
- 6.3 RS-422 218
- 6.4.1 RS-485 and RS-422 Tip 219
- 7.2.1 Returning Any Product 221
- 7.3 LIMITED WARRANTY 223
- 7.3.8 No Other Warranties 229
- 7.3.9 Allocation of Risks 229
- 7.4 Open Source Licensing 230
- 7.5 GNU Public License 231
- 7.6 Eclipse Public License 245
- 7.7 Python Public License 251
- 7.8 GCC Public License 257
- 8 Glossary of Terms 260
Verwandte Produkte und Handbücher für Relais Prosoft-technology MVI56E-LDM
(55 Seiten)© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.071 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern