If you go the DLL route you'll need to check that the parameters you require are compatible with LabVIEW data types. You might want to beta test the result with your other LabVIEW users first, as you won't be in a position to assess the quality of what they do yourself.

If you have users who are keen on LabVIEW then one of them might be happy to do the job for you for an appropriate discount or incentive - it's really not hard for anyone competent in LabVIEW to do and they are the ones who already have their hands on your device and understand what it does. If you can supply adequate documentation of your protocol and it's not hideously complicated then it should take them an afternoon. If you don't want to learn how to do this properly - which your second post suggests you don't - then either create a DLL that exposes the necessary functions, or commission a LabVIEW programmer to write the driver for you. serial port) and error in/out terminals which your VI's should provide.

LabVIEW programmers will chain a sequence of these together using the VISA resource (i.e. If you are prepared to invest a bit of time into learning how to program in LabVIEW, the relevant info on how to develop an instrument driver can be found here and hereĮssentially you should provide a set of VI's (the unit of LabVIEW code) that implement the various operations supported by your device.

Serial port labview driver