How to import LabVIEW block diagram from pdf file

[RTSLVU]

---

wiebe@CARYA wrote:

---

I'm still puzzled about the title of this thread. Is the goal to create a VI from a (any) PDF, or is the goal to create PDFs that contain snippets?

---

I believe the OP has a PDF with a LabVIEW block diagram that they want to import to LabVIEW like a snippet.

The rest is just topic drift.

[wiebe@CARYA]

---

@RTSLVU wrote:

---

wiebe@CARYA wrote:

---

I'm still puzzled about the title of this thread. Is the goal to create a VI from a (any) PDF, or is the goal to create PDFs that contain snippets?

---

I believe the OP has a PDF with a LabVIEW block diagram that they want to import to LabVIEW like a snippet.

The rest is just topic drift.

---

I agree.

I think the question has been answered ('not possible') in the first post though.

[altenbach]

Most likely this "PDF document" is a manual or research report that, in addition to some diagram pictures, also contains some body text.

If the document is to be taken seriously, there is authorship information, including affiliation and email. Best would to be contact whoever made that pdf.

[AnalogKid2DigitalMan]

Google image search is simply amazing, Fig 13 from this paper:

http://jsstec.org/_common/do.php?a=full&b=42&bidx=1989&aidx=24229

-AK2DM

[LLindenbauer]

---

@AnalogKid2DigitalMan wrote:

Google image search is simply amazing, Fig 13 from this paper:

http://jsstec.org/_common/do.php?a=full&b=42&bidx=1989&aidx=24229

-AK2DM

---

So ... it's basically a bit of DAQ wrapped around the NI Biomedical Toolkit?

[altenbach]

I really don't understand the need to do a publication with large (and utterly useless!) color figures of LabVIEW diagrams.

(In the words of the current dog food commercials on TV, it's all just "filler"!)

The outcome is binary:

• Those who don't know LabVIEW get confused and don't understand anything.
• Those who know LabVIEW, get annoyed by the ugly Rube Goldberg code!

The code (or executable of it), if public, simply need to be made available as supporting documents elsewhere.

(Random example: I did not feel the need to publish any diagram pictures on page 12 here, But yes, my code is not yet public, but will eventually be on GitHub).

[wiebe@CARYA]

---

@altenbach wrote:

I really don't understand the need to do a publication with large (and utterly useless!) color figures of LabVIEW diagrams.

(In the words of the current dog food commercials on TV, it's all just "filler"!)

The outcome is binary:

• Those who don't know LabVIEW get confused and don't understand anything.
• Those who know LabVIEW, get annoyed by the ugly Rube Goldberg code!

The code (or executable of it), if public, simply need to be made available as supporting documents elsewhere.

(Random example: I did not feel the need to publish any diagram pictures on page 12 here, But yes, my code is not yet public, but will eventually be on GitHub).

---

And even if the VIs are inserted in the PDF (see attachment in the attached PDF) a single VI is hardly useful nowadays.

So you'd have to embed a zip of the project... Or distribute a zip with the PDF in it.

Or indeed (and preferred) use GitHub.