I used the github copilot tui (since that was what my subscription was through) and told it what the devices were and what I was trying to accomplish. From there it was a mixture of different things to figure out how the protocols worked, like running the apps in wine and having it log and capture data as I changed settings, or have it flip bits and I would report to it what changed. If it discovers a component in the device is something off-the-shelf, have it find reference material from the component manufacturer.

As you figure out how a particular protocol works you have it document it until you have everything you need to build your own CLI to interface with the device. At that point you have a pretty good idea of how the device works and it’s capabilities and you can build out whatever features you want around it.

Oh I do pay for a subscription, just blew through my budget.

I have since moved to using mainly local models for everything. Running AI was why I was doing this PC build in the first place, just didn’t have it fully configured and I am wildly impatient when I get new stuff lol

I recently upgraded my PC and bought a case with a segmented display. Required a windows driver to work. I also bought a CPU liquid cooler with a display on it. Also required a windows app.

I threw about 30 bucks in tokens and now I have linux ports for both and with every added every feature I could come up with.

Now any weird or obscure piece of hardware I have that has been defunct for lack of software support has been getting the same treatment.