# 8.1 Vision client Launcher installation issues on 64bit Raspberry Pi

**URL:** <https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [October 25, 2022, 8:57pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680 "2022-10-25T20:57:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blake\_Bessinger](https://avatars.discourse-cdn.com/v4/letter/b/dec6dc/32.png) [@Blake\_Bessinger](https://forum.inductiveautomation.com/u/Blake_Bessinger)\
**Post date:** [October 25, 2022, 8:57pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/1 "2022-10-25T20:57:32Z")

</div>

I'm currently running into issues trying to get Vision Client to run on my Raspberry Pi. I have it running the latest version of the 64bit Raspbian OS. Downloaded the Client Launcher from my Gateway on the primary computer, downloaded as a .tar file. I unzipped that and have been unable to get it to actually execute. What I have done and tried so far:

- I have Java OpenJDK v.11 installed
- it's stored in my "usr/local/ignition" folder
- everything has execute permissions
- if I try executing the (.desktop) Launcher file by double clicking it does nothing
- executing the (.desktop) Launcher file by command line gives errors
- using the "sudo ./name start" on the .sh file in the app folder does nothing
- using the "sudo ./name start" on the .jav file in the app folder errors out

Any suggestions on what to do to move forward?

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [October 25, 2022, 9:06pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/2 "2022-10-25T21:06:01Z")

</div>

Client launchers do not work on RPis, even the 64 bit ones, you have to bootstrap it with `legacyClient.sh`  
[Version 8 32-bit vision clients - Ignition - Inductive Automation Forum](https://forum.inductiveautomation.com/t/version-8-32-bit-vision-clients/24658/3)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 25, 2022, 10:12pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/3 "2022-10-25T22:12:40Z")

</div>

JavaFX is not available on most ARM cpus, so anything in Ignition that depends on it will fail. The legacy launcher doesn't need javafx itself, and can therefore launch any client that also doesn't need javafx. (IIRC, you cannot use the JxBrowser component without javafx.)

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [October 26, 2022, 11:02am UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/4 "2022-10-26T11:02:30Z")

</div>

IIRC Liberica claims to support JavaFX. I've not had the opportunity to try it yet.  
EDIT: To clarify, I use Liberica on my Pi's but haven't tried JavaFX things yet.

> **[Download OpenJDK builds of Liberica JDK, Java 8, 11, 17, 19 | BellSoft Java](https://bell-sw.com/pages/downloads/#/java-11-lts)**
>
> Download Liberica JDK, supported OpenJDK builds. Open source Java 8, 11 and more for Linux, Windows, macOS.

---

<div class="post-metadata">

**Author:** ![batman01793](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@batman01793](https://forum.inductiveautomation.com/u/batman01793)\
**Post date:** [May 1, 2023, 12:03pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/5 "2023-05-01T12:03:05Z")

</div>

I’m interested in how to bootstrap this using legacy.SH  
As I have the same issue as the original poster.

So my questions are:  
1: where do I get the files required to launch a vision client on my raspberry pi 4  
2: what are the install steps  
2:a I have a blank pie ready to go so can start from scratch.

The reason for the need to put on a PI.

- I currently have a redlion cr3000 HMI that has its own MQTT & OPCUA server built in . I am using this HMI as a simple data collection device (every 1 second a tag is updated and used as a trigger for a transition group)  
This captures the state of various HMI button states as tags each second to a sql server.

I wanted to do the same with a PI but use ignition vision to be the HMI.  
(Can’t use perspective as I only have a vision client licence)  
So I want the PI to boot up and autostart a vision client project (auto logon project built)

Any guidance on how I can achieve what I want to do using a pi4

- note I have a 10” touchscreen connected to the PI.

---

<div class="post-metadata">

**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:** [May 1, 2023, 1:08pm UTC](https://forum.inductiveautomation.com/t/8-1-vision-client-launcher-installation-issues-on-64bit-raspberry-pi/65680/6 "2023-05-01T13:08:01Z")

</div>

> **[Ignition 8 32-bit Vision Clients](https://support.inductiveautomation.com/hc/en-us/articles/360047576471-Ignition-8-32-bit-Vision-Clients)**
>
> As of Ignition 8, 32-bit Vision Client support was dropped; the availability of 32-bit Java Runtime Environments (JRE) will diminish overtime as the technology is slowly deprecated.However, in an e...
