# AbstractDriver Stopped Working

**URL:** <https://forum.inductiveautomation.com/t/abstractdriver-stopped-working/34487>\
**Category:** Module Development\
**Tags:** ignition80\
**Created:** [May 6, 2020, 3:54pm UTC](https://forum.inductiveautomation.com/t/abstractdriver-stopped-working/34487 "2020-05-06T15:54:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [May 6, 2020, 5:47pm UTC](https://forum.inductiveautomation.com/t/abstractdriver-stopped-working/34487/4 "2020-05-06T17:47:13Z")

</div>

> [@OPC-UA driver for Ignition 8: New "Device" interface?](http://forum.inductiveautomation.com/t/opc-ua-driver-for-ignition-8-new-device-interface/25046/7):
>
> Ah, and just as a warning to you and anyone else who might be using this new Device API, there are some breaking changing coming down the line frowning Whenever Milo 0.5.0 is released and Ignition updates to it there will be some required changes to your Device implementations. You can get a feel for what’s changing here: [Update opc-ua-device example for upcoming Device API changes by kevinherron · Pull Request #43 · inductiveautomation/ignition-sdk-examples · GitHub](https://github.com/inductiveautomation/ignition-sdk-examples/pull/43) and the corresponding ch…

Does this statement apply to my module?

---

_[View the full topic](https://forum.inductiveautomation.com/t/abstractdriver-stopped-working/34487)._