id | lang | string |
---|
102 | 1033 | 0x0101@Failed to create Datalink component. |
103 | 1033 | 0x0101@Failed to create Transport component. |
104 | 1033 | 0x0101@Failed to create Application component. |
105 | 1033 | 0x0502@Failed no device connected or wrong channel number. |
106 | 1033 | 0x0101@Failed to get datalink, is the USB cable connected ? |
107 | 1033 | 0x0101@Failed to get cancontroller. |
108 | 1033 | 0x0101@Failed to create Simulation component. |
109 | 1033 | 0x0101@Failed to connect transport and datalink. |
110 | 1033 | 0x0101@Failed to connect transport and application. |
111 | 1033 | 0x0101@Failed to setup properties in kwp2000 layer. |
118 | 1033 | 0x0400@Data in ECUIdentificationScalingTable points outside ECUIdentificationDataTable or
data table contains undefined data. |
119 | 1033 | 0x0400@Data in ECUIdentificationScalingTable points outside the table itself or
contains wrong scaling information. |
120 | 1033 | 0x0400@ECUIdentificationScalingTable contains scaling not yet implemented. |
121 | 1033 | 0x0201@Requested test step not found in XML-file. |
122 | 1033 | 0x0201@Requested KWP-Service not found in XML-file. |
123 | 1033 | 0x0201@Security access key is missing in XML-file. |
124 | 1033 | 0x0400@Data in ECUScalingTable points outside the table itself or
contains wrong scaling information. |
125 | 1033 | 0x0400@ECUScalingTable contains scaling not yet implemented. |
126 | 1033 | 0x0201@Datadefinition requests data outside received data. |
127 | 1033 | 0x0201@Data is missing when creating a generic KWP-service. |
128 | 1033 | 0x0201@Value does not fit in defined bitfield. |
129 | 1033 | 0x0400@Invalid BCD-data. |
130 | 1033 | 0x0201@Value does not fit in defined scaling. |
131 | 1033 | 0x0201@Session definitions not found in XML-file. |
132 | 1033 | 0x0201@Session Modes definitions not found in XML-file. |
133 | 1033 | 0x0201@Requested data not found in XML-file. |
134 | 1033 | 0x0201@FingerPrint definitions not found in XML-file. |
135 | 1033 | 0x0201@ECU reset definitions not found in XML-file. |
136 | 1033 | 0x0502@More than one Scania VCI2 has power connected. |
137 | 1033 | 0x0400@Checksum could not be written in ECU. |
138 | 1033 | Create WorkManager failed. |
139 | 1033 | Create Product failed. |
140 | 1033 | 0x0602@No USB-key found. |
141 | 1033 | Failed to load SSK factory. |
142 | 1033 | Failed to create SSK instance. |
143 | 1033 | Init SSK failed. |
144 | 1033 | Create components failed. |
145 | 1033 | 0x0201@Data indication value is invalid in a KWP-service in XML-file. |
146 | 1033 | 0x0201@Data type for a value is invalid in a KWP-service in XML-file. |
147 | 1033 | 0x0201@Type of data in a KWP-service is invalid in XML-file. |
148 | 1033 | 0x0602@USB-key blocked. |
149 | 1033 | 0x0100@This response code indicates that an error is detected when creating a simulation file. |
150 | 1033 | 0x0400@Requested Id is missing in ECUScalingTable. |
151 | 1033 | Failed to load PSM factory. |
152 | 1033 | Failed to create PSM instance. |
153 | 1033 | 0x0303@Function not allowed when VCI connected to CAN. |
154 | 1033 | 0x0303@Failed to create KWP-loggfile/files. |
155 | 1033 | 0x0201@Error found in XML-definition for DutyCycles. |
156 | 1033 | 0x0400@Error found in responded data for a DutyCycle. |
157 | 1033 | 0x0201@Error found in XML-definition for FreezeFrames. |
158 | 1033 | 0x0400@Error found in responded data for a FreezeFrame. |
159 | 1033 | Used idtype is not implemented. |
160 | 1033 | 0x0201@Error found in XML-definition for Parameters. |
161 | 1033 | 0x0400@Error found in ECU-identification value. |
162 | 1033 | 0x0201@Error in created KWP-service definition. |
163 | 1033 | 0x0201@Error found in XML-definition for DynamicId. |
164 | 1033 | 0x0301@Dynamic id is not defined by application. |
165 | 1033 | 0x0301@Too many parameters for a Dynamic id. |
166 | 1033 | 0x0301@Mixed idtypes not allowed. |
167 | 1033 | 0x0201@Error found in dependency data. |
168 | 1033 | 0x0303@ECU-function already running. |
169 | 1033 | 0x0303@Not supported or relevant in demo mode. |
170 | 1033 | 0x0303@Not supported or relevant in batch mode. |
171 | 1033 | 0x0303@Busy executing a SCOMM internal function. |
172 | 1033 | 0x0303@Function not allowed when VCI is disconnected from CAN. |
173 | 1033 | 0x0501@There is no initialized CAN interface. The VCI CAN-components have not been loaded. Could be due to running SCOMM in permanent demo mode or that the VCI components are not installed. |
174 | 1033 | 0x0303@The connection password used when trying to connect to the network VCI was wrong. |
175 | 1033 | 0x0301@The Kvaser KvrLib library could not be loaded or setup for use, probably due to unavailable kvrlib.dll or one of its' dependencies |
176 | 1033 | 0x0303@There are too many network VCIs in the list of stored network VCIs. |
177 | 1033 | 0x0303@The network VCI cannot be connected to. It is probably because it is stored with too high index in the list of stored network VCIs (there is a built-in limitation). |
178 | 1033 | 0x0303@The license is not EnabledByConfig (the envelope can not be unlocked) or it is disabled or expired |
179 | 1033 | 0x0303@Failed to retrieve licenses. |
180 | 1033 | 0x0303@Failed to create licensehandler. |
181 | 1033 | 0x0303@Failed to create SCOMMConfigurationHandler. |
182 | 1033 | 0x0001@SCOMM configuration file has missing data or is corrupt. |
183 | 1033 | 0x0001@SCOMM configuration file is missing or wrong filepath. |
184 | 1033 | 0x0000@Dynamic activation error: |
185 | 1033 | 0x0000@This computer has already been activated. |
186 | 1033 | 0x0303@The supplied password used to open VCI for configuration was wrong. |
187 | 1033 | 0x0303@The read VCI configuration was verified as invalid or corrupt. Reset the VCI to factory configuration to be able to continue. |
188 | 1033 | 0x0003@The read VCI configuration could not be interpreted. Could be due to using a non-Scania tool to configure the VCI. If this happens, try to reset the VCI to factory configuration. |
189 | 1033 | 0x0003@The VCI configuration to write was verified as invalid or corrupt. This could be due to unfulfilled relations between different settings or wrong input checks. If it happens try to read the VCI configuration again. |
190 | 1033 | 0x0303@The VCI could not be opened for configuration. Another process might be using one of it's channels for CAN-communication (connected to CAN). |
191 | 1033 | 0x0303@The VCI is not a device that can be configured (at least not with this tool). It is not available for configuration. |
192 | 1033 | 0x0303@The VCI is not locally connected, which is required to perform requested action. |
193 | 1033 | 0x0001@There is no installed software license container. |
194 | 1033 | 0x0501@The supporting service for network VCIs is not running. |
195 | 1033 | 0x0303@The license update has allready been installed. |
196 | 1033 | 0x0303@A prior license update must be installed first in order to make this update. |
197 | 1033 | 0x0303@The loaded file is not a license update or the license update is corrupt. |
198 | 1033 | 0x0503@Device is currently being installed |
199 | 1033 | 0x0301@The Application Simulation Layer could not be loaded or setup for use, probably due to unavailable SCOMM_ApplicationSimLayer.dll. |
200 | 1033 | 0x0303@The VCI is configured with a non-empty data encryption password which is not supported by SCOMM. Reconfigure the VCI using Scania tools and try again. |
201 | 1033 | 0x0301@The application database (AppDataBase) is missing or corrupt. |
202 | 1033 | 0x0300@The license update is not valid for this computer. |
203 | 1033 | 0x300@Product key not found in license server. |
204 | 1033 | 0x303@There is no connection with license server. |
205 | 1033 | 0x303@Conditions not correct for erasing DTC(s). |
206 | 1033 | 0x0501@The ISO22900 DPDU dll is missing or corrupt. |
256 | 1033 | 0x0100@Datalink layer received illegal parameters when a function is called. |
257 | 1033 | 0x0100@Datalink layer is not initiated when a function is called. |
258 | 1033 | 0x0100@Datalink layer is not opened when a function is called. |
259 | 1033 | 0x0100@Datalink layer is not started when a function is called. |
260 | 1033 | 0x0502@Datalink layer has not found any device API. |
272 | 1033 | 0x0501@Datalink layer is indicating an internal error in the driver.
Indicates an error condition in the driver or DLL which couldn't be properly handled.
Please contact the friendly support at staff@kvaser.se. |
273 | 1033 | 0x0502@Datalink layer is indicating no channels avaliable.
There is indeed hardware matching the criteria you specified,
but there are no channels available, or the channel you specified is already occupied. |
274 | 1033 | 0x0500@Datalink layer is indicating no messages to read.
A function tried to read a message, but there was no message to read. |
275 | 1033 | 0x0502@Datalink layer is indicating specified device or channel not found.
There is no hardware available that matches the given search criteria.
For example, you may have specified canWANT_EXTENDED but there's no controller capable of extended CAN.
You may have specified a channel number that is out of the range for the hardware in question.
You may have requested exclusive access to a channel, but the channel is already occupied. |
276 | 1033 | 0x0501@Datalink layer is indicating out of memory.
A memory allocation failed. |
277 | 1033 | 0x0500@Datalink layer is indicating timeout.
A function waited for something to happen (for example, the arrival of a message),
but that something didn't happen. |
278 | 1033 | 0x0501@Datalink layer is indicating library not initialized.
The driver is not initialized. canInitializeLibrary() was probably not called? |
279 | 1033 | 0x0501@Datalink layer is indicating out of handles.
No handles are available inside canlib32. The application has too many handles open
(i.e. has called canOpenChannel too many times, or there's a memory leak somewhere.)
Note that we are not talking about Windows handles here, it's CANLIB's own internal handles. |
280 | 1033 | 0x0500@Datalink layer is indicating invalid handle.
The CANLIB handle you specified (if the API call includes a handle) is not valid. |
281 | 1033 | 0x0502@Datalink layer is indicating CAN driver mode not supported by the present hardware. |
282 | 1033 | 0x0501@Datalink layer is indicating transmit buffer overflow.
The transmit queue was full, so the message was dropped. |
283 | 1033 | 0x0502@Datalink layer is indicating a hardware error.
Something probably related to the hardware happened.
This could mean that the device does not respond (IRQ or address conflict?),
or that the response was invalid or unexpected (faulty card?) |
284 | 1033 | 0x0501@Datalink layer is indicating a driver DLL can't be found or loaded.
(One of) the DLL(s) specified in the registry failed to load. |
285 | 1033 | 0x0501@Datalink layer is indicating a DLL seems to have wrong version.
DLL version mismatch. (One of) the DLL(s) specified in the registry is
- probably - too old, or - less likely - too new. |
286 | 1033 | 0x0501@Datalink layer is indicating an error when initializing a DLL.
Something failed when a device driver was being initialized.
In other words, we can open the driver but it makes a lot of fuss about something we don't understand. |
287 | 1033 | 0x0501@Datalink layer is indicating a kernel driver can't found or loaded.
A device driver (kernel mode driver for NT, VxD for W95/98) failed to load;
or the DLL could not open the device. Privilegies? Driver file missing? |
288 | 1033 | 0x0501@Datalink layer is indicating DeviceIOControl failed. |
289 | 1033 | 0x0501@Datalink layer is indicating an error (missing data) in the Registry.
A registry key is missing, invalid, malformed, has gone for lunch or what not.
Program can_verify.exe might provide some insight. |
290 | 1033 | 0x0501@Datalink layer is indicating license not valid. |
291 | 1033 | 0x0501@Datalink layer is indicating an error in parameter.
Error in one or more parameters; a parameter specified in the call was invalid,
out of range, or so. This status code will also be returned when the call is not implemented. |
292 | 1033 | 0x0501@Datalink layer is indicating an error in the ini-file (16-bit only). |
293 | 1033 | 0x0501@Datalink layer is indicating that the operation is not supported
by hardware or firmware. |
294 | 1033 | 0x0501@Datalink layer is indicating that the kernel driver
could not be found or loaded. |
295 | 1033 | 0x0501@Datalink layer is indicating that the function DeviceIOControl failed. |
296 | 1033 | 0x0501@Datalink layer is indicating that required config s/w (e.g. CS/SS)
could not be founed. |
297 | 1033 | 0x0502@Datalink layer is indicating that the card was removed or not inserted. |
298 | 1033 | 0x0501@Datalink layer is indicating that the access was denied
to the requested functionality for some reason. |
299 | 1033 | 0x0501@Datalink layer is indicating that the requested feature or function
is not implemented in the device you are trying to use it on. |
300 | 1033 | 0x0501@Datalink layer is indicating that an error has occured when trying to access a file on the device. |
301 | 1033 | 0x0501@Datalink layer is indicating an error has occured
when trying to access a file on the host. |
302 | 1033 | 0x0501@Datalink layer is indicating a disk error has occurred.
Verify that the disk is initialized. |
303 | 1033 | 0x0501@Datalink layer is indicating that the CRC calculation
did not match the expected result. |
304 | 1033 | 0x0501@Datalink layer is indicating that the configuration is corrupt. |
305 | 1033 | 0x0501@Datalink layer is indicating other configuration error. |
306 | 1033 | 0x0501@Datalink layer is indicating a script has failed. |
307 | 1033 | 0x0501@Datalink layer is indicating an uknown errorreceived from KVASER API. |
336 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the function call failed (generic failure). |
337 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an unknown error occured. |
338 | 1033 | 0x0502@Datalink ISO22900 layer is indicating that the communication between host and MVCI protocol module failed. |
339 | 1033 | 0x0501@Datalink ISO22900 layer is indicating that the D-PDU API has not yet been constructed. |
340 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that a PDUDestruct was not called before another PDUConstruct. |
341 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the requested resource is already in use. |
342 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the requested resource table or module list has changed. |
343 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that something with the requested resource has failed. |
344 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the ComLogicalLink cannot be in the PDU_CLLST_OFFLINE state to perform the requested operation. |
345 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the ComLogicalLink must be in the PDU_CLLST_COMM_STARTED state to perform the requested operation. |
346 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that one or more of the parameters supplied are invalid. |
347 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that one or more of the handles supplied are invalid. |
348 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that one of the option values in PDUConstruct is invalid. |
349 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the IOCTL command id is not supported by the implementation of the D-PDU API. |
350 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the ComParam id is not supported by the implementation of the D-PDU API. |
351 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the physical ComParam cannot be changed because it is locked by another ComLogicalLink. |
352 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the ComLogicalLink's transmit queue is full; the ComPrimitive could not be queued. |
353 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that no more event items are available to be read from the requested queue. |
354 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the voltage value supplied in the IOCTL call is not supported by the MVCI protocol module. |
355 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the specified pin / resource are not supported by the MVCI protocol module for the IOCTL call. |
356 | 1033 | 0x0502@Datalink ISO22900 layer is indicating that the cable attached to the MVCI protocol module is of an unknown type. |
357 | 1033 | 0x0502@Datalink ISO22900 layer is indicating that no cable is detected by the MVCI protocol module. |
358 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the The ComLogicalLink is already in the PDU_CLLST_ONLINE state. |
359 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the physical ComParams cannot be changed as a temporary ComParam. |
360 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the resource is already locked. |
361 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the ComLogicalLink's resource is currently locked by another ComLogicalLink. |
362 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that the resource is already in the unlocked state. |
363 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the module is not in the PDU_MODST_READY state. |
364 | 1033 | 0x0501@Datalink ISO22900 layer is indicating that the API software is older than the MVCI protocol module software. |
365 | 1033 | 0x0501@Datalink ISO22900 layer is indicating that the MVCI protocol module software is older than the API software. |
366 | 1033 | 0x0502@Datalink ISO22900 layer is indicating that the requested pin is not routed by supported cable. |
367 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an invalid frame was received (e.g. wrong frame number, missing FC …) (CLL/CoP Error). |
368 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an error occured during transmit of a CAN frame (CLL/CoP Error). |
369 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an error encountered in transmitting a Tester Present message or in receiving an expected response to a Tester Present message (CLL/CoP Error). |
370 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the physical ComParam was not set because of a physical ComParam lock (CLL Error). |
371 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the receive timer (e.g. P2Max) expired with no expected responses received from the vehicle (CLL/CoP Error). |
372 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an error was encountered when receiving a message from the vehicle bus (e.g. checksum error …) (CLL/CoP Error). |
373 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that an protocol error was encountered during handling of a ComPrimitive (e.g. if the protocol cannot handle the length of a ComPrimitive) (CLL/CoP Error). |
374 | 1033 | 0x0502@Datalink ISO22900 layer is indicating that the communication to a MVCI protocol module has been lost (Module Error). |
375 | 1033 | 0x0503@Datalink ISO22900 layer is indicating that the MVCI protocol module has detected a hardware error (Module Error). |
376 | 1033 | 0x0501@Datalink ISO22900 layer is indicating that an failure occurred during a protocol initialization sequence (CLL/CoP Error). |
377 | 1033 | 0x0500@Datalink ISO22900 layer is indicating that an unknown error occured. |
512 | 1033 | 0x0502@Transport layer timeout, sending a CAN-frame. |
513 | 1033 | 0x0400@Transport layer timeout, waiting for a flow control frame. |
514 | 1033 | 0x0400@Transport layer timeout, wait for a consequtive frame. |
515 | 1033 | 0x0400@Transport layer received a consequtive frame with wrong sequence number. |
516 | 1033 | 0x0400@Transport layer received an unexpected PDU. |
517 | 1033 | 0x0400@Transport layer is indicating too many wait states received in flow control frames. |
518 | 1033 | 0x0100@Transport layer is indicating a busy state when sending a message is requested. |
519 | 1033 | 0x0100@Transport layer received illegal parameters when a function is called. |
520 | 1033 | 0x0100@Transport layer is indicating function not implemented. |
521 | 1033 | 0x0100@Transport layer is indicating an invalid interface. |
522 | 1033 | 0x0100@Transport layer is indicating an error when accessing a mutex. |
523 | 1033 | 0x0100@Transport layer is indicating no datalink connected. |
524 | 1033 | 0x0100@Transport layer is indicating a general error state. |
525 | 1033 | 0x0100@Transport layer is indicating an error in received confirmation from datalink. |
768 | 1033 | 0x0100@Application layer timeout, no confirmation. A message was sent
but the transport layer didn't receive within the given time limit. |
769 | 1033 | 0x0400@Application layer timeout, first frame indication too late.
The first frame of a responce message was not received from
the transport layer within the given time limit. |
770 | 1033 | 0x0400@Application layer timeout, indication received too late. A first
frame indication has been received from the transport
layer. But thereafter no indication showing that the
complete incomming message has been received within the
given time limit. |
771 | 1033 | 0x0400@Application layer timeout, a Response Pending has been received
from the transport layer. But thereafter no indication showing that the
complete incomming message has been received within the
given time limit. |
784 | 1033 | 0x0400@Application layer received illegal response. |
785 | 1033 | 0x0400@Application layer is indicating new request received prior to indication. |
786 | 1033 | 0x0100@Application layer is indicating message transmission disbled when request is transmitted. |
787 | 1033 | 0x0100@Application layer is indicating new request received prior to confirmation of transmitted request. |
788 | 1033 | 0x0100@Application layer waiting for confirmation. |
789 | 1033 | 0x0100@Application layer received zero length request from SCOMM. |
790 | 1033 | 0x0100@Application layer received illegal request from SCOMM wrong data format. |
791 | 1033 | 0x0100@Application layer is indicating no transport layer, transport layer not connected (created) . |
792 | 1033 | 0x0100@Application layer is indicating a general error state. |
793 | 1033 | 0x0100@Application layer received wrong data format, zero data length request from SCOMM. |
800 | 1033 | 0x0100@Application layer failed to set application layer specific properties (timeout settings ... ). |
801 | 1033 | 0x0100@Application layer is indicating an internal error. |
832 | 1033 | 0x0100@Application layer is indicating invalid message. |
833 | 1033 | 0x0100@Application layer is indicating unexpected confirmation. |
848 | 1033 | 0x0100@Simulation is indicating a thread running error. |
849 | 1033 | 0x0100@Simulation is indicating a error when sending a response. |
850 | 1033 | 0x0100@Simulation is indicating a found unkwon response type. |
851 | 1033 | 0x0100@Simulation is indicating an internal error. |
852 | 1033 | 0x0303@Simulation is indicating that the simulation file is missing. |
853 | 1033 | 0x0100@Simulation is indicating a scaling data handling error. |
854 | 1033 | 0x0100@Simulation is indicating a file type error. |
855 | 1033 | 0x0100@Simulation is indicating a response missing in database. |
856 | 1033 | 0x0100@Simulation is indicating request data is corrupt. |
857 | 1033 | 0x0100@Simulation is indicating a not implemented request. |
858 | 1033 | 0x0100@Simulation is indicating an error when reading the file. |
859 | 1033 | 0x0100@Simulation is indicating file version not implemented. |
1016 | 1033 | The service is rejected but the server (ECU) does not specify
the reason of the rejection. |
1017 | 1033 | This response code indicates that the requested action will not
be taken because the server (ECU) does not support the
requested service. |
1018 | 1033 | This response code indicates that the requested action will not
be taken because the server (ECU) does not support the
arguments of the request message or the format of the
argument bytes do not match the prescribed format for the
specified service. |
1033 | 1033 | This response code indicates that the server (ECU) is
temporarily too busy to perform the requested operation
and the requested service will not be started. In this
circumstance repetition of the "identical request message " or "
another request message" shall be performed by the
client (tester). This response code shall be returned for
example while a server (ECU) is in the process of clearing
stored DTC(s) information or fetching information |
1034 | 1033 | This response code indicates that the requested action will not
be taken because the server (ECU) prerequisite conditions
are not met. This request may occur when sequence
sensitive requests are issued in the wrong order. |
1035 | 1033 | This response code indicates that the request message was
properly received by the server (ECU) and the routine
(service), which has been initiated by the request message
is already in process, but not yet completed. The server
(ECU) knows in advance that the processing time is
greater than the P2 timing window. The successful
execution and completion of the request message will not
be indicated by a positive response message. |
1049 | 1033 | This response code indicates that the requested action will not
be taken because the server (ECU) detects the request
message contains a data byte(s) which attempt(s) to
substitute (a) value(s) beyond its range of authority (e.g.
attempting to substitute a data byte of 111 when the data
is only defined to 100). |
1051 | 1033 | This response code indicates that the requested action will not
be taken because the server's (ECU's) security strategy
has not been satisfied by the client (tester). |
1053 | 1033 | This response code indicates that security access has not
been given by the server (ECU) because the key sent by
the client (tester) did not match with the key in the server's
(ECU's) memory. This counts as an attempt to gain
security. The server (ECU) shall remain locked! |
1054 | 1033 | This response code indicates that the requested action will not
be taken because the client (tester) has unsuccessfully
attempted to gain security access more times than the
server's (ECU's) security strategy will allow. Refer to
message description of the securityAccess service definition. |
1055 | 1033 | This response code indicates that the requested action will not
be taken because the client's (tester's) latest attempt to
gain security access was initiated before the server's
(ECU's) required timeout period had elapsed. |
1064 | 1033 | This response code indicates that an attempt to download to a
server's (ECU's) memory cannot be accomplished due to
some fault conditions. |
1065 | 1033 | This response code indicates that an attempt to download to a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not support the type of download
being attempted. |
1066 | 1033 | This response code indicates that an attempt to download to a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not recognize the target address for
the download as being available. |
1067 | 1033 | This response code indicates that an attempt to download to a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not recognize the number of bytes
for the download as being available. |
1080 | 1033 | This response code indicates that an attempt to upload from a
server's (ECU's) memory cannot be accomplished due to
some fault conditions. |
1081 | 1033 | This response code indicates that an attempt to upload from a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not support the type of upload being attempted. |
1082 | 1033 | This response code indicates that an attempt to upload from a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not recognize the target address for
the upload as being available. |
1083 | 1033 | This response code indicates that an attempt to upload from a
server's (ECU's) memory cannot be accomplished because
the server (ECU) does not recognize the number of bytes
for the upload as being available. |
1113 | 1033 | This response code indicates that a data transfer operation
was halted due to some fault. |
1114 | 1033 | This response code indicates that a data transfer operation
was halted due to some fault, but will not be completed later. |
1116 | 1033 | This response code indicates that the starting address
included in a request message is either out of range ,
protected, the wrong type of memory for the receiving
data, or cannot be written to for some reason. |
1117 | 1033 | This response code indicates that the number of data bytes
included in the request message is either more than the
request message can accommodate, requires more
memory than is available at the requested starting address,
or cannot be handled by the software |
1118 | 1033 | This response code indicates that the
transferRequestParameter(s) included in the transferData
request message is (are) not valid for this application. |
1119 | 1033 | This response code indicates that the data checksum
calculated for the transferData messages does not agree
with the expected value. |
1120 | 1033 | This response code indicates that the request message was
received correctly, and that any parameters in the request
message were valid, but the action to be performed may
not be completed yet. This response code can be used to
indicate that the request message was properly received
and does not need to be re-transmitted, but the server
(ECU) is not yet ready to receive another request. |
1121 | 1033 | This response code indicates that the number of data bytes
that was expected to be sent was not the same as the
number of data bytes received. |
1128 | 1033 | This response code indicates that the requested action will not
be taken because the server (ECU) does not support the
requested service in the diagnostic session currently active. |
1144 | 1033 | This response code indicates that the requested action will not be taken because
the server (ECU) detects that conditions are not fullfilled. |
1145 | 1033 | This response code indicates that the diagnostic server (ECU) is not active. |
1146 | 1033 | This response code indicates failure in flash operation. |
1147 | 1033 | This response code indicates that the server (ECU) does not support multiframes in flashloading. |
1148 | 1033 | This response code indicates that the server (ECU) is executing in the boot loader code. |
1149 | 1033 | This response code indicates that the server (ECU) is executing in the application code. |
1316 | 1033 | This response code indicates that the requested action has been rejected by the server. |
1317 | 1033 | This response code indicates that the requested action will not be taken because the
server does not support the requested service. |
1318 | 1033 | This response code indicates that the requested action will not be taken because the
server does not support the service specific parameters of the request message. |
1319 | 1033 | This response code indicates that the requested action will not be taken because the
length of the received request message does not match the prescribed length for the specified service
or the format of the paramters do not match the prescribed format for the specified service. |
1333 | 1033 | This response code indicates that the server is temporarily too busy to perform the
requested operation. In this circumstance the client shall perform repetition of the identical request
message or another request message. The repetition of the request shall be delayed by a time specified in the respective
implementation documents. |
1334 | 1033 | This response code indicates that the requested action will not be taken because the
server prerequisite conditions are not met. |
1336 | 1033 | This response code indicates that the requested action will not be taken because the
server expects a different sequence of request messages or message as sent by the client. This may occur
when sequence sensitive requests are issued in the wrong order. |
1349 | 1033 | This response code indicates that the requested action will not be taken because the
server has detected that the request message contains a parameter which attempts to substitute a value beyond
its range of authority (e.g. attempting to substitute a data byte of 111 when the data is only defined to 100), or which
attempts to access a dataIdentifier/routineIdentifer that
is not supported or not supported in active session. |
1351 | 1033 | This response code indicates that the requested action will not be taken because the
server's security strategy has not been satisfied by the client. |
1353 | 1033 | This response code indicates that the server has not given security access because the
key sent by the client did not match with the key in the server's memory. This counts as an attempt to gain
security. The server shall remain locked and increment ist internal securityAccessFailed counter. |
1354 | 1033 | This response code indicates that the requested action will not be taken because the
client has unsuccessfully attempted to gain security access more times than the server's security strategy will allow. |
1355 | 1033 | This response code indicates that the requested action will not be taken because the
client's latest attempt to gain security access was initiated before the server's required timeout period had elapsed. |
1412 | 1033 | This response code indicates that an attempt to upload/download to a server's memory
cannot be accomplished due to some fault conditions. |
1413 | 1033 | This response code indicates that a data transfer operation was halted due to some fault. |
1414 | 1033 | This response code indicates that the server detected an error when erasing or programming
a memory location in the permanent memory device (e.g. Flash Memory). |
1415 | 1033 | This response code indicates that the server detected an error in the sequence of blockSequenceCounter
values. Note that the repetition of a TransferData request message with a blockSequenceCounter
equal to the one included in the previous TransferData request message shall be accepted by the server. |
1420 | 1033 | This response code indicates that the request message was received correctly, and that all parameters in
the request message were valid, but the action to be performed is not yet completed and the server
is not yet ready to receive another request. As soon as the requested service has been completed, the server shall send a
positive response message or negative response message with
a response code different from this. |
1426 | 1033 | This response code indicates that the requested action will not be taken because the server does not
support the requested sub-function in the session currently active. This response code shall only be used
when the requested sub-function is known to be supported in another session, otherwise response code SFNS
(subFunctionNotSupported) shall be used. |
1427 | 1033 | This response code indicates that the requested action will not be taken because the server does not
support the requested service in the session currently active. This response code shall only be used when the
requested service is known to be supported in another session, otherwise response code SNS
(serviceNotSupported) shall be used. |
1429 | 1033 | This response code indicates that the requested action will not be taken because the server prerequisite
condition for RPM is not met (current RPM is above a pre-programmed maximum threshold). |
1430 | 1033 | This response code indicates that the requested action will not be taken because the server prerequisite
condition for RPM is not met (current RPM is below a pre-programmed minimum threshold). |
1431 | 1033 | This is required for those actuator tests which cannot be actuated while the Engine is running.
This is different from RPM too high negative response, and needs to be allowed. |
1432 | 1033 | This is required for those actuator tests which cannot be actuated unless the Engine is running.
This is different from RPM too low negative response, and needs to be allowed. |
1433 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for engine run time is not met (current engine run time is below a pre-programmed limit). |
1434 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for temperature is not met (current temperature is above a pre-programmed maximum threshold). |
1435 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for temperature is not met (current temperature is below a pre-programmed minimum threshold). |
1436 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for vehicle speed is not met (current VS is above a pre-programmed maximum threshold). |
1437 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for vehicle speed is not met (current VS is below a pre-programmed minimum threshold). |
1438 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for throttle/pedal position is not met (current TP/APP is above a pre-programmed maximum threshold). |
1439 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for throttle/pedal position is not met (current TP/APP is below a pre-programmed minimum threshold). |
1440 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for being in neutral is not met (current transmission range is not in neutral). |
1441 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for being in gear is not met (current transmission range is not in gear). |
1443 | 1033 | For saftey reasons, this is required for certain tests before it begins, and must be maintained
for the entire duration of the test. |
1444 | 1033 | For saftey reasons, this is required for certain tests before it begins, and must be maintained
for the entire duration of the test. |
1445 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for torque converter clutch is not met (current TCC status above a pre-programmed limit or locked). |
1446 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for voltage at the primary pin of the server (ECU) is not met (current voltage is above a
pre-programmed maximum threshold). |
1447 | 1033 | This response code indicates that the requested action will not be taken because the server
prerequisite condition for voltage at the primary pin of the server (ECU) is not met (current voltage is below a
pre-programmed maximum threshold). |
16384 | 1033 | SCOMM internal common error. |
16385 | 1033 | 0x0300@Invalid argument received from application. |
16386 | 1033 | 0x0300@User has no access to requested function. |
16387 | 1033 | SCOMM internal pointer error. |
16388 | 1033 | 0x0300@Application requested a function not implemented. |
16389 | 1033 | 0x0300@Application requested an interface that does not exist. |
16397 | 1033 | 0x0300@ECU-function indicates an error. |
16398 | 1033 | 0x0300@ECU-function failed with an available result. |
65535 | 1033 | 0x0003@Function exited prematurely due to missing response(s) in batch mode.
Requests added to batch for execution. |