Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Gribo

  1. NI is shooting themselves in the foot with this approach. It is already difficult enough to find LabVIEW programmers. The IDE seems straight out of 2002, proprietary file formats, hard time integrating with version control and CI flows, Do they really want to drive away their potential customers?

    I use LV for many things, but I avoid the pay to deploy tools (IMAQ, Teststand). If I have to pay upkeep to NI, I'll recommend Python, the 3rd party hardware support is similar with pyVISA. No upkeep, no licenses, no deployment fees.

    • Like 1
  2. You should check that both the DLL and LV have the same bitness, 32 bits or 64 bits, not mixed.

    You might be able to bypass the entire problem, if you can create a raw printer file.

    1. Create a raw file - usually label printers use a text based encoding (for example, Zebra printers use ZPL, other vendors have similar formats). This will be your template file.

    2. If you are using Windows, create a printer share.

    3. Set the fields in the template.

    4. copy the file to the share - using the system call, issue a copy <filename> \\localhost\<share name> command.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.