LabVIEW to C code

[Dennis_Knutson]

That comment makes no sense. What industry?

If you must provide c code to a client instead of a dll written in LabVIEW, you should have taken note of that at the beginning. I don't think you would have any choice except to rewrite it the way the customer wants.

[_Bryan]

---

@Dennis_Knutson wrote:
That's the price I remember as well. It only supported a subset of the LabVIEW functions as well. What is your purpose for converting to c?

---

It was for a project where I wanted to use NI hardware/software instead of PLC's.  My boss saw the C generator and wondered if I could write the code in LabVIEW and convert it into C for the project.  But since LabVIEW software/harware was so much more expensive for this low volume project, they decided against it.

I do not know C, so I ended up in Michigan for a week learning Think & Do software so I could program PLC's for the project.

[BowenM]

---

@_Bryan wrote:

It was for a project where I wanted to use NI hardware/software instead of PLC's.  My boss saw the C generator and wondered if I could write the code in LabVIEW and convert it into C for the project. 

---

I played around with the LabVIEW to C generation for awhile and I didn't like it much. The functions that would convert were very limited (couldn't use event structures for example), and the actual code itself was obviously generated and somewhat difficult to follow.  Why don't you just import your C instrumentation drivers in to LabVIEW?

Edit: Clarity

[_Bryan]

---

BowenM wrote: 

I played around with the LabVIEW to C generation for awhile and I didn't like it much. The functions that would convert were very limited (couldn't use event structures for example), and the actual code itself was obviously generated and somewhat difficult to follow.  Why don't you just import your C instrumentation drivers in to LabVIEW?

Edit: Clarity

---

There was no C code.  The new project was based off of an older project that was written using a very old version of Think & Do.  The new version of Think & Do is not compatible with the old version, so I had to do a complete rewrite of the software with the new requirements.  The decision was made to stay with that software/hardware because that's what was used before.