With Version 3.60~68 and also 3.60~69 my external USB-CAN BMS Adapter ( CAN1) which is connected to my Pylontech Master did not work anymore.
It seems the adapter is no longer recognized. Even a reboot doesn’t help. I’m now back to version 3.60~59 and the adapter is working again.
Hi, we’ve sent you an email yesterday, can you have a look and reply?
It asks if its ok for is to login, to enable remote support, and paste the vrm url.
Thanks!
Hello, I didn’t see the email because it was in spam. I just replied, and remote support is now enabled. Thanks for your support !!
1 Like
Hello, I’m still having the same problem with version 3.60~72, so I’ve gone back to version 3.60~59. Will you be able to resolve this issue in future versions?
Hi, we checked by logging in - and somehow the adapter you’re using doesn’t work with the latest linux kernel / its drivers.
So thats out of our hands I’m afraid.
I recommend you complain at the supplier. Kernel version we’re using is 6.12.23. Very recent LTS version.
We tried a usb can adapter we have, and that works well.
Thank you for the answer.
Oh, that doesn’t sound good 
We actually use a widely used adapter from Innomaker:
As far as I know, some other users also use this adapter, so many others will have problems as well.
Yes sorry to hear that.
I see you made an issue here 
:
We have tested this one, which works OK: https://canable.io/.
More information here: RaspberryPi CAN Interfaces · victronenergy/venus Wiki · GitHub
I did another update yesterday to check a few things, and I noticed that there might be a general problem with the CAN port assignments, as CAN0 (VE CAN) and CAN1 on my external USB-CAN were somehow swapped. Maybe you should take another look at your system. I have a feeling something’s wrong and maybe there is no driver problem at all.
Hi again, I can always reproduce the problem now. After the update, my two CAN ports are swapped!!
Normally, the VM-3P75C Energy Meter is bound to “VE.Can port” in the settings, and my USB-CAN adapter is bound to “can1.”
With the new firmware, however, the Energy Meter no longer works until I change the settings from “can1” to "VE.Can & CAN-Bus BMS (250 kbps).
Normally, “can1” is set to "CAN-Bus BMS LV (500 kbps), which is correct for my USB-CAN adapter.
So what I’m trying to say is that after the update, the two CAN ports are somehow swapped, so I don’t think the problem is the drivers.
Hi @jupzup thanks for the further details.
We checked and indeed its possible that this re-ordering happens. There is no mechanism in place in Venus OS now, to, in a deterministic manner, define what name a usb connected CAN interface gets internally.
We’ll look into this - but not before doing the official v3.60 release. And possibly / probably quite a bit later.
I could be wrong, but can’t he use udev symlinks?
Maybe. Maybe not.
But we’re not now going to help with that I’m afraid.
If there is a way around - great.
If not, then the solution for now is to stick to v3.55.
Hi Matthijs, will you look at this again?
hey @jupzup,
The open issue for you is the re-ordering and naming of interfaces - right?
At some point yes. But not now sorry.
Using a USB-CAN device is quite rare, not an officially supported feature, and making this work 100% is not some trivial simple fix that anyone in the dev team can take care of.
Sorry, but in the light of the above said, what about these?
Are they not officially supported?
In the end, it’s your advertised product…
We don’t provide official support for the raspberrypi.
And exactly the issue that is going on here has been mentioned on that page you linked to. By the looks of it for years already.
I don’t understand why we need to discuss this. Surely you can’t expect us to dive onto each and every corner case, especially with a raspberrypi
And the product used here isn’t even the victron usb can dongle.
Its some other device, apparently broken, or not, in a recent kernel.
And the people responsible for the product are not even responding to that issue.
For the raspberrypi we need more doing and less discussing (!).
Yes that’s right…I think that is the problem and not a driver issue cause the USB Dongle is recognized correctly.
Many thanks for your support !!!
Come on… Peace 
- Apologies, if I push it too much
- Your response alone (tone and come back) shows that you care and for that, thank you!
I really like your environment and, like I kid, I always go for/want an additional candy.
But like my psychologist SWMBO says, limits must be imposed for such kids… 
ok