-
Notifications
You must be signed in to change notification settings - Fork 604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding a generic CANalyst-II backend #1298
Comments
@projectgus Could you take a look? |
Oh wow, this is very interesting! @mikisama I did not actually know there was a "genuine" CANalyst-II from ZLG available for sale. Here's all of the versions I can find:
It seems like there are two ways forward:
@mikisama @zariiii9003 Can you share about the exact Canalyst-II that you have? A photo, where you bought it, when you bought it, etc? |
Hi, @projectgus I have this one USBCAN-II The stuff in this zip is a ZLG-compatible DLL and manual. |
Thanks, that's interesting. So the one you have is actually a "ZLG USBCAN" compatible clone, not "Canalyst-II" exactly. But it all works with the same ControlCan DLL and the "CANPro" ZLG software? The Shenyang Guangcheng Technology CAN protocol support in their documentation actually sounds better than the basic Canalyst-II protocol support which doesn't allow much detection of CAN bus errors. I am wondering if I should get one of these and write a pure Python backend for it as well. :) I think #1209 by @keelung-yang will add support for this USBCAN device again, because this PR is using the DLL as well. It's interesting that USBCAN worked in the old versions using the DLL for canalystii backend though, I didn't know this and I don't think the maintainers knew this! |
As discussed with supporters from ZLG, they may use incompatible libraries just for supporting Windows/Linux or CAN/CAN-FD, or even for the same product as asked by different clients. We also discussed In short, there are huge compatibility issues among ZLG official libraries. You cannot expect compatible APIs to manipulate ZLG CAN devices, as Kvaser/Vector/Intrepid..., only if ZLG decide to develop one. Or there're many many works need to be done for compatibility. Update:For ZLG official Windows python-can package, you can access this page https://manual.zlg.cn/web/#/169/6075 |
I want to use python-can [canalst-II] in pyhton 2.7, what can i do? |
You can try install the old version
|
Hi, guys.
Version 3.x of python-can worked well with my CANalyst-II. However, in version 4.x, I found that the backend of python-can for CANalyst-II has changed. My CANalyst-II can not work with python-can.
As far as I know, the genuine CANalyst-II is manufactured by ZLG, but there are many cloned CANalyst-II devices on the market, whose manufacturers provide ZLG-compatible DLLs.
Version 3.x of python-can can support CANalyst-II of different manufacturers by simply replacing the DLL.
Version 4.x of python-can may only support CANalyst-II devices from Chuangxin Technology.
Would you consider adding a 'generic' CANalyst-II backend like the 3.x version?
The text was updated successfully, but these errors were encountered: