IviSwtch Compliance Test IVI Specific Driver in CVI crashing

I have problem with IviSwtch Specific driver. I have finished all code for this driver and try to test in CVI tool called "Test IVI Specific Driver". Structure and Function panel test runs without any error. Problem is with Compliance test which returns:
the driver could not be initialized through the class driver.
Compliance Test was halted.
Error returned: bffa0011
Error Message: Function or method not supported.
I tried to add exports to dll in according to this solution http://digital.ni.com/public.nsf/allkb/1DCA138862E75119862576C5006EA144
After doing this Compliance test just crashing and I have to close it down.
Does anybody met this kind of problem? I would be grateful for any help.
Regards
Tomasz
Solved!
Go to Solution.

>>The DLL version format is valid.
ERROR: The DLL version is inconsistent with the version in the header file.
All attributes have correct names.
All attributes have correct data types.
This error means the revision of the generated <driver_prefix>.dll does not match the Major and Minor version defined in header. This should not be a conern if you will not release the driver to customers and you take care of revision.
>>ERROR: The driver is not c>ompliant with the Inherent group because:
-The following Inherent attributes are not implemented:
INSTRUMENT_MANUFACTURER
INSTRUMENT_MODEL
It is hard to tell the root reason of this issue, but there might be something doesn't work in your code. How about post these attributions' definition? OR send your project to [email protected] I think NI could help to take a look into it.
Thanks,
Charles

Similar Messages

Delploying IVI-specific drivers

Whats the requirements for an IVI-specific driver to be listed in the Teststand-4.2.1 deployment tools Drivers and components list ? According to the windows software tool I've installed 6 IVI-specific drivers ( see picture)
but only 3 of them are listed in the deployment tool:

Markus,
you can only select drivers and components which are created by NI. Therefore, i assume the following things:
- You downloaded instruments drivers from ni.com. Even if you downloaded it there, the driver itself might not be created by NI.
- Since not all instrument drivers are from NI, they will not appaer as "NI component" in the deployment utility.
- If you would check the entry "NI Software" in the OS, the given three instrument drivers are also listed there, the other (missing) three are not.
I am not aware that you can change anything on this. If you want to distribute one of the other three instrument drivers not listed in the deployment utility, you will have to use "Custom Commands" to 'trigger off' installation of your drivers you supplied with the installer. To achieve this, add the installation package of the driver to the deployment kit and copy it to the target location using the installer settings. You can configure custom commands to launch the installers of the drivers.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Encore CS5.1 Blu-ray Replication Problem - Master Failed BDA Compliance Testing

I've authored a Blu-ray in Encore 5.1
I purchased and used BluStreak Tracer with Export BDCMF
I sent the BDCMF to Cinram for duplication.
From Cinram I received "Master Failed BDA Compliance Testing"
The specific error is:
Verifier: Sony BD-ROM Verifier for FS and AV
Version: Version 2.04 Build 0049
Compliance: ERRORS DETECTED
Errors: 1
Warnings: 0
INPUT INFORMATION:
Source: DISC IMAGE
Type: BD25
Layer 0 Logical Sector count: 9008416
Path: Z:\01 TO_BE_BD_AACS_PROCESSED\SA_BPVZBG1001.1.A\Lovers Exile BDCMF\UD.DAT
ERROR INFORMATION:
   Code: ES1711: Dolby Digital (AC-3) and Dolby Digital Plus audio streams
   Summary: The bsid field is not set to 1000b (8), or 110b (6). (See BD-ROM Part 3-1,
            9.9.4)
How may I fix this problem? How do I get Enocre to set the bsid field to where the specs require it?
Are there any other work arounds to this particular problem as I am in a bit of spot because my client wants to distribute this fine disc we have created and Cinram will not because the Encore authoring does not appear to be conforming to the official specifications? A fair bit of money is on the line.

Finally made it throug to tech support and they created a case number and they will call me when they have a solution. I'm not holding my breath. In the meantime I've got to find a solution.
The audio is encoded in the m2ts file so I’ve got to do the audio and video together. I’m considering re-encoding via Encore but using H264 instead of mpeg but I’m not sure what audio encoding options are available as of yet if I go that route.
I’m first trying to establish the tools (mediainfo run in cli) to be able to evaluate what BSID is spit out.
Another option I’m exploring is to re-render the m2ts files output by Encore (located in the stream dir) in Sony Vegas and see if they conform to BDA spec. I’d then have to replace the files in the Stream dir and wash it through BluStreak tracer but I’m not confident it will compile the CMF properly doing it that way.
A third option is to encode all the video via vegas, replace the footage in encore with the pre-encoded stuff (telling encore not to transcode it). I'm not sure if I can do this in Encore though.
Again, first step is to get the tools to “see” the problem.
Any advice is appreciated!
James

