UM-0086-A2
CANgate User’s Manual
Page 35
Requested CAN data are not returned
Use
the
STATUS
command to check the status of the slot, and double check the slot definition parameters, as
described above.
Have you actually polled the slot? A common mistake is to simply enter a
RQST
command, which by itself will do
nothing (unless the sample rate parameter is specified). Normally an
RP
command is required, which (for slot 0
definitions) can be appended to the end of the request command eg.
RQSTJ 2 61444; RP
Try switching on the diagnostic message display using
DIAG 3
, then poll the request slot. You should see a
CAN
x
TX>
message. Check whether there is any reply shown from the ECU – it is possible that the ECU does not
implement this request.
For J1939, it may be necessary to set the CANgate's network address (default is 0) to a value that is unique on the
network. Use the
SETADDR
command for this. Note that CANgate does not implement the network address
management protocol described in SAE J1939/81.
GPS data are not returned
Use
the
STATUS
command to check the status of the slot, and double check the slot definition parameters, as
described above.
Ensure that the GPS port baud rate (set using the
GPSBAUD
command) matches that of the GPS unit.
Use
SNOOP GPS
to check the NMEA-0183 strings being sent by the GPS. If you don't see the string you want then
you may need to send a command to the GPS (using
GPSSEND
) to enable it. Verify that the required data item within
the string is present in the field number specified in the slot definition.
Data Logger reports timeouts or scan errors
In this case CANgate is connected to the serial sensor port on a DT80 series data logger.
Check that the logger's serial sensor baud rate has been set to match that of CANgate, eg.
PS=57600
Check flow control settings – by default, CANgate uses hardware flow control, so the logger serial sensor port should
also be set to hardware flow control, using
PS=HWFC
. If CANgate has been configured to use software flow control
then the logger must be set likewise (
PS=SWFC
), otherwise the XON and XOFF characters may appear in the
received data stream, which will probably disrupt the parsing of the returned data.
With the logger in pass-through mode, verify that CANgate is configured for normal operation with no extraneous
output (ie.
VERBOSE OFF;DIAG 0
).
With the logger in pass-through mode, verify slot definitions using
STATUS
. Manually send some of the commands
that the logger is sending in its
1SERIAL
channel definitions and check that CANgate is returning data. Check that
the format of the data matches that expected by the input conversion in the serial sensor control string (eg. if CANgate
is returning a floating point value then the serial sensor string should be set up to read a floating point value (
%f
) and
not, for example, an integer (
%d
))
Alternatively, enable diagnostic mode on the logger (
P56=1
), which will display data received on the serial sensor
port in conjunction with the input conversions which are endeavouring to parse it. By examining these, it should be
possible to determine why the input conversions are not working.
CANgate repeatedly resets
If CANgate detects a serious firmware problem then it will trigger a hardware reset. If this does not clear the problem then
repeated resets may occur. If this is the case then to regain control it may be necessary to set the internal DIP switches to the
Factory Defaults setting (see
), and cycle the power.
Error Messages
If
Verbose mode
is selected, CANgate will return a descriptive message in the event that a problem is detected with any
received command or operational situation. If verbose mode is switched off, no unsolicited messages will be returned;
erroneous commands will be silently ignored.
Syntax Errors
If there is a problem with a command or parameter, a message is returned indicating where the error occurred. For example:
Error: [ SWOOPJ<err> 2 5000 ]
In this case the problem is clear: a misspelt command; note that the
<err>
tag immediately follows the problematic
command or parameter.
Error: [ 3 RECVJ<err> 2 61444 ]
Here the command name is OK but it is not valid in this context (eg. a slot number has been specified but CANgate is not in
Program Mode, ie.
BEGIN
has not been seen.)
Error: [ SNOOPJ <err> ]
In this case the
<err>
tag is not attached to any particular parameter – so the problem here is a missing parameter
(
CANport
).
