GPIB controller in charge

I have a PC attached to a number of test equipment via GPIB. This test rack is testing a UUT that has a GPIB interface we're trying to test. Main PC code is in labview, and UUT software is in CVI. I would like to (using LV) set the main PC to standby, then set the UUT as controller in charge. I would like the UUT to send the main PC a "*IDN?", and have the main PC respond with some known name string. Then, I need to set the UUT back to Standby mode (I guess after some predetermined time?). Just wondering what LabVIEW widgets I would need to use. Since I'm not talking to any specific GPIB instrument, I don't have a specific GPIB address, so how (in LV) do I refer to the GPIB interface at this level?

In the real system, the UUT is the controller, so we're trying to simulate that by making it the CIC. Then, the UUT is supposed to issue the IDN? to the SystemController (SC), and listen for an expected string. I ran a few experiments (without the UUT-unavailable), and a few things are more clear. However, I'm still not sure about a couple of things. (1) when the SC (in LabVIEW) uses PassControl, I'm not sure what to set the bus and address inputs to. When at the same computer, and the SC is talking to a sig gen, I tell it bus=0, and addr=19 (sig gen;s gpib addr). With two controllers, however, would the SC PassControl with bus=1? Not sure what address would be since UUT is a controller, and not a device on the its bus. (2) to get control back at the SC, would I (from the SC) send a SendIFC with bus=1? I plan on having a timeout, in case the UUT never replies.

Similar Messages

Command requires GPIB Controller to be Controller in Charge

I downloaded the labview driver HP428XA, the 'getting started.vi' works fine, but all other example application vi's keep giving me the following warning:
'Warning 1 occurred at VISA Read in HP428XA Fetch.vi->HP428XA Frequency Step Measurement .vi. Possible reasons:
LabVIEW: An input parameter is invalid.
or
NI-488: Command requires GPIB Controller to be Controller in Charge.'
I am a novice when it comes to labview, can anyone offer a solution?
thanks!

Hi,
The two error descriptions refer to the fact that the error code (1) has a different meaning depending on what software component gave the error: labVIEW or GPIB (NI-488.2).
Since you are able to use the Getting started VI, that means that the GPIB bus, driver and the VISA library are working porperly. Additionally, you would not get a Controller in Charge error if do not explicitly configure the board to be non system controller. labVIEW automatically configures the board to be controller.
So the error must refer to an incorrect parameter to some LabVIEW function. Open the HP428XA Frequency Step Measurement.vi and use the highlight execution tool to see where the error is generated.
I couldn't find the instrument driver at www.ni.com/idne
t, so I didn't take a look at the driver.
DiegoF
National Instruments.

Command requires GPIB Controller to be Controller in Charge on dequeue element

I have some funky stuff going on in the attached VI. What the VI does is simply to log data to a text file. It is built up as a state machine. This VI's Create state is called from a mainVI (with the help of named queues). I get more than one error and it seems completely random.The error usually occurs if I stop the mainVI, then starts it again. So the second (or following) times the DP VI is called, I get random errors such as the two below:
Error 1 occurred at Dequeue Element in DP.vi->PSS.vi
Possible reason(s):
LabVIEW: An input parameter is invalid.
NI-488: Command requires GPIB Controller to be Controller in Charge.
Error 1 occurred at Close File in DP.vi->PSS.vi
Possible reason(s):
LabVIEW: An input parameter is invalid.
NI-488: Command requires GPIB Controller to be Controller in Charge.
Why is this? I don't even have a GPIB controller?
Solved!
Go to Solution.
Attachments:
DP.vi ‏61 KB

Siniz wrote:
blawson, I think you found the error!
So shift registers only gets uninitialized again if I close the actual VI, and not when I start executing it again? So in reality, they actually behave like real shift registers? I found two solutions to this problem.
1) To initialize the error shift register with an empty error constant.
2) To remove the wire from the shift register to the Write to Text File. This works since I always call the Create state first.
Which one would you recommend?
Also, what is the reason to keep the typedef strict? I have seen non-strict in other code.
Generally you should always explicitly initialize your shift registers unless you want to retain the values from one execution to the next. This is required for Action Engines but in most other cases you should use initialized shift registers to avoid side effects like you encountered in this application.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Receive error-1 at TCP/IP read - GPIB controller must be controller in charge

I have a stripped down version of Talk Module from the LV TCP/IP examples. All it does is execute one TCP/IP read of 512 bytes and reset the output error to no error if a timeout or close connection error occurs. I placed it in the main loop of my program so it executes one time each loop but I receive an Error 1 "GPIB controller must be controller in charge" when it runs. I then stop the program and get that same error from a different source before it exits. I know it works because I can set it up in a separate VI and it works fine. The program is controlling a GPIB power supply and a VXI chassis. Any ideas what could be causing the error? Thanks.
Jason

All the inputs are wired correctly and the connection is opened first. I am using hyperterminal on another computer to check out the connection. Sometimes after running the close connection VI, hyperterminal says the connection is still open. When the VI stops running, the connection is always lost and when the VI runs again, it seems to have no problem opening the connection on the same port. Thanks for the advice, I will check into it.
Jason

TNT4882 as controller in charge?

Hello All,
Can anyone tell me if the TNT4882 chip can be configured to act as the
controller in charge on the gpib bus?
The software manual for the chip indicates that is has capability code
C0, which apparently means no controller capability. This seems
straightforward, but I understand that the TNT chip is basically a
supercharged NAT4882, which seems to have CIC capability.
Any information would be appreciated.
Thanks,
-- Tony Tero

Hi,
Thanks for the reply.
We don't usually need CIC capability in our products, but we have a
requirement for a custom one-of product where several of our boxes
need to talk to each other directly without a host PC. Since our
existing product has a GPIB interface using the TNT4882, we were
considering the possibility of having one becoming CIC and controlling
the others.
Our backup plan is to use RS485.
Thanks Again,
-- Tony Tero
On Fri, 4 Oct 2002 13:01:24 -0500 (CDT), DiegoF wrote:
>Hi,
>
>The TNT4882 does not have controller capabilities. This chip is only
>for talker/listener applications. The TNT uses much of the NAT4882
>circuitry, but also includes the bus transceiver and Turbo circuitry.
>
>You can get all the information o
n the available chips at :
>http://www.ni.com/support/gpib/reg_prog.htm
>
>What type of device are you developing?. Do you need controller
>capability?
>
>DiegoF
>National Instruments.

How do I create Labview VISA ports for *individual* GPIB instruments using Prologix USB GPIB controller?

Hello,
I'm trying to use a Prologix USB GPIB controller to control GPIB
instruments, and I would like to have a virtual serial (VISA) port for
*each instrument*, as is the case with a normal GPIB controller with a
standard NI driver. However this is not what the Prologix driver
provides -- it provides a single VISA virtual serial port for the
entire controller. To address the instrument with GPIB address 11,
you first send "++addr 11" to the serial port, and then you're talking
to instrument 11. However, this means I have to change all old
Labview programs.
Is it possible to create a "wrapper" function of some kind that will
define a virtual serial (VISA) port for each *instrument* on the
controller? For example, to talk to GPIB instrument 11, call it
ASRL3::11::INSTR, each time it is written to it would have to write to
the virtual serial port of the controller, say ASRL3::INSTR, first "+
+addr 11" and then the command that is sent to it.
A clearer explanation of the difference (i.e. incompatibility), and of
my objective:
1) A normal GPIB controller with NI driver: I go to the NI
Measurement & Instrumentation Panel, under GPIB, and Scan for
Instruments; all the live instruments show up; subsequently when I
want to use Labview programs that use VISA ports, the VISA drop boxes
allow me to choose a different port for each instrument, e.g.
"GPIB0::11::INSTR", "GPIB0::12::INSTR" would be instruments at
addresses GPIB 11 and GPIB 12.
2) The Prologix GPIB controller that plugs into a USB port: In
Labview you get a *single* VISA virtual serial port, ASRL3::INSTR, for
the entire GPIB0 controller. Therefore to address GPIB instrument 11,
you write "++addr 11" to the virtual serial port ASRL3::INSTR, and
then you are communicating with device 11, so you can write and read
ASRL3::INSTR to talk to that device. Then to talk to device GPIB 12,
you write "++addr 12" to the same VISA port, and then you are talking
to that device. The problem is that this requires recoding all
Labview code, whereas I would like to be able to use the same program
either with a normal or with a Prologix GPIB controller. Therefore, I
would like to create code that scans the controller for all GPIB
attached devices and creates VISA ports for all. Such ports, when
written to, would have to first write "++addr DEVICENUM" to
ASRL3::INSTR (i.e. the port of the GPIB-USB controller) where
DEVICENUM is the GPIB address of the instrument corresponding to that
port, and then would have to do a write or read or whatever function
is being done on that instrument VISA port.
I haven't figured out if it is possible to do this easily. Help and
pointers on where to look for hints would be much appreciated. Many
thanks!
Milos

My first impression is that if you don't want to make any changes at all to existing programs is that the wrapper you need is one around VISA. You would need to intercept all of the calls into the NI VISA driver. If you create your own visa32.dll and in there, change the addressing and then call the real VISA driver, you might (repeat, might) get something to work. If this would even work, you still might find that you have to make significant changes anyway. The serial connection is going to be considerably slower, and interface specific functions such as service request handling, bus triggering of multiple instruments, etc., would be difficult to impossible. This would be a lot of work, imho, to just save a couple of hundred dollars over a real GPIB controller. I've seen this Prologix device before and have even used NI's RS-232->GPIB controller. The Prologix intended use to me seems to me more for a hobbyist or very casual user. Of course, I'm used to having multiple GPIB instruments worth 10s/100s of thousands of dollars and the cost of an fully compliant GPIB controller is just lost in the noise.

Enet100 GPIB controller on 64 bit OS

After having to upgrade to the new LabView because of a bug and seeing how poor its performance is, I decided to give it the benifit of the doubt and got a brand new Core 2 3GHz PC w/ 8G of RAM.   I figured the time I am wasting trying to use the new interface will pay for the PC.   I now have XP-Pro-64 bit installed to take advantage of the memory, plus most of the tools I use have 64-bit versions now.
I went to install Labview and there appears to be no support for the Enet100 GPIB controller. This is how I talk to most of the test equipment. I know, your thinking why is he not using ethernet. Some of the equipment doesn't support it, and some of the even newest equipment, like the Tek AWG7102 arbs software is so poor that the GPIB is actually a faster way to talk to it.
Any idea when and/or if there will ever be new drivers to support the Enet100 on the newer 64-bit OSs?

Thanks for your help!
I had been looking on:
http://zone.ni.com/devzone/cda/tut/p/id/6893
and noticed:
National Instruments Products XP x86 (32-bit) Vista x86 (32-bit) Vista x64 GPIB-ENET firmware A.5
Assumed because there were no checks for it under Vista x64 there would be no driver.   I downloaded the drivers you linked to and they appear to work with XP Pro 64-bit even though there is no mention of this particular OS.   Tried a few things with the new PC and  LabView is still a little sluggish on it compared to 6.1 on a much slower PC. But it at least shoud require less hair pulling....
If I could just get NI to put the menus back to the way thay have been since the beginning of time and and allow me to do some sort of setup on that control menu so it does not pop up with that stupid express menu that I never seem to use.   If it were even smart enough to use the last setup I had it would go a long way to improve it. Or, even better, give me back the old menus so I can find things faster...

