Frequently Asked Questions for Win-I2CNTDLL:
 

Q: Can I get the current  DLL Software User's Manual that is included with the DLL kit?
A: Win-I2CNTDLL v4.x User's manual:
      Win-I2CNTDLL v4 Users Manual (pdf)

Q: Does Win-I2CNTDLL support Win-XP 64-bit or Vista Operating Systems?
A: Win-I2CNTDLL v5 now supports Win-XP and Vista 32/64-bit systems, but the hardware driver
    Limits I2C bus speed to the ~80khz range (PC system hardware dependent).   Users who need
    100khz+ I2C speeds and are not using XP-64 or Vista OS should continue using Win-I2CNT v4.x.
    Win-I2CNT v5 is now available from our Software Updates page (requires existing Win-I2CNTDLL
    v4/x installation).

Q: Are code examples included with the Win-I2CNTDLL v4.x kit?
A: Download them here:   Win-I2CNTDLL examples (zip archive)

Q: If I am a current user of Win-I2CNTDLL v3.2;  Do I need to upgrade to v4.2(4.7)?
A: If you need support for Windows XP, then you need the v4.2 DLL upgrade (requires changes to existing software);
    DLL Upgrade information

Q: How do I get upgraded to the newest version  of Win-I2CNTDLL?
A: If you wish to upgrade to DLL v5 (see note above) then please email us your user information and the serial number
     from the bottom of your I2CPort v2.0 adapter, or just email your completed <regfrmxx.txt> file from your current
     Win-I2CNTDLL v4.x  installation (Win-I2CNTDLL s/n is required).
     Email your info or regform to sales@demoboard.com
     We will email the DLL update once your S/N and information have been verified.

Q: Does Win-I2CNTDLL support I2C clock  stretching?
A: Yes, and the <SetWaitTime> function allows changing the value (see Win-I2CNTDLL Users Manual).

Q: Does Win-I2CNTDLL  support 10-bit Addressing?
A: Yes, and the Win-I2CNT Universal-Expert Mode can also be used for 10-bit device addressing; Example.

Q: Can the Win-I2CNTDLL printer port adapter (I2CPort v2.0) be used with the Win-I2CNT kit?
A: Yes, the printer port adapter is designed to work with Win-I2CNT and the DLL.

Q: How can a new application created for the DLL be used on another PC platform?
A: The target PC must first have Win-I2CNT v4.x software and the printer port adapter (I2CPortv2.0)  installed;
     the adapter can be from any licensed Win-I2CNT kit.  The DLL (sbsi2c4.dll) and hardware driver must be installed
     on the target PC platform; refer to the  Win-I2CNTDLL v4 Users Manual (pdf) for details.

Q: Can I get the latest Win-I2CNT Users Guide and Software Manual that are included with the DLL kit?
A:   Win-I2CNT Users Guide    Win-I2CNT Software User Manual

Q: Can I use any other printer port adapter with Win-I2CNT or Win-I2CNTDLL?
A:  No, the I2CPort v2.0 adapters included in the Win-I2CNT, and Win-I2CNTDLL kits are the only adapters
      that will work and have unique serial numbers assigned to them for the software user license.

Q: Can I power my target I2C board from the I2CPortv2.0 adapter?
A: In most cases, the current supplied via the PC printer port is only sufficient to power the adapter for
    purpose  of verifying the software/driver installation and correct adapter function. When connected to
    a I2C target board, VCC/SDA/SCL/GND from one of the three stake connectors should be connected to
    the I2C target and 3.3v or 5v  power supplied to the I2CPortv2.0 adapter from the target board.

Q: Do I need to supply VCC (5v or 3.3v) to the printer port adapter via the 4-pin stake connectors?
A: The I2CPort v2.0 adapter is self-powered from the PC's printer port and is usually sufficient to program
     the on-board 256B EEprom when running stand-alone. If the VCC/GND voltage at the 4-pin stake connectors
     is <3v (when the software/driver is running), then external 3.3v or 5v may be supplied to power the adapter.
    When the adapter is connected to your target system via the 4-pin stake connectors, it is recommended that
    the I2C reference pullup voltage (or VCC) from your target board be supplied to the adapter.

Q: What do I do if the adapter quits working (cannot even read/write the on-board EEprom)?
A: This can be caused by improper I2C connections to the adapter and possible damage to the 74HC05 IC;
     try replacing this socketed device first before contacting us for repair.
 

Back to Win-I2CNTDLL page

Dec 7, 2008