LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MAX 5.3.3 losing Aliases

 

Spoiler
EDIT: Somehow I Triggered a macro- "Have you read the manual for that device?"

 

 

This one has been driving me somewhat batty.

 

I have MAX 3.3.3f2 all the latest drivers and a PXIe 1078 Chassis sitting on my desk. 

Here is a screenshot of the system

Capture.PNG

 

Now maybe I want to get on a conference call and that fan is just a bit annoying so power OFF and now my configuration looks like so AFTER I OK the MAX Timeout error while waiting for a driverSmiley Surprised

Capture.PNG

 

Where did my ports go?  They were there a minute ago  but they ran away and hid somewhereSmiley Sad Now I can't turn on the Power supply sitting right here next to me on a USB Virtual COM Port remotely.  I actually have to reach over my mouse and use the fornt panel! (Oh! the humanity!)

 

I Know.  The Manual says it doesn't matter what order I power up the PC and the PXI Chassis.  Let's turn 'r' on!

....

Power Light is GREEN Link Light is GREEN Access light on the VST is green

MAX Still is unhappy

Capture1.PNG

What a great IdeaSmiley Very Happy I'll go to NI.com.  Its always FUN!Smiley LOL

 

After reading the white paper which doesn't offer much since I can't get to the VISA options (They won't launch) and clicking through the error. Half my equipment went bye-bye

  Capture.PNG

 

VISA resouces are MIA!  Trying to expand the Software tab shows

Capture.PNG

 

But I've got LabVIEW open, and MAX There must be some NI Software around here somewhereSmiley Sad

 

 

Now this much is pretty annoying but its just a development aid.  A reeboot with the 1078 powered on first will restore this system except for the COM Port AliasSmiley Surprised

 

The real trouble comes on the test system this goes into.  When I Power up the PC without the 1078 powered up MAX Looses Aliases for:

the Virtual COM Port

An Agilient N6701A Power supply USB TMC

A TCP/IP Raw Socket (Actually the entire socket is blown away) 192.168.255.201:4000"Master" must be re-created from MAX

This makes me very sadSmiley Sad and trying to explain to the customer is quite embarassingSmiley Embarassed

 

Is there a known workaround? the white paper wasn't much help.

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 1 of 14
(4,649 Views)

I always get worried when YOU are the one asking the question!  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 2 of 14
(4,632 Views)

@billko wrote:

I always get worried when YOU are the one asking the question!  😄


It worries me too...

 

 

Now that I re-booted and can see my software again... NI VISA is 5.2.


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 14
(4,611 Views)

Have you read the manual for that device?  Smiley Tongue

 

From chapter 3 of the MXI-Express x-1 Series User Manual...

 

MXIpwron.png

 

Stated otherwise ...

 

MXIpwroff.png

 

Message 4 of 14
(4,596 Views)

OK So why did my VISA Aliases dissapear?  Those Aliases shouldn't die ignominously should they?  They are rather special to me and I want them to have a long, happy and productive life. 

 

Or read another way: I don't mind needing to reboot to retore operation due to BIOS limitations but, I need the VISA Aliases and TCP/IP resource to come back.  These resources aren't even attached to the PXIe chassis.


"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 14
(4,589 Views)

Are they still not present, even after you've rebooted?

0 Kudos
Message 6 of 14
(4,586 Views)

Right- The non PXIe VISA Aliases and the TCP/IP resouce iare wiped out of the MAX configuration!


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 14
(4,581 Views)

I wonder if you are slowly corrupting your MAX database...

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 8 of 14
(4,575 Views)

I'm thinking Bill is on the right track, but before we try to remove the database corruption, I'd like to check the Windows Device Manager.  Jeff, does Windows detect that your 4071, 6509, and COM ports exist on the system?

0 Kudos
Message 9 of 14
(4,567 Views)

Let me clairfy.

 

After reboot all Devices are found and available.  The Alias Problem does not manifest for the DAQmx device, the RIO device or the NI DMM IVI device in the PXIe Chassis.  The NON chassis devices are apparently bolown away.  The VISA TPC/IP raw socket must be re configured, The USB Devices need to have there Aliases reentered but, since USB is Plug-n-Play, they are automaticaly remounted with Default VISA resource names. 

 

So what happened to the MAX Configuration for the devices and resources that are not in the PXIe Chassis?


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 14
(4,562 Views)