Monitoring 3 GPIB busses

I need to monitoring 3 GPIB busses with a GPIB analyzer. I have to find out the timing of the communication between the multiple devices on the 3 GPIB busses.
With 3 NI GPIB+ cards and the GPIB Analyzer of NI it's not possible I heard? Some ideas?
Thanks for answers!
Kind regards,
Marc

Thanks for the speedy replies, Harm, Stephen, though I am a little confused because they appear to contradict each other.
I was hoping to edit using three monitors with one video/frame on each, to simulate the effect three projectors will have on three walls of a room. The three monitors idea is more to allow me to see how it's going to be experienced by the viewer. Three pictures on the one monitor could be workable though, if not ideal.
I definitely don't want to output three clips within the one frame as the three clips need to go to three separate projectors.
Essentially, I want to be able to watch three separate videos at the same time, and to edit each video individually but synchronise edits across the three videos, ie so that even if they contain different vision, they will cut to new shots simultaneously. Kind of similarly to how 3D works, except that this is dealing with three cameras not two, and is going to be output to three screens, rather than edited down to one screen.
I guess I could edit the videos one at a time but then I won't be able to see how they are working together, and edit them in relation to each other.
I haven't got as far as researching the projection part yet. I was hoping the project acould finish up as three rendered video tracks in a laptop, slaved to the audio track, and then output video 1 to projector 1, video 2 to projector 2 and video 3 to projector 3.
I realise this may be rather ambitious as I can't find any info on the net that discusses this kind of set up.
When it comes to projection this probably does cross into the world of VJing or presentation. I'm not so worried about the projection part as I think there are ways to get around that, it's more the editing of three videos at once that I'm trying to solve, whether there is a way to do this in Premiere?
Hope this explains a little more clearly?

Similar Messages

Monitoring GPIB commands on GPIB bus automated without NiSpy

Does anybody know how NiSpy intercepts commands to the GPIB bus (first guess is a filter driver)? I need to monitor (automated) equipment activity on our ATE stations.

Basically the National Instrument drivers notify a NI-Spy DLL each time
a driver call is made. If NI-Spy is running, this information is
passed into the NI-Spy executable.
NI-Spy can monitor any supported National Instruments driver in this
manner, but it will not be able to monitor activity on the bus
itself. To monitor actual bus activity you would need something
like a PCI-GPIB+ analyzer card, and utilize the GPIB analyzer which is
included in the NI-488.2 driver.
Jason S.
Applications Engineer
National Instruments

Using a lan/hpib gateway (Agilent) with a NI GPIB pci card

Need to be able to use a E2050 lan/hp-ib gateway (Agilent) together with a NI GPIB pci card on the same workstation (windows). I need 2 seperate gpib busses but also need the remote functionality or the lan/hpib box. I would use ni enet but it will not work together with a installed gpib card, only one or the other. Read information on useing an hp card with a ni card in the same system but cannot get it to work with the lan box. I do not have a hp card to install in my computer to see if that works or not. Has anyone attempted a similar task?

