Firmware problems?

[HenrikSt]

Hello everyone,

I'm a newbee to CAN and unfortunately encountered a weird phenomenon when transmitting data. Question below.

In use is a PCAN-USB FD (Firmware-Version: 3.4.3) connected to a CAN2.0A Bus for setting up a communication in a CANopen protocol.
As in CANopen defined, Byte 1 and 2 of the data message are used to describe an index (in little-endian).
Transmitting an index from 0000h-3FFFh is working perfectly fine, but from 4000h-7FFFh the receiving device state they would receive an index 'subtracted by 4000h'. For example: Transmit Byte1=0x01, B2=0x40 => receive B1=0x01, B2=0x00.

When transfoming the Hex-numbers into binary it seems like it's always the 15th-Bit of the index, which do not switch to 1 when needed.
3FFFh : 0011111111111111 => received correctly
4000h : 0100000000000000 => not received correctly (0000h : 0000000000000000)
7FFFh : 0111111111111111 => not received correctly (3FFFh : 0011111111111111)
8000h : 1000000000000000 => received correctly
With this in mind I found out that the same Problem occours when sending Data with index higher than C000h:
C000h : 1100000000000000 => not received correctly (8000h : 1000000000000000)

Finally I come to my questions:
Are the devices takeing part in my CAN-Bus broke, while still beeing able to communicate just fine between each other? Or is there something wrong with my PCAN-USB FD?
At first I suspected PCAN-View (5.0.2), but I got the same problems with the Python API. So, I know it sounds rather unlikely, but is maybe the 'new' firmware the problem?
Had someone experienced similar problems with the second byte in the data message?

Greetings
Henrik

PS: Sorry if I wasted your time and the fault is at my CAN devices and not at the PCAN-USB FD

[M.Maidhof]

Hello Henrik,

to check if the problem is linked to the PCAN-USB FD, please connect another PC CAN monitoring device to your CAN Bus system, and check the transmitted CAN frames from the PCAN-USB FD.

regards

Michael

[HenrikSt]

Hello again,

That's kind of what I did. Though I've got just one PCAN and one from a third party.
And to add further complications: It seems I failed to recognize that the problem I descried is partly appearing in every second byte and not just when transmitting, but even when receiving.
I think I need to contact this third party provider. When it's not your fault his system (adapter and other devices) must have compatibility problems with CAN standard.

[M.Maidhof]

Hi,

can you please also send a screenshot of PCAN-View, to see what you have sent and what was received on the other side?

regards

Michael

[HenrikSt]

Here some examples. Some worked like expected, some not (highlighted).
Sent from top to bottom.

[M.Maidhof]

Hi,

can you please send a messages with all data bytes set to 0xFF and 0x00? And also send data to the PCAN-USB with data bytes set to 0x00 and 0xFF?

regards

Michael

[HenrikSt]

Again the recieving device reads different data (data subtracted by 40h) than sent with the PCAN-USB FD

[M.Maidhof]

Hi,

this looks like a hardware defect on the PCB. Please contact us by email using our support email address with the serialnumber of the device, to check the repair possibilities.

regards

Michael