GESRTP Communication Driver error codes
- Last UpdatedSep 05, 2024
- 3 minute read
The following table lists the exception codes that the Communication Driver generates through the SRTP protocol. These error codes, with their server-specific strings, are logged to the Logger. The log flag for all these error codes is DASProtFail.
|
SRTP Error Code |
Logger Message |
|---|---|
|
DASProtFail Messages |
|
|
1 |
Illegal Service Request: either not defined or not supported. |
|
2 |
Insufficient Privilege: the minor status field contains the privilege level required for the service request. |
|
4 |
Protocol Sequence Error: the CPU has received a message that is out of order. |
|
5 |
Service Request Error: Minor status field contains the request specific error code. See table of Minor Error Status Codes below. |
|
6 |
Illegal Mailbox Type: Service request mailbox type is either undefined or unexpected. |
|
7 |
The PLC CPU's Service Request Queue is full. The master should retry later. It is recommended that the master wait a minimum of 10 ms before sending another service request. |
|
178 |
Program block already exists and cannot be replaced. |
|
179 |
Length limit exceeded; includes read past end of transferred data, writes past end of program block. |
|
180 |
Attempt to alter interrupt list in MAIN DECL BLOCK during RUN MODE. |
|
181 |
Additive checksum comparison in Verify failed. |
|
182 |
Cyclic Redundancy Check (CRC) checksum comparison in Verify failed. |
|
183 |
Segment length in Verify not equal to the segment length of block in the PLC. |
|
184 |
Size of the Segment Selector Table in TYPDEF record is not correct. |
|
185 |
Executable flag in TYPDEF record not set. |
|
186 |
Block Set already exists, cannot create. |
|
187 |
Maximum length of a partial store exceeded. |
|
188 |
Block Type (e.g., data) not found. |
|
189 |
Block Set (subblock name) not found. |
|
190 |
Bad Block Type given in Load/Store. |
|
191 |
Illegal OMF record type/data contents. |
|
192 |
Bad OMF record checksum in store. |
|
193 |
Invalid block state transition. |
|
194 |
The OEM key is NULL (inactive). |
|
195 |
Text length does not match traffic type. |
|
196 |
Verify with FA Card or EEPROM failed. |
|
197 |
No task-level Rack/Slot configuration to read or delete. |
|
198 |
Control Program (CP) tasks exist but requestor not logged into main CP. |
|
199 |
Password(s) already enabled and cannot be forced inactive. |
|
200 |
Password(s) already enabled and cannot be forced inactive. |
|
201 |
Login using non-zero buffer size required for block commands. |
|
202 |
Device is write protected. |
|
203 |
A comm or write verify error occurred during save or restore. |
|
204 |
Data stored on device has been corrupted and is no longer reliable. |
|
205 |
Attempt was made to read a device but no data has been stored on it. |
|
206 |
Specified device has insufficient memory to handle request. |
|
207 |
Specified device is not available in the system (not present). |
|
208 |
One or more PLC modules configured have unsupported revision. |
|
209 |
Packet size or total program size does not match input. |
|
210 |
Invalid write mode parameter. |
|
211 |
User Program Module (UPM) read or write exceeded block end. |
|
212 |
Mismatch of configuration checksum. |
|
213 |
Invalid block name specified in Datagram. |
|
214 |
Datagram connection boundary exceeded. |
|
215 |
Invalid Datagram type specified. |
|
216 |
Point length not allowed. |
|
217 |
Transfer type invalid for this selector. |
|
218 |
Null pointer to data in segment selector. |
|
219 |
Invalid segment selector in Datagram. |
|
220 |
Unable to find connection address. |
|
221 |
Unable to locate given connection ID. |
|
222 |
Size of Datagram connection invalid. |
|
223 |
Invalid Datagram connection address. |
|
224 |
Service in process cannot login. |
|
225 |
No I/O configuration to read or delete. |
|
226 |
IOS could not delete configuration or bad type. |
|
227 |
CPU revision number does not match. |
|
228 |
Segment for this selector does not exist. |
|
229 |
DOS file area not formatted. |
|
230 |
CPU model number does not match. |
|
231 |
Configuration is not valid. |
|
232 |
No user memory is available to allocate. |
|
233 |
Segment selector not valid in context. |
|
234 |
Not logged in to process service request. |
|
235 |
Task unable to be deleted. |
|
236 |
Task unable to be created. |
|
237 |
VMEbus error encountered. |
|
238 |
Could not return block sizes. |
|
239 |
Programmer is already attached. |
|
240 |
Request only valid in stop mode. |
|
241 |
Request only valid from programmer. |
|
242 |
Invalid program cannot log in. |
|
243 |
I/O configuration mismatch. |
|
244 |
Invalid input parameter in request. |
|
245 |
Invalid password. |
|
246 |
Invalid sweep state to set. |
|
247 |
Required to log in to a task for service. |
|
248 |
Invalid task name referenced. |
|
249 |
Task address out of range. |
|
250 |
Cannot replace I/O module |
|
251 |
Cannot clear I/O configuration. |
|
252 |
I/O configuration is invalid. |
|
253 |
Unable to perform auto configuration. |
|
254 |
No privilege for attempted operation. |
|
255 |
Service request has been aborted. |