AnsweredAssumed Answered

VI_ERROR_NCIC with 34980A

Question asked by geeffland on Oct 5, 2012
Latest reply on May 4, 2016 by pfoy3

Like • Show 0 Likes0
Comment • 3

We had just recently upgrade from Vee 8.5 to 9.3 and Windows XP to Windows 7. We had run some previous tests in the software over the past 2 weeks or so. No issues popped up. No we are running our next test and in the past 3 days the software has crashed 4 times or more.

It now gets:

Error number: 751
Exception type: System.Runtime.InteropServices.COMException
Agilent34980A: IO Error: VI ERROR_NCIC: Not the controller-in-charge.returned error code: 0x80044212

Error occurred while calling a .NET object
Erroring call was in transaction number 1
Transaction was calling Reading = agilent34980AClass.Measurement.Read(ChannelList)

Object title: Read Sensor
Object type: IVI-COM
In UserFunction: readSensor

-----------------
To me this seems to indicate that the agilent 34980A went out of remote mode. Problem is that nobody was anywhere near the front panel of the 34980A when this error pops up...

Any ideas of how to debug this issue?

Thanks,
Greg

No one else has this question

Outcomes

pfoy3 Mar 1, 2016 4:30 AM

I have been getting this error message with an Agilent 8720ES Network Analyzer. It was during an extended period of
writing and then reading back data from the instrument. It just occurs now and again out of the blue. No one touched the front panel of the instrument when it occured.
Installed on the controlling PC is Agilent Libraries Suite 17.1. The OS was Windows 7.
I suspect it is a timing issue between the write and then the instrument not being prepared for the subsequent read - I will investigate.

Did the poster of the original comment resolve in any way that could be shared here?

Actions

Mike @ pfoy3 on Mar 2, 2016 3:04 AM

Oh that's going to be difficult to debug especially as it only happens occassionally. Is it exacly the same message ( not the controller error )?

My technique for dealling with all intermittents is to first make a ( handwritten ) log. From that you can gain an idea of frequency, regularity, when it happens during the day, whether it always occurs at the same place in the code and so forth. Either that will give you a clue or you can add more debugging e.g. if it always crashes at the same place in the code you can try trapping the error there, maybe save more details from that event and so forth.

HTH,

Mike Watts

Actions

pfoy3 May 4, 2016 11:19 PM

I seemed to have solved the issue I was experiencing, by putting a wait of 10 milliseconds between the write of the OUTPDATA or OUTPFORM key words and the subsequent read of the data series. I have not had reports of mysterious dropouts since.

Actions

3 Replies

pfoy3 Mar 1, 2016 4:30 AM
Mark Correct
Correct Answer
I have been getting this error message with an Agilent 8720ES Network Analyzer. It was during an extended period of
writing and then reading back data from the instrument. It just occurs now and again out of the blue. No one touched the front panel of the instrument when it occured.
Installed on the controlling PC is Agilent Libraries Suite 17.1. The OS was Windows 7.
I suspect it is a timing issue between the write and then the instrument not being prepared for the subsequent read - I will investigate.

Did the poster of the original comment resolve in any way that could be shared here?
Like • Show 0 Likes0
Actions
- Mike @ pfoy3 on Mar 2, 2016 3:04 AM
  Mark Correct
  Correct Answer
  Oh that's going to be difficult to debug especially as it only happens occassionally. Is it exacly the same message ( not the controller error )?
  
  My technique for dealling with all intermittents is to first make a ( handwritten ) log. From that you can gain an idea of frequency, regularity, when it happens during the day, whether it always occurs at the same place in the code and so forth. Either that will give you a clue or you can add more debugging e.g. if it always crashes at the same place in the code you can try trapping the error there, maybe save more details from that event and so forth.
  
  HTH,
  
  Mike Watts
  Like • Show 0 Likes0
  Actions
pfoy3 May 4, 2016 11:19 PM
Mark Correct
Correct Answer
I seemed to have solved the issue I was experiencing, by putting a wait of 10 milliseconds between the write of the OUTPDATA or OUTPFORM key words and the subsequent read of the data series. I have not had reports of mysterious dropouts since.
Like • Show 0 Likes0
Actions

VI_ERROR_NCIC with 34980A

Outcomes

Related Content

Recommended Content