Labview error GPIB controller not adressed correctly

I get this Labview error: GPIB controller not adressed correctly (LV5.1, win NT4) when i try to send data to a HP4275A LCR meter. How ever it works on an older system running with LabView 5.0 (also NT)!!!
How can I get rid of this problem????

Hi Diego, thanks for the hints!
I tried to configure (GPIB) everything standard.
when I try a 488 command initialze, I get the controller conflict, when i don't do this I get atime out problem either by 488 write-command or by 488.2 send-command.
the differences between the systems where it works and where not are:
working: Win 95, LV 5.0, GPIB-card/TNT (plug & play)
not-working: WinNT, LV 5.1, GPIB-card/PCI
i tried to set baord config to the same parameters...
on the faulti system however I see the instrument with the MAX and I can send commands, without problems !!!!
Also the driver you posted does not work (but the NI-communicate program ;-)
i have no clue what else to do!
btw. how do I copy the spy output when running the program? I may provide
this to find errors.
Since MAX indicates the board is all right I guess it is not necessary to reinstall the boarddrivers?!

Embedded systems (PIC based): We are looking to upgrade our GPIB controller chip from Ines iGPIB7210 to a more "mainstream" chip and are interested in NI's offerings.

Ines provides a library of ANSI C source to drive their GPIB chip from any suitable processor (as do ComputerBoards). Do NI have a source code library for their driver chips? BTW it doesn't need GPIB "Controller" capability. The uP controlling the GPIB chip is a Microchip PIC18C452.

Hi Mr James,
Thanks for your question ..We are also planning to have GPIB interface for our equipment .Again we are new to the interface design .For our equipment we dont need controller capability.I think Ni TNT 488.2 T/L is suitable for our application .But we are stuck with this ...Our equipment has a PIC 16c77 MCU.
If you can help regarding the procedures to be followed for having this GPIB interface that will be great!!!
I have some doubts regarding this.
1. How we can use the TNT 488.2 chip in our equipment board.
2. How we can controll this GPIB chip Is it is done by PIC controller?
3. Is above PIC is compatible with TNT 488.2 T/L.
4.Do we need to program the GPIB chip.I know that there is a devoper kit ESP-488 package is there .How we can
develop program for GPIB using this package.
5. Who will help in designing the same
Please help me .
Thanks in advance.
regards
Prasad

Sometimes GPIB controller did not command the instrument to talk while the high-level program did have "READ" command.

GPIB controller should send "UNL", "LA0", "TAxx" to command the instrument to talk. Though the program do have the "READ?" query, sometimes GPIB controller didn't send the above commands from NI Spy, resulting in the system is hanging there. It happens randomly.

HI,
It is not clear to me what is going on. I'd like to get more information.
Could you specify what programming language are you using?. Also, what functions are you using?. What driver version are you using?.
Include any information you think might be helpful. Also, attach the Spy capture.
DiegoF.

What kind of changes I have to do when I move from GPIB Controller to GPIB-USB Controller.

I want to know some information about GPIB-USB Controller. We are using National Instruments GPIB Controller to read and write data in a Instrument called Diagnostic Readout Box(DRB III) which will hook up with the Engine controller of the car. Now we plug-in the GPIB card in to the I/O slots of the Computer. Now, we want to use GPIB-USB Controller instead of GPIB Controller because of its portability and other features. However, we have developed some C++ applications which are available in the form of DLLs that will interact with the DRB III. Do we have to do any modifications in the coding of these applications when we move into the GPIB-USB controller?.

Once the GPIB-USB is configured, it behaves exactly like a PCI-GPIB board so you should not have to change your program. The GPIB-USB is only supported on Windows 95 and 98. If you are planning on using the GPIB-USB on 95\98 you would still use driver version 1.6 or 1.7. If you need to work on Windows Me or 2000, then you will need the GPIB-USB-A and driver version 1.0. The GPIB-USB is not supported on NT.
The USB-A driver does not allow you to use GPIB device templates. This issue is covered in Knowledge Base 266CNP00 (see link below).
http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/862567530005f09f862569ec006c8bef?OpenDocument
Kim L.
Applications Engineering
National Instruments