Hello-
It is possible to use a PCI and ENET board in Windows 9X/ME. The solution for Windows NT/2000 is to use the new VISA server technology using two computers.
Computer A:
This is a computer that will not use a GPIB plug-in board, but is on the network. Install the GPIB-ENET/100 driver and VISA 2.6. Then, set the appropriate VISA server permissions and run VISAServer.exe (see the VISA Programmer's Reference for more details ni.com/manuals).
Computer B:
Install the PCI-GPIB driver and VISA 2.6. Use Remote VISA to access the ENET/100 through the other computer's driver.
This is also a very useful technology for remotely controlling numerous instruments throughout a distributed laboratory.
Randy Solomonson
Application Engineer
Natio
nal Instruments

I am trying to monitor activity on an IEEE 488 bus with a NI9914.

I am attempting to do this using ISR2, and trigerring on ATNI. After set-up, I release the swrst in the acr - and the bus locks up. All I want to do is snoop the bus - I don't want to actively communicate. Does anyone know how to do this??
Thanx,Ben Smith

Bill,
There are 2 proper ways to "spy" on the GPIB Buss. One is to use a GPIB SPY card and/or use the NI 'GPIB SPY" application that comes with newer NI GPIB Cards.
You don't want to trigger or interfer with the signal lines of the GPIB buss. The Spy software provides a very complete picture for analyzing buss activity and data transactions. I don't know what platform you're on...let me know I can try to help some more.

GPIB analyzer

I am developing an application in which a diagnostic computer is attached to a system. The system has multiple GPIB devices. What I would like to do is monitor GPIB traffic and trigger events on the diagnostic computer. FOr example, if the main system tells a DMM to measure a voltage, I would like the diagnostic computer (containing an E-series DAQ card) to independently measure the voltage and the state of various I/O lines. The diagnostic application cannot depend on any re-programming of the main system. I had hoped the GPIB+ card would have a SDK allowing captured events to trigger actions, but apparently, that doesn't exist currently. Is there another solution for this application?

The analyzer software will only allow you to monitor the state of the data and control lines. When set, the trigger will just acts as a reference point for recorded data.
There isn't a good way to coordinate GPIB and DAQ measurements. What you can do is poll the data or control lines in software, send out an active edge using DAQ, and use that to externally trigger the DAQ on your diagnostic computer. Be aware that this can't really be used in time critical applications.
Winston L.
Applications Engineer
National Instruments

How can I monitor Status word From the other side of the GPIB bus

I develop Thermal system control that should be operate thru the GPIB IEE 488.2 bus , my instrument application already written in Visual Basic ,The system knowes to do basic operation such as SETPOINT ,AIRDUT , BEGIN , STOP and more but I have do a problem , any time that I capture command from the controller the status word stuck at listener mode and I can not send another command again because my loop is waiting for the other side (the controller ) to tallk by monitor the IBSTA word .
There is anyway to reset ,clear ,initialize STATUS word again to his default value ?
Note : I am using VB 6 , the Samples that you have here for Non-controller is good so far if I want to send and recive data manualy (c
omputer to computer)
What if I have A system that work and always waiting for capture command and do somthing ?
I will be very greatful if anyone can help me , send me sample code for Status checking loop.
MIKI-AVI

Hello Miki-Avi,
I'm having a little bit of trouble understanding what you're trying to do. It seems that you have an instrument application that you have written and works in some instances but gets into an infinite loop in other cases. I think that your loop is waiting for something in the Status byte to change, and you're wondering how you can get it to change.
I'm not sure what bit you're waiting for, but I would assume that it is the LACS bit 2. You do not want to simply reset the IBSTA byte because this byte tells you what is happening on the GPIB interface. So, if you're waiting for the LACS bit to change, then you are waiting for the board to be addressed as a listener. Your controller would address the non-controller as a listener once you sent it da
ta with an IBDEV and an IBWRT call.
If you are looking for code for a status checking loop, check the following resources. Remember that you must call ibwait 0 to update your IBSTA byte. The 488.2 Function Reference is very useful in figuring out what you need to do.
http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3EF8D56A4E034080020E74861&p_node=DZ52353&p_submitted=N&p_rank=&p_answer=&p_source=Internal
http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/9cc0939663f1c5de862565d70082e89e?OpenDocument
Please let me know if you need more assistance.
Scott B.
National Instruments
Applications Engineer

Is it possible to write a gpib monitor to wait for any other process to use it like NI-SPY does?

I need to create a QC application that runs in the background to monitor any sort of gpib communication from other processes to the board. We have several hundred PC's running GPIB programs in various configurations. Modifying existing programs is out of the question since they have already made it through quality control and I cannot have every program that we've written requalified. I had a couple of ideas but they require some tricky stuff. There must be something that I am overlooking...

ceetee, the best thing that I came up with is a bit sketchy, but here it goes. I am atempting this in C/C++.
1) binhex the gpib32 dll, this reports the (exported only?) function calls.
2) create a dll with the same name and function calls.
3) your functions will simply call the old ones, and in the process execute some code of your choosing.
check out this page for better information.
http://www.woodmann.com/fravia/fragas1.htm
This project has been put on the back burner by the brass here at my company, so I haven't gotten to implement it fully. But, I'm fairly certain that it will work even though it's a little arcane. This problem has caused a lot of acid reflux, so let me know if you come up with anything.

USB buss and monitor not being detected

