question

bathnm avatar image
bathnm asked

BMS Can and VE.Can on Cerbo GX

Having a few Can Bus issues with my Cerbo GX on both 2.62 Beta and 2.70 Beta.

The BMS Can Port is set to Can-bus BMS (500kbits) and the network screen shows

1612560057186.png


Command line does not show a can1 port...

root@einstein:~# dmesg | grep can

[ 3.378239] sun4i_can 1c2bc00.can: device registered (base=(ptrval), irq=60)

[ 34.800622] can: controller area network core (rev 20170425 abi 9)

[ 34.822224] IPv6: ADDRCONF(NETDEV_UP): can0: link is not ready

[ 34.832059] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready

[ 35.296992] can: raw protocol (rev 20170425)



and

root@einstein:~# ifconfig can1

ifconfig: can1: error fetching interface information: Device not found



do I have a hardware issue, software issue?
cerbo gxVenus OS
1612560051045.png (51.3 KiB)
1612560057186.png (51.3 KiB)
4 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Stefanie (Victron Energy Staff) avatar image Stefanie (Victron Energy Staff) ♦♦ commented ·

What do you have connected to the BMS.Can port?

What is the output of 'ip link show' ?

0 Likes 0 ·
bathnm avatar image bathnm Stefanie (Victron Energy Staff) ♦♦ commented ·

It is not shown. The system does not detect it. I think I have a hardware issue. It appeared briefly during today and has gone again.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1450 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000

link/ether 02:44:05:42:91:9d brd ff:ff:ff:ff:ff:ff

3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 100

link/can

4: wifi0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1450 qdisc pfifo_fast state DOWN mode DORMANT group default qlen 1000

link/ether 28:ed:e0:2c:ef:fa brd ff:ff:ff:ff:ff:ff

5: disabled-wlan1: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000

link/ether ac:5d:5c:c6:cd:80 brd ff:ff:ff:ff:ff:ff

6: ap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc mq state UP mode DEFAULT group default qlen 1000

link/ether ae:5d:5c:c6:cd:80 brd ff:ff:ff:ff:ff:ff

7: ll-eth0@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1450 qdisc noqueue state LOWERLAYERDOWN mode DEFAULT group default qlen 1000

link/ether ce:dd:b4:ec:94:d9 brd ff:ff:ff:ff:ff:ff

8: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 3

link/ppp

9: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100

link/none


0 Likes 0 ·
Stefanie (Victron Energy Staff) avatar image Stefanie (Victron Energy Staff) ♦♦ bathnm commented ·

Too bad.

I'm running the 2.70 beta as well, but no problems with that port. Guess you tried rebooting. I don't know of any troubleshooting except what's under debugging here: https://github.com/victronenergy/venus/wiki/canbus#debugging. But doesn't make sense when the port doesn't show up.So maybe time to have it replaced under warranty.

0 Likes 0 ·
bathnm avatar image bathnm Stefanie (Victron Energy Staff) ♦♦ commented ·

Yes rebooted, checked all cabling, termination ,etc.

0 Likes 0 ·
1 Answer
mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

Hey @Bathnm strange to have a hardware failure on that, but then again - nothing is impossible.


I recommend contacting your dealer. Apologies for the trouble

3 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

bathnm avatar image bathnm commented ·

@mvader (Victron Energy), I have had both my original unit and the RMA unit start working again. I have not had a chance to dig any further, but the only think to change was taking them both back to 2.6x images. I was on the boat today and it worked happily. At some stage I will take it back to 2.70 and see what happens. Maybe there is a kernel level driver change that is impacting things in 2.70. I will keep you informed if I see anything,

0 Likes 0 ·
Show more comments