When a bench finishes a test and still needs a nameplate, certificate, or traceability label, the sequence often already lives in LabVIEW. Many plants used to call BarTender or Codesoft automation from that same VI. LabVIEW already speaks HTTP. LuckNext is an HTTP print gateway: submit a job, preview, list printers, health-check. Templates are designed in LuckDesign, with fields bound in the template. Luck label software belongs on that station’s evaluation sheet.
Two jobs on the bench—not a second test suite
LabVIEW keeps acquisition, limits, and pass/fail. The label stack handles size, barcodes, variables, and label printing. Do not ask the label gateway to rewrite the test sequence, and do not treat LuckNext as another LabVIEW.
- LuckDesign: templates for nameplates, certificates, and trace labels, plus local printing.
- LuckNext: the station submits print jobs over LuckNext HTTP API; it can run on an internal server.
Excel, LuckData, or a staging table can still feed templates. When the station must print as soon as the test passes, the print exit is mainly LuckNext.
How the station used to reach a printer, and what changes
| Common legacy hook | With LuckNext | |
|---|---|---|
| How the VI prints | Local COM / ActiveX / desktop automation, tight to one designer | HTTP job submit; LabVIEW’s HTTP client is enough |
| Where the printer sits | Often on the same test PC | Local, or stations submit print jobs via LuckNext HTTP API |
| Who edits the template | Automation scripts and the template often change together | Templates are designed in LuckDesign; the VI sends this-run variables |
| What you accept | This PC can open the designer and print labels | A real template, a floor printer, and one live test record print from LabVIEW |
Put BarTender, Codesoft, and Luck label software on the same sheet and accept on real jobs. Do not write that one product must be retired.
A practical bring-up order
- In LuckDesign, lay out and bind three must-print templates, map variables to test fields, and print one local sample.
- Deploy LuckNext (plant LAN, a station-side box, or the node in the project) and confirm the health check.
- Configure identity and tokens from the delivery docs. Paths and payloads follow those docs and the developer site—do not rename old COM methods one-for-one.
- In LabVIEW, list printers, preview, then submit the job. On failure, read the queue and the response; do not lay out the label in the block diagram.
- Prove two floor printers and one real test record, then decide whether stations submit print jobs through LuckNext.
Product notes: LuckNext. The same print exit is used when ERP or MES pushes jobs: ERP and business-system integration.