IMDTouchKnowledge BaseShop main store

Selection guide

How to Select an Industrial PC for LabVIEW ATE Development

Panel PCs and displays Published 7 min read

Short answer

Run 32-bit LabVIEW unless one buffer or array cannot live under the 4 GB address space of a 32-bit process and every toolkit and driver you need exists in 64-bit form; bitness alone adds no speed to ATE code. Specify the industrial PC from a counted inventory of the interfaces the target testers use, from a supplier who will hold the configuration unchanged.

On this page
  1. Choose the LabVIEW bitness from memory, then from dependencies
  2. Audit toolkits and drivers before committing to 64-bit
  3. Count every interface before you choose a chassis
  4. Develop against simulated hardware
  5. Freeze the hardware and keep a tested image
  6. The decision for each case
  7. Questions asked

Specify the software before the metal. Run 32-bit LabVIEW unless one buffer or array in your application cannot live under the 4 GB address space of a 32-bit process and every toolkit and driver you call exists in 64-bit form — bitness by itself adds no speed to ATE code. Then buy the industrial PC from a counted inventory of the interfaces your target testers actually use: board types, slot widths, serial wiring, USB positions and network controllers. A mid-range machine matched to that inventory, bought from a supplier who will hold the configuration, beats a maximum-specification box that is missing one slot or one driver.

Choose the LabVIEW bitness from memory, then from dependencies #

A 32-bit process addresses 2³² bytes = 4,294,967,296 bytes, a hard ceiling, and the memory actually available to your code sits below it because the runtime and loaded libraries map into the same space. Moving to 64-bit LabVIEW buys that address space and nothing else: code runs faster only when it, or the libraries it calls, genuinely uses wider instructions or processor optimizations the 32-bit build cannot reach. Scanning, instrument control, logging and reporting never approach the ceiling, so 32-bit is the default for ATE.

The operating-system side is documented by NI: 64-bit LabVIEW installs and runs only on 64-bit Windows, while 32-bit LabVIEW runs on both 32-bit and 64-bit Windows. Choosing 32-bit therefore leaves every deployment target open.

Illustrative worked example — replace these numbers with yours:

  • Vision tester. A 5-megapixel monochrome camera at 8 bits per pixel produces 2448 × 2048 = 5,013,504 bytes per frame. A 900-frame in-memory ring buffer holds 5,013,504 × 900 = 4,512,153,600 bytes ≈ 4.20 GB. That one array exceeds the 4,294,967,296-byte ceiling, so no 32-bit process can hold it even with nothing else loaded. Decision: 64-bit LabVIEW on 64-bit Windows, ordered only after the dependency audit below.
  • DAQ tester. 16 channels at 1 kS/s, double-precision samples of 8 bytes, a 60-second capture: 16 × 1,000 × 8 × 60 = 7,680,000 bytes ≈ 7.3 MB, about 0.18% of the ceiling. Decision: 32-bit LabVIEW, with room to spare for queues, displays and toolkits.

Hold a planning margin, because processing copies, display images, queues and fragmentation grow during commissioning: once the projected total of live allocations passes 2 GB — half the ceiling — specify 64-bit rather than manage the remainder.

Audit toolkits and drivers before committing to 64-bit #

NI's compatibility documentation is plain about the limit: 64-bit LabVIEW does not support all the toolkits that 32-bit LabVIEW supports, and the support varies by operating system. One unported toolkit, instrument library, DAQ driver, database connector or external code node is enough to block the 64-bit build, and no processor can repair a missing 64-bit driver. Write the dependency list first — vision, control, report generation, database connectivity, every instrument driver — and confirm a 64-bit version of each before the machine is specified.

If your license permits both editions on one development computer, install both. The 32-bit environment then becomes the recovery path when a toolkit blocks the 64-bit build: recompile and continue there. Recompiling proves the code links; it proves nothing about the target hardware.

Count every interface before you choose a chassis #

Build the inventory from the deployed testers, not from a generic checklist. For each target system, record the board type, connector, electrical layer, driver, required slot width and how many systems use it.

Interface What to record Decision rule
PCI / PCIe Board type; physical and electrical lane requirement (x1, x8); clearance; power Count installed boards plus service positions; a connector can be present and still wrong for lane width, clearance or power
ISA Which irreplaceable legacy board needs it Keep the slot only while that board is irreplaceable; open the board's migration the day you order the PC
9-way D-type serial Pinout, electrical standard, framing, handshaking, per instrument Count instruments; the 9-way shape alone identifies neither the electrical layer nor the application wiring
RS-485 Two-wire or four-wire requirement of each device A device needing separate transmit and receive pairs requires a four-wire-capable port; a two-wire-only port cannot reproduce that link
Parallel port Validated software or quick digital I/O that depends on it Keep a native port where the validated image uses it; never assume an adapter duplicates native access and timing
USB Deployed devices, service tools, license hardware, spare positions; motherboard headers Order the matching rear breakout with the PC; uncommon breakouts are hard to source separately later
Gigabit Ethernet Traffic separation across plant, instruments and service; controller model Two ports give isolation; verify the controller against driver requirements before ordering
Graphics Which slot the graphics card consumes Prefer onboard graphics so no test board loses a slot

Mixed PCI and PCIe backplanes with 14 slots exist because fielded testers have come close to filling them, and some of those testers still carry one ISA board nobody will replace. On network controllers, do not stop at "gigabit": a camera application using NI's high-performance driver needs a controller that driver supports, and fielded systems of that kind were built around Intel Pro 1000 controllers, so verify the exact controller against the driver's supported list before ordering. Treat AGP graphics on an existing tester as a compatibility requirement to match, never as something to specify new.

