-
Well I guess this explains why the IR189USB cable I bodged together this evening works with my 189 but results in not so much as a flicker of IR with my 89 IV. At least it didn't cost me anything to build as the bits had already been scavenged
I take it your Arduino code is just for 87 IV and 89 IV and won't work on 18x/28x series?
This has inspired me to finally start dabbling with Arduino. As far as I can see it shouldn't be too difficult to extend the code to use additional pins to select between 8xIV and 18x mode (another interrupt which would switch the main interrupts to point at two different pairs of routines?) and rising/falling trigger mode.
-
Yes it would be easy to add some code to just pass trough all incoming serial data to IR TX and RX leds.
And add a switch of jumper to select desired mode... -
My Arduino arrived today. After a bit of poking and prodding (and failing to read the mode switch with an interrupt, possibly due to switch bouncing)... it works!
The code below expects an SPDT switch connected to pins D10 (pulled high by the Nano), D11 (wiping contact) and D12 (pulled low). This is used as a mode selector, with the Nano's LED indicating the mode; off for 87/89 IV, on for 187/189 mode (and presumably 287/289 as well). Of course you could do it with the switch connected to Vcc, D11 and Ground, but doing it with D10 and D12 allows a three-pin toggle switch to directly mount to the board.
In 87/89 IV mode it uses Frenky's interrupts. In 187/189 mode it disables the interrupts and uses my quick-and-dirty loop which just keeps reading the Tx and IrTx inputs and copying them to the IrRx and Rx outputs. The two modes can be switched at any time, no need to reset the Arduino.Code: [Select]#include "DigitalIO.h"
const uint8_t interruptPinIrRx = 3;
const uint8_t interruptPinRX = 2;
const uint8_t PINIrTx = 7;
const uint8_t PINSerialTX = 1;
const uint8_t ModeSelHigh = 10;
const uint8_t ModeSel = 11;
const uint8_t ModeSelLow = 12;
const uint8_t LED = 13;
void setup() {
fastPinMode(LED, OUTPUT); //Mode indicator LED
fastPinMode(ModeSelHigh, OUTPUT); //High side of mode selector switch
fastDigitalWrite(ModeSelHigh, HIGH); //Keep high
fastPinMode(ModeSelLow, OUTPUT); //High side of mode selector switch
fastDigitalWrite(ModeSelLow, LOW); //Keep low
pinMode(ModeSel, INPUT);
fastPinMode(PINSerialTX, OUTPUT);
fastDigitalWrite(PINSerialTX, HIGH);
pinMode(interruptPinIrRx, INPUT_PULLUP);
fastPinMode(PINIrTx, OUTPUT);
pinMode(interruptPinRX, INPUT_PULLUP);
}
void IrDA_RX() { //Receive IrDA from Fluke 8xIV
fastDigitalWrite(PINSerialTX, LOW);
delayMicroseconds(105);
fastDigitalToggle(PINSerialTX);
}
void IrDA_TX() { //Transmit IrDA to Fluke 8xIV
delayMicroseconds(46);
while (digitalRead(interruptPinRX)==LOW){
fastDigitalWrite(PINIrTx, HIGH);
delayMicroseconds(20);
fastDigitalToggle(PINIrTx);
delayMicroseconds(85);
}
}
void loop() {
if (digitalRead(ModeSel) == 0)
{ //Switch is off, select 87IV/89IV (IrDA) mode
attachInterrupt(digitalPinToInterrupt(interruptPinIrRx), IrDA_RX, FALLING);
attachInterrupt(digitalPinToInterrupt(interruptPinRX), IrDA_TX, FALLING);
fastDigitalWrite(LED, LOW); //Turn off mode LED
while (digitalRead(ModeSel) == 0)
{
}
}
if (digitalRead(ModeSel) == 1)
{ //Switch is on, select 187/189/287/289 (IR passthrough) mode
detachInterrupt(digitalPinToInterrupt(interruptPinIrRx));
detachInterrupt(digitalPinToInterrupt(interruptPinRX));
fastDigitalWrite(LED, HIGH); //Turn on mode LED
while (digitalRead(ModeSel) == 1)
{
fastDigitalWrite(PINSerialTX, digitalRead(interruptPinIrRx));
fastDigitalWrite(PINIrTx, 1-digitalRead(interruptPinRX));
}
}
}
I just need to tidy it up a bit now.
-
Fantastic!
-
This is excellent - nice work!
I was looking to buy the cable as I want to update the 289 to v1.16, but I have a few arduino's kicking around so might give this a go, especially as I've got a 87-IV, 189 and 289 so this would be a great all-in-one solution.
Which IR components did you go for in the end please?
Is there a blog page/update schematic to have a look at?
-
Thanks a lot for such a useful information.
Also, I found that Fluke 286/287 are using faster speed : 115200 Baud, no parity, 8 bits, 1 stop bit
So, phototransistor is no longer acceptable.
It is better to use fast photodiodes.
-
Sorry for bring back from the dead...
If i'm not wrong, and if i well understood, i not really need the arduino. I need only an ir module, a tir1000 and an usb-232 chip?
Thanks! -
Sorry for "invade" this discussion, but seem the only one about the fluke ir interface for older meters using irda protocol.
Trying to made it simple (and not use an arduino to do the ir encoding/decoding), i've bought an old USB-IRDA adapter model MI620 of the winxp era, as per photo.
Inside i've found an PL2303HX (usb to 232), an eeprom(containing customizations for the 2303), and a chip labeled HS153SN (that i think is a custom mcu for encode/decode the irda protocol) .
As was impossible fo find the drivers for windows 10, i've removed the eeprom (that contained the customized VEN/PID), so now it's recognized as a normal PL2303 device, and i've installed the drivers.
But the meter was not seen by the software. So i've attached the logic analyzer, and sending characters with a terminal with no flow control i had the output to the photodiode, but with flukeview sending the 0x73 0x68 0x13 command i not had any output to the photodiode. I think that flukeview try to use some sort of flow control the my setup can't use (maybe because not using the correct drivers for the module). So i've removed the pins of flow control from 2303 to the HS153SN encoder and now i have a good signal to the photodiode (as seen the logic analyzer output). If i put a glass in front of the transceiver i get back the signal so i think that must work. But flukeview still not see the meter.
The photodiode pulses are encoded correctly (1,62us pulses, as per irda standard) but i not get back anything from the meter at the output of the phototransistor. If while flukeview is sending the data, i put an old phone sending irda data, i have correct signal at the output of the receiver, so or the meter is not understanding the irda code, or it simply not answer. My meter is a fluke 87-IV firmware 1.01. Maybe on that firmware the irda port is not enabled, and is only for the 89-IV?
-
Done! After few mods got it working.
Removed the eeprom, cut traces to pin 7 of the irda enc/dec chip and connected it to pin 4(vcc) and cut trace of pin 9 and connected to gnd.
Work perfectly!
-
Hi collages.
I also try to make a diy infrared communication cable for my Fluke 87IV multimeter, but I have a little trouble.
Generally, I build my schematic around FT232RL & MCP2120. With the jumpers I set the baud rate to 9600 (pins 9, 8, 10 of MCP2120 are connected to GND).
I’m using TFDU4101 infrared transceiver module. I use as reference the information in this post and the schematic from this blog http://lemmini.de/IrDA%20USB/IrDA%20USB.html.
So my problem is that when I point the board to the meter and turn the meter ON I don’t get any response in FlukeViewForms. The software says that “No meter is found” on the corresponding COM port.
I check in the documentation and I didn’t find additional information about some key combination or something else in order to start transmitting from multimeter side.
Please see my schematic and correct me if I’m wrong or share some experience with this multimeter.
-
I have bought a Fluke 87 IV, I like it, I have the IR189USB, but doesn't work with this meter, someone know what is the original cable for this meter?
Regards. -
What about implementing the code to an attiny85?
-
I have bought a Fluke 87 IV, I like it, I have the IR189USB, but doesn't work with this meter, someone know what is the original cable for this meter?
Regards.
I wonder if the 87 IV is different from the 187 and 189. I have the 189 and it works with the IR189USB cable as well as the older IR to RS-232. -
Yes, is different, even fluke says ir189usb for 18x and 28x series, what rs 2323 oldcable have You?
-
87/89IV encode/decode the data using IrDA protocol, while the 187/189 simply send/receive to/from the ir transceiver the rs232 data, that's why it not work. In 87/89 IV there is a chip (mcu/asic/etc) between usb-232 chip and ir that encode (and decode) the data. If you look my previous posts you see that i've adopted an old cheap usb adapter found on ebay, with a chip that was doing the correct idra encoding/decoding. Studyng the protocol you can also program an mcu that do it, but i've found simpler finding something already working and adapting it to the meter.
-
Yes, is different, even fluke says ir189usb for 18x and 28x series, what rs 2323 oldcable have You?
Is not the same with the Fluke 5x-II series of thermometers too? From what I got in old newsgroups - https://sci.electronics.design.narkive.com/qh8BODEw/fluke-54-ii-thermometer-ir-portQuote from: John Doehttps://www.amazon.com/gp/customer-reviews/R23T1IHGHG43CS/
"I highly recommend purchasing the flukeview forms package - you need to make
sure you get the IR receiver designed for the 187 meter and not the 189 meter
(they changed specs in between those two) - the 54 and the 187 use the same
sensor so IF YOU HAVE A 187 FLUKEVIEW FORMS KIT, YOU ARE READY TO GO WITH THE
54 THERMAL METER OUT OF THE BOX."Quote from: Cydrome LeaderGave fluke a call today. Here's the story
- the 5x II series has different IR than the 5x II B series. They are not
compatible. They must use different IR transceiver cables. The B series must
use the USB +IR cable. The older meters must use the serial cables, which
are discontinued. The fancy software comes with the cable itself.
Although they mention on the same post said discrepancy between the 187 and the 189 using different receivers and being compatible with the 87IV.
I suppose the user just said something out of his mouth without knowing what he was saying (going by the testing masterx81 done, and I believe more on him).
I know that the 54IIB uses the normal 187/189/287/289 IR receiver REVII with the plastic adapter that is used in the 187/189, since I saw it working. But the original 54II doesn't work with that.
Are you planning in providing a BOM and schematics/PCB to be redone? -
Yes, is different, even fluke says ir189usb for 18x and 28x series, what rs 2323 oldcable have You?
I can't see any part number. It has the 9 pin female RS-232 at one end rather than the USB A connector. I use this with an USB-RS232 adapter and it works for both the 189 and 289. The cable came with the 189. I also have the IR-USB cable that came with the 289 and it also works with both the 189 and 289. -
Don't worry, the serial cable works with 89 IV true?
-
Don't worry, the serial cable works with 89 IV true?
It works with the 189. I don't have the 89 IV that is why the question are they different? -
Because Fluke 87 IV & 89 IV just using IrDA protocol like show in posts above. Early Flukes like 187, 189, 287 and 289, works with serial protocol, I think my IR189USB doesn't work with 87 IV.
-
I put the code in my arduino uno, works very fine, I don't need remove the infrared cover, I can configure the meter from PC and synchronize hour.
-
hello, this mod work on fluke 287?
-
Yes, the Fluke 28x series and the Fluke 18x series share the same cable/protocol (with an adapter to fix it to the meter). The Fluke 189 is a rebranded Fluke 87IV with few improvements.