Well , he's got the hardware and I have to wonder how many companies would use 110 bytes for their data message length? My guess, you both bought the same thing.
Near the start he did get data on the unit and the message format:
Unfortunately these is no information online for the IrDA.
I have managed to get the following from the device manufacturer:
The Baud rate is 2400
The character format is one start bit, followed by 8 data bits and one stop bit (no parity)
The IrDA output data adheres to the following format:
[SOH (Hex01)][NULL (Hex00)][LEN (nn)][STX (Hex02)][DATA (Len)][ETX (Hex03)][BCC (nn)]
SOH: Start of Header (Hex 01)
NULL: Null character Hex 00
LEN: Data length (hex 00-FF) Indicates the number of bytes between ETX and STX, exclusive.
STX: Start of text character (hex 02)
DATA: Actual sensor data as defined below.
ETX: End of text character (hex 03)
BCC: Binary Checksum of all message bytes from SOH to ETX (inclusive).
DATA FIELD: (BYTE TOTAL = 104)
PC: Len=12, ASCII
FRC: Len=9, ASCII
MSN: Len=3, Binary
CN: Len=2, Binary
USN: Len=16, ASCII
MD: Len=3, Bit Field
R1R1: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
R1R2: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
R1R3: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
R2R1: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
R2R2: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
R2R3: Len=5, BCD (Represents 7 integer digits and 3 decimal digits)
Reserved: Len=1, Binary
SF: Len=1, Bit Field
EF: Len=1, Bit Field
ACT: Len=3, BCD
R1T: Len=3, BCD
R2T: Len=3, BCD
PUT: Len=3, BCD
PFC: Len=2, Binary
WC: Len=1, Binary
RWC: Len=1, Binary
Reserved: Len=10, Binary
Identifying the Start of the Message:
As the message is in binary format it might very well contain the SOH, STX and ETX characters
that makes finding the start of the message more challenging. To simplify the process of identifying the
start of a message it is probably best to wait for the quiet time that occurs between each message.
The sensor transmits a message once every second. We suggest that the receiver program should wait
approximately 100 ms without receiving a character from the sensor to identify the quiet time preceding the SOH
character that marks the start of the next message. Message parsing should then proceed to verify that the
message is properly frames abd that the BCC is valid.
We never did get around to checking the checksum, but that wouldn't be enormously hard to do. For end of line there is a check for over something like 250 ms without serial.available being an end of line condition. Hey, it works.
To tell the truth, I don't know what most of the data is. Never got a map or guide to those bit fields.