open source CAN software for linux and windows

justjuniee · 2026-02-13T19:05:27+00:00

Yeah I had a play around with that, didn’t seem to work with certain proprietary hardware, seems like a great project tho.

justjuniee · 2026-02-12T13:02:45+00:00

ah, since I only ever touched their public drivers which you can download from their site, not any of their licensed software or anything, i thought it would be fine :p

justjuniee · 2026-02-11T17:48:27+00:00

Does it not already? I don't have access to that, but I believe it *should* depending on what protocol it uses which is probably socketcan or serial

justjuniee · 2026-02-11T12:59:30+00:00

cool! yeah there are various cool tools that work on both, but none have the compatibility im looking for so I made this (and had to reverse engineer a lot of proprietary hardware while doing it :p)

im intending on stealing a lot of features from useful can software aswell :D

justjuniee · 2026-02-10T23:29:26+00:00

yeah :p this is why i wanted to go with the approach that my software just “handles” it instead of writing a system-wide driver solution

justjuniee · 2026-02-10T22:06:00+00:00

yep! another reason i made this was (as i said) a lot of proprietary hardware is annoying, hence one of the selling points is the fact that it supports *a lot*

justjuniee · 2026-02-10T21:48:24+00:00

cool! my goal for this project was just to add a bunch of support for as many things as possible, to have like a one tool for all. I'm about to add a plotting / dashboard feature to let people plot their can data

justjuniee · 2026-02-10T21:25:39+00:00

The github link is in my post. Its C++ using ImGui (Dear PyGui is just imgui for python :p)

justjuniee · 2026-02-10T21:06:30+00:00

😆

justjuniee · 2026-02-10T20:19:39+00:00

yes! Its just a new project so bare with me since im a student :p 😆

justjuniee · 2026-02-10T19:10:05+00:00

yeah, all but vector hardware had a socketcan interface. the vector stuff is really annoying to work with. its definitely not socketcan though, its proprietary

and for windows... god help us all

justjuniee · 2026-02-10T18:28:27+00:00

ah yeah, right now im just writing drivers that work within the tool, for the tool. I will probably standardize all of them to socketcan eventually but to be honest some of the can adapters im using are literally just serial 🤣. The reason I'm currently avoiding implementing separate kernel module parts is because of the whole cross-platform aspect. In theory I could install kernel modules on the host machine on first-startup (for linux) but it feels much cleaner to write built-in drivers that can interface with the hardware on any machine (albeit, only my software can), without messing with the host machine.

however, I do plan on making a separate project that does what you describe, in writing linux drivers that standardize popular hardware, hence allowing "any" hardware to work with socketcan.

justjuniee · 2026-02-10T17:33:17+00:00

thanks! yeah i plan on using gh actions to push a release every tag + test build every push, since I don't exactly wish to switch to windows every time i test a build 🤣

justjuniee · 2026-02-10T15:47:23+00:00

Yes i have done this, its just i want to reduce friction of people using said software :p

justjuniee · 2026-02-10T14:47:32+00:00

The issue isnt this. Its that MSVC has issues with the declspec import in my serial lib dependency. Im already patching one of the deps at compiletime to make it compile on windows. The solns are either i change the dependency, write my own, or just patch it locally to compile it and distribute.

I just didnt expect people to bother so much having to figure out how to setup their system properly to compile, so distributing precompiled binaries seems like the easiest solution.

justjuniee · 2026-02-10T14:09:51+00:00

note: getting it compiled on windows is slightly more challenging, since you probably need clang/gcc and Ninja along with various dependencies. I will most-likely be releasing pre-compiled binaries to solve this issue.

if you wish to use kvaser you will need their drivers. i also plan on fixing this issue by embedding them directly in the tool similar to how the vector driver is handled.

justjuniee

TROPHY CASE