I've been having an issue this last week, where when I start up my Mac Pro does not output video. Judging by the hard disk sounds, it is booting up, but it doesn't detect the video. I think there is an issue with the USB bus, because if I remove all usb devices (including the keyboard) when it boots up it will send video to the monitor.
I've felt since I bought the computer that something hasn't been right with the usb system, it isn't entirely hot pluggable as it should be, and sometimes some peripherals seems to be competing for resources, i.e. if I hook up a phone to sync via USB my USB midi system will won't be detected. Since Snow Leopard these issues have gotten worse, but it could just be coincidence and be an underlying hardware failure that has chosen become worse.
The times when the monitor isn't being sent video, if I press any key on the keyboard it will make a clicking sound through the built-in speaker.
Anyone experience anything similar? I would run the hardware diagnostic utility, but because I need to hold down the 'd' key on the keyboard, and having anything plugged into USB prevents it from detecting the monitor I can't run it. Thanks.
Message was edited by: Eugene Scalisi

Hello Eugene,
Interesting - possible - coincidence. I just posted about a similar seeming issue here:
<http://discussions.apple.com/thread.jspa?messageID=10425731#10425731>
Notice that I've checked Disk Utility's repairs report as well as the System Log with Console: both show mention of USB related items.
This may not have anything to do with your issue but I thought it worth mentioning.

NI GPIB driver support for linux 2.4

Is the NI linux GPIB driver compatible with the Linux 2.4 kernel? Does the NI linux GPIB driver provide a generic device interface (i.e. independent of LabVIEW)? I would like to access the driver using the POSIX interface (i.e. read/write/mmap etc.) via a standard device node (i.e. in '/dev'). We are looking to add a PCI-GPIB interface to our generic control and monitor system. The initial application will involve special purpose software interfacing with external test equipment (scope, power supply, etc.). The current platform is an Intel based industrial PC running Linux 2.4. This system will NOT be able to support data visualization via LabVIEW.

Unfortunately, the current BETA driver (0.6) released by NI does not support version 2.4.x of the Linux kernel. There are plans for support in the future but no timeline has been specified. I would suggest checking back with NI on occassion at http://www.ni.com/linux for the latest news and support of the Linux OS.
Ryan Mosley
National Instruments, Applications Engineer
http://www.ni.com/exchange

Mercury transmit issue - 2nd monitor won't play on 2nd monitor (!)

Hi there
Having an issue with mercury transmit. Am attempting to get playback on my second monitor out of after effects, however all it will do once Transmit is activated is display the feed overlaid on the same screen (i.e. my 'home' screen) rather than on the second monitor.
Have tried every setting I can find, varied preferences, monitor locations, screen sizes etc but nothing seems to work. It works absolutely fine out of Premiere so it is purely an After Effects issue. It is outputting via HDMI to a Panasonic Viera monitor and am working on a new Mac Pro 3Ghz 8-Core Xeon E5 with dual AMD FirePro D700 cards.
Any suggestions gratefully accepted!

Thanks for the screenshot, Zen.
Given all the troubleshooting you have done, and the fact that I can not reproduce the problem, I'm at a loss for an explanation. What appears to be happening is that After Effects is using incorrect coordinates for the second monitor. Whether it is receiving incorrect coordinates from Mac OS or it is incorrectly adjusting the coordinates itself, I can't tell.
That's not to say I'm out of ideas yet.
One question is what do you have plugged into the Thunderbolt ports on the Mac Pro? I assume your primary monitor is connect to one, but what else is connected and which ports are they plugged into?
There are 6 Thunderbolt ports on the Mac Pro, but they only serve 3 Thunderbolt busses, and the HDMI shares one of the busses (ports 1 & 3 are bus 1; ports 2 & 4 are bus 2; ports 5, 6, & HDMI are bus 0). It's recommended you do not have more than one display device connected to a single bus.
So, if you have more than one display device connected to a single Thunderbolt bus, or if your primary display is on bus 0, try changing the ports the displays are plugged into.
Here's a number of other ideas and questions off the top of my head:
- In the Preview panel, is the Full Screen option enabled?
- In System Preferences > Display, for that monitor, what happens if you set the Resolution to Scaled and set the resolution to 1280x720, or any other value?
- Try creating a new user account, and test After Effects under that account. Sometimes there are non-obvious preferences or settings, this is the easiest way to isolate to that.
- Try resetting the SMC and/or NVRAM (PRAM):
-- https://support.apple.com/en-us/HT201295
-- https://support.apple.com/en-us/HT204063

