MAX17043/MAX17044
Compact, Low-Cost 1S/2S Fuel Gauges
with Low-Battery Alert
10
Figure 6 shows an example application for a 1S cell
pack. The MAX17043 is mounted on the system side
and powered directly from the cell pack. The external
RC networks on V
DD
and CELL provide noise filtering of
the IC power supply and A/D measurement. In this
example, the ALRT pin is connected to the micro-
processor's interrupt input to allow the MAX17043 to
signal when the battery is low. The QSTRT pin is
unused in this application, so it is tied to GND.
Figure 7 shows a MAX17044 example application using
a 2S cell pack. The MAX17044 is mounted on the sys-
tem side and powered from a 3.3V supply generated
by the system. The CELL pin is still connected directly
to PACK+ through an external noise filter. The ALRT pin
is left unconnected because the interrupt feature is not
used in this application. After power is supplied, the
system watchdog generates a low-to-high transition on
the QSTRT pin to signal the MAX17044 to perform a
quick-start.
PACK-
PACK+
PROTECTION IC
(Li+/POLYMER)
SYSTEM GND
SYSTEM V
DD
BATTERY SYSTEM
MAX17043
CELL
EP
1µF
1k
10nF
150
GND
CTG
SCL
SDA
QSTRT
V
DD
ALRT
SYSTEM µP
I
2
C BUS
MASTER
INTERRUPT
INPUT
4.7k
Figure 6. MAX17043 Application Example with Alert Interrupt
PACK-
PACK+
PROTECTION IC
(Li+/POLYMER)
SYSTEM GND
SYSTEM V
DD
BATTERY SYSTEM
MAX17044
CELL
1µF
1k
GND
CTG SCL
SDA
QSTRT
V
DD
SYSTEM PMIC
SYSTEM µP
I
2
C BUS
MASTER
3.3V OUTPUT
WATCHDOG
ALRT
EP
Figure 7. MAX17044 Application Example with Hardware Reset
MAX17043/MAX17044
Compact, Low-Cost 1S/2S Fuel Gauges
with Low-Battery Alert
11
2-Wire Bus System
The 2-wire bus system supports operation as a slave-
only device in a single or multislave, and single or multi-
master system. Slave devices can share the bus by
uniquely setting the 7-bit slave address. The 2-wire
interface consists of a serial-data line (SDA) and serial-
clock line (SCL). SDA and SCL provide bidirectional
communication between the MAX17043/MAX17044
slave device and a master device at speeds up to
400kHz. The MAX17043/MAX17044s’ SDA pin operates
bidirectionally; that is, when the MAX17043/MAX17044
receive data, SDA operates as an input, and when the
MAX17043/MAX17044 return data, SDA operates as an
open-drain output, with the host system providing a
resistive pullup. The MAX17043/MAX17044 always
operate as a slave device, receiving and transmitting
data under the control of a master device. The master
initiates all transactions on the bus and generates the
SCL signal, as well as the START and STOP bits, which
begin and end each transaction.
Bit Transfer
One data bit is transferred during each SCL clock
cycle, with the cycle defined by SCL transitioning low-
to-high and then high-to-low. The SDA logic level must
remain stable during the high period of the SCL clock
pulse. Any change in SDA when SCL is high is inter-
preted as a START or STOP control signal.
Bus Idle
The bus is defined to be idle, or not busy, when no
master device has control. Both SDA and SCL remain
high when the bus is idle. The STOP condition is the
proper method to return the bus to the idle state.
START and STOP Conditions
The master initiates transactions with a START condi-
tion (S) by forcing a high-to-low transition on SDA while
SCL is high. The master terminates a transaction with a
STOP condition (P), a low-to-high transition on SDA
while SCL is high. A Repeated START condition (Sr)
can be used in place of a STOP then START sequence
to terminate one transaction and begin another without
returning the bus to the idle state. In multimaster sys-
tems, a Repeated START allows the master to retain
control of the bus. The START and STOP conditions are
the only bus activities in which the SDA transitions
when SCL is high.
Acknowledge Bits
Each byte of a data transfer is acknowledged with an
acknowledge bit (A) or a no-acknowledge bit (N). Both
the master and the MAX17043 slave generate acknowl-
edge bits. To generate an acknowledge, the receiving
device must pull SDA low before the rising edge of the
acknowledge-related clock pulse (ninth pulse) and
keep it low until SCL returns low. To generate a no-
acknowledge (also called NAK), the receiver releases
SDA before the rising edge of the acknowledge-related
clock pulse and leaves SDA high until SCL returns low.
Monitoring the acknowledge bits allows for detection of
unsuccessful data transfers. An unsuccessful data
transfer can occur if a receiving device is busy or if a
system fault has occurred. In the event of an unsuc-
cessful data transfer, the bus master should reattempt
communication.
Data Order
A byte of data consists of 8 bits ordered most signifi-
cant bit (MSb) first. The least significant bit (LSb) of
each byte is followed by the acknowledge bit. The
MAX17043/MAX17044 registers composed of multibyte
values are ordered MSb first. The MSb of multibyte reg-
isters is stored on even data-memory addresses.
Slave Address
A bus master initiates communication with a slave
device by issuing a START condition followed by a
slave address (SAddr) and the read/write (R/W) bit.
When the bus is idle, the MAX17043/MAX17044 contin-
uously monitor for a START condition followed by its
slave address. When the MAX17043/MAX17044
receive a slave address that matches the value in the
slave address register, they respond with an acknowl-
edge bit during the clock period following the R/W bit.
The 7-bit slave address is fixed to 6Ch (write)/
6Dh (read):
Read/Write Bit
The R/W bit following the slave address determines the
data direction of subsequent bytes in the transfer. R/W
= 0 selects a write transaction, with the following bytes
being written by the master to the slave. R/W = 1
selects a read transaction, with the following bytes
being read from the slave by the master. (Table 5).
MAX17043/MAX17044
SLAVE ADDRESS
0110110
MAX17043/MAX17044
Compact, Low-Cost 1S/2S Fuel Gauges
with Low-Battery Alert
12
Bus Timing
The MAX17043/MAX17044 are compatible with any bus
timing up to 400kHz. No special configuration is
required to operate at any speed.
2-Wire Command Protocols
The command protocols involve several transaction for-
mats. The simplest format consists of the master writing
the START bit, slave address, R/W bit, and then moni-
toring the acknowledge bit for presence of the
MAX17043/MAX17044. More complex formats, such as
the Write Data and Read Data, read data and execute
device-specific operations. All bytes in each command
format require the slave or host to return an acknowl-
edge bit before continuing with the next byte. Table 5
shows the key that applies to the transaction formats.
Basic Transaction Formats
A write transaction transfers 2 or more data bytes to the
MAX17043/MAX17044. The data transfer begins at the
memory address supplied in the MAddr byte. Control of
the SDA signal is retained by the master throughout the
transaction, except for the acknowledge cycles:
A read transaction transfers 2 or more bytes from the
MAX17043/MAX17044. Read transactions are com-
posed of two parts, a write portion followed by a read
portion, and are therefore inherently longer than a write
transaction. The write portion communicates the starting
point for the read operation. The read portion follows
immediately, beginning with a Repeated START, slave
address with R/W set to a 1. Control of SDA is assumed
by the MAX17043/MAX17044, beginning with the slave
address acknowledge cycle. Control of the SDA signal
is retained by the MAX17043/MAX17044 throughout the
transaction, except for the acknowledge cycles. The
master indicates the end of a read transaction by
responding to the last byte it requires with a no
acknowledge. This signals the MAX17043/MAX17044
that control of SDA is to remain with the master following
the acknowledge clock.
Write Data Protocol
The write data protocol is used to write to register to the
MAX17043/MAX17044 starting at memory address
MAddr. Data0 represents the data written to MAddr,
Data1 represents the data written to MAddr + 1, and
DataN represents the last data byte, written to MAddr +
N. The master indicates the end of a write transaction
by sending a STOP or Repeated START after receiving
the last acknowledge bit:
The MSB of the data to be stored at address MAddr
can be written immediately after the MAddr byte is
acknowledged. Because the address is automatically
incremented after the LSB of each byte is received by
the MAX17043/MAX17044, the MSB of the data at
address MAddr + 1 can be written immediately after
the acknowledgment of the data at address MAddr. If
the bus master continues an autoincremented write
transaction beyond address 4Fh, the MAX17043/
MAX17044 ignore the data. A valid write must include
both register bytes. Data is also ignored on writes to
read-only addresses. Incomplete bytes and bytes that
are not acknowledged by the MAX17043/MAX17044
are not written to memory.
SAddr W. A. MAddr. A. Data0. A. Data1. A... DataN. A
Read: S. SAddr W. A. MAddr. A. Sr. SAddr R. A. Data0. A. Data1. N. P
Write Portion Read Portion
Write: S. SAddr W. A. MAddr. A. Data0. A. Data1. A. P
KEY DESCRIPTION KEY DESCRIPTION
S START bit Sr Repeated START
SAddr Slave address (7 bit) W R/W bit = 0
MAddr Memory address byte P STOP bit
Data Data byte written by master Data Data byte returned by slave
A Acknowledge bit—master A Acknowledge bitslave
N No acknowledge—master N No acknowledge—slave
Table 5. 2-Wire Protocol Key

MAX17043X+

Mfr. #:
Manufacturer:
Maxim Integrated
Description:
Battery Management 1S/2S Fuel Gauge
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union