# Problem with telecontrol using new DNP3 driver

**URL:** <https://forum.inductiveautomation.com/t/problem-with-telecontrol-using-new-dnp3-driver/102892>\
**Category:** Ignition\
**Tags:** perspective, ignition81, scripting\
**Created:** [February 26, 2025, 10:02am UTC](https://forum.inductiveautomation.com/t/problem-with-telecontrol-using-new-dnp3-driver/102892 "2025-02-26T10:02:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 26, 2025, 12:26pm UTC](https://forum.inductiveautomation.com/t/problem-with-telecontrol-using-new-dnp3-driver/102892/2 "2025-02-26T12:26:35Z")

</div>

These scripting functions are only available in the gateway scope. You'll have to trigger them from the Gateway somewhere, or add a message handler that you use `system.util.sendMessage` with from the Client, or use something like @pturmel's [free toolkit module](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/121) that has a handy `@runInGateway` decorator.

---

_[View the full topic](https://forum.inductiveautomation.com/t/problem-with-telecontrol-using-new-dnp3-driver/102892)._