Are there any tools from NI can generate the pass-through layer (IVI class driver) for IVI class specific driver?

IVI class driver (layer) will provide interchangeable feature for a IVI class specific driver. It would work as a pass-through layer and finally make calls to the IVI class specific driver. Since there could be a lot of functions to be passed through. Are there any tools from NI (Labwindows/CVI or Labview) can do this ?
Thanks a lot.
BTW: the IVI class specific driver interface is generated from Labwindows/CVI tools.

Hi Chris,
Yes, I did. To support interchangability, from my understanding of the IVI specs, there should be another layer IVI-C class driver on top of this IVI class specific driver. As in the IVI‑3.1: Driver Architecture Specification:
Although IVI‑C class drivers export inherent,
base, and extension capabilities, they do not actually implement them. Except
for a few inherent functions and attributes defined exclusively for class
drivers, class driver functions and attributes provide a pass‑through layer to
the IVI‑C specific driver. An IVI‑C specific driver is responsible for
implementing the operations of functions and attributes and for communicating
with the instrument. The IVI‑C specific instrument driver contains the
information for controlling the instrument, including the command strings,
parsing code, and valid ranges of each instrument setting"
So where is this IVI-C class driver and how is it created and communicate with my class specific driver?
Thanks a lot.
Cheers,
IVI‑3.1: Driver Architecture Specification

Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

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 411014

stick to the original thread.

哪位仁兄有TDS3000 IVI-COM specific driver?

Tek發布哪個好像是Tektronix 5000/5000B/5000BE, 6000/6000B, 7000/7000B and 70000 series ，隻有部分function可用在tds3000上，不知是不這樣？
NI的TDS3000 IVI-C specific driver當然可用，用VB6.0的話,還是IVI-COM方便一些。
謝謝，
已解決！
轉到解決方案。

完全看不懂您要表達的東西。
您的程式語言是?
您打算控制的儀器型號是?
您可以上太克的網站找找。
由 Fatty 在 03-31-2009 09:20 PM
上編輯的訊息

IVI-COM Driver

I have recently prototyped an IVI-COM class-compliant specific driver for an instrument. This is still a BETA version but I am going to contribute the driver as an IVI-compliant driver when the development has completed. I would like to know how we can take compliance test and how we can contribute the driver. I previously contacted IVI foundation but no response.

Makoto,
We would be happy to post your contributed driver to the IDNet website in either its beta or completed form. You can submit the driver by completing the submission form on IDNet.
As stated on the IDNet Website, our test tools are currently configured for drivers written in LabWindows/CVI that come with Function Panels (i.e. IVI-C). The only way for us to test your IVI-COM driver is if you could provide an IVI-C wrapper for it.
Finally, who did you contact at the IVI Foundation? The best working group to contact about IVI-COM compliance is the COM Working Group
. I would also suggest that you join the IVI Foundation, so you gain access to shared components and can shape future instrument driver classes.
Thanks,
Bankim Tejani
National Instruments

Specific driver (tkdpo7k) not working in .exe

Hi, I am currently using the IVIscope driver together with the specific driver tkdpo7k. Running the labVIEW code in the labVIEW IDE has no problem but when I build my code into .exe format and run my code, my code returns something like this
The following image is a simpler version of my labVIEW code.
I have tried to debug the application file and probed to check the instrument handler wire before the tkdpo7k block and found out that the logical name is indeed transfered. But everytime the execution reachs the tkdpo7k block, the error above pops out. Does anyone experience this and has any solution for that?
The attachment below is my VI file as shown in the image above.
Thank you.
Attachments:
App Test.vi ‏19 KB

I agree with Ravens Fan.
It does sound like the indicator rounding up due to the number of significant digits being displayed and rounding up.
R

IVI specific drivers usage in Teststand

Hi,
I am using Teststand 2.0.1 and i want to use some of the IVI specific drivers in my application. Can somebody guide me how to do that. Another clarification, if we use the IVI drivers which fall into any of the classes how do we achieve the interchangeability? Is it only through MAX that we achieve it.
Regards,
Siddu

