# Error writing values to tag: Read time out **URL:** \ **Category:** Ignition\ **Created:** [December 24, 2024, 10:47am UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191 "2024-12-24T10:47:01Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Frederik\_Verstraete](https://avatars.discourse-cdn.com/v4/letter/f/ed8c4c/32.png) [@Frederik\_Verstraete](https://forum.inductiveautomation.com/u/Frederik_Verstraete)\ **Post date:** [December 24, 2024, 10:47am UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/1 "2024-12-24T10:47:01Z")
Configuration installation: PLC's are connected to kepserver. Kepserver is configured as OPCUA via ignition gateway. Since replacing a PLC, we are experiencing very slow communication between ignition and the kepserver. after entering a value via ignition client, it takes a lot of time to accept the value, most of the time this error appears: Error writing 95 to tag [Tags]"Tag path" com.inductiveautomation.ignition.client.gateway\_interface.GatewayException Read timed out The new PLC (Schneider M580) is replacing an old Schneider Premium TSX PLC. The Logic, Tags, parameters are mostly identical. The program on the PLC runs with normal cyclus-times We've checked the communication between PLC and kepserver, no read or write failiures, communication is stable. How could we solve this problem? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [December 24, 2024, 11:16am UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/2 "2024-12-24T11:16:24Z")
Have you tried restarting the kepserver? ---
**Author:** ![Frederik\_Verstraete](https://avatars.discourse-cdn.com/v4/letter/f/ed8c4c/32.png) [@Frederik\_Verstraete](https://forum.inductiveautomation.com/u/Frederik_Verstraete)\ **Post date:** [December 24, 2024, 12:22pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/3 "2024-12-24T12:22:17Z")
Yes I did, thanks for reaching out ---
**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:** [December 24, 2024, 2:32pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/4 "2024-12-24T14:32:56Z")
Sounds like the new PLC is less capable than the old, at least for communications. There may be communication resource adjustments needed in the M580. ---
**Author:** ![Frederik\_Verstraete](https://avatars.discourse-cdn.com/v4/letter/f/ed8c4c/32.png) [@Frederik\_Verstraete](https://forum.inductiveautomation.com/u/Frederik_Verstraete)\ **Post date:** [December 24, 2024, 3:05pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/5 "2024-12-24T15:05:12Z")
Thanks for reaching out Mr. The strange thing Is that dataflow between PLC and kepserver goes flowless, when data changes in PLC, it changes on ignition within a second. When writing a value in ignition, kepserver is blocking. When writing a value via a modbus tool to the PLC, it goes flowless. ---
**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:** [December 24, 2024, 3:10pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/6 "2024-12-24T15:10:01Z")
Try writing to the same slow tags with another OPC UA client such as [UaExpert](https://www.unified-automation.com/downloads/opc-ua-clients.html). If it's slow there too you might need to get support from Kepware. If it's not slow there, disable security on the OPC UA connection to Kepware and then get a Wireshark capture while initiating a write from Ignition. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 29, 2024, 11:50pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/7 "2024-12-29T23:50:18Z")
I wouldn't waste your time on Kepware, in my experience it causes more issues than it solves. Consider going to the manufacturer provided solution that you can get direct support from the PLC manufacturer with. > **[BMENUA0100 - communication module, Modicon M580, OPC UA | Schneider Electric...](https://www.se.com/au/en/product/BMENUA0100/communication-module-modicon-m580-opc-ua/)** > > Schneider Electric Australia. BMENUA0100 - communication module, Modicon M580, OPC UA. ---
**Author:** ![Usha\_Vilash](https://avatars.discourse-cdn.com/v4/letter/u/b5a626/32.png) [@Usha\_Vilash](https://forum.inductiveautomation.com/u/Usha_Vilash)\ **Post date:** [December 30, 2024, 11:29am UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/8 "2024-12-30T11:29:56Z")
Hi Frederik, it sounds like the new PLC might handle writes a bit differently than the old one. Have you tried changing the write settings in Kepserver? That might fix the delay. Also, testing with another OPC UA client like UaExpert could help check if the issue is with Kepserver or Ignition ---
**Author:** ![Frederik\_Verstraete](https://avatars.discourse-cdn.com/v4/letter/f/ed8c4c/32.png) [@Frederik\_Verstraete](https://forum.inductiveautomation.com/u/Frederik_Verstraete)\ **Post date:** [February 10, 2025, 5:07pm UTC](https://forum.inductiveautomation.com/t/error-writing-values-to-tag-read-time-out/100191/9 "2025-02-10T17:07:57Z")
Hi Everyone, thanks for reaching all out. The problem was the M580 CPU, we did the test with a stronger CPU BMEP584040 instead of BMEP582020 and it worked. The CPU of the PLC could not handle all the modbus traffic internal between drives and STB-islands.