# Schneider Electric UMAS driver?

**URL:** <https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907>\
**Category:** General Discussion\
**Created:** [July 7, 2016, 7:05pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907 "2016-07-07T19:05:38Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\
**Post date:** [July 7, 2016, 7:05pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/1 "2016-07-07T19:05:38Z")

</div>

I was talking yesterday with Schneider Electric and they were mentioning that it’s possible to read the status of the system bits and Words (%S and %SW) provided you were using the UMAS protocol. Apparently, this is a special protocol that sits on top of the Modbus protocol, but it’s propriety for some crazy reason.

Can Ignition make use of this protocol by any chance? Or is there a way to directly read those system bits without having to map them to memory registers?

I ask because I’d like to get the %S12 bit (PLC running) status, but when the PLC isn’t running then it doesn’t update the status of the memory coil 😒

---

<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 7, 2016, 7:08pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/2 "2016-07-07T19:08:10Z")

</div>

We don’t know anything about this protocol. You’ll have to stick to what you can get through regular Modbus.

---

<div class="post-metadata">

**Author:** ![Richard\_Hart](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@Richard\_Hart](https://forum.inductiveautomation.com/u/Richard_Hart)\
**Post date:** [March 25, 2024, 2:33pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/3 "2024-03-25T14:33:40Z")

</div>

This is a very old thread, but has UMAS been considered again for ignition? OFS is the only OPC Server that supports UMAS and thus reading symbolic tags from Schneider PLCs. It would be great if others could do this too.

---

<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 25, 2024, 2:40pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/4 "2024-03-25T14:40:08Z")

</div>

No, even if it weren't old and obscure, proprietary and undocumented protocols are not generally up for consideration.

---

<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:** [March 25, 2024, 2:50pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/5 "2024-03-25T14:50:39Z")

</div>

If you can get Schneider to cough up a specification, I'd be happy to review it for inclusion in my alternate driver.

---

<div class="post-metadata">

**Author:** ![ben.hutche](https://avatars.discourse-cdn.com/v4/letter/b/9fc348/32.png) [@ben.hutche](https://forum.inductiveautomation.com/u/ben.hutche)\
**Post date:** [March 25, 2024, 5:16pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/6 "2024-03-25T17:16:12Z")

</div>

@pturmel I have been playing around with umas in the plc4x project, and have been able to get it working on a simulator ( at least read support anyway) If you are interested in developing a driver for it, it might be a good starting point.

> **[plc4x/plc4py/plc4py/drivers/umas at develop · apache/plc4x](https://github.com/apache/plc4x/tree/develop/plc4py/plc4py/drivers/umas)**
>
> PLC4X The Industrial IoT adapter. Contribute to apache/plc4x development by creating an account on GitHub.

---

<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 25, 2024, 5:20pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/7 "2024-03-25T17:20:14Z")

</div>

There's also this series of articles by somebody who reverse engineered parts of it: [Liras en la red: The Unity (UMAS) protocol (Part I)](http://lirasenlared.blogspot.com/2017/08/the-unity-umas-protocol-part-i.html)

---

<div class="post-metadata">

**Author:** ![ben.hutche](https://avatars.discourse-cdn.com/v4/letter/b/9fc348/32.png) [@ben.hutche](https://forum.inductiveautomation.com/u/ben.hutche)\
**Post date:** [March 25, 2024, 5:21pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/8 "2024-03-25T17:21:04Z")

</div>

Yes that is super helpful

---

<div class="post-metadata">

**Author:** ![Richard\_Hart](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@Richard\_Hart](https://forum.inductiveautomation.com/u/Richard_Hart)\
**Post date:** [March 26, 2024, 10:14pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/9 "2024-03-26T22:14:09Z")

</div>

I'd also like to add that the ability to read symbolic tags out of Schneider PLCs even if it is only the M580 series would be a significant benefit especially from a maintenance perspective to a large install base in Australia. After many years of neglect (2009-2015) OFS from 2016 onwards has been worked on and updated constantly by Schneider electric.

---

<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:** [March 26, 2024, 10:27pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/10 "2024-03-26T22:27:17Z")

</div>

I didn't find either link very helpful in the sense of making a driver I could stand behind. If someone gets Schneider to cough up a proper spec, I'd be interested.

---

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [April 1, 2026, 9:34am UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/11 "2026-04-01T09:34:19Z")

</div>

I know this thread is old, but I’m currently working on finalizing a working UMAS driver, now that my ADS driver is no longer consuming all of my time 😉

So far it supports:

- Tag Browsing
- Tag Reading
- Tag Writing

Hopefully soon I’ll also be able to add the TLS secured communication.

Anyone interested in this work?

---

<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 1, 2026, 8:54pm UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/12 "2026-04-01T20:54:20Z")

</div>

I imagine everyone suffering from Schneider's horrifically bad Modbus implementation will be interested.

---

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [April 2, 2026, 7:49am UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/13 "2026-04-02T07:49:48Z")

</div>

Well … really not quite sure why Schneider added that sort of completely unneccesary layer of ModbusTCP to UMAS. But yesterday also added: Tag Subscriptions 😉

And even if I did post the last message on April 1st … it actually wasn’t an April’s fool joke 😉

---

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [September 28, 2026, 9:28am UTC](https://forum.inductiveautomation.com/t/schneider-electric-umas-driver/11907/14 "2026-09-28T09:28:43Z")

</div>

Hi all,

I just added our ToddySoft Connect UMAS driver to our website:

> **[Schneider Electric UMAS Driver - ToddySoft Connect — Ignition Modules](https://toddysoft.com/products/connect/ignition/#schneider-electric-umas)**
>
> Pick the Ignition version you need and request a trial or a quote. | Your partner for sustainable digital transition in industrial automation.

It's still a very fresh module ... so I'm planning on bundling the first year of support for the next few months (Which usually defaults to 20% of the purchase cost).

Chris