Sbus and scsi gpib controllers

I have a Sun box with an sbus gpib controller in it and need to another
controller.
I am considering adding the scsi bus gpib controller. Is this possible?
My main concern is over driver/kernel parameter conflicts - is it a
valid concern?
Has anyone else done this? What were your results?
thx.

It is difficult to specify the expected lifetime of the card.
You said that your system works if you change the cables, making the total cable length shorter. Can you change the cables without making the total cable length shorter? This may indicate a faulty cable rather than a drive problem with the controller.
When your system fails does the card lose context? By this I mean do the registers reset to their default values? You should be able to determine this by checking status to see if the board is still listen/talk addressed or CIC like it was before the failure.
Also, can you be more specific about the failure? How do you know it has failed and what do you do to fix it?

NI 488: command requires GPIB controller to be controller in charge

Hi I'm trying to simulate a charge controller for an electrical vehical prototype. I'm using cRIO for communication between the charging station and LabVIEW. Sometimes while running the program, the above error is displayed and I have to restart the communication module, charger and motor for controlling the vehicle prototype. The error points to the enqueue element function and this happens rarely, but randomly.
it says "an input parameter is invalid". what do i do to fix this?

First of all, if you aren't using GPIB, then ignore the GPIB part of the error message. Look at the part before that. Error code 1 returns this:
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
When coming from a Dequeue Element, that tell me that either a) you closed your queue but didn't stop your consumer loop or b) you somehow lost your reference in your consumer loop.
we need code in order to properly diagnose this. I recommend zipping up your project and posting that zip file.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to configure the GPIB controller in LABVIEW or MAX to send UNLISTEN and UNTALK when each message ends?

In a PC to PC GPIB configuration, one PC is used as a non-controller and it reads either LACS or TACS status bits continuously. It apears that the controller PC does not send UNTALK and UNLISTEN at the end of each message. The non-controller reads and writes therefor times-out.
What is the correct message synchronisation for a non-controller?
I use Labview 6, PCIIA, WIN98SE.
Thanks.

Are you using LabVIEW as the controller, non-controller, or both?
NI-488.2 does have a configuration option to enable unaddressing. I am not sure of where it is in LabVIEW, but if you search for unaddressing, you should find some information on it. With unaddressing, NI-488. will unaddress the device after communicating with it.
If you are not using LabVIEW as the non-controller, National Instruments does have a software package called NI-Device that may help. This is an API designed for non-controllers. It does not currently have a LabVIEW interface. It works under C++ with a PCI-GPIB board.
A third option is to rewrite your device application. Your device should really not care about TACS or LACS as you read them from the status register Your device
should only look for LACS, DCAS, and perhaps DTAS (if you desire triggering). When it is LACS, it should read data. After a read has completed, it should interpret the data and get ready for a response. It is only at that moment that the device should look for TACS (and DCAS). It is hard to put a flowchart here, but if you design the flow of a standard instrument, you will see some patterns about when to look for certain status bits.

PS3 Controller Help: Controller not charging/or syncing

Hi I have recently moved, i have the same console (cech-2002a) and 2 Sony controllers i went to set up my console, but the controllers wont charge/sync i plug in the cord and press the ps button on the controller and nothing happens the controller lights just blink then turn off after 20 seconds, so then i brought another cord from kmart and still nothing both the controllers wont charge when i plug them in they just blink then turn off i have tried both the usb ports on the console but still nothing i have also tried the reset button on the back of the controller, i have also tried leaving it plugged in but the controllers wont even charge someone please help !

Can you spell "warranty?"

GPIB controller in charge

Similar Messages

Maybe you are looking for