# DNP3 Binary Output Operation Via Tag

**URL:** <https://forum.inductiveautomation.com/t/dnp3-binary-output-operation-via-tag/58759>\
**Category:** Ignition\
**Created:** [April 22, 2022, 7:12pm UTC](https://forum.inductiveautomation.com/t/dnp3-binary-output-operation-via-tag/58759 "2022-04-22T19:12:25Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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 31, 2022, 9:32pm UTC](https://forum.inductiveautomation.com/t/dnp3-binary-output-operation-via-tag/58759/10 "2022-08-31T21:32:01Z")

</div>

There’s 5 parameters that follow the device name and indices array, but you only have 4.

Your code would be clearer and the mistakes spotted easier if you used named parameters for all the parameters, e.g.:

```auto
system.dnp3.directOperateBinary(deviceName="Dnp3", indexes=[1], opType=1, tcCode=0, count=1 onTime=5000, offTime=5000)

```

---

_[View the full topic](https://forum.inductiveautomation.com/t/dnp3-binary-output-operation-via-tag/58759)._