We recently upgraded our PCs from Lenovo C20 to C30. Both are running Win7 64-bit, in combination with a NI GPIB card. We are currently using version 2.8 of the NI-488.2 library. All these PC's are used to communicate with different GPIB devices. C30 PC's is however raising unexpected GPIB CIC errors (Controller In Charge), during the communication with the devices. The same program has been running fine over many years on the C20 PC's without the CIC errors.
Here are some of my observations:
1. When the NI-SPY program is running the CIC error did not occur ever after 2 days. When the NI-Spy program was closed, the CIC error occured within a day.
2. I tried changing the IbaTiming config parameter from 350 ns to 2 us as suggested by one of the threads here. That didnt help.
3. I also the added the condition where If the CIC bit was not set, wait until the CIC was set or until it timeouts before calling the Send() and ReadByte() commands. See below code:
if ((Ibsta & CIC) == 0)
{
OutputDebugString("Waiting for CIC or TIMO to be set");
ibwait(nBoardID, (CIC | TIMO));
if(Ibsta & TIMO)
{
OutputDebugString("Timeout Error Waiting for CIC");
}
}
Sleep( 10 );
Send( nBoardID, nDeviceAddress, ptrBuffer, lLength, nEOT );
I never saw the "Timeout Error Waiting for CIC" indicating that the CIC was surely set before calling the Send() or ReadByte() commands, neverthless I see the CIC error.
4. I also tried using ThreadIbsta() instead if Ibsta variable. But that didn't make any difference.
Does anyone have a suggestion or solution for this problem?
Thanks in advance,
SK