AnsweredAssumed Answered

VRf-Binary switch problem

Question asked by VRFuser on Jun 19, 1997

Like • Show 0 Likes0
Comment • 4

Sue,

I solved the problem by replacing all "VI_ONs" and "VI_OFFs" in the .fp
file with simple "1" and "0". I figured out that the problem was not in
the source code (in this case compiled to .dll) but in the way VEE reads
the .fp file. I am satisfied with this solution.

I went thru the VXI PNP spec several times (it is actually part of my
job ) and I agree with you - it is sort of lax. You did a good job at
HP. VEE at least can read .fps. I just wanted to say that it would
definitely be nice if it supported all the vpp types.

Regards

Michal

--
     Michal.Harhaj@vsb.cz
VSB-Technical University Ostrava
     tel: +420 69 6994882
     fax: +420 69 6919597

No one else has this question

Outcomes

4 Replies

VRFuser Jun 17, 1997 7:25 PM
Mark Correct
Correct Answer

> I have got a Plug&Play instrument driver written in National Instruments
> LabWindows/CVI. I created (also in CVI) a dll out of this driver. I load
> this dll in HP-VEE (3.2) as an I/O PNP instrument. In this instrument I
> call a function that has few parameters including a binary switch with
> VISA values VI_ON and VI_OFF. When I turn things on or off nothing
> happens. All other parameters are changed accordingly to changes made on
> the function panel EXCEPT the binary switch.

Michael,

VEE will only parse and use the #defines that are defined in your PREFIX.h
file, not all the VISA ones too.

In 4.0 VEE will by default handle VI_TRUE, VI_FALSE, VI_NULL, VI_SUCCESS,
and VI_ERROR even if they're not in your .h file.

So I'd say you need to #define those in your PREFIX.h file. Or, upgrade
to 4.0 and use the standard VI_TRUE and VI_FALSE.

Regards,
Sue Wolber
HP VEE engineer
Like • Show 0 Likes0
Actions
VRFuser Jun 17, 1997 11:18 PM
Mark Correct
Correct Answer
Hi VEE users,

has anyone came accross the following problem?

I have got a Plug&Play instrument driver written in National Instruments
LabWindows/CVI. I created (also in CVI) a dll out of this driver. I load
this dll in HP-VEE (3.2) as an I/O PNP instrument. In this instrument I
call a function that has few parameters including a binary switch with
VISA values VI_ON and VI_OFF. When I turn things on or off nothing
happens. All other parameters are changed accordingly to changes made on
the function panel EXCEPT the binary switch.

Any idea?

Thanx

Michal

--
     Michal.Harhaj@vsb.cz
VSB-Technical University Ostrava
     tel: +420 69 6994882
     fax: +420 69 6919597
Like • Show 0 Likes0
Actions
VRFuser Jun 18, 1997 7:31 PM
Mark Correct
Correct Answer
> > I have got a Plug&Play instrument driver written in National Instruments
> > LabWindows/CVI. I created (also in CVI) a dll out of this driver. I load
> > this dll in HP-VEE (3.2) as an I/O PNP instrument. In this instrument I
> > call a function that has few parameters including a binary switch with
> > VISA values VI_ON and VI_OFF. When I turn things on or off nothing
> > happens. All other parameters are changed accordingly to changes made on
> > the function panel EXCEPT the binary switch.
>
> Michael,
>
> VEE will only parse and use the #defines that are defined in your PREFIX.h
> file, not all the VISA ones too.
>
> In 4.0 VEE will by default handle VI_TRUE, VI_FALSE, VI_NULL, VI_SUCCESS,
> and VI_ERROR even if they're not in your .h file.
>
> So I'd say you need to #define those in your PREFIX.h file. Or, upgrade
> to 4.0 and use the standard VI_TRUE and VI_FALSE.
>
> Regards,
> Sue Wolber
> HP VEE engineer

Thanx Sue, finally a light in the darkness.
Anyway, how is it with the PNP spec and HP-VEE? I expected that having
VXIPNP installed on my machine is really all I have to do. Is there
available some written specification of VEE vs. PNP? If VEE does not
automatically know VI_ON, VI_OFF etc. - it is not VXI PNP!?

Regards

Michal
--
     Michal.Harhaj@vsb.cz
VSB-Technical University Ostrava
     tel: +420 69 6994882
     fax: +420 69 6919597
Like • Show 0 Likes0
Actions
VRFuser Jun 18, 1997 7:57 PM
Mark Correct
Correct Answer

> Anyway, how is it with the PNP spec and HP-VEE? I expected that having
> VXIPNP installed on my machine is really all I have to do. Is there
> available some written specification of VEE vs. PNP? If VEE does not
> automatically know VI_ON, VI_OFF etc. - it is not VXI PNP!?

Michal,

The VXIplug&play specifications are available off the web site
http://www.vxipnp.org In VEE 4.0, using VXIplug&play drivers is covered
in the 'Controlling Instruments' manual.

If you read the specifications, you'll find the requirements for
applications supporting VXIplug&play drivers are very lax. For example,
Visual C "supports" drivers, yet it does not read the .fp function panel
file.

VEE, LabWindows/CVI, and LabView are the 3 apps that give you the visual
support, reading the function panel file. Even then, there's no
requirement to parse the .h file or automatically load the .dll or
anything. The only requirement is that if the app does read a file, it
shall not crash unless it finds something illegal. There's no
requirement that the app reads _any_ of the .h files, nor that it supports
_any_ of the defines. And there's no requirement that the app does
all the extras VEE does, like automatically call init and close, check
error return values, pass the VI handle around, allow automatic allocation
of memory, etc. Sigh.

Or, there's no requirement that the app that reads the function panel
(.fp) file shall show the tree view hierarchy, and in fact LabView doesn't
(which in my opinion makes it very hard to use).

But you are right, it would be nicer if VEE supported all the #defines
in vpptype.h and visatype.h, and I have submitted an enhancement request
for this.

Regards,
Sue Wolber, HP VEE engineer
Like • Show 0 Likes0
Actions

VRf-Binary switch problem

Outcomes

Related Content

Recommended Content