CAN connect issues

Topics about the Hardware of Revolution Pi
Post Reply
oddek2
Posts: 2
Joined: 12 Mar 2021, 16:34
Answers: 0

CAN connect issues

Post by oddek2 »

We have bought a CAN connect module, to use with our RevPi Connect.

We have hooked up the CANbus as showed in this forum post:
viewtopic.php?t=1932

And followed the guide located here:
https://revolution.kunbus.com/tutorials ... ansteuern/


When running: dmesg | grep can, we get this output, which looks fine:

Code: Select all

$ dmesg | grep can
[    4.616900] hi3110 spi0.0 can0: 3110 successfully initialized.
[  107.049422] IPv6: ADDRCONF(NETDEV_UP): can0: link is not ready
[  107.049463] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
And we check this command which also looks okay.

Code: Select all

$ ip -det -statistics link show can0
5: can0:  mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10
    link/can  promiscuity 0
    can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 0
          bitrate 50000 sample-point 0.875
          tq 1250 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
          hi3110: tseg1 2..16 tseg2 2..8 sjw 1..4 brp 1..64 brp-inc 1
          clock 16000000
          re-started bus-errors arbit-lost error-warn error-pass bus-off
          0          0          0          0          0          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    0          0        0       0       0       0
However, after enabling candump can0, and try to send a message using cansend, candump shows nothing. dmesg | grep can shows this:

Code: Select all

$ dmesg | grep can
[    4.616900] hi3110 spi0.0 can0: 3110 successfully initialized.
[  107.049422] IPv6: ADDRCONF(NETDEV_UP): can0: link is not ready
[  107.049463] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[  292.285353] can: controller area network core (rev 20170425 abi 9)
[  292.297811] can: raw protocol (rev 20170425)
And we can see that the can state has gone in to ERROR-PASSIVE:

Code: Select all

$ ip -det -statistics link show can0
5: can0:  mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10
    link/can  promiscuity 0
    can state ERROR-PASSIVE (berr-counter tx 128 rx 0) restart-ms 0
          bitrate 50000 sample-point 0.875
          tq 1250 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
          hi3110: tseg1 2..16 tseg2 2..8 sjw 1..4 brp 1..64 brp-inc 1
          clock 16000000
          re-started bus-errors arbit-lost error-warn error-pass bus-off
          0          0          0          1          1          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    0          0        0       0       0       0
The device we are trying to communicate with is a computer with an Ixxat USB-toCAN v2, at 50 kbps, with both highspeed and FT settings but nothing seems to work.

However, if we turn loopback on, we do get to see the messages we send in candump, however these are of course not sent over the bus.

We don't know whether or not this is a hardware error or software error and would greatly appreciate some help.

Kent.
oddek2
Posts: 2
Joined: 12 Mar 2021, 16:34
Answers: 0

Re: CAN connect issues

Post by oddek2 »

Dear Kunbus

It turns out that the schematic that is printed directly on the CAN Connect is WRONG.
Image

Regards Kent.
Post Reply