0

Problems using Fluke 9640A after upgrading to Met/Cal 8.3 ?

I was wondering if anyone else after upgrading from met/Cal 7.3 to version 8.3 if they expeienced problems with using their old procedures using the Fluke 9640A-LPN  ?

It seems my 9640A RF Output keeps turning off with the newer version of Met/Cal.  Anyone else seen these problems? 

 

8 comments

Date Votes
0
Avatar
Michael Johnston

What FSC are the procedures using? Is your 9640 in emulation mode?

0
Avatar
Steve Reeves -X (stevreev - SIMCO ELECTRONICS at Cisco)

I checked yesreday and the 8640A is not in one of the HP 3335A or 8662 / 8663 emulation modes.

The procedures that I have are admitedly older and for the most part use explicit IEEE commands sent to the UUT and cal standards. Even EVAL, MEMC and other misc functions turn off the 9640A RF now. I'm not using the 9640 FSC in the procedures as my dozens of other 9640 procedures were written pre-version 8.x.

I hate to think I have to now modify all 9640 procedures to make them work now. I may have to just install version 7.3 on a different computer. My new 8.3 version was recently installed on a new Win 10 O/S computer. My old computer was Win 7 but ran MC 7.3 fine - never had this issue with the 9640.

Here's an example of some of the explicit coding I used - nothing fancy like Fluke and other experts now provide:

 52.003  IEEE         IP;DONE?[I]
 52.004  IEEE         [@9640]*RST
 52.005  IEEE         [@9640]INST SINE
 52.006  IEEE         [@9640]UNIT:POW DBM
 52.007  IEEE         [@9640]POWER -62
 52.008  IEEE         [@9640]FREQ 50E6
 52.009  IEEE         [@9640]OUTPUT ON
 52.010  IEEE         [@9640]*OPC?[I]
 52.011  IEEE         SNGLS;LG 1DB;CF 50MHZ;SP 50KHZ;RB 3KHZ;VB 30HZ;RL -60DM
 52.012  IEEE         TS;MKD;MKA?[I]
 52.013  ACC          0.00D          0.001U
# 51.013  MEME
 52.014  MEMC         D              0.05U         reference_10dB
 53.001  MATH         M[1] = MEM1
 53.002  IEEE         [@9640]INST SINE
 53.003  IEEE         [@9640]UNIT:POW DBM
 53.004  IEEE         [@9640]POWER -52
 53.005  IEEE         [@9640]FREQ 50E6
 53.006  IEEE         [@9640]OUTPUT ON
 53.007  IEEE         [@9640]*OPC?[I]
 53.008  IEEE         AT 20DB;RL -50DM;TS;MKPK HI;MKA?[I]
 53.009  MATH         MEM = MEM-10
 53.010  ACC          0.00D          0.09U
 53.011  MEME
 53.012  MEMC         D              0.6U          20dB_STEP

 

 

 

 

0
Avatar
Michael Johnston

That's really strange. There's nothing different in 8.x that would cause explicit IEEE commands to shut down the output.

I would suggest contacting the software support group at softwaresupport@flukecal.com and see if they have some insight on the issue.

0
Avatar
Steve Reeves -X (stevreev - SIMCO ELECTRONICS at Cisco)

Anyone know how to access the Instrument Configuration menu when you can only get this error:

 

                                E2494:  The System Configuration File is in use by another application ( "Editor" ).

And yes I'm in the Editor. Also tried MC Runtime with Editor closed. Also tried stopping / restarting Metbase.

Also tried restarting my computer and restarting the programs several times. Nothing seems to want to release the System Configuration file so it can be viewed / modified . . .      So far I don't like version 8.3.

0
Avatar
Michael Johnston

Open your metcal.ini file (Start>Programs>Fluke Calibration>Fluke Program Data). There will be a line that's something like "lock=editor" (can't remember the exact syntax). Delete that line, save, reopen MET/CAL.

8.3 is a dramatic improvement in a lot of ways. You'll need to get used to it if you've been using 7 for a long time, but the editor is a huge improvement as a procedure developer and PXEs are a superior procedure format.

0
Avatar
Steve Reeves -X (stevreev - SIMCO ELECTRONICS at Cisco)

Solutions found !

First, I have 2 Michaels to thanks for your timely help as I advance upward in the Met/Cal version chain.

Michael Johnston - Thanks your suggestion on how to release the locked file that prevented access to the Instruments Configuration file - works !

And to Michael Schwarz of Cal Lab Solutions for the solution of adding a replacement in the Instruments Configuration for the Fluke 9640A-LPN with FLK_9640. That avoids the version's 8.3 interpretation that  it should use the 9640 FSC and allows control by use of explicit IEEE commands to the 9640 so other function don't reset the 9640 or turn off the RF output.

 

Thanks guys.

 

Steve Reeves

 

 

0
Avatar
Michael Johnston

Good to know that about the FSC issue when you're configuring it as a standard! Thanks for sharing what you got from other Michael.

0
Avatar
Chad D.

Hi Steve, what you are experiencing is a side effect of adding the LPN FSC and corresponding System Instrument name "Fluke 9640A-LPN".   Prior to this enhancement, the LPN was simply an attribute to "Fluke 9640A".   Now that "Fluke 9640A-LPN" is a recognized as a System Instrument, the driver automatically turns the output off under the standard conditions (post test displayed, ASK+ Q, etc.).  This occurs when the instrument is configured as "Fluke 9640A-LPN", regardless of whether the procedure actual uses the LPN FSC.

-Chad

Please sign in to leave a comment.