Signal Generators

cancel
Showing results for 
Search instead for 
Did you mean: 

trigger line conflicts

Hi Tony
 
Are you mapping triggers manuallly?  Then you also need to reserve the lines in MAX. Otherwise, TClk will grab the same lines and they will get double driven.
 
J
0 Kudos
Message 11 of 21
(5,485 Views)
I reserved the lines that we use (1-5), the MapTrigger calls no longer return errors but the unmapTrigger calls still return the same error.

Message Edited by tonys10 on 02-02-2006 05:43 PM

0 Kudos
Message 12 of 21
(5,479 Views)
I have been playing with reserving trigger lines in max and it is still a bit inconsistent. The routing is "Dynamic" for all channels and Triggers 1-3 will only be used on Bus 2 and Triggers 4 & 5 will only be used on Bus 3. In addition I am using Trigger 6 for the start trigger on both Bus 2 and Bus 3. What "should" the settings be for this?
0 Kudos
Message 13 of 21
(5,469 Views)
From you Capture.spy file I see that you're calling viUnmapTrigger before the viSetAttribute functions. Try calling viSetAttribute before the viUnmapTrigger calls, since that  way the segments in the chassis will be configured. I believe the viUnmapTrigger is failing because the chassis is not yet fully configured (i.e. trigger 6, but from which segment, etc.).
0 Kudos
Message 14 of 21
(5,459 Views)
I moved the UnmapTrigger after the SetAttribute and still get an error, I guess I need to address this problem first.
0 Kudos
Message 15 of 21
(5,445 Views)
any ideas on this?
0 Kudos
Message 16 of 21
(5,417 Views)

Hi

 

From your Spy log, it seems that you have resources or devices in use when VISA is trying to access them to map the triggers.  We need more information, such as your setup or what else is running at the time when making calls to viMapTrigger. This information would be helpful so that we know what has control over the device(s).

 

At this point, I think you should call into NI support to get this issue resolved as quickly as possible.  An application Engineer will be able to work with you on what information we need to determine the issue.

 

Jerry

0 Kudos
Message 17 of 21
(5,394 Views)
I was given a support ID # 710864 on 2/24 but have not heard back from anyone on this. This is the most important issue I have right now so I need to get going on resolving it. Anyone have any ideas?
0 Kudos
Message 18 of 21
(5,322 Views)
Hi Tony
 
I just checked that number and it doesn't come up as a valid number.  How did you get it?  Did you talk to an Applications Engineer?  I think this requires someone who can coordinate different experts to bring the different issues together to solve.
 
Jerry
0 Kudos
Message 19 of 21
(5,320 Views)
sorry, it's 7105864
0 Kudos
Message 20 of 21
(5,318 Views)