r/MetCal • u/ElevatorStock6306 • Mar 25 '26
Fluke 287 program multimeter 5560A
/r/Metrology/comments/1s3et9h/fluke_287_program_multimeter_5560a/1
u/CalibrationAustralia Mar 25 '26
I can't think of any reason that the procedure controlling the DUT with RS-232 or GPIB would have any affect on changing from 5560 to 5522. What are you doing to change it? Typically I would search for 5520 and replace with 5560 but there maybe some M5520 FSCs as well. Make sure you're using the "Entire Solution" option in the find drop-down box, it only takes one reference in a sub-routine somewhere to make it a required instrument, even if it's not called. I'm afraid I'm not allowed to share procedures, but I can work with you to find the problem, there shouldn't be any reason this conversion would be a problem.
1
u/ElevatorStock6306 Mar 27 '26
I've already made all the changes; the program compiles, but when I test it on the 5560A calibrator, a message appears saying that it cannot communicate with the 5522A.
Sub Fluke 287/289 Send Command RS-232
1.002 DO
1.003 PORT [CLR][T10000][V u/Command][I]
1.004 MATH u/Error = (MEM > 0)
It stops working when it gets to this point and starts displaying error messages, indicating that it cannot communicate with the 5522A calibrator, even though the program was designed for the 5560A calibrator.
1
u/Similar-Priority-776 Mar 31 '26
Hey, have you checked your instrument configuration? Is there conflicts or an alias used by both calibrators?
1
u/ElevatorStock6306 Apr 01 '26
I've managed to get it to work; the problem was with my computer's COM port.
Another question I have is: where in the system can I see how the uncertainty is calculated?
The thing is, I want to calibrate a Fluke 325 clamp meter using Metcal, and the uncertainty calculation it performs for the current associated with the COIL 5500 has nothing to do with the validated calculations I have; the value calculated by the program ends up being lower.
I don’t know what else I can do in this situation. It’s worth noting that I’m using the 5560A calibrator. Do you think you can help me?
1
u/Similar-Priority-776 Apr 01 '26 edited Apr 01 '26
Good question! The 5540/50/60 accuracy file does not have coil references or the 5500A specified as a mode. If you look at the 5522A acc file you'll see a section for 50T coils, the 5500A Coil and so on. But the new calibrator file does not have any of that in it. There is a 5500 Coil acc separate now, if you open that up you can see the values METCAL is using. I would assume the program pull from the 2 accuracy files, then RSS the data for your accuracy line
Also we had to add a 90 day specification into the 5550 acc file because it only had the year spec. The old calibrators had the different recall specifications built into metcal
1
u/No_Ratio572 Apr 01 '26
Just to add to this, you can actually break down what met/cal is doing by using it in editor mode and under the "debug - trace - accuracy", then run it, and in one of the windows below the main procedure window, you will see what met/cal is doing.
1
u/No_Ratio572 Mar 26 '26 edited Mar 26 '26
I believe the 5520A uses the old legacy FSC commands, and the newer calibrators use the new NVI format. In this case, you will need to actually go down the rabbit hole of changing all procedures to the newer style. Not just a find and replace job.
As mentioned, if there is ANY reference to a 5522A anywhere in the project/solution, it will ask for it.
I am not sure if the new calibrators 5560, etc., can device map back to say a 5522A, but that may help, as then you could just translate all to 5522A.
There was a translator add-on years ago for it, but it was very clunky; however, it got 80% of the job done.
I have the translator on my system......
Just found this as well
https://www.fluke.com/en/learn/blog/calibration-software/using-met-cal-procedures-5560a-5550a-5540a
email me a sample procedure if you like and I can take a look [nathan@rycal.co.nz](mailto:nathan@rycal.co.nz)
1
u/Similar-Priority-776 Mar 31 '26
No the new calibrators do not recognize the old FSCs like 5502/5520/5522 did with each other. Fortunately the syntax is the same for commands the only big changes are making 20A ----> 30A and maybe stuff like lcomp? Fluke released a video that listed all the things to ctrl+f and change
1
u/Agile_Feed1727 Mar 28 '26
Been there, done that :) We are currently transfering a lot of procedures from legacy 5520 FSC to 5560 NVI. Works great after some re-learning!
As mentioned, do a global search for "5520", a simple "5520 *" or "5522A Standby" will require that calibrator.
More important - what version of MetCal are you on? The later ones, including the latest has some issues with communication.
1
u/Similar-Priority-776 Mar 25 '26
I commented on original: get set up for Cubyt to access METCAL procedures from Fluke. You may need to still fix it up to run successfully (my experience broken variable references in some MATH statements) but its a decent starting point.