trigger line conflicts

[tonys10]

I have 10 5421 AWG's installed in a chassis (6 in PCX bus #2, 4 in PCX bus #3) operating as pairs through software control. Triggering works fine between the first 3 pairs but fails with the second two pairs with an error indicating that the trigger line was already allocated yet I cannot determine why the system thinks that. I have included a NiSpy capture. (note, remove the .txt extension to import into NiSpy)

[JerryAL]

Hi Tony

Do you have the PXI controller and PXI chassis configured in MAX?

Jerry

[tonys10]

yes

[JerryAL]

Are you using NI TClk?   And only TClking the modules together that are on the same PCI bus segment?  Is this in one large application, or three applications running concurantly? 

[tonys10]

One application, we have 5 clocks in slots 2-6, and then 10 AWGs after that. Are we having some sort of clock signal line conflicts?

[kirsch]

Hello Tony

It's hard to tell what your problem is from the information above. Please describe with more detail:

What chassis are you using?
What version of NI-FGEN are you using?
What are you trying to output with the NI 5421s?
Are you trying to start the signal generators with a HW trigger? All at once? In groups? One by one?
Where is this HW trigger coming from (if it's a HW trigger)?
Are you using NI-TClk to synchronize the NI 5421s?
How are you clocking the signal generators?

The NI-SPY log appears to be corrupted so that's not being very helpful.

Thanks

Marcos Kirsch
Staff Software Engineer - Signal Generators
National Instruments

[JerryAL]

Hi Tony

Can you attach a MAX System Information report?

In MAX, go to the Help pull down menu and select “System Information”.  A window should pop up containing the software information.  At the bottom, a button labeled “Report…”.  Click on the Report button.

IN a new window, select “Simple Report” and select a directory to save it to.  Then click on the Finish button.  It will create an html file containing system information.  It is typically labeled: nireport.html.

Before sending it, please look at the file and verify that it contains a “Max Summary”, which should also list the modules you have and the slots they are in.

Also, we were able to open the spy file after Marcos's post.

 

Jerry

[tonys10]

here you go

[JerryAL]

Hi Tony

Can you answer the questions Marcos posted? 

I didn't see anything out of the ordinary in the nireport file.

Thanks

J

[tonys10]

I actually found a problem with viMapTriggers which may be helpful here. I have included an NI Spy dump of my application initialization. Are there some tricks involving mapping and unmapping of triggers that we are not catching? I also noticed that upon a clean reboot of the PC and external chassis the test case actually functions properly (at least the last set of AWG's that were previously reporting an error)