No part of this manual may be reproduced, published or publicly displayed in any form
or by any means, electronic or mechanical (including photocopying), nor may its
contents be modified, translated, adapted, sold or disclosed to a third party without prior
written permission of the copyright holder. Translated manuals and translated portions
of multilingual documents are based on the original English versions. In ambiguous
cases, the English versions are applicable, not the translations.
The contents of this manual are subject to change without prior notice.
This manual does not create any legally binding obligations for Vaisala towards
customers or end users. All legally binding obligations and agreements are included
exclusively in the applicable supply contract or the General Conditions of Sale and
General Conditions of Service of Vaisala.
HMM105 has an inter-integrated circuit (I2C) interface for interfacing
with the incubator’s control computer. HMM105 implements I2C slave
functionality, with the incubator’s computer acting as the master. The
interface can be used to read measurement values and status information,
set operation parameters, and make adjustments.
Physical Interface
The physical interface is a non-isolated 3-wire interface. Wires are SDA,
SCL and ground. SDA and SCL lines are buffered. Ground is shared
with power supply. There are small pull-up resistors for SCL and SDA.
Maximum cable length should not exceed 5 m and maximum capacitance
between communication lines and ground should not exceed 500 pF.
1405-072
Figure 1 Hardware Schematic
The physical connector is a Molex 87832-1007, 2 mm pitch shrouded
pin header with a locking window. It is marked X6 on the component
board. See Table 3 on page 4.
HMM105 supports a maximum clock speed of 50 kHz. Protocol bits are
sent most significant bit (MSB) first. Parameter bytes are sent using little
endian order.
Addressing
HMM105 uses 7-bit addressing. The address consists of:
- 4-bit device type identifier part (default “0101” for HMM105)
- 3-bit sub address (default “111”)
The full 7-bit default address is “0101111” (2Fh). In I2C communication,
the address should be provided by the master in the standard way after
the I2C start condition, with the read/write bit as the least significant bit
(LSB).
Table 4 HMM105 I2C Address
The I2C implementation of the HMM105 also includes the address inside
the message frame. The purpose of this is to make the I2C
implementation easier, since the I2C address can be lost by the I2C
hardware. This address is provided without the read/write bit, with zero
as the most significant bit (MSB).
This ACK/NACK refers to message level acknowlegde. I
includes separate byte level acknowledge.
Message Segment
Length
Content
Start
I2C start condition.
I2C address
1 byte
See Table 4 on page 4.
Command
1 byte
Identifier of command.
Device address
1 byte
See Table 5 on page 4.
Frame length
1 byte
Length of invoke message in bytes
Minimum invoke frame length is 5 bytes.
Data
Variable length
Content and length depending on the
contains no data in the invoke message.
Checksum
2 bytes
See section Checksum on page 9.
Stop
I2C stop condition
Message Segment
Length
Content
Start
I2C start condition.
I2C address
1 byte
See Table 4 on page 4.
Status
1 byte
See section Status Byte on page 9.
Command
1 byte
Identifier of the command that was used
valid invoke), command code is FFh.
Device address
1 byte
See Table 5 on page 4.
Frame length
1 byte
Length of the response message in
length is 6 bytes.
Data
Variable length
Content and length depending on the
command.
Checksum
2 bytes
See section Checksum on page 9.
Stop
I2C stop condition
Communication Flow
Basic communication flow always includes I2C write and read
commands. First the master writes a command to the slave device, and
then the master reads the results of that command from the slave.
When the master reads data from the slave, there is an ACK/NACK-bit in
the status byte that informs the master whether or not communication
was success. ACK is defined as zero and NACK is defined as one in the
logical level.
2
NOTE
Command messages sent by the master are called invokes. Replies sent
by the slave are called responses. Note that also responses include the
device address.
Table 6 Invoke Message in HMM105 I2C Interface
C protocol
(excluding I2C address, including CRC).
command. May be left out if command
Table 7 Response Message in HMM105 I2C Interface
in the invoke that the slave is
responding to. If slave is in idle state (no
bytes (excluding I2C address, including
CRC). The minimum response frame