# Serial IO On Raspberry PI

**URL:** <https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848>\
**Category:** Ignition\
**Created:** [March 27, 2015, 10:55am UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848 "2015-03-27T10:55:52Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Malcolm](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/malcolm/32/5970_2.png) [@Malcolm](https://forum.inductiveautomation.com/u/Malcolm)\
**Post date:** [March 27, 2015, 10:55am UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/1 "2015-03-27T10:55:52Z")

</div>

Hi,

I have been trying out an Ignition Client on a Raspberry Pi B Version 2, It is now much more capable than previous version.

One issue I have which may just be a lack of understanding linux,

I wish to connect a barcode scanner using a USB/Serial adaptor and have installed it and it appears as dex/ttyUSB0 when I do a ‘ls -l \dev\tty\*’ command.

When I try to start the open the port in the ignition client via script I get the following error

java.lang.UnsatisfiedLinkError: Serialio.SerialPortLocal.SerOpenPort(LSerialio/SerialConfig:)I

The previous command to configure the serial port does not throw and error so I believe the serial module has to be present.

I have Ignition 7.7.3 and Serial Client Module 2.73 installed

Code Used on Button

```
system.serial.configureSerialPort(\
port="dev/ttyUSB0",\
bitRate=system.serial.BIT_RATE_9600,\
dataBits=system.serial.DATA_BITS_8,\
handshake=system.serial.HANDSHAKE_NONE,\
hardwareFlowControl=False,\
parity=system.serial.PARITY_NONE,\
stopBits=system.serial.STOP_BITS_1)

system.serial.openSerialPort("dev/ttyUSB0")

```

Any help appreciated

Malcolm

---

<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:** [March 27, 2015, 1:31pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/2 "2015-03-27T13:31:21Z")

</div>

The serial module packages up some native libraries for each platform that allow serial port access, and unfortunately the module doesn’t include ARM binaries right now, so it won’t work on the RPi. I’ll check and find out if ARM binaries are included with the library we’re using or not.

---

<div class="post-metadata">

**Author:** ![ottom8](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@ottom8](https://forum.inductiveautomation.com/u/ottom8)\
**Post date:** [April 15, 2015, 4:54pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/3 "2015-04-15T16:54:41Z")

</div>

Would like to know other than the serial issue how is the general performance of a client on a RPI?  
I am looking to use it as a remote viewer.

Thank you. 😃

---

<div class="post-metadata">

**Author:** ![ovendenk](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@ovendenk](https://forum.inductiveautomation.com/u/ovendenk)\
**Post date:** [July 21, 2016, 11:53pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/4 "2016-07-21T23:53:29Z")

</div>

Sorry to dig up an old post, but we are having the same problem. Was this ever resolved with the ARM binaries since the issue came up? Thanks in advance!

---

<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:** [July 22, 2016, 3:13pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/5 "2016-07-22T15:13:18Z")

</div>

No it turns out we don’t have any ARM binaries for the serial library.

---

<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:** [July 22, 2016, 7:31pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/6 "2016-07-22T19:31:01Z")

</div>

You might try the [Codesys runtime](http://store.codesys.com/codesys-control-for-raspberry-pi-sl.html) on it. I haven’t used the serial library, but the OPC-UA server portion of it is really slick, and I have read on their forums on how to get serial working.

---

<div class="post-metadata">

**Author:** ![dan.kobus](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@dan.kobus](https://forum.inductiveautomation.com/u/dan.kobus)\
**Post date:** [August 11, 2017, 8:21pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/7 "2017-08-11T20:21:14Z")

</div>

Kevin. has there been any changes to the serial library binaries since the addition of ARM specific installers being released?

---

<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:** [August 11, 2017, 8:34pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/8 "2017-08-11T20:34:58Z")

</div>

It looks like support from the vendor exists now. I made sure there’s a ticket in our tracker for the upgrade. When there’s a milestone assigned by the maintenance team I’ll try and remember to update this post.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/malcolm/32/5970_2.png) [@Malcolm](https://forum.inductiveautomation.com/u/Malcolm)\
**Post date:** [October 22, 2017, 10:37am UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/9 "2017-10-22T10:37:56Z")

</div>

Kevin. has this support been added yet ?

---

<div class="post-metadata">

**Author:** ![hweidknecht](https://avatars.discourse-cdn.com/v4/letter/h/8c91f0/32.png) [@hweidknecht](https://forum.inductiveautomation.com/u/hweidknecht)\
**Post date:** [September 4, 2018, 3:49pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/10 "2018-09-04T15:49:11Z")

</div>

Is there any update on this thread? I really need this to on a Pi 3.

---

<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:** [September 4, 2018, 4:04pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/11 "2018-09-04T16:04:09Z")

</div>

Sorry, nothing has changed, the issue is still open with low priority.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/malcolm/32/5970_2.png) [@Malcolm](https://forum.inductiveautomation.com/u/Malcolm)\
**Post date:** [September 4, 2018, 5:42pm UTC](https://forum.inductiveautomation.com/t/serial-io-on-raspberry-pi/9848/12 "2018-09-04T17:42:36Z")

</div>

I have successfully implemented the JSSC (Java Simple Serial Library) on RPI 2 and 3 to retrieve date from a USB-Serial Converter into Ignition Client on the Raspberry PI. The JSSC Library can be distributed automatically from the gateway after being compressed.  
Only Issue I have with the code I used is the serial library handle for the com port is lost when Ignition Updates are Sent to the RPI, but using a client script triggered on the Project Change I Forced the Client to re-launch itself which worked around this.
