Q: Can I get the
DLL User's Manual that is included with the kit?
A: Win-I2CUSBDLL(v4-v5) - DLL User's Manual
Q: Can I get the
Win-I2CUSB Software Installation Guide and Software Manual that are
with the kit?
A: Win-I2CUSBDLL (v5) - Installation & Hardware Manual Software User's Manual
Q: Where do I get
latest Win-I2CUSBDLL Software Updates?
A: Win-I2CUSBDLL v5.x is the newest version, and replaces all previous versions of the software.***
We recommend un-installing previous versions of Win-I2CUSBDLL before installing the new version to insure the
new drivers are properly installed. Download the new Win-I2CUSBDLL software from our software Updates Page.
Q: Is Win-I2CUSB/DLL
supported under Windows 7?
A: Win-I2CUSBDLL v5 supports Windows-XP/Visa/7 (32bit and 64bit). D/L latest version from our Updates Page.
Q: Is Win-I2CUSB/DLL
supported under Windows XP or Vista x64 platforms?
A: No, the USB driver does not support x64 platforms.
Q: ***Will The
kit work with a older Windows computer?
A: The latest software v5 supports Win-XP and newer Windows operating systems.
The latest v5 software does not support Win-2000, Win-NT, Win-98, Win-95, DOS, or other operating systems.
Q: Is a demo version
A: The full software version can be downloaded from the Updates Page and will function as a demo (without the hardware adapter).
Q: Is source
supplied with the Win-I2CUSBDLL kit?
A: We do not provide any source code.
Q: Win-I2CUSBDLL v4
was just installed, but Windows returns a "GDIplus.dll" missing error
attempting to run Win-I2CUSB
A: "gdiplus.dll" error received when starting the application is usually due to missing GDI+ files;
These fare available from Microsoft (search for "gdi+")\
Q: Can the
support byte-level commands that are available in Win-I2CNT/DLL
A: No, the USB version does not support the byte level commands that are available in Win-I2CNT.
The Win-I2CUSB adapter uses microcontroller hardware to generate I2C signalling, making byte-level commands
difficult, and the USB protocol would insert millisecond delays between bytes.
The parallel adapter (Win-I2CNT) generates I2C signalling directly using software toggling the hardware-port pins.
Q: How do I
the Serial Number of my USB-to-I2C hardware adapter:
A: The s/n sticker is located on the socketed (PLCC) controller IC (v2.2-v2.3) and on the PCB (v3.1) hardware adapters.
If the sticker is missing, the s/n can be read from the software main menu "Options".
The adapter must be connected to the PC USB port and detected by the software to read the s/n.
Q: When the
adapter is connected to the PC for the first time, Windows is asking
the USB driver;
where is the driver located?
A: The USB driver is located in the \Documentation directory of the Win-I2CUSBDLL v5 instllation CD included with the kit.
It is also located in the default HDD installed location: C:\Program Files\The Boardshop\Win-I2CUSB\USBDriver\
Q: Are code examples
with the Win-I2CUSBDLL kit?
A: Yes, basic examples are included on the installation CD for the supported enviornments, and can be downloaded
here: Win-I2CUSBDLL Examples (zip Archive)
support 10-bit Addressing?
A: Yes, and the Win-I2CUSB Universal-Expert Mode can also be used for 10-bit device addressing; Example.
Q: Can the
printer port adapter (I2CPort v2.0) be used with the Win-I2CUSBDLL kit?
A: No; the software, drivers, and DLL included with Win-I2CUSBDLL work only with the included USB-based I2C adapter.
Q: What connections
needed between the Win-I2CUSB adapter and a I2C target board?
A: Assuming the target is independetly powered (3.3v or 5v), only the SDA, SCL, GND connections are needed.
I2C pullup resistors for SDA/SCL should be provided on the target board and the two pullup resistor jumpers
(J_PU) on the adapter should be removed when connected to the I2C target board.
Q: Can I power my
I2C board from the Win-I2CUSB adapter?
A: Yes, but the maximum 5v or 3.3v current supplied to the target I2C board must not exceed 40-50mA, depending
on the enabled output voltage (3.3v or 5v) from the adapter. Separate 3.3v and 5v stake connectors (2-pin) are
provided for supplying power to the I2C target board.
Q: What are the
between Win-I2CUSB v2.2/v2.3 and v3.1 hardware adapters?
A: Win-I2CUSB v2.2 adapter uses a surface-mount USB connector, and v2.3 uses a thru-hole USB connector.
The newest v3.1 adapters use a newer design/architecture, but share the same connector configuration and
PCB dimensions as the earlier v2.x Win-I2CUSB adapters.
Note: Win-I2CUSB v3.1 adapters require the latest Win-I2CUSB/DLL v5 software/drivers; download from our Updates Page.
Q: What do I do if
adapter stops working properly?
A: Please email us and describe the details of the problem you are experiencing: firstname.lastname@example.org
Back to Win-I2CUSBDLL page