I would prefer both, but the generic-device option would be most useful to
me at this time. I have a PXI-5102, but have to share the card with someone
who actually uses the asset. I just need to be able to develop software for
the other person and get my system to behave in a reasonable enough matter
so that I can "work on other aspects" as you say. I would have access to
the real device on enough occasions to make sure I didn't attempt any
unsupported parameter values...
The device-aware option would be useful if I have written a solution around
one device ( such as the 5102 ), and need to test the software's behavior if
another device is used at a later time.
You guys probably have a better handle on the different scenerios than I...
Does NI-Scope work in with RDA??? ( I've made simple, unsuccessful attempts
at getting it to work ).
Thanks
Michael Enz wrote in message
news:388f6a84@newsgroups.ni.com...
> Simulation is not supported in NI-Scope 1.5. But it will be in the
future.
>
> How would you use simulation support? Do you want generic support, so a
> program that runs on a specific device (such as the 5112) works without
the
> device. This would allow working on another aspect of the program without
> the hardware being present, but the scope parameters would not be checked
> the same as when the device is present. The simulation support could be
the
> same for all NI products, but it wouldn't accurately check if the hardware
> supported the functionality being simulated. For example, we could allow
> the user the program flexible resolution mode during simulation, but the
> code may only work with a 5911 when you actually have a 5102.
>
> Another option is specific support for each NI board so a program could be
> developed without the device and would work when the device was added?
This
> requires explicit definition of which device to simulate and it would
> accurately check inputs. For example, error messages would indicate if
the
> user attempts to simulate outside of the allowable voltage ranges or uses
> flexible resolution mode when the hardware doesn't support it.
>
> Thanks for your comments,
>
> Michael Enz
>
> Chris Lincoln wrote in message
> news:388cb59a@newsgroups.ni.com...
> > What does it take to use the NI-Scope library when no hardware is
present?
> > I have installed the following chunks of software:
> >
> > NI-DAQ 6.6.0
> > Visa 2.0.1
> > IVI 1.5.2
> > NI-Scope 1.5
> >
> > In the measurement and automation explorer, there are all sorts of
> > interesting simulation options, but I can't seem to get anything to
work.
> >
> > I am using the GettingStarted MSVC MFC sample. The errors I am getting
> > back, depending on how I have fiddled with the MAX, are:
> >
> > 0xBFFF0011 ( resource not present )
> > 0xBFFF0012 ( parsing error )
> > 0xBFFA4001 ( driver simulation is not possible in NI-SCOPE )
> >
> > Can someone please enlighten me on the steps necessary to configure a
> > resource for simulation which can be used by an MSVC application?
> >
> > Thanks,
> > Chris Lincoln
> > ULTRAX, Inc.
> >
> >
>
>