NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR: Dequeue Element in Acquire Semaphore

Hi

 

I'm working with TS4.1 + LV8.6

 

Here's the full error I'm getting:

 

A Run-time error has occurred in step: xMCP Alive?
Sequence: MainSequence
SequenceFile: R:\HLXC1536\Seq\FCU.seq

Error Message: Dequeue Element in Acquire Semaphore.vi:1->NI_InternetTK_Core_VIs.lvlib:Telnet

Read.vi:1->TelnetReadWrite.vi->TelnetReadWrite.vi.ProxyCaller
Error Code: 1

 

Could somebody please give me a hint to what sort of problem I'm looking at?

 

The error only shows up when I select to run another UUT (from the preUUT sequence).  If I select no and let the sequential model finish the test, it will not happen on the next run.

 

The error itself is in a ReadWrite Telnet vi which works fine.  It happens on the first time it is used after the open telnet vi.  Again, it only happens when I select 'Yes' on the question 'run another UUT'.

 

And thought?

 

Thanks

Rafi

 

0 Kudos
Message 1 of 4
(3,656 Views)

Hi,

 

Have you Close the link and not performed the Open again?

 

Regards

Ray Farmer

Regards
Ray Farmer
0 Kudos
Message 2 of 4
(3,638 Views)

Hi Ray,

 

The answer is No.  As I indicated in my original mail (last line) it happens right after the open step.

 

I placed a breakpoint at the open telnet step.  I verified that there's no link before the step and that link exist after this step.  Nevertheless, I get this error message...but only when I chose 'run Another UUT'.

 

Any thought?

 

Thanks

Rafi

0 Kudos
Message 3 of 4
(3,636 Views)

Rafi,

 

In your ReadWriteTelnet VI, are you using all four semaphore VIs (obtain semaphore reference, acquire semaphore, release semaphore, release semaphore reference)? or are you passing in the semaphore reference from somewhere else?  Just make sure you are releasing the semaphore properly and the semaphore reference (either in this VI or at the end of your sequence) properly.  The fact that this only happens on the second UUT seems to suggest that there is a problem with your references not being closed properly.

Eric B.
National Instruments
0 Kudos
Message 4 of 4
(3,565 Views)