10-23-2008 11:40 PM
10-24-2008 12:20 AM
10-24-2008 12:51 AM
If you using a recent version of LabVIEW there is a instrument driver project wizard, which I think saves a lot of time and creates a standardized driver library that users should be familiar with.
You can use NI VISA for RS232 communication and modify any of the VIs created from the wizard. See "Instrument Driver Modification Instructions" in the LabVIEW help.
10-24-2008 12:10 PM
10-24-2008 07:40 PM
10-25-2008 09:40 AM
10-25-2008 09:26 PM
From the original post:
>>> I want to isolate the user from having to encode communications to the
>>> device and from parsing the results.
You can do all the programming in LabVIEW and still have this request as well. It is called subVI's.
You would do all the encoding and parsing in lower level subVI's. Use higher level subVI's that act as a wrapper for calling the lower level subVI's. It would expose a list of commands (reset, get value, set value, .... whatever makes sense for the device) in an Enum. The user would drop the upper level subVI in his program can select the appropriate command from the Enum that he wants to do. The subVI would call all the appropriate lower level subVI's for encoding and parsing as needed.
The user is isolated from the low level stuff, and the programmer doesn't have to worry about dealing with .dll's, activeX or any other tricky programming to get the communication to work. If the original poster wrote the original app, he can probably figure out how to rewrite all of in LabVIEW.
10-26-2008 10:40 PM
10-27-2008 09:10 AM