586x 1.1 Bad distribution from NI.com

[JÞB]

I downloaded the driver from here yesterday.  Co-worker at a remote site did the same.

That dog won't hunt!  Uninstall / reinstall from DVD works fine.  Have someone look into it would you?

[MikhailK]

Hi Jeff,

Thanks for pointing this out. I will look into this. Why do you say the driver from here doesn't work? Do you get any specific errors? Does your USB power meter appear in MAX? Are you using 5680 or 5681?

[JÞB]

What I observed:

•  Device showed up fine in MAX
• SFP worked
• LabVIEW examples reported "Insufficient location information" Using LabVIEW 2012 f3

I then created a IVI logical session (Don't ask me why my mind went down that path)

•  LabVIEW examples ran but the readings reported were incorrect (@-10dBm expecting @-46dBm with no source connected)
• Took the meter to another station and got expected results.

So I uninstalled the driver, Wiped the IVI config from MAX and installed NI 568x 1.1 from DVD.

Normal operation was observed no trouble at all!

Figured either I got a bad download (Unlikely, I used the downloader) or, you got a bad build up there.   Sorry if you wind up chasing your tail for a bit.

[MikhailK]

Hi Jeff,

I compared the NI568X110 driver distribution from our website to the distribution that we have included in the DVD and they both had the same number of files (698 Files, 68 Folders) and size (365 MB (382,947,986 bytes)). So I don't think there is a problem with the distribution. Now I have seen some intermittent behavior with USB 5680 RF power meter and NI 568X 1.1 driver in the past, so it could be linked to that. The good news is that 568X 1.1.1 driver is coming out soon and it does fix a few bugs that 568X 1.1 driver had.

[JÞB]

Thanks for checking it out.  Must have been a fluke on my machine during the install.  Darndest thing I ever saw. VISA Interactive works VISA Driver busted. and thats a 5681.

[JÞB]

Surprise surprise! this undesired action returned!

That is SFP works fine

LabVIEW Examples exhibit unexpected functionality.

I did some digging and tracked down the root cause!  The problem comes and goes by Renaming the COM port alias.

So for the LabVIEW examples to work Assuming the device installed at COM9:

The VISA Alias must be "COM9".

A device on COM9 aliased with  "RFMTR" gives unexpected results:

"Measurements" are allways "Complete" so averaging is impossible

"Readings" are some point on a 200mSec sine wave @ 1 dB Pk and -9.8dBm RMS Irrespective of actual input to the sensor!

[I Shudder that a log reading has a linear sine wave component]

I have repeated this on multiple stations with multiple 5681's LabVIEW 2012 / MAX 5.3.3.

I assume this is an unintended feature.

I can work around the problem but.....Uhm, this moves the USB 568x driver from a "minor inconvieniance" To Wit: the User must Change Alias when swapping meters for cal since I can't catch the connection event in Devmon like a USB DAQmx device (It requires user training in MAX for maintenance) to a major inconvieniance  since Now not only do I need the user trained in MAX to verify the configuration, I have to teach the user how to use the advanced panel in Windows Device manager for the port to change the COM port number assigned.  Not very cool

[MikhailK]

Hi Jeff,

Sorry for the delayed reponse. Can you attach the MAX Technical report for one of the computers where you can see the issue with the VISA alias? Also which LabVIEW example did you run to uncover this behavior? Does the SFP work with alias? Finally, as far as I understand if you don't use an alias both SFP and LabVIEW example work fine. Is this correct?

[JÞB]

The SFP does respect any valid Alias

All LabVIEW examples return false readings with any alias other than COMx where x is the COM port assigned in Windows

The Scope example demos the disturbing false data pattern and is included in the attached tech report

[JÞB]

I've debated this enough with myself.   I need the programming manual for the 5681.  I will write my own VISA driver to make this a positive experience for my client.

(Darn it, I really hate it when some text coding weenie messes with my LabVIEW mojo!)

[MikhailK]

Hi Jeff,

I reproduced the behaviour you were observing on my end and I have created a CAR (corrective action request) #406711  for 568X R&D driver team. So far I cannot give you a timeline on when the fix for this will be implemented. Now, as far as programming manual is concerned refer to RF meter help file.

Regards,