The gateway is up on the Raspberry Pi. The web interface loads. Then you look for a Designer Launcher for the same box, or the panel PC beside it, and there isn't one for Linux ARM. The x86-64 Linux launcher won't execute. Perspective Workstation isn't an option either.
That is not a broken install. Ignition 8.3 adds ARM launcher support for macOS and Windows. Linux ARM is not covered. Here is why, what not to waste time on, and how to build around it.
Stop Trying These Fixes
These are the moves people make first. None of them produce a supported, working Designer on Linux ARM.
| What you see | What you tried | Why it fails |
|---|---|---|
| Shell reports an exec format error or the binary will not start | Downloaded the Linux x86-64 launcher onto the ARM box | The launcher and its bundled Java runtime are compiled for x86-64. An aarch64 or armv7 CPU cannot execute them. |
| Launcher window never appears, or fails on missing JavaFX classes | Installed the distro OpenJDK for ARM and tried to run the launcher against it | The launcher UI needs a Java runtime that includes JavaFX. Standard distro ARM JDK packages typically ship without it. |
| Launcher gets further, Designer or Workstation still fails | Found a JavaFX-enabled ARM JDK and forced the launcher onto it | Designer and Perspective Workstation embed JXBrowser, which uses native Chromium binaries. No Linux ARM build of those binaries ships with Ignition. |
| Very slow, crashes, or library errors under emulation | Ran the x86-64 launcher through a user-mode x86 emulation layer | You are now debugging an emulator, not Ignition. Outside vendor support, and the native Chromium components are the heaviest part to emulate. |
| Still no Linux ARM launcher download | Upgraded to 8.3 expecting ARM launchers everywhere | 8.3 ARM launcher support covers Apple and Windows only. |
Start here: stop patching the ARM box to run the tools. The fix is architectural, not a missing package.
Understand What Actually Blocks the Launchers
The gateway is a server process and runs fine on ARM Linux. The desktop tools are a different stack. Three dependencies have held Linux ARM back:
- Java runtime with JavaFX for Linux/ARM. The launchers use JavaFX for their UI. Inductive Automation has not had a Linux/ARM runtime build that included JavaFX to bundle.
- JXBrowser for Linux/ARM. JXBrowser is the embedded Chromium engine. Designer depends on it, and Perspective Workstation is essentially built on it. This is the main blocker today.
- Download and install size. Every additional platform runtime bundled into the Ignition installer grows it for everyone.
Splitting the Client and Designer Launchers into separate downloads, the way the mobile apps are distributed, would solve the size problem. The launchers are not version-locked to a gateway the way modules are. It does not solve JXBrowser. A Linux ARM launcher without JXBrowser could not open a Designer or a Perspective Workstation, which removes most of the reason to want one.
A further constraint: JXBrowser on ARM may require a minimum GLIBC version. Older or stripped-down ARM distributions can fall below it, so even a future build may not run on every Pi image in the field.
Check the Platform First
Before you plan anything, confirm what you are actually running. Run these on the ARM box:
uname -m # aarch64 = 64-bit ARM, armv7l = 32-bit ARM
ldd --version # first line reports the GLIBC version
cat /etc/os-release-
armv7lmeans a 32-bit OS. Many older Raspberry Pi images are 32-bit even on 64-bit hardware. Any future native tooling is most likely to target 64-bit first. - Record the GLIBC version. If a Linux ARM launcher or JXBrowser build appears later, compare it against the stated minimum in the release notes before you commit hardware.
- Confirm the gateway itself is healthy from another machine's browser before blaming the tools.
Split the Roles: Gateway on ARM, Tools on Supported Hardware
This is the layout that works today.
- Keep the Ignition gateway on the Raspberry Pi or ARM Linux device. That part is supported and runs as-is.
- Pick an engineering workstation on a platform with an 8.3 launcher: Windows or Linux on x86-64, macOS on Apple silicon or Intel, or Windows on ARM.
- Download the Designer Launcher from the gateway's web interface on that workstation.
- Add the ARM gateway to the launcher by its IP or hostname and the configured HTTP or HTTPS port.
- Do all project development from that workstation. The ARM box never needs to run Designer.
- For an operator screen on an ARM Linux panel, build the HMI in Perspective and open the project in a standard Chromium or Firefox browser on the panel. Launch the browser in kiosk or full-screen mode at boot for a dedicated HMI.
- If the operator screen must be Vision, put a Windows or x86-64 Linux panel PC at that location. There is no Linux ARM Vision Client Launcher.
Skip Perspective Workstation on ARM Linux. It depends on JXBrowser, so a plain browser in kiosk mode is the only path on that hardware.
Verify the Setup
- From the engineering workstation, open the gateway web page. If it does not load, fix networking or firewall rules first; the launcher will fail the same way.
- Launch Designer against the ARM gateway and log in. Open, edit, and save a project. Confirm the change reaches the gateway.
- On the ARM panel, open the Perspective session in the browser. Confirm tag values update live and that bidirectional writes work.
- Reboot the panel and confirm the kiosk browser comes back to the correct project without operator input.
- Watch CPU and memory on the Pi while a session is running. Gateway and browser on the same small board compete for resources; split them onto separate devices if the gateway lags.
Avoid the Recurring Traps
- Buying ARM Linux panels for Vision. No launcher, no client. Check the HMI technology before the hardware order.
- Assuming a future launcher means a future Designer. A Linux ARM launcher without JXBrowser gives you no Designer and no Workstation.
- Running a 32-bit image on 64-bit hardware. Move to a 64-bit OS if you want the best chance of future native support.
- Ignoring GLIBC. Long-lived images on older distributions are the ones most likely to fall below a JXBrowser minimum.
- Treating emulation as production. Fine for curiosity. Not for a plant floor.
FAQ
How do I run Ignition Designer when my gateway is on a Raspberry Pi?
Install the Designer Launcher on a Windows, macOS, or x86-64 Linux workstation, then add the Pi gateway by IP or hostname and port. Designer runs on the workstation and connects to the gateway over the network.
How do I display a Perspective HMI on a Linux ARM panel?
Open the project's Perspective session in Chromium or Firefox on the panel and set the browser to launch in kiosk mode at boot. Perspective Workstation is not available on Linux ARM because it depends on JXBrowser.
How do I check whether my ARM device is 32-bit or 64-bit?
Run uname -m. aarch64 is 64-bit and armv7l is 32-bit; a Pi with 64-bit hardware can still report armv7l if it runs a 32-bit OS image.
How do I find the GLIBC version on my Linux ARM box?
Run ldd --version and read the version on the first line. Compare it against the minimum stated in the release notes of any Linux ARM launcher or JXBrowser-based tool before deploying it.
When should I contact Inductive Automation support about Linux ARM launchers?
Escalate when your project requires Designer, Vision, or Perspective Workstation to run natively on Linux ARM and the split-role layout cannot meet the requirement. Open a request through Inductive Automation's official support channel with your distribution, uname -m output, and GLIBC version so it can be tracked against their ongoing work on Linux ARM and JXBrowser.