hp34401a_measure fn

[paulb1]

Help everybody!!

Just down to the one Undefined symbol error - '_hp34401a_Measure@16' referenced . . . . this is after I added the below line to hp34401a.h since it was not present and we have alot of old functions that use measure.

ViStatus _VI_FUNC  hp34401a_Measure (ViSession vi, ViInt32 measFunction,
                                     ViInt32 maxTime, ViReal64 *reading);

Is there any thing else I have to change or modify to get this one sorted?

Many Thanks

Paul

[Seamus_C]

HI Paul,

I have checked our database for any issues found while using the with the HP34401A.  I will need some more information before I can help you further. 

I.   Are you communicating via GPIB or Serial.
2.  What Operation System are you using.
3. What Version of LabWindows are you using.

Thanks,

Seamus

[paulb1]

Hi Seamus

1.   Are you communicating via GPIB or Serial.  Now using GPIB, through a USB-B, was using GPIB through the ISA, but I had problems with the drivers for the ISA
2.  What Operation System are you using. Win2000
3. What Version of LabWindows are you using. Lab8.0

Thanks,
Paul

[Seamus_C]

Hi Paul,

I have a 34401A set up on my machine at the moment.  I do not see any problems.  If you want to send in your code I can have a look at it here for you.

Just attach it to this fourm.  If you have any other questions or if you want to supply some more information about your application, you can add that to your post also.

rgds,

Seamus

[thehobbs]

There are IVI-C and VXIpnp drivers available for the 34401A on NI's Instrument Driver Network.  Make sure that you are using the correct one that your application was developed with.  You should not have to add any entries to the header file, as it would already exist in the driver  you developed the application with.

Jason Hobbs

[paulb1]

Hi Jason,

How can I check if I have the correct  IVI-C and VXIpnp drivers installed?

Thanks

PAul

[thehobbs]

My understanding is that your application was developed with a driver; in particular, a driver with a function called hp34401a_Measure.  You can download the VXIpnp and IVI-C drivers for the 34401a from our site and look for this function in the header file.  Agilent may also provide a different VXIpnp driver for this instrument, so you can check that one as well.

For the future, it would be best to document in your code which driver you are using and where to get it.

Good Luck,

Jason

[thehobbs]

My understanding is that your application was developed with a driver; in particular, a driver with a function called hp34401a_Measure.  You can download the VXIpnp and IVI-C drivers for the 34401a from our site and look for this function in the header file.  Agilent may also provide a different VXIpnp driver for this instrument, so you can check that one as well.

For the future, it would be best to document in your code which driver you are using and where to get it.  Just

Good Luck,

Jason

[thehobbs]

My understanding is that your application was developed with a driver; in particular, a driver with a function called hp34401a_Measure.  You can download the VXIpnp and IVI-C drivers for the 34401a from our site and look for this function in the header file.  Agilent may also provide a different VXIpnp driver for this instrument, so you can check that one as well.

For the future, it would be best to document in your code which driver you are using and where to get it.  Just a

Good Luck,

Jason

[thehobbs]

My understanding is that your application was developed with a driver; in particular, a driver with a function called hp34401a_Measure.  You can download the VXIpnp and IVI-C drivers for the 34401a from our site and look for this function in the header file.  Agilent may also provide a different VXIpnp driver for this instrument, so you can check that one as well.

For the future, it would be best to document in your code which driver you are using and where to get it. 

Good Luck,

Jason