Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>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 <a href="http://www.ni.com/devzone/idnet/development.htm" rel="noreferrer">here</a> and <a href="http://zone.ni.com/devzone/cda/tut/p/id/3271" rel="noreferrer">here</a> . </p> <p>Essentially you should provide a set of VI's (the unit of LabVIEW code) that implement the various operations supported by your device. LabVIEW programmers will chain a sequence of these together using the VISA resource (i.e. serial port) and error in/out terminals which your VI's should provide. See the second link for an example.</p> <p>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. If you can supply adequate documentation of your protocol and it's not hideously complicated then it should take them an afternoon. 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. 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.</p> <p>If you go the DLL route you'll need to check that the parameters you require are compatible with LabVIEW data types. I'm not a C/C++ programmer so I can't tell you in detail what this means but <a href="http://lavag.org/topic/10902-whitepaper-on-how-to-write-a-labview-compatible-dll/" rel="noreferrer">this</a> might be helpful (Rolf Kalbermatter is the guru on interfacing LabVIEW with external code).</p> <p>If you want to find a LabVIEW programmer then National Instruments can refer you to one through their alliance scheme.</p> <p>(Edited to add link to LAVA forum post on writing DLLs for LabVIEW)</p>
    singulars
    1. This table or related slice is empty.
    1. POLabVIEW "driver" - getting started
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USnekomatic
    1. USnekomatic
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. I will definitely do it the right way when we have time to get to it. I just assumed it would be fairly straightforward to get this working.
      singulars
      1. PO
      1. USTim
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload