1

commandline runtime parameter bug in metteam 3.0 with MET/CAL 10.2.x

in further versions of mettrack and than in metteam I could start a metcal procedure by parameter in metconnect and mettrack versions it could be used cID, that is similar to I4201 in Mettrack like:

"C:\Program Files (x86)\Fluke\METCAL\mcrt.exe" -a "dummy"

to step over the asset choose dialog. this was very helpful. In METTEAM I need to use 

e.g.

"C:\Program Files (x86)\Fluke\METCAL\mcrt.exe" -a "352C3404-6594-4763-B143-8BF88B8CAB73"

where the UUID (Asset.uid) where used. This has now stopped working in METTEAM 3.0 and MET/CAL 10.2.2 When I now start my commandline, that was working in Metteam V2.x I get blank asset window:

can someone explain if this is a bug? This command option is needed to work for integration in workflows. Why this is different I have also never understand. -a stands for ASSET and it works fine in Metcal for MET/TRACK and MET/CONNECT. So it should changed in METTEAM Version also.

4 comments

Date Votes
0
Avatar
Rene Buske

Ok, I have reengineered arround and I´m sure this is a bug. The parameter -a will noticed by METTEAM at startup. If I start without -a the asset search view is presented to choose the asset. When I use -a the command will seen and step over the choose asset dialog. I assume as MET/CONNECT runtime change for -a [cBarcode] is coded, MET/TEAM behavier is not checked. Have tested Versions 10.2.0 - 10.2.3 of MET/CAL - all are working with MET/CONNECT, but not with MET/TEAM.

The parameter for procedure path will noticed and runs well, only -a in MET/TEAM needs to fix

0
Avatar
Rene Buske

Any comments from officials so far?

0
Avatar
James Steeds

when launching MCRT from the commandline I pass it the following parameters 

 

-pui = @nProcedureUID
-w = @nCallSheetUID

 

I've not tried sending an nAssetUID.  I'd be interested to know if this works.

0
Avatar
Rene Buske

- a is working fine in MET/CONNECT with the use of the cID (Asset name). This is perfect so it is not needed to create an workorder before. MET/TEAM can also work with the workorder creation by MET/CAL, so I don´t need the CallSheetUID when I start the procedure. In version 2 of MET/TEAM it was running to start -a [nAssetUID] -x [procedure-path]. This was fine, but now it is not working anymore. But why? At the moment it do not work and in the documentation I cannot find anything about commandline parameter start. Since Version 5 I´m using this system of starting procedures with asset - a and now without any comment it does not work anymore. It seems like a bug.

Please sign in to leave a comment.