Hardware setup

XCP device definition

Devices are defined in Hardware setup. Add button will add one device and Remove button will remove selected one. There is no auto detection so all device parameters must be entered manually. Interface type (CAN or ETH), name, ASAP (a2l) file have to be set for both interfaces. Have in mind that ASAP file name is used as unique identification of device. This unique identification will also be used when loading setup. Then each interface has few additional parameters: -For Ethernet device IP address and both side ports (Remote and Local) must be defined. -For CAN device CAN port (port number from Hardware setup CAN port list) must be selected. Selected CAN port will then be exclusively assigned to XCP plugin. No checking is done if CAN port exists and if it’s really connected to XCP device. So double check if you entered the right port. Second parameter is Baud rate. It must be selected even if it’s the same as chosen CAN default baud rate.

CAN setup

CAN port operation mode must be set to Acknowledge to use it for XCP data transfer. None special device should be selected.

Connecting

Each device can be connected separately. Because CAN busses can’t be used in hardware setup the connection for CAN devices is moved in channel setup. Device hardware settings are disabled and can’t be changed if device is connected.

Ethernet

ETH device can be connected in HW setup (and it is automatically connected when Dewesoft starts). You can see connect/disconnect button on the left and status on the right.

CAN

CAN device can’t be connected in HW setup. They should be connected in XCP channel setup or will be automatically connected when measurement starts. It’s better to connect it manually before starting measurement, because there is no guarantee that connection will be successful when staring measurement. Connecting on measurement start will also cause additional delay

Timing

There is also additional timing option for CAN interface. Normally the XCP timing will be used for synchronization, but with CAN there is alternative. CAN timing (time of CAN messages) can be used for synchronization. If CAN timing is used additional fixed delay can be defined.

Some devices do not support XCP timing. In those cases CAN timing is the only choice.

Setup

Setup can be done online (when device is connected) or offline (when it’s not). Data acquisition is not running in setup, so there is also no data preview in setup mode.

All the signals are already defined in ASAP file (a2l). They are read and shown in device channel setup. If they are grouped also the tree view can be used. Channels just need to be selected and connected to suitable event. In addition also prescaler can be selected if needed (signal sampling rate will be devided by it). Colors and names can also be changed directly in the list.

Keep in mind that XCP device and used bus have limitations and select just the channels which are really needed.

Other signal parameters can be accessed with setup button. This way all signal information is shown and can also be changed.

Measure

In measure mode XCP signals are Dewesoft channels like any other. They are grouped by devices in channel selector.

Because of XCP device and used bus limitation it can happen that some signals data will not be transferred. For example 8byte signals can’t be sent over CAN bus.