# Problem with IEC61850

**URL:** <https://forum.inductiveautomation.com/t/problem-with-iec61850/101650>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 30, 2025, 9:57pm UTC](https://forum.inductiveautomation.com/t/problem-with-iec61850/101650 "2025-01-30T21:57:19Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![tevis](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tevis/32/40783_2.png) [@tevis](https://forum.inductiveautomation.com/u/tevis)\
**Post date:** [July 31, 2025, 11:17pm UTC](https://forum.inductiveautomation.com/t/problem-with-iec61850/101650/7 "2025-07-31T23:17:23Z")

</div>

Thanks Kevin, I think its likely to be an issue with how I have configured the IEC61850 server in my end device (Brodersn RTU32). I'm getting similar unexpected values when using 3rd party IEC61850 clients but just thought I would check here as the solution may have been the same..

I will raise the issue with support regarding the logging in my previous thread. ([IEC 61850 Client Driver logging](https://forum.inductiveautomation.com/t/iec-61850-client-driver-logging/109180))

---

_[View the full topic](https://forum.inductiveautomation.com/t/problem-with-iec61850/101650)._