LabVIEW or C? Could you rephrase the question?

[RobCole]

Been a while, but I'm still out here...

I'm now working for a large company developing software that could be deployed to thousands (yes thousands) of computers in the company. LabVIEW was considered and rejected due to licensing issues. Even NI-DAQmx has a license fee and there are a LOT of sites that would need NI vision licenses as well. When you throw in the fact that there can be hundreds of programmers adding modules to the software, the licensing fees were prohibitive.

I still love working with LabVIEW, but I've seen both sides and understand that each language has its strengths and weaknesses.

If you're wondering, I'm doing most of my work in C# .NET these days.

Back to the topic - it's a good article.

     Rob

[RavensFan]

DAQmx does not have a license fee, unless I'm completely mistaken.

Vision certainly does, so that makes sense why you need to avoid the cost of that if lots of sites need it.

[GregFreeman]

---

@Intaris wrote:

---

@Hornless.Rhino wrote:

---

@altenbach wrote:

Just wait until they join the workforce ... 😄

---

We'll see pages of threads here about coding for liquid helium cooled magnetic field control units suitable for use in sub-atomic particle beam deflection?

---

Funnily enough, that's pretty close to what we do on a daily basis.....

Shane

---

NERDS!

[crossrulz]

---

@for(imstuck) wrote:

NERDS!

---

And proud of it.  But I prefer GEEK.

[RobCole]

---

@RavensFan wrote:

DAQmx does not have a license fee, unless I'm completely mistaken.

Vision certainly does, so that makes sense why you need to avoid the cost of that if lots of sites need it.

---

Interestingly enough, when I log in as a worker from my company and look for NI-DAQmx, I get a page that lists a price for an NI-DAQmx license. The license fee is waived if we use NI hardware. Not all of our sites use NI hardware.

But, really, the big cost would be for vision systems and having hundreds of developers.

     Rob

[altenbach]

How would you even use DAQmx with non-NI hardware??

[JÞB]

---

@altenbach wrote:

How would you even use DAQmx with non-NI hardware??

---

I think that's the point... Buy the "Expensive Hardware" that DAQmx supports or buy the "Reasonably Priced Hardware" and pay through the nose for the time your developer needs to code the C API-  After all, that C codeing weenie is already on the payroll anyway so his time is free  (and possibly billable if it is a "time and material" contract)

Mr Cole,  I think you need to state the obvious-  C/ C++ is employment insurance!

Unless you are really, really good at it-   No offence meant to those who"... code in C so I don't have too!"  but do check the cost vs the price