has anybody here designed their own server VIs for use w/ DSC?

[dingler44]

I've been browsing viserver.pdf and the DSC documentation to understand what needs to be done to implement a server VI for DSC... but I'm finding the documentation difficult to understand.
I understand the basic 3 tiered layering of DSC with a GUI VI on top, the Tag Engine in the middle and the server VI on the bottom aquiring data directly from the device in question.
Is this server VI supposed to be programmed as if its a driver - sending low level(GPIB in this case) commands to the device to write and read info? I guess where I'm hung up is here: I've already written a driver for my temperature controller device and w/ this taken care of, I'm confused about the roll of the server VI
. Should the server VI use the driver to aquire data from the temp controller or should the server VI itself be the driver and server combined?
I've looked at some of the server VI examples that come w/ LV but I'm relatively new to LV and have almost no time w/ DSC... so the examples aren't helping much.
Any direction or tips for a DSC beginner using a server VI would be great.

Thanks,
Jim

[Chad_Pelletier]

Perhaps a simpler solution for you at this time would be to use the driver VI that you have already created to serve data to DSC. This is done by writing your data to memory tags. Once your data is stored in a memory tag, all of the functionality of DSC will then be available (logging, alarming, security, trending, etc).

National Instruments offers basic skills training courses for many of it's products, including DSC. I recommend that you attend the LabVIEW Basics I and DSC Basics courses. All of the information that you need to perform the above operation are covered in these courses.


Chad Pelletier
Applications Engineer
National Instruments

[dingler44]

Thanks for the suggestion.
Would it be possible for me to do what you suggested and have the Tag Engine on a different computer than the driver VI?

Jim