IVI Drivers : RangeCheck initialization option true : Unable to get an out-of-range error

[NIIVI]

Hi there,

I'm new to IVI drivers (started using them last week) and I have a problem with the RangeCheck initialization option.

In order to get used to IVI drivers, I used the example that comes with the IVI-COM AgilentE36xx driver (on my computer it's located at C:\Program Files\IVI Foundation\IVI\Drivers\AgE36xx\Examples\VS.NET\Cpp\Example1).

I have been able to do all I wanted except getting an out-of-range error when passing an out-of-range value to a function. I set the RangeCheck init option to true but I did not get any error in simulation neither with the hardware connected.

Attached is the code (from the Agilent example) but modified in a way that it should throw an out-of-range error when setting the voltage at the following line: spOutput1->VoltageLevel = 1000; // ... why no error.

Still it's executing fine. Can anyone point me to what I'm not doing correctly.

Regards,

Romain

[gagi1]

It probably depends to what extent the range checking feature is implemented in the driver. National Instruments does not support Agilent IVI-COM drivers so it would probably be better if you ask Agilent for help. I am not sure which exactly model you use but NI provides these two IVI-C drivers: 

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E91E8659CE034080020E748...

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E90F3659CE034080020E748...

[NIIVI]

Hi gagi1,

Thank you for your answer. Yes, I will contact Agilent.

In the meantime, do you have any example of C/C++ code (using IVI-C or IVI-COM drivers from NI) that throw an out-of-range error?

Regarding the links in your reply, I think the drivers are either for LabWindows/CVI or for LabVIEW. Unfortunately, I use C/C++ as ADE.

Regards,

Romain

[NIIVI · Accepted solution]

Hi,

I posted the question on the Agilent Forum.

Here is the link to the post: http://www.home.agilent.com/owc_discussions/thread.jspa?threadID=33348&tstart=0

The problem is now solved. Thank you for your help.

Regards,

Romain