Products > Test Equipment
Fluke 5x-II series thermometer tear-down and hacks
jggearhead10:
Final pic of 54-II pcb (3/3)
jggearhead10:
Ok. Here are the specs to talk to the meter... (1/2)
9600 Baud, parity: none, 8 bits, 1 stop bit.
Command responses:
0\r [30 0D] - command accepted
1\r [31 0D] - command not recognized
5\r [35 0D] - no data available in meter memory (after sending 'QD 1' command)
DS - Power cycles meter (won't go back to IR mode until toggled by user).
ID - Gives model number and software version in plain text.
Should respond something like: "FLUKE 54-II, V1.5"
RI - Resets the meter to factory specs **except** calibration values (clears internal memory, clears clock).
CD - Clear data (does the same as the Clear Memory function on meter).
QD 0 - queries the meter setup data. Returns binary data.
Binary data structure: <8 bit clock is set?><32 bit time><16 bits records in memory>
Bytes:
0 - record count byte 0
1 - record count byte 1 (record count int between 0 and 500; byte 0 + byte 1)
2 - time byte 0
3 - time byte 1
4 - time byte 2
5 - time byte 3
6 - clock set byte (0x00 = not set, 0x01 = set)
Time = number of seconds since 00:00 + (days since memory last cleared * 86400 seconds/day)
ST - Sets the time.
Example:
send - "st HHMMSS" to set time to HH hours, MM minutes, and SS seconds
jggearhead10:
How to retrieve the actual data stored in the memory: (2/2)
QD 1 - qeries the data stored in the meter internal memory. Returns binary data.
Data are returned in 64 bit packets - either containing data or metadata (init packet). Every batch of measurements logged to the device creates an init packet (If I log 10 measurements then 2, I would expect 2 init packets and 12 data packets). Note: there is only enough memory to store 499 total 64 bit packets regardless of type (every set of measurements uses n+1 packets).
Init packet byte structure:
<1 bit Packet type (always 1 for init packet)><2 bits units><5 bits><8 bits TC type><1 bit><1 bit interval unit><13 bits interval int><16 bits offset 1><16 bits offset 2>
Bytes:
0 - Calibration offset integer for probe 2, byte 0
1 - Calibration offset integer for probe 2, byte 1
2 - Calibration offset integer for probe 1, byte 0
3 - Calibration offset integer for probe 1, byte 1
4 - Interval, byte 0
5 - Interval, byte 1
6 - Thermocouple type (ASCII char)
7 - Units (also packet type)
Calibration offset:
If units are F -
F = (<Cal Offset> / (10 * 1.5))
If units are C or K -
C / K = ((<Cal Offset> / (10 * 1.5)) * (9/5))
Interval:
The lower 13 bits of the interval bytes are an integer. The 14th bit (mask with 0x2000) is 0 if the interval units is set to seconds, 1 if set to minutes.
Units:
Two bits of the last byte sent (mask with 0x60).
00 = C
01 = F
10 = K
Data packet byte structure:
<1 bit packet type (always 0 for data packet)><31 bits time><16 bits T1 temp><16 bits T2 temp>
Bytes:
0 - Thermocouple probe 2 temperature int byte 0
1 - Thermocouple probe 2 temperature int byte 1
2 - Thermocouple probe 1 temperature int byte 0
3 - Thermocouple probe 1 temperature int byte 1
4 - Time int byte 0
5 - Time int byte 1
6 - Time int byte 2
7 - Time int byte 3 (also packet type)
Converting from Fluke's arbitrary units to real temps:
If units are F -
F = (<Fluke Temp> / (10 * 1.5)) - 459.67
If units are C -
C = ((<Fluke Temp> / (10 * 1.5)) * (5/9)) - 273.1
If units are K -
K = ((<Fluke Temp> / (10 * 1.5)) * (5/9))
Time int:
number of seconds since 00:00 + (days since memory last cleared * 86400 seconds/day)
(same as "QD 0" response)
jwrodgers:
Just bought one of these from a local CashConverter. It's a 54-II, but was in pretty bad shape. (Missing rear battery cover missing, small cracks in case etc. I manage to get a good deal, but one of the channels (T1) was not working when I plugged a therocouple in. T2 was working, but would like both to be working well.
I took apart, and checked all the obvious. Turned out that one of the little wires from the thermocouple board to the main board was 'loose', i.e. the solder had become deteched or loose. It 'buzzed' out with a meter OK before and after resoldering. Assembled meter and it worked fine. Seems that the small resistance that can be present from a loose or poor connection and affect these meters.
Just thought I'd leave this as hope to others with similar meters, some thing to check as I have head a few of these with one channel not working properly.
I'm gonna try and find a battery cover now!
Black Phoenix:
I'm not sure if I have an extra battery cover or not. I will check and then say something to you.
EDIT: I was checking and only have the back cover were the batteries contacts are.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version