Siddu 140,
I am not one of our TestStand supporters so I may not understand your core question exactly...but I'll give it a shot! We can keep track of our IVI drivers and IVI sessions in MAX as Aaron alluded to. You will have an IVI Drivers tab in your Configuration window in MAX where you can perform a variety of actions. From what I understand, once you have correctly configured your IVI Driver in MAX you can see it in TestStand. I have attached a ZIP file containing a text file of instructions and screenshots pertaining to the instructions that discuss how one configures IVI Drivers in MAX. Also the help window on the right-hand side of MAX when you select the IVI Drivers tab is a great resource (see also: National Instruments' IVI for more information).
With regards to the CAN driver there really isn't the concept of a CAN IVI driver. National Instruments provides a CAN driver for our CAN product line. More information on National Instruments CAN products can be found here: National Instruments' CAN.
I hope this information helps out and if you have any other questions please post back!
Craig H.
Attachments:
IVI Screenshots.zip ‏627 KB

Compiling IVI-C driver source code

I'd like to make some fixes into source code of IVI-C driver 'cause I have found some SCPI-command bugs in there.
What are main steps in compiling the source code, which library function I must include (VISA-library?)?.
I'm using LabView 7.1 and the driver in question is agpsgmxg (source code file is agpsgmxg.c) which I have downloaded from NI's idnet.
I have MS Visual Studio environment.

In CVI you would use Ctrl+K for compiling and then you would re-create the DLL and replace or rename it the existing one that is in IVI/Bin or IVIFoundation/Bin. Can you send feeback to [email protected] mentioned with the bugs found in the driver? So we can document and look into the issue?

SCSI Compliance Test (LOGO), StorageParameters.exe command is failing

Hi,
We have a Virtual StorPort mini driver and I'm running SCSI Compliance Test
(LOGO) as part of HCK, but the test is failing with following error when run against our device.
======================
Exception
TypeName StorageDevices.Device
Message The type initializer for 'StorageDevices.Device' threw an exception.
InnerException
   Message Exception has been thrown by the target of an invocation.
   InnerException
    Message The system cannot find the file specified
    TargetSite System.String QueryDosDevice(System.String)
    StackTrace at StorageDevices.Device.QueryDosDevice(String deviceName) at
StorageDevices.Volume.InitializeObjectCache()
    Source StorageDevices
    HResult 0x80004005
   TargetSite System.Object _InvokeMethodFast(System.IRuntimeMethodInfo,
System.Object, System.Object[], System.SignatureStruct ByRef,
System.Reflection.MethodAttributes, System.RuntimeType)
   StackTrace at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo
method, Object target, Object[] arguments, SignatureStruct& sig,
MethodAttributes methodAttributes, RuntimeType typeOwner) at
System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object
target, Object[] arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeType typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean skipVisibilityChecks) at
System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr,
Binder binder, Object[] parameters, CultureInfo culture) at
StorageDevices.Device.RegisterDeviceClassesFromAssembly(Assembly assembly, Type
typeToRegister) at StorageDevices.Device..cctor()
   Source mscorlib
   HResult 0x80131604
TargetSite StorageDevices.Device GetDevice(System.String)
StackTrace
   StackFrame
    Class StorageDevices.Device
    Method GetDevice
    Signature StorageDevices.Device GetDevice(System.String)
   StackFrame
    Class StorageParameters.StorageParameters
    Method Main
    Signature Void Main(System.String[])
Source StorageDevices
HResult 0x80131534
======================
I also tried to run the test against the MSFT VHD but it also fails with the
same error, here is the command the test is trying to perform
StorageParameters.exe /device
SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\6&1D8CC2C5&0&000000 /outscript
set_params.cmd /sort LargestNonBoot /strictness Preference
From this error I'm not able to figure out what is missing for this test to
fail. Can anyone please help me in understanding the issue here?
Thanks,
Sunil.

Kashif Khan wrote:
THE ISSUE HAS BEEN RESOLVED!
With the same configuration the installation completed successfully on Oracle's Virtual Box. I had a lot of issues while installing Grid Control 11g on VMware, but, that got installed successfully as well on the Virtual Box.
Hence proved, VMware is no good for Oracle virtualization any more.
Hi,
Good if you have it resolved. Now could you please mark the thread as answered to avoid confusion
Cheers

How to deal with visession in IVI-C driver program ?

a ViSession is an identifier that corresponds to a session.
My instrument is a remote internet device . i can call VISA library to implement
communication between labwindows and my remote internet device.In this case , what is meaning of Visession
? It looks as if Visession does not have a relation to my IVI-C driver program.
if it has a relation to my driver, how to deal with the ViSession in IVI-C driver program?thank you

