# Reading ASCII from a Click PLC

**URL:** <https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339>\
**Category:** General Discussion\
**Tags:** perspective\
**Created:** [April 21, 2025, 5:54pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339 "2025-04-21T17:54:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ivan.a.lestan](https://avatars.discourse-cdn.com/v4/letter/i/9e8a1a/32.png) [@ivan.a.lestan](https://forum.inductiveautomation.com/u/ivan.a.lestan)\
**Post date:** [April 21, 2025, 5:54pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/1 "2025-04-21T17:54:09Z")

</div>

Hello, I'm trying to read a part number containing numbers and letters from a Click PLC. I scan the number into the HMI, which stores the 12-character string into 12 TXT registers in the click. Trying to figure out how to retrieve them, in proper order, as a single entry in Perspective. I have modbus addresses for each register, but I'm lost. I do this succesfully with ascii strings from Allen Bradley PLC's, but the Click does not have ascii.

More of a PLC guy than a code, guy, so help would be appreciated.

Modbus addresses in PLC.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d218c3c29b8ce902594ae27f376c9b276c8ed681.png)

What the tags look like. Not understanding this.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/2/82fca92709aef4cca1434d1eae512b8be53b5769.png)

---

<div class="post-metadata">

**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 21, 2025, 5:58pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/2 "2025-04-21T17:58:08Z")

</div>

Can you show a screenshot of your current tag(s)? What values are they displaying and what's the datatype? And what does your ultimate destination look like?

---

<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:** [April 21, 2025, 6:08pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/3 "2025-04-21T18:08:00Z")

</div>

As @paul-griffith mentioned, include a screenshot of your setup for the best help, but what you are looking for is string addressing in the manual.  
[Modbus Addressing | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/modbus-addressing)

Specifically, this part

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/9/f9f75c3b28c667d467a26bd3e681b1a2ec9bf2d4.png)

The device connection also has some string handling (advanced) options that will need to be considered

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/a/cae2d77a82e480ee641a76934f4be03d2b3c9cff.png)

---

<div class="post-metadata">

**Author:** ![ivan.a.lestan](https://avatars.discourse-cdn.com/v4/letter/i/9e8a1a/32.png) [@ivan.a.lestan](https://forum.inductiveautomation.com/u/ivan.a.lestan)\
**Post date:** [April 21, 2025, 7:09pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/4 "2025-04-21T19:09:30Z")

</div>

Updated.

---

<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:** [April 21, 2025, 7:30pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/5 "2025-04-21T19:30:36Z")

</div>

Try this in a single OPC tag

```python
[yourDeviceName]1.HRS36865:12

```

- **[yourDeviceName]** tells Ignition which configured device to use
- **1** is the modbus unit Id
- **HRS** means holding register with string-type value
- **36865** is the starting address
- **:12** means read 12 characters from contiguous memory locations starting from above

---

<div class="post-metadata">

**Author:** ![ivan.a.lestan](https://avatars.discourse-cdn.com/v4/letter/i/9e8a1a/32.png) [@ivan.a.lestan](https://forum.inductiveautomation.com/u/ivan.a.lestan)\
**Post date:** [April 21, 2025, 7:44pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/6 "2025-04-21T19:44:59Z")

</div>

Brilliant, thank you. That worked perfectly! Really apprreciate it!

---

<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:** [April 21, 2025, 7:46pm UTC](https://forum.inductiveautomation.com/t/reading-ascii-from-a-click-plc/105339/7 "2025-04-21T19:46:52Z")

</div>

Mark as solution, please 👉 👈 🥹
