NI-488 2.2.6 vs NI-488 2.2.7

I am using NI-488 version 2.2.6 and older on my PC, mostly with Visual Basic Test programs.
Since the installation of TestStand 4.2 and LabView 2 days ago, the NI-488 is now updated with version 2.2.7.
Now when I execute Visual Basic programs accessing GPIB, my computer and Windows XP crash, giving a blue screen with the following info:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
PAGE_FAULT_IN_NONPAGED_AREA
If this is the first time, ..........
Check to make sure ..............
If the problem continue, .......
Technical information:
** Stop: 0x00000050 (0xFFFFFFFD, ox00000008, 0xFFFFFFFD,0x00000000)
Beginning dump of physical memory.....
De-installing and re-installing of NI-488 drivers gives no correction.
Any corrective action (or application note) is available?
Thanks.

After investigation, the crash is due not the NI-488 driver, but to the NI-DAQ 7.4.4 (legacy) driver. We have PCI-DIO-96 cards on our PC, with driver 6.9.3. When TestStand 4.2 and LabView was installed, the 6.9.3 driver was not properly removed, and there was a confilct with version 7.4.4.
By doing a repair on the NI-DAQ 7.4.4, the driver 6.9.3 was then removed, 7.4.4 was repaired, and the crash problem was then solved.

Similar Messages

Error 7 occurred at Open File+.vi:Open File,NI-488: Nonexistent GPIB interface

I did some clean-up of my computer and have been having issues ever since.
I'm not the one that did the programming; the person who did is long gone.
The VI loads fine but when I hit run I get:
Error 7 occurred at Open File+.vipen File
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
All the necessary VIs are available and I've tried changing all the file calls in the VIs to the new locations but the error is the same.
Any suggestions?
Thanks.

Error 7 is a generic file not found. If it is happening after cleaning up files, more than likely you moved some subVIs called in a main VI to a new location on your computer. If all the VIs are in a project, a possible solution would be to remove the vis in the project directory and add them back to the project as they may be pointing to a previous location where the files were once stored. Perhaps this is what Anon123123123 meant by "linking". Hope this helps.
Regards,
Isaac S.
Regards,
Isaac S.
Applications Engineer
National Instruments

Bad Performance with NI-VISA and NI-488.2 under Win XP

I have an application (originally developed under LW/CVI 5.5.1), that use VISA for both, GPIB and serial communication. The application runs fine under NT 4.0 but under XP there are delays in conjunction with serial communication, which slow down the whole application. I already compiled the application with LW/CVI 6.0, installed NI-VISA V. 2.6.0 and NI-488.2 V. 2.0 but this didn't change anything. Do you have any ideas?

Hello Michael,
We have noticed the reduction in system performance in Windows XP when multiple ports are installed, and large packets are being read/written at high baud rates (460.8k). Performance is acceptable when using smaller packet sizes or slower baud rates (115.2k for example). It appeared to be a bug in XP, because the problem was fixed when a prerelease version of XP service pack 1 was installed.
Regards,
Ray Kong
NI Applications Engineer

A page item on page 'SCHEDULE' at location 34,488 requires rasterization, but is too large to rasterize. Resize it smaller and try again

I keep getting this error,
A page item on page 'SCHEDULE' at location 34,488 requires rasterization, but is too large to rasterize. Resize it smaller and try again

This basically means that there is an object that has its top left corner at x: 34 y: 488 which is too large to be rasterized, it could be due to any large object that is extreme wide or tall.
Try to check page content and then resize it to verify the behavior. Please let me know how it goes.
Thanks,
Sanjit

Error in installing NI 488.2 in PXI system

