Q: Can I get the latest
Users Guide and Software Manual that are included with the kit?
A: The current
Win-I2CNTv4.x installation and software manuals are available:
Win-I2CNT
Users Guide Win-I2CNT Software
User Manual
Q: Does Win-I2CNT support
Win-XP 64-bit or Vista Operating Systems?
A: Win-I2CNT 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.
Q: Is a demo version of
Win-I2CNT available?
A: Download the fully
functional current version of Win-I2CNT from our software updates page:
http://www.demoboard.com/updates/
Q: Why is the connected
I2C bus device is not acknowledging the slave address?
A: Make sure the connected
I2C device documentation is not describing the slave address as 7-bits
+ R/W bit.
Win-I2CNT assumes 8-bit I2C slave addresses and the LSB (R/W bit)
is included as part of the address.
Q: How do I get upgraded
to the current released version of Win-I2CNT?
A: See the <regfrmxx.txt>
file in your current Win-I2CNT installation directory for the instructions.
Verify your current Win-I2CNT version via <Help-About> from the main
menu screen.
Q: Does Win-I2CNT support
I2C clock stretching?
A: Yes, it is configured
to support SCL clock stretching (by another slave device; up to 25mS).
Q: Does Win-I2CNT support
10-bit Addressing?
A: The Universal-Expert
Mode can be used for 10-bit device addressing; Example.
Q: Does Win-I2CNT support
I2C slave or bus monitoring functions?
A: Win-I2CNT is only
a I2C bus master. The I2C-Trace kit
supports I2C bus monitoring functions.
Q: If I am planning to
create my own I2C applications, does Win-I2CNT support this capability?
A: Win-I2CNT includes
two Universal Modes to allow supporting I2C devices not listed in the GUI
menus,
but does not support software code development.
The Win-I2CNTDLL kit also includes
the drivers and examples to write your own software applications.
Q: Can the Win-I2CNT printer
port adapter (I2CPort v2.0) be used with the Win-I2CNTDLL kit?
A: Yes, the printer port
adapter is designed to work with Win-I2CNT and the DLL.
Q: How can I connect a
longer cable between my PC (running Win-I2CNT) and my I2C target?
A: If more than 1M distance
is needed, a longer I2C cable is preferred over using a DB-25 printer extension
cable.
Exceeding
the maximum 400pf I2C bus capacitance may result in communication
error messages; try
a
slower I2C bus frequency.
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-I2C, 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 to 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
or PCF8582 ICs.
"Adapter Not Functioning" is usually caused by a damaged/overstressed IC
(>5v applied to the adapter stake connectors.
Replace these socketed DIP devices first before contacting us for repair;
this usually will solve the problem.
Q: What if Win-I2CNT reports
the error message: "Adapter Not Functioning" with only the adapter plugged
into the
printer port and no other I2C connections?
A: Remove the 256x8 EEprom
from the I2CPortv2.0 adapter and re-start the software. If this corrects
the error message,
then
the EEProm has been electrically damaged. Replace with Philips PCF8582C2N.
For additional help and
troubleshooting tips, refer to Appendix F in the Win-I2CNT
Users Guide
Dec 7, 2008