How to monitor DAQ card outputs during TestStand operation?

I am trying to debug a rare failure mode on a test station that runs on TestStand. TestStand controls measurement equipment through a PCI-GPIB controller and a DUT and DUT switch box through two NI-DAQmx devices; PCI-6509, and PCI-6534. I believe that root cause of the failure is due to the software not putting the DUT into the correct state for the test. In order to check this I need to monitor the changes on the GPIB and DAQ cards. I was able to use NI Spy to monitor the commands on the GPIB bus but I have not been able to monitor the state of DAQ cards. Is there a tool that will allow me to pause TestStand during its operation and look at what logic states the PCI-6509 and PCI-6534 outputs are in? Or at least monitor the I/O of the PCI-6509 and PCI-6534 cards similar to what NI SPY offers for the GPIB cards?
Regards,
David

I am not aware of a tool similar to NI SPY for I/O cards.
However you can introduce a break point at the point of interest in a test sequence(step).TestStand will stop execution at that point.
You can then manually verify the I/O status using a DMM .
Hope this helps.

Intermittent GPIB error 6 (EABO)

my system: Mac OS 8.6, Labview 5.1, NI-488.2 for Mac OS version 7.6.3, PCI-GPIB card, Keithley 2182 Nanovoltmeter and Keithley 24xx Sourcemeters.
I have a Labview application (modeled on Keithley's application note "Automatic Resistance Measurements on High Temperature Superconductors") which runs well with >99% reliability. The other times it hangs on a GPIB read with a EABO error. The Keithley instruments will complain "Query interrupted" or "Query unterminated". These problems seem to be more prevalent if the computer is distracted with mouse action or other applications, but it'll fail even without such challenges.
Since the application runs, I know my syntax is good. I've tried increasing the timeouts, but this does not pr
ovide immunity. Software delays help somewhat, but with an unacceptable duty cycle penalty. I suspected that I was getting spurious SRQ's for a while, but the GPIB reads that fail most frequently are not those preceded by Wait RQS.
All my GPIB functions are the old style (not 488.2). I'm not using VISA anywhere, since I've found the VISA functions to be even less reliable on my system.
Any suggestions?

Hello,
I realize I getting into this stream after some correspondence, and that you are asking another poster a question. But, if you are simply trying to get your LabVIEW program not to stop and indicate an error, rather continue and discard it, all you have to do is monitor the error cluster, for example, by wiring it to an error cluster selector input, and then in the error case, simply pass out a fresh, new error cluster constant with status = false (no error), code = 0, and an empty source string. The easiest way to do this is to first wire through the no error case to create a tunnel at the output, and then right click to create a constant in the error case. Attached is a screenshot showing both the the error case and no error cases in a quick example.
I hope this helps! Repost if you are having any further or continued problems!
Best Regards,
Jassem
Best,
JLS
Sixclear
Attachments:
Ignore Errors.PNG ‏5 KB

Signal degradation when using busses/auxes.

i reviewed some mixes done three years ago, when i didn't use subgrouping and the busses were only used for fx returns. my current projects sound muddier than these older ones. am using auxes to sum different sections of the arrangement together now. the results are harsher and muddier. yes, delay compensation is on. transients are smeared right across the spectrum. have gone back to master1-2 outs for final mixes. check it out for yourselves.
G4 Mac OS X (10.4.4) LP7.1.1

Hi kirsen, jim, et al. back in the analog daze, when tracking, the monitor mixer of the neve, ssl was used. at mix time, the signals were routed to the consoles regular input strips. result, increased muddiness, stereo image blur, you name it. solution: use the shortest signal path to the master bus possible. more circuitry = less fidelity. the monitor mix section is simpler (no eq, no inserts, etc) = more accurate reproduction of the source. same is true with daws. macs a serial but reeeeeally fast. so, we get reeeeally fast phase problems. it is all a conjuring trick. the problem cannot be fixed. it can be controlled: do only live recordings with no over dubbing, do dance beatz using only software instrument from the same brand(or same plugin), use only sample patches from the same library and same recording room/sound stage, take all room/ambience/spill out of tracks. we never used sub groups back in the analog daze. mixes took longer, but sounded closer to the original source material. i'm a purist (i love good audio) - so shoot me!
note to jim: try your excellent lavry's with a set of dual concentrics(eg tannoy's) and you will hear this problem better - just make sure the test speakers go down (flat as possible) to 40 or so cycles. all the best DJR.
G4 450DP Mac OS X (10.4.4) digidesign, motu, apogee

