The CAN Update mode is a little more complex than the USB Update mode. Many
things have to be considered. Otherwise the transfer won't work or the CAN network
can be damaged.
1. The ClientUpdater uses as default CAN Port 2 on the device. If you want to
use instead CAN Port 1 you can change the port here .
If the ClientUpdater uses the same CAN Port as a CAN Protocol in the
project, please always check that the Baud rate for the ClientUpdater is the
same as the one in the used CAN Protocol in the project.
2. To transfer the project between HostUpdater and ClientUpdater, 4 CAN IDs
will be used. These 4 CAN IDs are neccesary and will all be used.
The IDs can be changed here . Please check, in case another protocol is
running on the same CAN Port, that the CAN IDs won't be used by any other
entity connected to the port.
3. The ClientUpdater only enables the CAN Interface if the value of the pre-
defined variable @EnableUpdater has been set to 0x2 or 0x3. So check if
the variable is set properly in the project (e.g. in a script for the event
OnProjektInit).
4. The first project update has to be done via the USB drive . With this update
the new CAN Settings for the device will be set. Only then the CAN interface
can be enabled and will not damage your CAN network.
Please follow these steps carefully.
To Next Page
Loading...