wrong memory zone accessed

[bilayer]

Hi, I'm programming a Keithley 2400 sourcemeter with Labview 7 express. Whenever I run the initialize vi, it gives me an error with code 3. I checked the manual and it says "Internal error  Wrong memory zone accessed." I'm not sure what it means. I run the program with other sourcemeter using Labview 6 before and never had this problem. Does anyone know if it's the problem of the instrument or software and how to fix this? Thanks.

[johnsold]

The other definition of Error 3 is "NI-488: GPIB Controller not addressed correctly." Look at the Explain Error... under the Help menu.

What are you using to communicate between LV and the Keithley? What kind of GPIB controller?

Lynn

[bilayer]

Hi Lynn, I have an NI GPIB card (PCI-GPIB for windows 2000/XP) installed on my PC to run all the instruments. It seems that Keithley got the command since it's put in the remote mode once I run the program. But if I search for GPIB instruments it never shows up on the list. Does it have any conflict with the card? Thanks.

Bilayer

[jaga1984]

 have the same problem with GPIB bus , I´m using a GPIB-USB-HS with a 4395 analyzer,  I downloaded the drivers and I can access via block diagram -> functions-> instruments I/O-> Instruments drivers ->ag4395a     ag4395a_from_panel.vi and when I run this vi it takes control of analyzer but when I press calibration button ->calc kit 7mm->CAL KIT (N 50 ohm)  i get:

Error 3 occurred at Send in ANALSEND.VI->NETCAL.VI->Ag4395A_front_panel.vi

Possible reason(s):

LabVIEW:  Internal error. Wrong memory zone accessed.
=========================
NI-488:  GPIB Controller not addressed correctly.

I hope someone  could help me.

Thanks in advance.

[Raj_V]

Hi Jaga,

Perhaps the following snipped from the knowledgebase article here is helpful.

Error Condition:GPIB board (GPIB0 or GPIB1) is not addressed correctly.
Description: EADR occurs when the GPIB board is Controller-In-Charge (CIC) and is not properly addressing itself before read and write functions. EADR is also returned by the function ibgts when the shadow handshake feature is requested and the GPIB ATN line is already unasserted. In this case, the shadow handshake is not possible and the error is returned to notify you of that fact.
Possible Cause: Your GPIB board is configured for the same primary address as the instrument with which you are trying to communicate.
Solutions:

• Never configure your GPIB board to the same address as your device. You should (almost) always leave your GPIB board configured for primary address 0 and no secondary address. Call ibpad 0 and ibsad 0 at the beginning of your program to properly configure your board’s address.
• Make sure that the GPIB board is addressed correctly before calling ibrd, ibwrt, RcvRespMsg, or SendDataBytes.
• Avoid calling ibgts, except immediately after an ibcmd call. The ibcmd function causes the ATN line to be asserted, which tells instruments to expect command messages, instead of data messages.

[valralf]

I'm know I'm replying to an extremely old post but anyhow I'm stuck with the exact same problem you had about 4 years ago: the error 3 message when trying to communicate with a HP/agilent 4395A spectrum analyzer. Did you ever manage to find a workaround for this problem.

Let me know. Thanks

Ralf

[Reyquaza]

Hi Ralf,

Feel free to make a new forum thread! The way our forum works, you'll be much more likely to find help on this issue if you make a new thread rather than reviving an old one.

Rey

NI Applications Engineer