Instrumentation Driver Developer Guide Documentation Error p9-44 Ivi_UnlockSession
The source code as listed causes subsequent calls to attribute methods to lock up the development session. Which solution is preferable? Remove the Ivi_UnlockSession statement or add a Ivi_LockSession statement at the top of the method?
Hello Larry,
This looks like a mistake in the DDG Manual. The recommendation would be to add Ivi_LockSession at the top as in the following code (from the latest fl45 source):
ViStatus _VI_FUNC fl45_ConfigureHold (ViSession vi, ViBoolean holdEnable,
ViInt32 holdThreshold)
ViStatus error = VI_SUCCESS;
checkErr( Ivi_LockSession (vi, VI_NULL));
viCheckParm( Ivi_SetAttributeViBoolean (vi, VI_NULL, FL45_ATTR_HOLD_ENABLE,
0, holdEnable), 2, "Hold Enable");
if (holdEnable)
viCheckParm( Ivi_SetAttributeViInt32 (vi, VI_NULL, FL45_ATTR_HOLD_THRESHOLD,
0, holdThreshold), 3, "Hold Threshold");
checkErr( fl45_CheckStatus (vi));
Error:
Ivi_Un
lockSession (vi, VI_NULL);
return error;
If you are interested in driver development, I would recommend downloading some drivers from our website (http://www.ni.com/idnet) and walking through them -- we provide the source to many complete drivers.
Sincerely,
Jeremiah Cox
Applications Engineer
National Instruments
http://www.ni.com/ask
Similar Messages
-
Is there a USB Instrument driver developer tool for CVI
Is there a USB instrument driver developer tool/guide for CVI?
Thanks
Chip B.
Solved!
Go to Solution.Hi! ASIC LabRat,
I agree with your comment. IVI drivers take too much overhead and the executing speed can be very slow compared to the drivers developed using VISA platform. The previous link sent by the NI engineer was very old (2001) and doesn't really help you at all.
Please take a look at this one instead: http://zone.ni.com/devzone/cda/tut/p/id/4713. -
HI, I am having query regarding; Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)
LabVIEW: LabVIEW Instrument Control Course Day 1 coves subject like Communicating with Instruments This lesson describes how you can use LabVIEW tocommunicate with instruments. You will learn how touse NI-VISA, NI Spy, SCPI commands, and theInstrument I/O Assistant to perform instrument I/O. My question is to you,Does LabWindows/CVI: IVI Instrument Driver Development Course covers similar kind of training like Communication with Instruments? I am more interested in learning How to use SCPI commands to perform instrument I/O. Will you please guide me? So I can choose correct training course. Thanks & Regards,Jay +91 90110 62790EXFO Electro Optical Engineering India Pvt. Ltd.701, 7th floor The Ceribrum IT Park,Kalyani nagar. Wadgaown Sheri India, Maharashtra, Pune 411014stick to the original thread.
-
Advanced LabVIEW Instrument Driver Development Techniques
Hi, reading AN006-Developing a LabVIEW™
Instrument Driver and in page 2 I find:
"refer to the Advanced LabVIEW Instrument Driver Development Techniques application note."
I can not find this AN. Is the name correct ?
Bye
LucaHi Luca,
the link you're looking for should be this:
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/e7a1635c2166e0728625680a005b0b9a?OpenDocument
Happy new year,
Alberto -
Labview Instrument driver development-career path
Hi,
How is the career path for a labview Instrument Driver Developer ( Third party instruments like Scope,DMM).First off LINK, just click on your name the link is duplicated in your recient posts on your profile page. (Lots of interesting features in the forums)
As far as career potential for a LabVIEW developer:
All the skill in the world with LabVIEW won't do much unless you can apply it effectively. It is a good skill set to have but, LabVIEW itself is a means to accomplish something else. In my case it facillitates developing automated tests. From your post it would facillitate development of instrument drivers likely, secondary to the goal of facillitating the sales of those instruments. So, you need more than LabVIEW, you should develop skill and knowledge about Instrument driver standards, instumentation, and communications protocols. While you are doing that you also need to be able to demonstrate your LabVIEW proficeincy. Certification can help with that.
Couple some serious understanding of test and measurement techniques with NI Certification and.... well lets just say you can pay the bills with it. I Know.
Jeff -
Instrument driver development wizard strange behavior
Hi,
I was using the driver development wizard and I started getting strange results. It started creating VI's where the text builder portion ws seperate from the VISA communication portion of the code. I had to delete indicators and controls and wire the seperate sections. Also, the VI's dropped the VISA commands and replaced them with nonsense commands. Very strange. I closed and re-opened LabVIEW, but no change.
Has anyone had this happen to them?
Mark RamsdaleHi Mark,
That does seem like some strange behavior. Could you fill me in on some more information?
I'd like to see if I can recreate the issue on my end.
What OS are you running?
Version of LabVIEW?
Version of Measurement & Automation Explorer?
DAQmx Driver?
VISA Driver?
What were you trying to build a driver for? At what point did it start having issues?
Any other useful information you can think of?
Applications Engineer
National Instruments
CLD Certified -
Is there any place where there are open projects for delveloping
drivers using IVI? I know one is ivifoundation.org but that does not
list if any comapny wants the driver to be developed for his/her
instrument.
u'r help will be appreciated as I am interested in developing IVI
drivers.
Thanks,
RKI'm not aware of any listing of companies needing drivers written. I'm assuming that you would like to get paid for driver development so you could try contacting instrument manufacturers and see if they have any need. The biggest (i.e. Tektronix, Agilent) include driver developement in the planning of any new product and usually have an in-house staff doing this type of work but occasionally do go outside. You might also approach instrument manuafacturers that aren't part of the IVI Foundation and try to convince them that a driver will improve sales and that you're just the person that can help. You can also browse the other NI forums such as LabWindows/CVI and Instrument Connectivity to search for driver requests. NI also has a Certified Instrument Driver
Developer program that you might want to investigate as it would probably help you get jobs. Also, you might not want to limit yourself to IVI developement (which requires LabWindows/CVI) but also include the creation of LabVIEW drivers. -
Newly released BOEXI31 Java Developer Guide available
I've been slogging along with the OLD BOEXI3x Java Developer Guide documentation which incorrectly references various security and principal classes.
However, I've just noticed this morning that a NEWER version of the DG is available at:
http://help.sap.com/businessobject/product_guides/boexir31/en/boesdk_java_dg_12_en.zip
which DOES reference the correct packages in the examples and scenarios.
...in case anyone shared my confusion.Thanks for posting!
If you find any further doc bugs, please post in the forums, and I'll be able to forward the info.
Sincerely,
Ted Ueda -
"undefined symbol" error while using a custom instrument driver
Hello all, I'm facing a problem related to instrument driver creation.
I want to pack a part of my code to a .FP to be able to reuse it in other applications of mine. This part of code includes calls to Windows API and a third party dll. I have included both windows.h and the include for the dll in the header file for the instrument. I developed the source code and next a little application that simply calls one function to test the result of my work, but I get some 'undefined symbol' errores while linking the test application with the instrument. The instrument header file is included in program source file.
Situation is as follows:
I can run the test application if I include the source file for the instrument directly in the project (without loading the instrument)
I created a static library and can have the test program up and running if directly including the library in the project (again without the .fp file)
I get linker errors when trying to use the instrument I created based on the same code, both when including the instrument at source code level and when including at library level. Adding the .fp to the project makes no difference
Linker errors are all related to WinSDK and third-party dll functions.
Question is: where and how I have to declare the symbols apart including the appropriate .h files in the instrument header file?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?Being waited on to log on... how flattering
I wish I had a simple and obvious solution, but I don't.
The problem in this case is that, whereas DLLs (via their import libraries) carry no additional build-time dependencies to their clients, that is not the case with object files and static libraries: any project that uses those .obj and .lib files must satisfy all of their dependencies when that project builds.
There is a mechanism, with .fp files, to advertise such dependencies to the clients of the .fp, and that is the auto-load list (Edit>>FP Auto-Load List, in the function tree editor). The caveat, however, is that these indirect dependencies must have a companion .fp that you can add to this list. And in your case, you don't have one. So the only solution I can think of is for you to create a very thin wrapper module where you would wrap all of the SDK functions that you need, then create a basic .fp for this wrapper -- you can do this semi-automatically, from the header file (Options>>Generate Function Tree) -- and then add this .fp to the auto-load list of your primary .fp. And then you'll probably have to create a second .fp wrapper for your other dependency (a non-SDK third-party DLL?).
Once you have declared the dependency chain for this .fp, you should then be able to use it on any test application and CVI should know to link in these additional static libraries whenever it builds the test application.
If you choose to go this route, you'll probably have to deal with a bunch of non-standard data types in the parameters of the SDK functions. I don't remember if these are automatically added to the .fp when you create it from the header file. If not, all you need to do is add them to the .fp later (Options>>Data Types, from the function panel editor). Don't worry about providing the definitions for these data types. They're not necessary. You just need to make sure that their names are in the list.
Luis
Message Edited by LuisG on 05-19-2010 10:43 AM -
Error Deploying Sample Portal from Development Guide
I am going through creating a New Portal from WebLogic Portal 7 Development
Guide and I am running into the following problem.
After completing Step 2: Create the New Portal, when I try to Hot Deploy the
application, I get the following error.
Hot deploy failed with the following message:
Unable to add module: NewPortalWebApp to application descriptor for:
portalApp.
The log has the following information..
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
portlets\Portlet1.portlet to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\tools.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\webflow-extensions.wfx to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\user_account.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\portal.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\security.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\NewPortal.portal to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
-Scott
Mike Friesen wrote:
I'm sorry you were right.. I tried it and everything works... thanks..
Mike
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Hi Mike,
I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
(down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
hot-deploy?
If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
to BEA Support.
Now my curiosity is piqued so I hope you'll let me know either way.
Best Regards,
Scott Ellis
BEA Systems
Mike Friesen wrote:
yes..
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Can you please try something for me? Paste the following URL into abrowser:
http://java.sun.com/dtd/application_1_3.dtd
Does it come up?
Thanks,
Scott
Mike Friesen wrote:
Actually, my computer does have internet access, so I don't think that
is
the problem.
Mike
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Hi Mike,
I would bet that you are working on a machine that doesn't have
Internet
access, correct?
The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
dtd from Sun's website.
If you can't get Internet access, here is the workaround:
- save the attached file to your harddrive (just save it to c:\)
- edit the application.xml file for your project as follows:
- first copy the entire DOCTYPE declaration and save it somewhere
in
a
separate text file (in case want to revert back to it later)
- edit the DOCTYPE declaration so that it looks like this:
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
( notice that the java.sun.com web address is replaced with the URI
to
the file on your harddrive)
- save your changes and hotdeploy will work with or without Internetaccess
Thanks,
Scott Ellis
BEA Systems
Mike Friesen wrote:
I am going through creating a New Portal from WebLogic Portal 7
Development
Guide and I am running into the following problem.
After completing Step 2: Create the New Portal, when I try to Hot
Deploy
the
application, I get the following error.
Hot deploy failed with the following message:
Unable to add module: NewPortalWebApp to application descriptor for:
portalApp.
The log has the following information..
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
portlets\Portlet1.portlet to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\tools.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\webflow-extensions.wfx to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\user_account.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\portal.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\security.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\NewPortal.portal to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.
<!--
Copyright (c) 2000 Sun Microsystems, Inc.,
901 San Antonio Road,
Palo Alto, California 94303, U.S.A.
All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to
technology embodied in the product that is described in this document.
In particular, and without limitation, these intellectual property
rights may include one or more of the U.S. patents listed at
http://www.sun.com/patents and one or more additional patents or
pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed
under licenses restricting their use, copying, distribution, and
decompilation. This document may be reproduced and distributed but
may
not be changed without prior written authorization of Sun and its
licensors, if any.
Third-party software, including font technology, is copyrighted and
licensed from Sun suppliers.
Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail and and
Enterprise JavaBeans are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
Federal Acquisitions: Commercial Software - Government Users Subjectto
Standard License Terms and Conditions.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright (c) 2000 Sun Microsystems, Inc.,
901 San Antonio Road,
Palo Alto, California 94303, E'tats-Unis.
Tous droits re'serve's.
Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
relatants a` la technologie incorpore'e dans le produit qui est
de'crit
dans ce document. En particulier, et sans la limitation, ces droits de
proprie'te' intellectuels peuvent inclure un ou plus des brevets
ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
brevets plus supple'mentaires ou les applications de brevet en attente
dans les E'tats-Unis et dans les autres pays.
Ce produit ou document est prote'ge' par un copyright et distribue'
avec des licences qui en restreignent l'utilisation, la copie, la
distribution, et la de'compilation. Ce documention associe n peut
e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
licence, le cas e'che'ant.
Le logiciel de'tenu par des tiers, et qui comprend la technologie
relative aux polices de caracte`res, est prote'ge' par un copyright et
licencie' par des fournisseurs de Sun.
Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail et and
Enterprise JavaBeans sont des marques de fabrique ou des marques
de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
pays.
LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
CONTREFAC,ON.
-->
<!--
This is the XML DTD for the J2EE 1.3 application deployment
descriptor. All J2EE 1.3 application deployment descriptors
must include a DOCTYPE of the following form:
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
-->
<!--
The following conventions apply to all J2EE deployment descriptor
elements unless indicated otherwise.
- In elements that contain PCDATA, leading and trailing whitespace
in the data may be ignored.
- In elements whose value is an "enumerated type", the value is
case sensitive.
- In elements that specify a pathname to a file within the same
JAR file, relative filenames (i.e., those not starting with "/")
are considered relative to the root of the JAR file's namespace.
Absolute filenames (i.e., those starting with "/") also specify
names in the root of the JAR file's namespace. In general, relative
names are preferred. The exception is .war files where absolute
names are preferred for consistency with the servlet API.
-->
<!--
The application element is the root element of a J2EE application
deployment descriptor.
-->
<!ELEMENT application (icon?, display-name, description?, module+,
security-role*)>
<!--
The alt-dd element specifies an optional URI to the post-assembly
version of the deployment descriptor file for a particular J2EEmodule.
The URI must specify the full pathname of the deployment descriptor
file relative to the application's root directory. If alt-dd is not
specified, the deployer must read the deployment descriptor from the
default location and file name required by the respective component
specification.
Used in: module
-->
<!ELEMENT alt-dd (#PCDATA)>
<!--
The connector element specifies the URI of a resource adapter archive
file, relative to the top level of the application package.
Used in: module
-->
<!ELEMENT connector (#PCDATA)>
<!--
The context-root element specifies the context root of a web
application.
Used in: web
-->
<!ELEMENT context-root (#PCDATA)>
<!--
The description element is used to provide text describing the parent
element. The description element should include any information that
the application ear file producer wants to provide to the consumer of
the application ear file (i.e., to the Deployer). Typically, the tools
used by the application ear file consumer will display the description
when processing the parent element that contains the description.
Used in: application, security-role
-->
<!ELEMENT description (#PCDATA)>
<!--
The display-name element contains a short name that is intended to be
displayed by tools. The display name need not be unique.
Used in: application
Example:
<display-name>Employee Self Service</display-name>
-->
<!ELEMENT display-name (#PCDATA)>
<!--
The ejb element specifies the URI of an ejb-jar, relative to the top
level of the application package.
Used in: module
-->
<!ELEMENT ejb (#PCDATA)>
<!--
The icon element contains small-icon and large-icon elements that
specify the file names for small and a large GIF or JPEG icon images
used to represent the parent element in a GUI tool.
Used in: application
-->
<!ELEMENT icon (small-icon?, large-icon?)>
<!--
The java element specifies the URI of a java application clientmodule,
relative to the top level of the application package.
Used in: module
-->
<!ELEMENT java (#PCDATA)>
<!--
The large-icon element contains the name of a file
containing a large (32 x 32) icon image. The file
name is a relative path within the application's
ear file.
The image may be either in the JPEG or GIF format.
The icon can be used by tools.
Used in: icon
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
-->
<!ELEMENT large-icon (#PCDATA)>
<!--
The module element represents a single J2EE module and contains a
connector, ejb, java, or web element, which indicates the module type
and contains a path to the module file, and an optional alt-ddelement,
which specifies an optional URI to the post-assembly version of the
deployment descriptor.
The application deployment descriptor must have one module element for
each J2EE module in the application package.
Used in: application
-->
<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
<!--
The role-name element contains the name of a security role.
The name must conform to the lexical rules for an NMTOKEN.
Used in: security-role
-->
<!ELEMENT role-name (#PCDATA)>
<!--
The security-role element contains the definition of a security
role. The definition consists of an optional description of the
security role, and the security role name.
Used in: application
Example:
<security-role>
<description>
This role includes all employees who are authorized
to access the employee service application.
</description>
<role-name>employee</role-name>
</security-role>
-->
<!ELEMENT security-role (description?, role-name)>
<!--
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the application's
ear file.
The image may be either in the JPEG or GIF format.
The icon can be used by tools.
Used in: icon
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
-->
<!ELEMENT small-icon (#PCDATA)>
<!--
The web element contains the web-uri and context-root of a web
application module.
Used in: module
-->
<!ELEMENT web (web-uri, context-root)>
<!--
The web-uri element specifies the URI of a web application file,
relative to the top level of the application package.
Used in: web
-->
<!ELEMENT web-uri (#PCDATA)>
<!--
The ID mechanism is to allow tools that produce additional deployment
information (i.e., information beyond the standard deployment
descriptor information) to store the non-standard information in a
separate file, and easily refer from these tool-specific files to the
information in the standard deployment descriptor.
Tools are not allowed to add the non-standard information into the
standard deployment descriptor.
-->
<!ATTLIST alt-dd id ID #IMPLIED>
<!ATTLIST application id ID #IMPLIED>
<!ATTLIST connector id ID #IMPLIED>
<!ATTLIST context-root id ID #IMPLIED>
<!ATTLIST description id ID #IMPLIED>
<!ATTLIST display-name id ID #IMPLIED>
<!ATTLIST ejb id ID #IMPLIED>
<!ATTLIST icon id ID #IMPLIED>
<!ATTLIST java id ID #IMPLIED>
<!ATTLIST large-icon id ID #IMPLIED>
<!ATTLIST module id ID #IMPLIED>
<!ATTLIST role-name id ID #IMPLIED>
<!ATTLIST security-role id ID #IMPLIED>
<!ATTLIST small-icon id ID #IMPLIED>
<!ATTLIST web id ID #IMPLIED>
<!ATTLIST web-uri id ID #IMPLIED> -
INI instrument driver and fatal run time errors
Hey everyone, I'm experimenting with the INI instrument driver and running into a fatal run time error. Here's what I know so far:
The runtime error only happens during the very first Ini_Putxxx
It only happens if the target INI file does not yet exist. After the file is created with a Ini_WriteToFile, then the program will proceed with all my Put functions without any errors.
Ideas?
Solved!
Go to Solution.Are you sure about that? I just tried calling these functions in the Interactive Execution window without errors (the destination file wasn't there before the call and has been created without errors):
#include "inifile.h"
static int error = 0;
static IniText T = 0;
T = Ini_New (0);
Ini_PutString (T, "General", "Item 1", "Test string");
Ini_PutInt (T, "General", "Item 2", 123);
Ini_PutDouble (T, "General", "Item 3", Pi ());
error = Ini_WriteToFile (T, "C:\\test.ini");
Ini_Dispose (T);
Ini_PutXX functions do not make any disk access, they work entirely in memory; the only functions where the instrument accesses the disk are Ini_WriteToFile and Ini_ReadFromFile. Which error are you receiving? Can you post a sample code that exhibits the error?
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos? -
An error on Java Web Start 1.4.2 Developer Guide
I tried to deploy my application using Java Web Start. I used the script in the section "Creating the Web Page That Launches the Application" of the Java Web Start 1.4.2 Developer Guide (http://java.sun.com/j2se/1.4.2/docs/guide/jws/developersguide/contents.html). Nevertheless, it does not detect my JWS 1.4.2 installation. After I search thru the registry on my Windows 2000, I found that the COM object ID is not correct. The orginal VBScript to detect the installation of JWS 1.4.2:
If Not(IsObject(CreateObject("JavaWebStart.isInstalled.3"))) Then
javaws142Installed = 0
Else
javaws142Installed = 1
End If
should be:
If Not(IsObject(CreateObject("JavaWebStart.isInstalled.1.4.2.0"))) Then
javaws142Installed = 0
Else
javaws142Installed = 1
End If
Could JWS tech support or documentation team change this error on the website soon so other developers will not run into the same problem again?
Thanks,
A.A.Please submit a bug.
I believe this is the only way to guarantee Sun will track this. -
I get an error when I use the instrument driver KE230x.
Good day. I am using the ke230x instrument driver connected to a Keithley 2306-PJ. I am using the USB to GPIB to communicate with the instrument
I load the Getting Started VI and when I hit run I get the following error message
====================================================================
Error - 1074003951 occured at ke230x Initialize With Options.vi
Possible reason(s):
Driver Status: (Hex 0xBFFC0011) Primary Error: (Hex 0xBFFC0011) Identification query failed.
Elaboration: Failed to Recognize Model
=====================================================================
When I place the "id query" switch into the false position, everything appears to be working. I have left the "reset device" in the true position and I see the instrument resetting.
I do not understand what is happening?
Thank you for your time and help.Good day. Dennis - thank you for your response. My next question is if I leave the ID Query off (false) position, I still cannot get the program to work.
My guess is that I am doing something wrong (I am relatively new to LabView). I use the Getting Started vi and everything looks to be working okay. I then start the Application Example (I run the Getting Started vi before I run the Application Example to make sure that the Application Example has the correct instrument handle). When I run the Application Example I get the following error message
Error -1074130544 occurred at ke230x Configure Current Limit.vi
Possible reason(s):
Driver Status: (Hex 0xBFFA1190) The session handle is not valid.
Any help or advice would be greatly appreciated.
Michael -
Hi Friends,
When i schedule the report in infoview ,i am getting this error, could you please let me know how to solve this error.
10901: Database error: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.. Contact your Business Objects administrator or database supplier for more information. (Error: WIS 10901)
Thanks
sreedharHi,
I am able to refresh the report in Infoview and data is dispalying , but when i schedule the report in infoview i am getting that error.
I am not clear on below one could you please elaborate on this
You need to create ODBC for SQL server.Check your BO server is able to connect SQL Server.
Thanks
sreedhar -
2 Day Plus Application Express Developer Guide - error?
Good day !
In "Oracle Database Express Edition 2 Day Plus Application Express Developer Guide" chapter 8 "How to Upload and Download Files in an Application" at the topic "Store the Document in a Custom Table" ( page 8-10, 8-11) is recommended:
6. Under Source, replace the process with the following:
IF ( :P1_FILE_NAME is not null ) THEN
INSERT INTO file_subjects(id,NAME, SUBJECT, BLOB_CONTENT, MIME_TYPE)
SELECT ID,:P1_FILE_NAME,:P1_SUBJECT,blob_content,mime_type
FROM HTMLDB_APPLICATION_FILES WHERE name = :P1_FILE_NAME;
WHERE name = :P1_FILE_NAME;
DELETE from HTMLDB_APPLICATION_FILES WHERE name = :P1_FILE_NAME;
END IF;
7. Scroll up to the top of the page and click Apply Changes.
After this I receive Error Message:
ORA-06550: line 6, column 1: PLS-00103: Encountered the symbol "WHERE" when expecting one of the following: begin case declare else elsif end exit for goto if loop mod null pragma raise return select update while with << close current delete fetch lock insert open rollback savepoint set sql execute commit forall merge pipe
Now I can't find mistake. Please, help me ( if difficulties not so big )
WinniReplace by:IF ( :P1_FILE_NAME is not null ) THEN
INSERT INTO file_subjects(id,NAME, SUBJECT, BLOB_CONTENT, MIME_TYPE)
SELECT ID,:P1_FILE_NAME,:P1_SUBJECT,blob_content,mime_type
FROM HTMLDB_APPLICATION_FILES WHERE name = :P1_FILE_NAME;
DELETE from HTMLDB_APPLICATION_FILES WHERE name = :P1_FILE_NAME;
END IF;The second WHERE clause is superfluous.
Regards, Marc
Maybe you are looking for
-
Is it possible to change the values of fields In Me21n tansaction?
I Have to put in some logic to change the values of already existing Shipping condition field in the SHIPPING subscreen at the Line item level in ME21n transaction. I searched for the user exit to do soo. Did not find anything to do this. I would lik
-
Restriction of creating p.o with refe. to service P.R
Dear cons There is no restriction of creating service P.O with reference to service P.R in our company. That means we can create as many number of ser. P.O under one P.R. In case of material P.R restiction has been activated.how can we solve the
-
Re: Bootmanager is missing on Satelite A210-15Y with W Vista
Hi everyone I have a serious problem with my Notebook Satellite A210-15Y. For two weeks I bought it. Yesterday without warnings I had opened just one Window for Internet explorer and suddenly I received around 20 windows of IExplorer. I stopped all t
-
Corrupted iWeb site - Unicode character 194 appears throughout site
I'm using iWeb 3.0.4. The website I created for my wife's business, BarbroDesigns.com, looks perfect within iWeb. When "Put" to ftp-dom.earthlink.net via Fetch, character 229 (Unicode character 194) appears throughout the website. When I first upload
-
2.1 EA1: 8i Connections
Hi, Although unsupported, previous releases of SQL Developer are able to connect to 8i databases but the 2.1 EA1 release displays the following message "Unsupported Oracle Database Version". Is this restriction likely to remain in the stable release?