Hi, all
We have a VA-HR instrument and agilent power supplies, which we are being controlled through USB interface in one computer. all the supplies and VA-HR are controlled via single USB.
Now we want to controll these instruments from another computer which is a PXI system with NI PXI 8105 Embedded controller. (PXI system contains Windows XP service Pack 2)
When the USB cable was plugged into PXI system, it gave folowing message:
Found new hardware, USB serial controller D, and also the GPIB-USB-HS.
So we came to conclusion that it requires USB serial controller D drivers as well as GPIB-USB-HS(GPIB-USB-B) drivers.
For that i did download NI 488.2 2.7.3 from NI website and tried to install that into PXI SYSTEM. But during installation, the process rolled back from driver installation and gave an error. i tried this for atleast three times. In other PC the same .exe source of NI 488.2, successfully installed NI 488.2 software without any error.
I can't understand why this NI 488.2 is not being installed.
LABview 8.6 is already installed in the system.
In short i want to connect my Power supplies and VA-HR to PXI system. Please help me out in this installation error.
thanks and regards,
vishal sakarvadiya

muks
Proven Zealot
What is the error you are getting?
HI, muks
Now I have attached the images with this message which shows sequence of process that was followed during installation of NI 488.2 in PXI system.
STEP-1...
STEP-2...
STEP-3....
STEP-4.....
STEP-5.....

File permission error; NI-488: DMA hardware error detected

I'm running LabVIEW 8.0 on the latest supported SUSE linux. My vi saves a data file. If I save a file named "/home/bill/LabVIEW/data/file.dat," it saves okay the first time. But then if I run the program again, it gives me an error instead of just writing over file.dat (which is what I want it to do).
Error 8 occurred at Open/Create/Replace File in filename.vi
Possible reason(s):
LabVIEW: File permission error.
NI-488: DMA hardware error detected.
Also, I don't know if this is related, but when I click on the folder icon to the right of the file path on the front panel, and navigate to the directory mentioned above, then type "file.dat," I get the message "/home/bill/LabVIEW/data/file.dat does not exist." Shouldn't this *create* the new file?
Thanks,
Bill

You should really start your own thread describing your problem in detail. One of the issues here is that there are two possible sources for the error code 8. Which one is applicable to you? What platform are you on? What version of LV? What are you trying to accomplish? What exactly triggers the error?
Please start again with your own thread and with the answers the questions I asked (as well as anything else that you think might be of value).
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Mapping 488.2 errors to NI iberr

Is there a mapping between iberr and 488.2 standard ESR bits (Command Error, Exec Error, Query Error and Device Err)?
How does one relate to another?
Does the NI driver set iberr based on the values in ESR? If so, what is done with a 488.1 device which does not have an ESR at all.
Thanks
Raj

The ESR is an added function of the 488.2 standard. Its use is primarily from an application standpoint. That is, how the ESR is handled depends on your application and not the driver. The Ni-488.2 is a backward compatible driver that will support both standards. As such, its error codes are generated by a marriage of driver level and hardware level queries. The ESR is not involved with the IBERR generation.

Communication between Lync - Mediant . 488 evt from mediant site when SBC Remote Early Media RTP parameter is set to Delayed

