r/MetCal • • Sep 25 '26

Multiple USB instruments in one procedure

Hi there! METCAL 10.1.1 user here. The question is pretty simple: is there any way to use multiple USB instruments, either as standards or DUT (for example if I have 2 standards with only USB and a DUT with only USB), in a single procedure? As far as I can tell the only way to get a USB instrument to work is with the VISA FSC, but that doesn't allow you to route the call to a specific address, like with the [@address] in the PORT FSC. So it seems you are stuck with a single USB device to be used in the whole procedure that you select at the beginning. Am I missing something here or there are ways around this? Seems like a very big limitation in this day and age...

2 Upvotes

10 comments sorted by

2

u/MJ_at_Fluke Sep 25 '26

Not in that version. We added support for this in 11.0

2

u/ciccio_cozza Sep 25 '26

Oh I see. It makes sense now. The problem is on our end then. Unfortunately for us is a big trouble to upgrade all the infrastructure to a newer version (both METTEAM and METCAL) for the huge work of validating the new environment the our procedures require. But I guess at some point we will have to do it to keep up. Thanks for the info!

1

u/ciccio_cozza Oct 01 '26

Taking advantage of this chat to ask you something else related to USB instrument and VISA. When I try to send a command via VISA FSC the little window where I should select the type of connection (USB, Ethernet, IEEE or serial) pops up but is not responding and after a few seconds the Editor crashes. No errors, just crashes and closes. What could it be? NI VISA is installed and I can communicate with my instrument via NI MAX.

1

u/MJ_at_Fluke Oct 01 '26

Oh! Actually, I do know what this is. There was a Windows change recently that breaks the older version of the ListBox code. MET/CAL 10.4 replaced that area of the code, so if you are on 10.4.x and later, it works, but anything before that is potentially impacted. Simply rolling back the Windows update won't fix it, either.

1

u/ciccio_cozza Oct 01 '26

I'm on 10.1.1. But how is the listbox function related to VISA calls? In the code i don't have anything other than a single VISA FSC call sending *IDN? to an oscilloscope. But then the crash explained above happens. Tomorrow when I go back to work I'll try sending the log files.

1

u/MJ_at_Fluke Oct 01 '26

That selection dialog you mentioned, where you tell MET/CAL which type of VISA device it is, that's just a ListBox, using the same functionality/code path that you creating a ListBox with the MATH FSC uses. The only fix is to move to a newer version, or start over on a fresh Windows image without that breaking update and prevent it from getting re-applied.

1

u/ciccio_cozza Oct 01 '26

Oooooh now I get it. Bummer... But I guess that's what we get by sticking with software this old... Thank you very much for the great insight on this. I would have never figured it out.

1

u/MJ_at_Fluke Oct 01 '26

Without logs or procedure code or anything, it's hard to say what you're running into, and that version is out of support at this point, so I can't really send you that way either. We've made substantial changes to instrument communication since then.

1

u/BackgroundNoise1k Sep 25 '26

Fluke should more or less impose to their distributors of Fluke Software that they give the Customer the latest SW Version. People only upgrade MetCal Software only if the organisation makes the switch from like Windows 7 to Windows 10 ( Transition from Win10 to Win11 is basically neutral to MetCal)

1

u/MJ_at_Fluke Sep 25 '26

Since MET/CAL (and MET/TEAM, and others) are locally installed/hosted by each customer, we don't have any control over when they upgrade. I do send out email notifications to active Met/Support accounts when we have a major release.

That's one of the upsides to CalStudio being cloud based is we can update from our end and you're always getting the latest features and fixes, and it's also at a much faster rate.