ViSession is necessary as part of a larger picture and fills an important role in good architecture. Intrument handles (stored as the ViSession type) are necessary for large projects, which may require commanding multiple instruments.
There is no function to call which can get or set a ViSession value, similar to the way other attributes are set with driver functions. The ViSession intrument handle is created and returned to the application when an instrument is initialized; it represents a connection with one particular instrument.
This allows users to have multiple instruments connected, which can be controlled programmatically with one application. Then, the application can quickly specify which instrument it would like to send a command, just by sending one instrument handle or another.
Yes, you could remove the ViSession as parameter in your functions, but it would cripple the big picture effectiveness of the driver. In place of the ViSession, you would have to send each function the Resource Name or Resource ID for the particular instrument as well as the Option String. So really, it is just more practical and better practice to use an instrument handle (stored as the ViSession type).
That being said, for certain functionality (adding two numbers), you absolutely do not need a ViSession instrument handle parameter. You will have to use your best judgement to determine where to include or exclude this parameter. I suggest using the ViSession instrument handle parameter with any function that communicates with an instrument.
Also, Ebalci is correct regarding the difference between ViSessions and channels. ViSessions are used to communicate with different instruments. To reference or read a specific channel from an instrument you will have to refer to the guidance in the manual for the instrument in question. There will likely be a command to select a specific channel when reading from the instrument. And for general guidance, I suggest reviewing another IVI driver, possibly for an instrument of the same class or type or maybe from the same family, if such a driver already exists.
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

E3631A IVI class driver can not enable power supply three channel outputs at same time

Hallo,
with E3631A IVI class driver i am trying to enable all the channels at the same time,The problem is that class driver supports only Channel Switching between three Channel,i find in this Forums this Discussion
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/E3631A-IVI-class-driver-cannot-enable-power-s...
is it possible to enable all outputs at same time that I modify the source code and recompile the drivers,but it is complicated for me.
Is there a another easy way to solve this problem??
Would appreciate if someone who has worked on it suggest a method appropriately. Thanks!
Note：Labview 2009 sp1

You'll either have to modify yourself, ask the poster in that other thread for it, or use the LabVIEW driver.

ViClose session not called after Read operation Timeout in an IVI COM driver

Hi everybody
I have a small VI sample that is initializaing an IVI COM driver for an OPM instrument, set some parameters into the instrument then is doing a single Read power measurement. My Read operation receives a single parameter called MaxTimeout that user could change depending on his own interest. Inside the Read function I change temporarily the VISA query timeout to user timeout but at the end of Read operation the original VISA session timeout is reverted to its original value before Read operation was called. If the Read operation timeout is long enough for the Read operation to complete ( 100 ms or more) the VI is doing its job and when finished the viClose is called twice for DefaultHandler and for OpenHandler.
If the Read operation timeout value decrease ( 50 ms) then Read operation could not be completed and a Read Operation Timeout error is thrown from inside this method. This error is then propagated trough Error path until the VI end in a Simple Error Handler. Now on my VI I close all open references to my driver interfaces but I don't know why VISA itself is not calling viClose on the DefaultHandler and OpenHandler as in the case when was no VI error. I could see all these diferences in my NI Spy window and I could post this if that could be of any help. Bear with me cause I am more a C, C++, VB programmer and much less of a LabVIEW programmer. BTW the Error Handling from LabVIEW looks a a little weird and the only sure thing is that I wired in Error In and Error Out path in all my VI calls. What kind of error handling should I perform on the Read method in order for VISA to close properly both OpenHandlers even if there is an error in my VI?
Thansk
sorinvalea

So viClose is not called by VISA after an error takes place in a VI that is calling some operations on an IVI COM driver.
I discovered that all VI sessions opened trough VI that encountered a timeout error in Read operation and that were not properly closed after VI completed are in fact viClose by the LabView itself when I am closing LabVIEW application.
So these left over open vi sessions are kept aside by LabVIEW until it closes itself and then clean them one by one by calling viClose on them....

How to count interrupts of a specific driver / HW

I am using Perfmon to get #interrupts/sec.
I can also drill down to single core resolution (e.g. core0, 1, 2, 3 in a 4 core CPU)
This is good, but i would like to get interrupts/sec for a specific source (e.g. network interface card) or all interrupts handled by a specific driver.
Couldn't find this capability in Perfmon.
does anyone have an idea?
Thanks,
Ami

No version of Reader offers word counting or word auditing.

IviSwtch Compliance Test IVI Specific Driver in CVI crashing

Similar Messages

Maybe you are looking for