Hi,
I have a problem with Early Media functionality between Lync and Mediant 1000 E-SBC. If SBC Remote Early Media RTP parameter is set to Delayed (on IP Profile Settings level) i cannot establish connection. After receiving 183 Session progress (from Lync site)
call is released with 488 event (488 is sent from mediant site). Before "Not applicable here" in logs i can see:
6d:9h:46m:35s (      lgr_flow)(18219     ) #MediaResourcesConnector::AllocateMediaResources
(lgr_media_connector)(18220     ) MediaResourcesConnector:CalculateResourcesForAppExtensions Leading:DSP Opposite:NONE MediationLevel:NONE
(lgr_media_service)(18221     ) ServicesMngr: Allocate Media channel. current active: 0 and max is: 0
6d:9h:46m:35s (lgr_media_service)(18222     ) !! [ERROR] ServicesMngr: Cannot allocate more Media channel. current active: 0 and max is: 0
6d:9h:46m:35s (lgr_media_service)(18261     ) (#292) ChannelResource Deallocated.
6d:9h:46m:35s (lgr_media_service)(18262     ) (#293) ChannelResource Deallocated.
I need this because if im using SBC Remote Early Media RTP = Immidiately i cannot hear ringtone. Could someone give me any clues what is wrong in config?
I enclosed detailed logs:
Log is Activated 6d:9h:46m:35s (       lgr_sbc)(18057     ) (#51) SBCRoutesIterator Allocated.
(       lgr_sbc)(18058     ) Classification Succeeded - Source IP Group #2.
(       lgr_sbc)(18059     ) CallAdmission::AddDialog: Type INVITE Direction In IP group 2: 1 SRD 2: 1 SRD ovflw:1 used unres:1
(      lgr_flow)(18060     ) (#51)SBCRoutesIterator::Change State From: InitialRouting To : AlternativeRouting
(       lgr_sbc)(18061     ) CallAdmission::AddDialog: Type INVITE Direction Out IP group 1: 1 SRD 1: 1 SRD ovflw:1 used unres:2
(      lgr_flow)(18062     ) (#51)SBCRoutesIterator::Next route found: Route by: IPGroup , IP Group ID: 1, Live:1
(       lgr_sbc)(18063     ) Routing Succeeded -IP2IPRouting Rule #2.
(      lgr_flow)(18064     ) ---- Incoming SIP Message from switch:5060 to SIPInterface #2 UdpTransportObject[#2] ----
6d:9h:46m:35s INVITE sip:1234@Mediant;user=phone SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: replaces,timer,path,100rel
User-Agent: OmniPCX Enterprise R10.1.1 j2.603.33.a
Session-Expires: 1800;refresher=uac
Min-SE: 900
P-Asserted-Identity: "TPSA 12" <sip:221111111@switch;user=phone>
Content-Type: application/sdp
To: <sip:1234@Mediant;user=phone>
From: "TPSA 12" <sip:221111111@switch;user=phone>;tag=434636a077aeb3418ef3d5c0887debbd
Contact: <sip:221111111@switch;transport=UDP>
Call-ID: 5050e7eb34568795c049d14a6b088172@switch
CSeq: 1290334631 INVITE
Via: SIP/2.0/UDP switch;branch=z9hG4bK668ced008893ef177292c6f0f662ca02
Max-Forwards: 70
Content-Length: 265
v=0
o=OXE 1415263596 1415263596 IN IP4 switch
s=abs
c=IN IP4 172.16.20.32
t=0 0
m=audio 32156 RTP/AVP 8 4 97
a=sendrecv
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:30
a=rtpmap:4 G723/8000
a=ptime:30
a=maxptime:30
a=rtpmap:97 telephone-event/8000
(     sip_stack)(18066     ) New SIPMessage created - #57
(     sip_stack)(18067     ) New SIPSBCCallLeg created - #1695
6d:9h:46m:35s (     sip_stack)(18068     ) New AcSIPCall created - #1922
(     sip_stack)(18069     ) AcTransactionUser::AddMessageToQueue: Queueing message
6d:9h:46m:35s (     sip_stack)(18102     ) SIPCall(#1922) changes state from Idle to Invited
6d:9h:46m:35s (     sip_stack)(18164     ) SIPCall(#1921) changes state from Idle to Inviting
(     sip_stack)(18165     ) SIPSessionTimer<TU#1921>::FillSTRequestData - Session-Timer mode: TRANSPARENT
(      lgr_flow)(18166     ) ---- Outgoing SIP Message to Lync2:5068 from SIPInterface #1 TcpTransportObject[#648] ----
6d:9h:46m:35s (      lgr_flow)(18178     ) ---- Incoming SIP Message from Lync2:5068 to SIPInterface #1 TcpTransportObject[#648] ----
SIP/2.0 183 Session Progress
FROM: "TPSA 12"<sip:221111111@switch;user=phone>;tag=1c1656521459
TO: <sip:1234@Mediant;user=phone>;tag=499c98c8cd;epid=DE8F26F104
CSEQ: 1 INVITE
CALL-ID: 1656462877611201494635@Mediant
VIA: SIP/2.0/TCP Mediant:5068;branch=z9hG4bKac1657277504;alias
CONTACT: <sip:lyfe02.grupa.lukas:5068;transport=Tcp;maddr=Lync2>
CONTENT-LENGTH: 281
CONTENT-TYPE: application/sdp
ALLOW: CANCEL
ALLOW: BYE
ALLOW: UPDATE
ALLOW: PRACK
REQUIRE: 100rel
SERVER: RTCC/5.0.0.0 MediationServer
Rseq: 1
v=0
o=- 89 1 IN IP4 Lync2
s=session
c=IN IP4 Lync2
b=CT:1000
t=0 0
m=audio 52882 RTP/AVP 8 97
c=IN IP4 Lync2
a=rtcp:52883
a=label:Audio
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-16
m=audio 0 RTP/SAVP 8 4 97
(     sip_stack)(18180     ) New SIPMessage created - #55
(      lgr_flow)(18181     ) |       |(SIPTU#1921)183 State:Proceeding(1656462877611201494635@Mediant)
6d:9h:46m:35s (   lgr_stk_ses)(18182     ) |       |       |       #1694:SIP_ALERT_EV(1656462877611201494635@Mediant)
(     sip_stack)(18183     ) SDPBody::New - id = 126
(     sip_stack)(18184     ) SDPBodyMedia::New - id = 541
(     sip_stack)(18185     ) SDPBodyMedia::New - id = 540
(     sip_stack)(18186     ) <BaseSIP SDPSESSION #1694> UpdateChosenMediaByCN - CN as Remote -1
(     sip_stack)(18187     ) SDPBodyMedia::New - id = 539
(     sip_stack)(18188     ) SDPBodyMedia::New - id = 538
(   lgr_stk_ses)(18189     ) SBCOfferAnswerMngr(#1694) changes state from SIP_MEDIA_OFFERING to SIP_MEDIA_COMPLETED
(   lgr_stk_ses)(18190     ) <SESSION #1694> SendToCall - event: MEDIA_NEGOTIATION_COMPLETED_EV m_Call#1852
(      lgr_flow)(18191     ) |       |       (#1852)SBCCall <- (#1694)SIPSBCCallLeg: MEDIA_NEGOTIATION_COMPLETED_EV
(      lgr_flow)(18192     ) |       (#59)SBCCallPlacementFeature <- (#1852)SBCCall: MEDIA_NEGOTIATION_COMPLETED_EV
(      lgr_flow)(18193     ) |       (#1853)SBCParticipantEndPoint <- (#59)SBCCallPlacementFeature: MEDIA_NEGOTIATION_COMPLETED_EV
6d:9h:46m:35s (      lgr_flow)(18219     ) #MediaResourcesConnector::AllocateMediaResources
(lgr_media_connector)(18220     ) MediaResourcesConnector:CalculateResourcesForAppExtensions Leading:DSP Opposite:NONE MediationLevel:NONE
(lgr_media_service)(18221     ) ServicesMngr: Allocate Media channel. current active: 0 and max is: 0
6d:9h:46m:35s (lgr_media_service)(18222     ) !! [ERROR] ServicesMngr: Cannot allocate more Media channel. current active: 0 and max is: 0
6d:9h:46m:35s (lgr_media_service)(18261     ) (#292) ChannelResource Deallocated.
6d:9h:46m:35s (lgr_media_service)(18262     ) (#293) ChannelResource Deallocated.
6d:9h:46m:35s (      lgr_flow)(18263     ) |       |       (#1853)SBCCall <- (#1695)SIPSBCCallLeg: RELEASE_EV
(      lgr_flow)(18264     ) |       |       (#1853) SBCCall changing states from:AlertingState to:DisconnectingState
(      lgr_flow)(18265     ) |       (#1852)SBCParticipantEndPoint <- (#1853)SBCCall: RELEASE_EV
(      lgr_flow)(18266     ) (#1852) SBCParticipantEndPoint changing states from:InitiatedState to:ReleaseingState
(      lgr_flow)(18267     ) (#1035)SBCController <- (#1852)SBCParticipantEndPoint: RELEASE_EV
(      lgr_flow)(18268     ) |       |       (#1035) SBCController changing states from:EstablishingState to:DisconnectingState
(      lgr_flow)(18269     ) |       (#1853)SBCParticipantEndPoint <- (#1035)SBCController: RELEASE_EV
(      lgr_flow)(18270     ) (#1853) SBCParticipantEndPoint changing states from:InitiatedState to:ReleaseingState
(      lgr_flow)(18271     ) |       (#59)SBCCallPlacementFeature <- (#1853)SBCParticipantEndPoint: RELEASE_EV
(      lgr_flow)(18272     ) (#59) SBCCallPlacementFeature changing states from: Initiated to: Releasing
6d:9h:46m:35s (      lgr_flow)(18273     ) |       |       (#1852)SBCCall <- (#59)SBCCallPlacementFeature: RELEASE_EV
(      lgr_flow)(18274     ) |       |       (#1852) SBCCall changing states from:AlertingState to:DisconnectingState
(      lgr_flow)(18275     ) |       |       |       (#1694)SIPSBCCallLeg <- (#1852)SBCCall: RELEASE_EV
(     sip_stack)(18276     ) New SIPMessage created - #52
(      lgr_flow)(18277     ) |       |(SIPTU#1921)DISCONNECT_REQ State:Proceeding(1656462877611201494635@Mediant)
(     sip_stack)(18278     ) New SIPMessage created - #49
(      lgr_flow)(18279     ) ---- Outgoing SIP Message to Lync2:5068 from SIPInterface #1 TcpTransportObject[#648] ----
CANCEL sip:1234@Mediant;user=phone SIP/2.0
Via: SIP/2.0/TCP Mediant:5068;branch=z9hG4bKac1657277504;alias
Max-Forwards: 70
From: "TPSA 12" <sip:221111111@switch;user=phone>;tag=1c1656521459
To: <sip:1234@Mediant;user=phone>;epid=DE8F26F104
Call-ID: 1656462877611201494635@Mediant
CSeq: 1 CANCEL
User-Agent: E-SBC/v.6.60A.260.002
Reason: SIP ;cause=488 ;text="488 Not Acceptable Here"
Content-Length: 0
(     sip_stack)(18281     ) Resource SIPMessage deleted - #49
6d:9h:46m:35s (     sip_stack)(18354     ) New SIPMessage created - #42
(     sip_stack)(18355     ) Resource SIPMessage deleted - #42
(      lgr_flow)(18356     ) |       | TransactionUserMngr::ReturnTransactionUser - #1921
(     sip_stack)(18357     ) SIPCall(#1921) changes state from Disconnected to Idle
6d:9h:46m:40s (     sip_stack)(18358     ) New SIPMessage created - #47
(     sip_stack)(18359     ) Resource SIPMessage deleted - #47
(      lgr_flow)(18360     ) |       | TransactionUserMngr::ReturnTransactionUser - #1922
(     sip_stack)(18361     ) SIPCall(#1922) changes state from Disconnected to Idle

Hi,
On Mediant 1000 E-SBC SBC tab, when set Remote Early Media RTP Behavior to
Delayed, but also check if the following configuration set correctly:
SBC Media Security Behavior: SRTP
PRACK Mode: Optional
Remote Update Support: Supported Only After Connect
Remote Re-INVITE: Supported Only With SDP
Remote Delayed Offer Support: Not Supported
Remote REFER Behavior: Handle Locally
Remote 3xx Behavior: Handle Locally
Enforce MKI Size: Enforce
You can refer this
link
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Communicating between GPIB IEEE 488-1978 Instrument and LabView

Hi,
I'm currently trying to convert some old BBC BASIC Code into Labview 6.1.
The BBC Computer has a GPIB Comms Unit attached to it to communicate with an old Marconi Instruments Microwave Counter 2440 using GPIB IEEE 488-1978.
I am currently trying to get Labview to communicate with the Counter using GPIB 488 vis and a NI GPIB 488.2 Card but I'm not able to get anything out of the Counter or get MAX to even acknowledge the equipment exists.
I was wondering if anyone out there knows if it is possible to communicate with a GPIB IEEE 488-1978 instrument in Labview 6.1 (or any other LV Versions) and if it is, does anyone have a driver for the instrument (Marconi Instruments Microwave Counter 2440 circa 19
84) or having any helpful tips on the protocol for talking to a IEEE 488-1978 instrument.(I have some previous experience using VISA.)
Many Thanks in Advance for your help.
Sammy Mason

I have done this with several instruments. It is best to get a hold of the manual for this instrument and see what commands it uses.
MAX will not find this using the *IDN? query. In MAX, open the "Communicate With Instrument" window and type "ID?" (without the quotes), and hit query. You should get some basic information back from your instrument.
I use GPIB Read and GPIB Write most often. Your instrument probably doesn't support much else. Maybe Clear and Poll.
Be careful if you are using a newer, faster computer. There are Knowledge Bases and Discussion Forum topics that discuss the problems that can arise. To prevent these problems, I created my own Read and Write VIs. They just have a few milliseconds delay before the read or writ
e takes place
Attachments:
GPIB_Read_with_Delay.vi ‏37 KB
GPIB_Write_with_Delay.vi ‏35 KB

AT-GPIB NI-488.1 Jumper settings

I have an old ISA AT-GPIB board (180210-V1 Rev A3) with NI-488.1 DOS-driver that works fine with an old DOS computer. Now I want to move the board to a new computer with ISA-bus but it is not possible to change the application software that is using the card. The old I/O-address of the board conflicts with something else on the new motherboard, so I have to try another I/O-address, but I haven't been able to find documentation of the jumper and dip-switch settings.
Where can I get the infrmation how to set the jumpers and DIP-swithes to use different settings?

Thanks for the answers. I have already found these documents, but the jumpers are different. Attached is a picture of the card.
The working settings corresponding the jumpers and switches in the picture are:
DMA channel: 1
Base I/O address: 02E1H
Interrupt jumper setting: none
Attachments:
NI-AT-GPIB.jpg ‏526 KB

Can a 488.2 controller be used with 488.1 device?

I was wondering if a 488.2 controller can be used with a 488.1 device? I have used the same controller with 488.2 devices with no problems but not with a 488.1 device.

srm,
A 488.2 controller (such as any of NI's GPIB boards) is backwards compatible with a 488.1 device. Both use the same digital communication protocol to address the bus. The main differences in 488.1 and 488.2 are the status model (which is also backwards compatible, 488.2 just added additional functionality on top) and that the 488.2 specification added additional software specifications, such as a common command set and syntax & data structure guidelines, that a 488.1 device would not necessarily understand. So if you were trying to address a 488.1 device using commands or programming calls specific to 488.2, this could be the cause of the problem. I know these abilities are separated into two different palettes in LabVIEW, I'm not sure exactly how they are separated in the text-based languages.
Regardless, a 488.1 device should show up when you "Scan for Instruments" with your GPIB card in MAX. Some things to check are that the GPIB card is installed with the proper drivers (the latest verison of NI-488.2 compatible with your OS) and is detected by Windows and MAX, the cable connections are made properly and the instrument is powered on and has its GPIB interface configured with an address that does not conflict with another instrument. Hope this helps clear up the confusion, have a good day!
Sincerely,
Ross C

Does NI-488.2 gpib driver fo Linux work with RedHat 7.2

ibconf requires libncurses.so.4.0 and in my RedHat 7.2 installation there is libncurses.so.5.0.
So ibconf doesn't work

Hi,
Yes, 488.2 will work on Red Hat 7.2. The easiest way to overcome the problem with libncurses is to use the binary in the static subdirectory instead of the version that is dynamically linked. If this is not an option for whatever reason, many times you can just create a symbolic link in /usr/lib with in this case, the name libncurses.so.4.0. Typically libraries remain backward compatible, so this would also be an option.
Hope this helps out!
Best Regards,
Aaron K.
Application Engineer
National Instruments

NI-488 error after installing 7.1

I just upgraded from 7.0 to 7.1, but I also have 6.1 on my system. Now I am trying to use my 6.1, each time I try to open a file I get the folowing message:
Error 7 soccured at Open File+.vi: Open File
Possible reasons:
LabVIEW: File not found
or
NI-488: non-existent board.
Can anyone, PLEASE, help?

Hey scientist,
Are you using anything related to GPIB/Serial? You posted the question talking about the NI-488 error, but really I think the error you are receiving is more pertinent to the LabVIEW: File not found error. Errors in LabVIEW generally have two possible causes - one is what the error means if LabVIEW caused it, the other is what it means if it was related to the NI-488.2 driver.
So you get a file not found error anytime you try and open any (????) file in LabVIEW 6.1? Does that mean when you try and open a VI in 6.1, or when you use a File I/O VI inside of a 6.1 VI? Can you open that same file up using LabVIEW 7.0 and 7.1? What is the type of file that you are trying to open, and where is it located?
JaredA

Installer Error: Cannot Upgrade NI-488.2

Hi all,
I recently created an installer for one of my LabVIEW programs, and when I ran the installer on another computer I recieved this error:
"Installation Cannot Proceed: Cannot upgrade NI-488.2 : This installer cannot upgrade the installed feature set of NI-488.2 prior to 14.0. Uninstall NI-488.2 then run this installer again. This process will remove NI-488.2 Configuration support and Application Development support (if present)."
Can someone help elaborate on this error, and is there is there a way to not force an uninstall for someone who may have the driver(s) previously installed?
I'm new to building applications so I appreciate any help!

I'm including it because I won't know which customers will have it and which ones will not, so I assumed it would be safer including it in the installer.
However, since I'm new to LabVIEW installers I wasn't aware that this could present a problem for users who already have the driver installed. Would you then suggest leaving it out and letting the cusomers know elsewhere that they need to install it (as a consequence of not being able to opt out of the driver) vs forcing them to unistall to properly run the installer?
Thanks
Josh

NI IEEE 488.2 and Borland C++ Builder 1.0

I have an NI IEEE 488.2 card connected to a HP DVM. I am using this as a
test bed to develop the 488.2 base code for other projects. The rack system
normally runs off of LabVIEW 6.1.
I will eventually move this code over to run an old prober. When I initiate
the program level commands, ibdev or ibwrt for example, through WIBIC I have
no problems. Neither setting up or reading from the meter. When I utilize
these very same commands in the compiled software I get nothing. It's as if
the program isn't even going out and looking for the card.
I have called the decl-32.h and the NI provided .obj file as the language
translator, but nothing.
Any help?
Seth

Diego,
Thanks for the reply. I fixed the problem. It was the machine I was working
on. I had our IT guy give me a more up to date machine and comm. commenced
nicely. I've only written a small bit of C++ and like the Builder
environment. There never was anything wrong with the card, the NI 488.2 or
NI 488 commands.
But, I'm moving on to our LabVIEW 6i. As an engineer, I was appalled to
find that we owned a full version of 6i Development System and are still
testing our production devices by hand.
Being that I am learning LabVIEW, you are sure to hear from me quite a bit.
Any help as to the location of some nice info on communicating with Excel
from LabVIEW?
Regards,
Seth
DiegoF wrote in message
news:50650000000500000034270100-10423
[email protected]..
> Hi Seth,
>
> Do you get any compiler/linker errors? How about run-time errors from
> the GPIB calls?. Do you check the status of ibsta after ibfind or
> ibdev?.
>
> Try to run one of the examples to see what happens. It is really
> strange that nothing happens at all.
>
> DiegoF
> National Instruments.

NI-488 2.2.6 vs NI-488 2.2.7

Similar Messages

Maybe you are looking for