NSFW wrote:Welcome to the forum!
You might consider taking the code from the Devices and Ports directories of the PcmLibrary and PcmLibraryWindowsForms projects here:
https://github.com/LegacyNsfw/PcmHacks/ ... velop/Apps
That gives a Device base class with derived classes for all of the interfaces mentioned above. If you revise your app to use the Device class instead of talking to the Dice hardware directly, you can support the same set of devices. And maybe write a DiceDevice class for compatibility with that hardware.
The ELM and J2534 device classes are pretty mature, the XPro works but is still changing regularly (and the hardware isn't for sale yet), and the AVT code used to work... but something went wrong there and we need to investigate. Future changes will probably be small though, and you can pull the fixes from the PcmHack code when the bugs get worked out.
I have the source zip on my computer, thanks for the hint and that you allow me to do so
Unfortunately i really really really don't like C# and classes at all, coming from microcontroller development
But i will check it and if it can be integrated, for sure.
Using one library for communication in tools will surely have benefits...