-
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
Add ZLG interface #1209
base: main
Are you sure you want to change the base?
Add ZLG interface #1209
Conversation
Hey @keelung-yang, I did see your proposal (🥳!) but I currently do not have time to review it. Sorry for that 😒. |
@felixdivo Thanks. It's OK for waiting and improving my code in actual usage before merging. |
ZLG can interface has added by #1351 |
@keelung-yang would you mind reviewing #1351 and comparing? |
Hi @hardbyte & @zhuyu4839 ZLG should take response for universal APIs to access their various CAN devices, like others, such as kvaser and so on. But they don't want, according to the communications with their technical assistants and developer. Even for the same device, such as USBCAN(FD), there are 3 different bundles of API just for CAN or CANFD, Linux or Windows. That's why zhuyu's API wrapping is very long, almost 1500 lines: https://github.com/zhuyu4839/zlgcan-driver/blob/main/zlgcan/zlgcan.py ZLG tried to add their offical python-can interface implement before releasing python-can v4.0. But they gave up: https://manual.zlg.cn/web/#/169/6070 For my implement, I don't want to be disarray by ZLG's native libraries. And on the other hand, on Windows, ZLG has official GUI app and development libraries which reqiring VC runtime 2005、2008、2010、2012、2013(https://manual.zlg.cn/web/#/152/5332). So, let's goto Linux since I have to use them in my daily work, and share if others want too. In short, ZLG APIs are in chaos, users should take care of oneself. For python-can, it's hard to implement universal APIs to support almost all ZLG CAN devices, both in CAN and CANFD, Linux and Windows. Only when ZLG want to do that. P.S. for zlgcan-driver project, containing .so/.dll from ZLG is not a good idea since they should be published by the vendor ZLG. |
I have separated the code for different platforms. |
what's up with checks? I can't see details. |
I reran the tests. I'd prefer if this was implemented using the plugin interface |
I see this log in some checks:
That's because I do have no any .so file uploaded into repository. |
No description provided.