Please share a screen shot if possible. It will be important to make sure the driver is properly installed and registered with your system in device manager. Also, make sure only one application attempts to use the COM port of the USB to I2C Converter.
Thank You,
Ryan
Ok, it looks like the COM port COM9 is properly registered, this is a good sign.
Next, please run our AnyI2C software to communicate with the MCP23008:
A problem was discovered in the Scan function on earlier versions of firmware for the USB to I2C Converter. This has since been resolved. The device is fully functional other than scan. This list should only display the connected devices instead of all possible devices.
Nonetheless, please use the MCP23008 control panels in AnyI2C software to talk to your device, it should be really easy to use, but you might have to experiment with addressing. Do not install the pull-up jumpers when using our converter.
Thanks,
Ryan
Are you saying that you get both messages at the same time?
My experience was that I would only see one or the other. Regardless…on the surface it looks like the only difference between my situation and yours is that you are using I2C Version Set: 4 while I’m using I2C Version Set: 6. In any case it looks like the NcdSerialI2C.js driver has no support for any driver set above version: 3. My post explains how I was able to add a check for version 6 in the NcdSerialI2C.js file. Hopefully NCD will update their COM module soon and fix this issue. It’s not good for business.