Review on 📱 I2CDriver by Excamera by Alexis Guiney

I had high hopes for I2CDriver. I bought it a few months ago (September 2019) and put it on the bench for future I2C monitoring and debugging efforts. Well, today was the day - I installed the GUI this afternoon while testing the functionality of the I2C port on the microprocessor I'm building. I immediately noticed that the GUI often failed to start - even though two processes were started each time. it was a double click (checked in task manager). When it ran (about 1 try out of 10) it was a crappy shooter as to whether it recognized the USB port of the I2CDriver device. - in less than half of the cases nothing would be in the drop-down port window; Other times I've seen a COMx port connected to an I2CDriver connected to my PC's USB port. I'm running Windows 10 (fully updated) on a Surface Book 2 so my platform is solid and I use it on a daily basis. When the GUI started it froze from time to time and I had to kill it via the task manager. I've tried everything: and turning off the I2CDriver (by unplugging the USB cable), running the GUI with the I2CDriver disconnected from the target hardware. I2C, starting the GUI with an I2CDriver connected to the target I2C hardware port, restarting the GUI multiple times (this is where I ran into bad stats on successful startup), uninstalling and reinstalling the GUI. all to no avail and much disappointment. I've also tried all of the above workarounds with a known good I2C port/processor and a connected device - no fun except about 10% success with each hardware target where the GUI actually starts and allows monitoring of the I2C port on the Device I2C driver. But even when the GUI ran successfully, the logging feature (if enabled through the GUI) failed to fill the CSV file with data, even though an empty file was created. I will say that when the I2C DID monitoring function started on the I2CDriver's LCD after enabling it via the GUI, it was pretty smooth. In my opinion, I2CDriver just needs to be MUCH more stable to be useful and trustworthy. I REALLY wanted this product to work reliably as it would be very handy for I2C debugging - hopefully it catches on; or vice versa, my experience is limited to a defective device. I will also add that the online manual needs some work, but my main criticism is the stability of the actual product. FYI: I'm an electrical engineer with over 20 years of experience in hardware and embedded software design, so I'm not exactly new to the art or use of such products. My home lab (where I'm trying to use this device right now) competes with what I usually use at work, so I pretty much live by it.