Develop against simulated hardware #

Keep project-specific hardware behind defined interfaces: DAQ reads, serial exchanges and digital outputs belong in modules with simulated implementations that return deterministic values, timeouts, invalid measurements and device faults. Sequencing, calculations, reports, operator screens and alarm handling then run on the development PC with no production hardware attached, which is the only practical way to serve several projects from one machine.

Be clear about what such a run closes and what it cannot: it validates logic, not electrical levels, acquisition timing, bus contention, grounding, cable faults or instrument-specific error behavior. Those close only at commissioning on the real tester. Mark simulated runs so a passed software test is never mistaken for a completed hardware acceptance test.

Keep a dependency record per project:

  • LabVIEW bitness and installed edition
  • Required toolkits and external libraries, each with its 64-bit support confirmed or refuted
  • DAQ and instrument drivers with versions
  • Board type, slot type and connector for every interface
  • Serial and network settings read from the deployed equipment
  • Build specification and target-computer assumptions

Freeze the hardware and keep a tested image #

Downtime on a running line is the dominant cost, not the computer. Buy from a supplier that will hold the hardware configuration without change for the life of the tester, so a failed unit is replaced by an identical one and the tested drive image is mirrored back in the shortest possible time. Keep one tested spare. Before swapping anything, diagnose the failure: the video, POST and storage checklist for an industrial PC that will not boot tells you whether you are restoring an image or repairing hardware. Where the deployed executable and its operator screens need a touchscreen computer at the machine, specify industrial panel PCs and hold them to the same interface inventory.

One safety note: isolate the tester and discharge the cabinet before swapping boards or wiring serial links; interface work on a live backplane risks both the board and you.

The decision for each case #

  • Logging, instrument control and DAQ whose largest allocation stays in the megabytes: 32-bit LabVIEW, deployable to 32-bit and 64-bit Windows alike.
  • Any single array that exceeds the 32-bit ceiling, or a projected total past 2 GB: 64-bit LabVIEW on 64-bit Windows, ordered only after every toolkit and driver on the list is confirmed in 64-bit form.
  • A dependency with no 64-bit version: stay 32-bit, or port the dependency — the processor cannot fix it.
  • A tester carrying an ISA-only legacy board: keep the ISA slot and open the migration, because a new PC without the slot strands the board.
  • An instrument that needs separate transmit and receive pairs: a four-wire-capable RS-485 port in the specification, not an adapter.
  • Every production station: one supplier with a frozen configuration, one tested image, one spare.

Questions asked

Is 64-bit LabVIEW faster than 32-bit for ATE work?

Not by itself. A 64-bit build runs faster only where the code or the libraries it calls actually use wider instructions or processor optimizations the 32-bit build cannot reach. What 64-bit buys is address space beyond the 32-bit process ceiling of 4 GB, which matters for large image buffers and arrays. A 64-bit build also cannot load 32-bit DLLs, which is why external code heads the audit before you commit.

Can I install 32-bit and 64-bit LabVIEW on the same development PC?

Yes, when your license covers both editions, and it is worth doing. The 32-bit environment is the fallback when a toolkit or driver has no 64-bit version: recompile and continue there. Keep separate build specifications and dependency records for each environment, and remember that a successful recompile proves the code links, not that the target hardware works.

How many expansion slots does an ATE industrial PC need?

As many as your inventory counts, plus service positions. Count every board in every target system, record each board's slot width and lane requirement (x1, x8), and add positions for boards you expect to fit later. Mixed PCI and PCIe backplanes with 14 slots exist because fielded testers have come close to filling them, so a large chassis is rarely wasted.

Do I need a four-wire RS-485 port?

Only if a connected device requires separate transmit and receive pairs. Check each instrument's manual for its RS-485 mode before ordering the computer. A two-wire-only port cannot reproduce a four-wire link and no driver setting changes that, so the port capability has to be right in the original specification.

Why order the USB rear breakout with the PC instead of later?

Motherboard USB headers need a matching bracket to reach the rear panel, and proprietary or uncommon breakout brackets are difficult to source separately afterwards. Order the breakout with the computer, count license dongles, service tools and spare positions in the USB budget, and keep one bracket together with the spare unit.

Keep reading

  • Selection guide

    Selecting a thin-bezel industrial HMI display for a cutout

    A bezel under 3 mm puts the cutout within about 6 mm per axis of the active display area, so the decision rests on the model's own cutout drawing, front-only IP66 sealing with a separately rated rear enclosure, and whether the station needs a panel PC or a standalone monitor.

    Panel PCs and displays

  • Troubleshooting

    Industrial PC Will Not Boot: Video, POST or SSD Fault

    A blank screen proves nothing on a CPU card with no onboard video. Yes, you can clear CMOS without a monitor, but only through the board's documented jumper and only after video works. Split the fault into power, video or SSD boot before changing parts: fit a basic ISA VGA card in a verified slot, read the BIOS, then decide between a settings reset and SSD recovery.

    Panel PCs and displays

  • Selection guide

    HMI Panel PC RAM, SSD and Windows Selection Guide

    Order 4 GB of RAM as the default: the documented floor of one size lower suits only a panel running a single lightweight runtime such as AdvancedHMI. Take 128 GB of SSD storage unless logs are small or purged quickly, when 64 GB is enough. Order 64-bit Windows 10, ideally the IoT Enterprise LTSC build, and have RAM, SSD and the OS printed on the quotation before the enclosure is cut.

    Panel PCs and displays