# ERROR S71200 Driver **URL:** \ **Category:** General Discussion\ **Created:** [February 14, 2019, 7:38pm UTC](https://forum.inductiveautomation.com/t/error-s71200-driver/22590 "2019-02-14T19:38:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![augustod](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@augustod](https://forum.inductiveautomation.com/u/augustod)\ **Post date:** [February 14, 2019, 7:38pm UTC](https://forum.inductiveautomation.com/t/error-s71200-driver/22590/1 "2019-02-14T19:38:29Z")
Hi, I am writing to you because I have a problem in a communication with an S7 1200 PLC. Normally it works correctly, but once or twice a day an error is generated that is registered in the log. The variable is a bit in the memory position M1.1 in the PLC that is written to change its value from 0 to 1. The error is as follows: INFO | jvm 1 | 2019/02/14 13:20:05 | INFO [CABEZAL] [13:20:04,995]: Writing… INFO | jvm 1 | 2019/02/14 13:20:05 | ERROR [WriteContext] [13:20:05,002]: Write timed out. INFO | jvm 1 | 2019/02/14 13:20:05 | java.util.concurrent.TimeoutException INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.devices.syncops.SynchronousWrite.waitForItems(SynchronousWrite.java:43) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext.processWritableValues(WriteContext.java:107) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext.writeDeviceNodes(WriteContext.java:72) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext.execute(WriteContext.java:54) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.AbstractOperationHandler.handleOperation(AbstractOperationHandler.java:26) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.base.StandardAddressSpace.write(StandardAddressSpace.java:219) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.addressspace.base.XOPCAddressSpace.write(XOPCAddressSpace.java:410) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.core.services.attribute.WriteService.executeInternal(WriteService.java:43) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.core.services.attribute.WriteService.executeInternal(WriteService.java:19) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.core.services.AbstractService.execute(AbstractService.java:53) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.stack.AbstractUAServer$RequestServer.serveRequest(AbstractUAServer.java:77) INFO | jvm 1 | 2019/02/14 13:20:05 | at com.inductiveautomation.xopc.server.stack.AbstractUAServer$RequestServer.run(AbstractUAServer.java:66) INFO | jvm 1 | 2019/02/14 13:20:05 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) INFO | jvm 1 | 2019/02/14 13:20:05 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) INFO | jvm 1 | 2019/02/14 13:20:05 | at java.lang.Thread.run(Thread.java:745) INFO | jvm 1 | 2019/02/14 13:20:05 | ERROR [Provider [default]] [13: 20: 05,007]: [[default] Caladores / Calador\_1 / Calador / Habsuccionador] Error writing to OPC address [[Ignition OPC-UA Server] [Caladores\_PLC] MX1.1]. Result code: Unknown INFO | jvm 1 | 2019/02/14 13:20:05 | ERROR [S71200Driver [Caladores\_PLC]] [13: 20: 05,050]: No optimized AddressBlock list found for items: [com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@4a154f21, com.inductiveautomation.xopc.server. addressspace.contexts.WriteContext$PendingDriverWrite@628c02e8, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@b669899, ​​com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@ea5fb24, com.inductiveautomation. xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@6ea9c196, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@6c3005e9, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@532deaa6, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@72f0473c, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@52f58d85 , com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@3e86d57f, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext$PendingDriverWrite@2c270d3, com.inductiveautomation.xopc.server.addressspace.contexts.WriteContext $ PendingDriverWrite @ 727b1e10] I do not know why it happens. Somebody could help me? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b44f0b4bd40f20ba9e137d92b2c6aaa180f8992f.png) ---
**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\ **Post date:** [February 15, 2019, 7:00am UTC](https://forum.inductiveautomation.com/t/error-s71200-driver/22590/2 "2019-02-15T07:00:27Z")
Why you have Data Type as Int1? If the tag is MX1.1 (bit) then Data Type must be Boolean. ---
**Author:** ![augustod](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@augustod](https://forum.inductiveautomation.com/u/augustod)\ **Post date:** [February 15, 2019, 1:08pm UTC](https://forum.inductiveautomation.com/t/error-s71200-driver/22590/3 "2019-02-15T13:08:30Z")
Maybe it is a mistake, however it works for days, and only in a few moments generates an error. Maybe it’s a network problem where the connection to the PLC fails. ---
**Author:** ![jimschaefer](https://avatars.discourse-cdn.com/v4/letter/j/c6cbf5/32.png) [@jimschaefer](https://forum.inductiveautomation.com/u/jimschaefer)\ **Post date:** [July 24, 2020, 12:09pm UTC](https://forum.inductiveautomation.com/t/error-s71200-driver/22590/4 "2020-07-24T12:09:36Z")
I am getting the same error, but for different code. Would like to understand what this error indicates.