CAN@net II/Generic, Version 1.5
FAQ List
35
Operation
Q: Cannot connect to the ASCII-Protocol server.
A: Make sure that the network between your Internet Browser and the
CAN@net II/Generic is transparent for connections to TCP Port 19227.
This is especially the case when crossing network boundaries with
switches or gateways. Please check with your system administrator.
If the Ethernet (ETH) LED is red, the device is probably configured in
bridge mode, see 5.2 Device Configuration to set the device to server
mode.
Q: The ASCII-Protocol server sends many ERR_QUEUE_OVERRUN and
ERR_DATA_OVERRUN messages.
A: Every time the CAN@net II/Generic receives a CAN message on the
CAN bus and cannot hand it to the ASCII-Protocol server, it sends one of
these two error messages. One or more CAN messages will be
discarded. The CAN@net II/Generic is not able to follow the data rate of
your system.
Q: The CAN@net II/Generic does not send my ASCII-Protocol CAN
messages on the CAN bus.
A: Make sure that the CAN controller is initialized with the correct baud rate
and that it is started. Check the demo.cpp described in the manual as a
simple example.
Q: The CAN@net II/Generic forwards CAN messages from the CAN bus to
the Ethernet side with IDs which clearly are not listed in the filter list.
A: Make sure that filtering is enabled. This is done by selecting "enable" on
the filter configuration page of the CAN@net II/Generic Web Interface.
Q: The CAN@net II/Generic does not show all messages from the CAN bus
on the Ethernet side.
A: Check the current settings in the filter list (if enabled). Only CAN
messages with IDs set in the filter list are forwarded to the Ethernet side.
Q: If the connection to the ASCII-Protocol server is closed, the connection
could not be opened immediately.
A: Whenever the TCP connection is closed or timed out, the CAN@net
II/Generic reboots. The device starts again after 3 seconds with the
stored configuration.
