Within the Measurement & Automation Explorer I can create Visa Aliases for my GPIB instruments which I can use as the resource name to the VISA Open VI. eg using DMM1 instead of GPIB::9::INSTR.

[ketan121]

Hello Dan,

I want to change the aliases in VISA layer. The reason i want to change the aliases is when i am communicating through the serial ports, my instrument address is different from the one stores in the NI MAX software. 

For example while i am communicating through serial port, my generated address is ASRL4::INSTR for COM 4 and the address stored in NI MAX software is  COM 4 for ASRL6::INSTR and for COM 3 it has ASRL4::INSTR

So can you please tell me are there any vi functions to rename the aliases. I am using the MAX version 4.6

Awaiting your replies.

Reagrds,

Ketan

[billko]

Did you try editing the visaconfig.ini file as mentioned in this thread?

[ketan121]

Hello Bill,

I do not want to do that manually. Is there any way to reset or change the visaconf.ini file programmatically?

Ketan

[billko]

---

@ketan121 wrote:

Hello Bill,

I do not want to do that manually. Is there any way to reset or change the visaconf.ini file programmatically?

Ketan

---

Did you actually read anything in this thread?  It shows exactly how to do this.  Unfortunately, no one ever reported back whether this actually works or not.  Maybe you could be the guinea pig - errr superstar - that puts all those theories to the test?

[ketan121]

I have tried making the connection through the one suggested in the document, but that is not the answer I am looking for. Is there any other way to erase the file completely through any of the VISA functions or events?

[billko]

Sorry, what I meant is, did you read Dennis' post about using the config file VIs?  Unfortunately this is a relatively unexplored path.  The reason is that usually you would usually bring along the visaconf.ini that accurately describes the hardware as named in your application.  What I normally do if I am coding offline is to grab the visaconf.ini file from the target and use that to devlop with.  Testers should be built identically, really - same cards (same revisions!) in the same slots in the same make/model of PC with the same OS updated to the same levels.  Check that the hardware maps the same in devoce manager and in MAX.  It's far easier to have them conforming at the beginning than it is to configure them at runtime...

[OrHirshfeld-SK]

Maybe its an old theard bu still relvant.
I just tried this solution and it worked.
Also you can use Configuration File VIs that built for handling ini files.
Thank you for the solution