I’ve written lots of code to talk to FTDI devices in the past. I’m not sure why I can’t talk to this one, but writing 3 bytes to it never returns. I’m writing POSIX code on OS X. Any ideas? My I2C protocol analyzer doesn’t see any activity, the LEDs don’t blink when I write. The port is opened as 19200 bps, 8N2 (an odd config, but ok).
I have the USB-I2C, not USB-ISS (I wish I had realized there was a better adapter to buy). I tried installing the USB-I2C software on a pristine installation of XP SP3, after first installing the USB-ISS software. That installation installed .NET 4.0, but the USB-I2C installed .NET 3.5. When the USB-I2C installation tried to complete, it said it couldn’t be installed because it requires .NET 4.0, which is presumably already installed.
I hate Windows so much, it makes me want to stab my eyes out.
Do you have anything that’s not Windows? My windows VM died and I can’t seem to get it to recognize the CD to reinstall.
We (or at least I personally) share your emotion towards Windows.
The USB-ISS is indeed more versatile than the one you got. We would understand if you wanted to exchange it. Simply send us a message to the support centre and the Returns an Exchanges department will take care of the RMA.
Also, if your USB-ISS is not working with the sample programs in the page below, it might be indeed defective. You can send us a message to the support centre with your order number to exchange it.
robot-electronics.co.uk/htm/usb_i2c_tech.htm
Although we just tested one of these devices, we did not perform tests in Windows XP (only 7). So it might be an issue of drivers or software not being installed properly. As always (with windows), do not forget to restart the computer when in doubt.
We are sorry you are having troubles with RB-Dev-41. Is the device working with the sample programs available here: robot-electronics.co.uk/htm/usb_iss_tech.htm
If not, it might mean it is defective.