# Broadcast Ignition Client to a Raspberry Pi hooked up to TV using VNC Viewer

**URL:** <https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [April 30, 2018, 6:41pm UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872 "2018-04-30T18:41:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrowe](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@rrowe](https://forum.inductiveautomation.com/u/rrowe)\
**Post date:** [April 30, 2018, 6:41pm UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872/1 "2018-04-30T18:41:24Z")

</div>

I want to know if anyone has tried just using VNC Viewer (or the like) on a Raspberry Pi hooked up to a Smart TV via HDMI to display an Ignition Client that is running on an arbitrary box that is perhaps just in a server room. I have tested this with two different computers and it seems to be fine right now, but the goal is to have this be running continuously and be undisturbed. For the end client, this is just a non interactive TV screen that will always be running and showing some overview information.

- _If you have tried this setup, was it successful? If not, what prevented it from being successful?_

- _Does anyone foresee any issues with this?_

- _Could this be a workaround for the issues that some people seem to be having with Chromebits?_

---

<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:** [April 30, 2018, 6:48pm UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872/2 "2018-04-30T18:48:20Z")

</div>

I haven’t tried this, but it seems like a bunch of trouble. Why not just run the client on the rPi directly? Running it elsewhere and cobbling together a remote viewing layer just adds more breakable parts to the setup. IMNSHO.

---

<div class="post-metadata">

**Author:** ![rrowe](https://avatars.discourse-cdn.com/v4/letter/r/c57346/32.png) [@rrowe](https://forum.inductiveautomation.com/u/rrowe)\
**Post date:** [April 30, 2018, 7:13pm UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872/3 "2018-04-30T19:13:35Z")

</div>

Yeah, that was my thinking for this as well, but I know that this project is very busy–many different tags, transactions and queries are being polled regularly.

Granted I know that the Gateway does most of the “work” in this regard (please correct me if I’m wrong), but so too does the machine that is running the project client as well, right? If that’s the case, then does the rPi 3+ have the specs to actually run a client such as this? I was thinking it would not be able to, which made me think that I should just have it behave as a remote viewing layer as you put it, would be better. If it is the case that the client can be pretty lean in terms of specs, then I will just have the rPi run project.

---

<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:** [April 30, 2018, 7:28pm UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872/4 "2018-04-30T19:28:40Z")

</div>

The only kicker would be if the app was too complex to fit in a 32-bit java runtime. Otherwise, I’d expect the latest rPi’s to be more than suitable.

---

<div class="post-metadata">

**Author:** ![craigb](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@craigb](https://forum.inductiveautomation.com/u/craigb)\
**Post date:** [May 1, 2018, 12:29am UTC](https://forum.inductiveautomation.com/t/broadcast-ignition-client-to-a-raspberry-pi-hooked-up-to-tv-using-vnc-viewer/17872/5 "2018-05-01T00:29:00Z")

</div>

Asus do a very similar board called the tinker. Same form factor but with more horse power.

If you can run network cables to the TV, you could run HDMI over it and miss out the pi altogether.
