GPIB Analyzer not working with IO Trace on same computer

[Kenado]

Following advice on Knowledge bases I want to perform an IO Trace capture simultaneously with the

Analyzer capture on the Field PC.  This is because I have to go to a customer site and want to only

nonintrusive capture GPIB traffic.  The IO Trace does not capture on the field PC which has the GPIB+

card.  When I run IO Trace on the Test PC, it works fine.  I however want to avoid intruding on the

customers setup by say installing IO Trace. 

If I run a Basic Serial Write and Read VI EXE on the Field PC and perform only IO Trace capture this

works fine (no instruments attached - just to check that IO Trace works on Field PC).  If I run the NI

trace on its own on the Field PC and then run the Test PC controlling the Instruments, IO Trace does

not work.

At this stage I am wondering whether Analyzer and IO Trace can't run simultaneously on the same PC? 

Does NI Trace not work with GPIB+ cards? 

Help very much appreciated.  Thanks

[JasonSmith · Accepted solution]

NI I/O Trace and GPIB Analyzer can be run on the same machine, but not in the way you are wanting.

The GPIB Analyzer is actually a logic analyzer that 'listens' to all of the GPIB lines directly from hardware. For this reason, it can be run from any computer connected to your GPIB topology, even it is is not involved in the transers. This allows almost completely non-intrusive logging of the bus.

NI I/O Trace works with NI Drivers to log function calls that are made. These function calls can only be captured from the system where they are called, so NI I/O Trace must run on the test computer. NI I/O Trace will always have a small impact in the timing of the test system, due to the time it takes to log each call.

-Jason Smith

[Kenado]

Many thanks - that makes it much clearer.

Luckily the customer had Measurement and Automation Explorer (MAX) so I was able to run NI IO Trace on their PC.  I used the Field PC with the Analyzer separately.

Many thanks again.