Thanks for everyone's replies - I've been able to track down the
communications manual, and it seems fairly straightforward. That said, if
anyone has some old VIs lying around that they don't mind passing on, I'd
really appreciate not having to re-invent the wheel :)
Cheers,
Christopher
Thanks Lewis - I appreciate your help.
Chris
---
EULA
1) This is a private email, and although the views expressed within it may
not be purely my own, unless specifically referenced I do not suggest they
are necessarily associated with anyone else including, but not limited to,
my employer(s).
2)
G'Day all,
Has anyone had any experience using Brooks Smart Series Flow
Controllers? We've had a customer contact us, and is interested in talking
to their controllers using RS-485, but we haven't had any luck in finding
the comms protocols...
Ta,
Chris
---
EULA
1) This is a private ema
We often have a similar scenario when installing PC based DAQ (including PXI
with Windows) at clients' sites. Usually, the client contact asks us not to
mention certain terms in any of our documentation (eg: PC, Operating System,
PCI Card, etc), and instead call the PC a "Data Acquisition Platform
FYI: Here's the official standpoint from the NI Oceania Branch regarding
their support in New Zealand:
> The main reason for the price difference is the local support and services
> provided. This includes, phone and email support, and on-site services
via
> the local FSE. Basically, this is wha
>From having a quick look through the license agreement, it looks like you
can distribute the DLLs (and no, they don't require registration) freely, as
long as they are part of your professional application (eg: no
redistributing just the DLLs, or including any of their source code, or as a
part of
G'Day Mihai,
As far as I'm aware, although there is no longer a physical NI NZ
office, NI still has a FSE (Archie Garcia) on the ground parttime in NZ.
That said, I'm sure that you're always welcome to either chat to Archie when
he's not in NZ, and/or someone here at Neo Vista System Integ
G'Day Dan,
Have a look at the LabVIEW config file VIs (Functions>>File I/O>>Conjuration
File Vis) - they were created using OOP principles. Probably one of the
most important Vis you want to look at in their hierarchy is "Config Data
Registry" - this is the structured LV2-Style global that acts a
> Subject: Re: How to talk my company into allowing OpenG usage?
> From: "Jim Kring" <[EMAIL PROTECTED]>
> Date: Wed, 14 Apr 2004 17:11:49 -0700
>
> PS - Have you read your NI Software License Agreement lately? Is your
> application authorized and will it be authorized tomorrow? OK, gotta
> ru
The LabJACK is a pretty good starting point - it's USB, has decent LabVIEW
drivers, and doesn't cost the earth: http://www.labjack.com
Chris
Christopher G. Relf
Certified LabVIEW Developer
National Manager
Neo Vista System Integrators Pty Ltd
[EMAIL PROTECTED]
Phone: +61 2 9817 8813
Fax: +61 2 9
> "Accepting the past is smart. Predicting the future is really hard!"
>
> Greg McKaskle
I don't know if that quote was orginated by you Greg, but I like it!
...although I think my staff and clients will come to dislike it in the very
near future :)
> Subject: RE: [W] VI Server vs. System Exec.
> From: "Junginger, Johann" <[EMAIL PROTECTED]>
> Date: Wed, 4 Feb 2004 18:15:34 -0500
>
> >As I understand it a version of LabVIEW can always(?) open a VI written
> >with an earlier LV version but the converse is not true.
>
> That is only true for
12 matches
Mail list logo
