Public Support

Hi Balazs,

you are using Device Toolbox 3.0.0 (not BETA) ?

ADTF3 Can communication filters are not working at all.(CAN Config Decoder/Encoder, Demo CAN Decoder/Encoder)

First of all, what exactly are you trying to do ?
How is your session and how do you start ?

The error messages are very late so please check the complete console log what the errors are before.
If you are using GUI control, make sure your setup contains a console view service or use LOG Info Tool.

Second, what do you mean by these components are not working at all ?

„demo_can_decoder.cpp” source code is not available, at all. It is built already, but this way there is no way to make any changes in the ADTF3 CAN filter implementation.

• ./src/examples/src/can_config_decoder
• ./src/examples/src/can_config_encoder

• Demo CAN Config Encoder Filter
• Demo CAN Config Decoder Filter

And Using CMake with the ADTF Device Toolbox for how to build the examples again.

vxlapi64.dll -> DLL entry points are also giving errors (xlGetKeymanBoxes). Even though that the mentioned .dll file contains the entry point.

This is a different error right ?
This error is ADTF Plugin Description Generator, this has no connection to the runtime exception.

You are trying to generate a plugin description... for which component ?
What is your call in CMake ?
We know this error from the BETA but it is fixed in stable 3.0.0 release.

I guess your whole setup has one missing, so please check the log from my first suggestion.

Now with the new version of the device toolbox(STABLE 3.0.0), there are new error messages when we try to use the adtf filter “Vector Can Device Receiver” from the toolbox. Afterwards I added all services for can. I’m not sure what I have to configure in ADTF3. For example , how can I set the hardware ( Vector Box VN7600XL) in configuration editor? I have attached the screenshots about the errors.

Hi Balazs,

first of all, you should check the whole log for further information.
To do so, start the ADTF Log View Tool before launch and on the same URL, add the logging service to your session or use the launcher with --console option, then have a look at errors before.

Assuming, that you have a Vector Box (e.g.: VN7600, VN8970, etc.), a valid license and the boxes are already plugged in. Within the Vector Hardware Config Tool you have to connect the ADTF Application with the channels of your Vector Box.

Make sure CAN channel maps to the same you are using in ADTF.
For further information take a look into the Vector documentation (here). From this moment on, the ADTF Application (in combination with the Device Toolbox) is connected with the selected Vector Boxes and is ready to use.
If you set ADTF as application, it will match the default setup of the Receiver Streaming Source (property application_name).

That's it and should work.

Otherwise there must be more information in the log.

Hi Balazs,

using ADTF 3.4.0 and Device Toolbox 3.0.0 needs a patch, did use it ? -> Link

I guess the keyman error is not your problem, can you check the complete log ?
Is your Vector license on device or keyman dongle ?

But I guess there is another error before and you can ignore this bug.

Any further hints in the complete log ?

I attached the logs that the tester collegue sent me, using a VN7600. Normal, non Vector CAN messages can be read, but no Vector CAN messages. Is it possible that the keyman is only supported from VN8900?

Thank you in advance.