0 event messages, Malfunction event, Waiting for 5 baud init – ScanTool 5100 ECUsim User Manual
Page 10: Waiting for fast init, 0 error messages, Can error, Cmd not found, Ecu not found, Invalid, Invalid param count

ECUsim 2000/5100
10 of 13
www.obdsol.com
ECUSIMPMB
3.0 Event Messages
Status message, indicates that a Fault Event was
generated via the ‘Fault’ button press, or a software
command.
ECUsim is waiting for the OBD tester to start the 5-
baud ISO 9141 or ISO 14230 initialization sequence.
ECUsim is waiting for the OBD tester to start the fast
ISO 14230 initialization sequence.
<5 BAUD INIT: OK>
Detected a successful 5 baud initialization sequence.
Detected a successful ISO 14230-4 fast initialization
sequence.
All virtual ECUs had timed out, because a supported
request had not been received within P3
MAX
(ISO 9141-2
and ISO 14230-4 protocols).
UART transmit buffer overflow detected.
4.0 Error Messages
CAN ERROR
The CAN peripheral had trouble transmitting or
receiving messages. Possible causes include:
Device not connected to the CAN bus
Wrong protocol/CAN baud rate
Wiring problem
CMD NOT FOUND
Unrecognized command.
ECU NOT FOUND
Specified ECU does not exist.
INVALID
Incorrect command syntax, or the command is not
appropriate for the context (e.g., send OBD message while
the protocol is set to NONE).
INVALID PARAM COUNT
Too few or too many parameters specified.
OUT OF MEMORY
Not enough available RAM to complete the requested
operation.
PARAM ERROR
Invalid parameter specified.
PROTOCOL LOCKED
Unable to switch to the specified protocol, because
the protocol has not been enabled.