Desperate user need help. My GPIB instrument get stuck with my labview program frequently

Hello to all labview users,
i am a beginner in using labview. I am currently writting a labview program to automatically control a digital control rotator HD201e and a network analyzer 8720a to work with the anechoic chamber. The program receives an initial position, amount of increment and # of steps. My program will then ask the controller to rotate to the initial position and at the meantime, the program will monitor the position of the rotator to ensure the requested position is reached. After that, at the position, the program will ask the NA to perform a reading of the measurement. Once the reading is done, the program will ask the controller to rotate to the next position and does a reading of the measurement and so on.
My program seems to be able to perform the tasks; however, the dig.controller part seems to get stuck around 50% of the time when running the program. Sometimes, even the controller receives the requested position (can be seen from the lcd screen of the controller), the rotator just simply would not rotate; also, sometimes, the controller just simply does not respond when sending the command of moving a position, as in the debug mode (the one with a lightbulb), i see that i got "ok" on all the blocks in the writing portion ofthe program, but the controller just doesnt seem to receive the position (as seen no new position received from the lcd screen) and the cursor on the lcd screen blinks weirdly, due to that problem, my program will then get stuck in an infinite loop.....
Usually, that problem occurs after few positions have been reached.....
so, when that happens, i have to stop my program and re-run it. that means the program will have to re-do the measurement that were read previously....
sometimes i have to stop and re-run my program several times to get all the measurement of all the positions done.....so...that bug renders that program to be an unefficient program.
I have been trying to resolve that bug for weeks...but no success....i have tried to put some wait time between each block....result is not much different...
I have also tried putting "clear" block before and after the "write" block.....same problem.....
I have heard that the serial GPIB "flush" block may help...but i tried..but it seems the controller doesnt recognize/accept flush....
i have also tried using the "Visa open" and "Visa close" block to see if ithat reduces the stucking thing....but seems that the controller can still get stuck....
i have also even tried using "lock asyn" and "unlock asyn" block...but didnt seem to work....
Has anyone experienced such problem.? Is it a known problem with some gpib instrument?
Is there any discrepancy or bugs in my program that i am unaware of that causes this problem?
Any advice and or opinion would be greatly appreciated....
PS: i attached the controller part of my program and the overall program
desperate happyguy......
Happy guy
~ currently final year undergraduate in Electrical Engr. Graduating soon! Yes!
~ currently looking for jobs : any position related to engineering, labview, programming, tech support would be great.
~ humber learner of LabVIEW lvl: beginner-intermediate
Attachments:
HD201_Controld.jpg ‏231 KB
AChamber_Measurements_v1d.jpg ‏857 KB
AChamber_Measurements_v1d3.jpg ‏463 KB

hi xseadog
i got what you meant about the gpib reference
actually, that final frame works because the gpib reference is already done inside that subvi.
but my problem doesnt arise from that. most of the time ive seen, it arises between the writing frame and the while loop frame. as i mentionned, sometimes. the controller just simply doesnt rotate even i can see the requested position display on the controller lcd screen; also sometimes, just the controller is stuck without acknowledging the write position command. but in labview...while in debug mode. it is shown ok on the block.
Happy guy
~ currently final year undergraduate in Electrical Engr. Graduating soon! Yes!
~ currently looking for jobs : any position related to engineering, labview, programming, tech support would be great.
~ humber learner of LabVIEW lvl: beginner-intermediate
Attachments:
HD-201 RPosd.jpg ‏39 KB

Monitoring two instruments in one vi

I have two instruments that I want to controll (with LabVIEW) and monitor their output. What is the best programmatic way to do this? Use two parallel while loops?

Hi,
If you are using Visa have a look at locking.vi in the Hardware Input and Output | Visa folder of the examples supplied with labview.
I have used this to avoid tying to address two instruments at the same time when you only have one gpib card.
Regards
Ray Farmer
Regards
Ray Farmer

Monitoring 3 GPIB busses

Similar Messages

Maybe you are looking for