# Ignition 8 Client on Raspberry Pi **URL:** \ **Category:** Ignition\ **Created:** [April 29, 2019, 3:26pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464 "2019-04-29T15:26:59Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 3:26pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/1 "2019-04-29T15:26:59Z")
Hi, I'm trying to see if there's a way to use ignition 8 on raspberry pi as a client. The main ignition install is already on a x86\_64 machine and works fine. However, since the change to native client launchers, I don't see a way to run (easily) ignition on a 32bit pi as the client launchers are expecting a different architecture. What options do I have? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 3:38pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/2 "2019-04-29T15:38:43Z")
The easiest option would be to use Perspective as your “client”. Vision will require you to have your own ARM-compatible JDK installed and run the launchers and client with that. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 3:46pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/3 "2019-04-29T15:46:59Z")
Seeing as I’ve already developed a vision based system, there’s likely not a simple “perspective shift” is there? I’ve also dug into the clientlauncher and found the .jar file. Is there no more .jnlp download available? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 29, 2019, 3:49pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/4 "2019-04-29T15:49:14Z")
No, Webstart is dead in Java 11+, which Ignition 8 requires to run. And, no, there’s no easy migration to Perspective, for a variety of technical reasons. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 3:51pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/5 "2019-04-29T15:51:24Z")
I think you’ll have to use Oracle JDK or OpenJDK ARM builds to run the launcher and Vision clients: [https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot](https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot) The ARM JDK we bundle with the gateway and launchers is headless. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 4:11pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/6 "2019-04-29T16:11:36Z")
Using this jdk for arm32 I get the following error (followed by others) ```auto pi@RevPi15201:~ $ ./jdk-11.0.3+7/bin/java -jar visionclientlauncher/app/launcher-vision-client-linux.jar INFO [ClientLauncher] [2019/04/29 18:10:40]: Using /home/pi/.ignition/clientlauncher-data/visionclientlauncher.log to store logging info. Check there for all future logging events. OpenJDK Server VM warning: You have loaded library /home/pi/.openjfx/cache/11.0.2/libprism_es2.so which might have disabled stack guard. The VM will try to fix the stack guard now. It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'. Loading library prism_es2 from resource failed: java.lang.UnsatisfiedLinkError: /home/pi/.openjfx/cache/11.0.2/libprism_es2.so: /home/pi/.openjfx/cache/11.0.2/libprism_es2.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch) java.lang.UnsatisfiedLinkError: /home/pi/.openjfx/cache/11.0.2/libprism_es2.so: /home/pi/.openjfx/cache/11.0.2/libprism_es2.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch) ``` ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 4:13pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/7 "2019-04-29T16:13:48Z")
Try the arm64 build? ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 4:23pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/8 "2019-04-29T16:23:45Z")
Ok, so it appears that the revpi core 3 (the pi I’m using) doesn’t actually have the armv8 BCM2837 chip in in. /proc/cpuinfo shows BCM2835 (that’s a pi1 cpu) and uname -m shows armv71 (32 bit). I’ll see what I can do reaching out to them in the meantime. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 4:53pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/9 "2019-04-29T16:53:24Z")
I guess the launchers aren’t built for ARM either (there’s a JavaFX native component that complicates things). You’d have to invoke launchclient.jar directly in order to launch a client. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 5:13pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/10 "2019-04-29T17:13:51Z")
Correct, but will get errors if not on a 64bit os. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 5:18pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/11 "2019-04-29T17:18:39Z")
There errors were from running the _launcher_, the launcher in turn is running `launchclient.jar` which has no native components. Or am I missing something? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 29, 2019, 5:49pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/12 "2019-04-29T17:49:41Z")
Launch command line should be something like: ```auto /home/pgriffith/.ignition/clientlauncher-data/launchclient.jar -Djavaws.sr.gateway.addr.0=http://10.10.70.55:80 -Djavaws.sr.launchts=1556560041806 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Djavaws.sr.platform.edition= -Djavaws.ignition.sso=true -Xms32M -Xmx256M -Djavaws.sr.memory.init=32M -Djavaws.sr.memory.max=256M -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=false -Djavaws.sr.screen=0 -Djavaws.sr.scope=C -Djavaws.sr.project=Test com.inductiveautomation.ignition.client.launch.BootstrapSwing ``` Or, more legibly: ```auto /home/pgriffith/.ignition/clientlauncher-data/launchclient.jar -Djavaws.sr.gateway.addr.0=http://10.10.70.55:80 -Djavaws.sr.launchts=1556560041806 -Djavaws.sr.main=com.inductiveautomation.factorypmi.application.runtime.ClientLaunchHook -Djavaws.sr.platform.edition= -Djavaws.ignition.sso=true -Xms32M -Xmx256M -Djavaws.sr.memory.init=32M -Djavaws.sr.memory.max=256M -Dsun.java2d.d3d=false -Dsun.java2d.noddraw=false -Djavaws.sr.screen=0 -Djavaws.sr.scope=C -Djavaws.sr.project=Test com.inductiveautomation.ignition.client.launch.BootstrapSwing ``` ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 6:03pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/13 "2019-04-29T18:03:29Z")
Let me see what I can do when I get the system back online. Reflashing now with 64bit os. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 7:57pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/14 "2019-04-29T19:57:55Z")
Where can I find launchclient.jar? ---
**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\ **Post date:** [April 29, 2019, 8:23pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/15 "2019-04-29T20:23:41Z")
`/home/username/.ignition/clientlauncher-data/` obviously, replace “username” with the user you’re logged in as. Might be easier to take what PGriffith posted, but modify the username ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 8:36pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/16 "2019-04-29T20:36:50Z")
Hardly correct. Ignition isn’t installed on the pi. No .ignition directory exists. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 29, 2019, 8:49pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/17 "2019-04-29T20:49:09Z")
I did get the legacyclientlauncher.tar.gz downloaded from a 7.9 install and ran that on the pi. It worked fine with the 7.9 edge server it was connecting to. I modified the project name, the platform.edition to blank, and the gateway.addr to the correct ip. I got errors regarding unpacking java-cup-10k.jar Are the legacy client launcher files no longer available in 8? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 29, 2019, 9:25pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/18 "2019-04-29T21:25:28Z")
You can get a copy of `clientlauncher.jar` from the `lib/core/launch` folder of an Ignition 8 install. The location @Paul.Scott suggested is where it ends up when the launcher downloads it but you aren’t able to get that far. The legacy launchers are not available with Ignition 8. ---
**Author:** ![cbiela](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cbiela](https://forum.inductiveautomation.com/u/cbiela)\ **Post date:** [April 30, 2019, 12:07pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/19 "2019-04-30T12:07:11Z")
So it appears that arm is not compatible with Ignition v8. Is this known/intentional? How long will 7.9 be supported? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 30, 2019, 12:35pm UTC](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464/20 "2019-04-30T12:35:39Z")
7.9 is an LTS version so it’s supported for 5 years from the first release, so it’s supported until December 2021 in this case. Ignition 8.0 supports running the gateway on ARM and we’re aware the Vision Client and Launchers don’t run on ARM. I’m not sure if this will change significantly. We may be able to ship launchers that have native components compatible with ARM sometime in the future but it would still require that the system have its own JDK installed because the ARM JDKs we license and ship with are headless. [Next page](https://forum.inductiveautomation.com/t/ignition-8-client-on-raspberry-pi/24464.md?page=2)