# Siemens WinLC RTX communication with Ignition **URL:** \ **Category:** Ignition\ **Created:** [May 17, 2017, 6:01am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316 "2017-05-17T06:01:17Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Neel](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@Neel](https://forum.inductiveautomation.com/u/Neel)\ **Post date:** [May 17, 2017, 6:01am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/1 "2017-05-17T06:01:17Z")
I am trying to communicate with Siemens WinLC RTX (Soft PLC) with S7 400 Driver, But the communication is not healthy, and the load factor which is displays on ignition gateway status page is around 6000% which very high… Have any one done it before with winlc ??? Pl suggest… ---
**Author:** ![taglias](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@taglias](https://forum.inductiveautomation.com/u/taglias)\ **Post date:** [May 17, 2017, 6:57am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/2 "2017-05-17T06:57:39Z")
I use it with the S7 300 driver and Ignition 7.6.7 and it works, in some way. The problem is that there is an error continuously logged in the gateway because the driver does not handle correctly the first zero length packet that receives from the PLC, so I usually disable the logging for the device (if you search for “winlc” in the forum you will find my post about it). I don’t know if this could be your problem. It works well enough for me, because I use it only for testing the PLC software. ---
**Author:** ![Neel](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@Neel](https://forum.inductiveautomation.com/u/Neel)\ **Post date:** [May 17, 2017, 9:07am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/3 "2017-05-17T09:07:04Z")
Thank you for your reply… You are correct but the communication varies continuously between good quality and bad quality tag… Is such problem you have faced?? ---
**Author:** ![taglias](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@taglias](https://forum.inductiveautomation.com/u/taglias)\ **Post date:** [May 17, 2017, 10:03am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/4 "2017-05-17T10:03:02Z")
I just tried to change the driver to S7 400, but, as expected, the behavior is the same as the S7 300: the error is logged, but the communication works correctly. Sorry, but I cannot replicate your problem. Other than the error logging, the communication and the variables work correctly, I have no issues at all. Which version of Ignition are you using and which operative system? Maybe the behavior changed in the newer versions or with a different OS (I’m using windows). ---
**Author:** ![Neel](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@Neel](https://forum.inductiveautomation.com/u/Neel)\ **Post date:** [May 17, 2017, 10:06am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/5 "2017-05-17T10:06:20Z")
V7.9.2 and also i have done these with ignition 7.8 ---
**Author:** ![Neel](https://avatars.discourse-cdn.com/v4/letter/n/f475e1/32.png) [@Neel](https://forum.inductiveautomation.com/u/Neel)\ **Post date:** [May 17, 2017, 10:07am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/6 "2017-05-17T10:07:15Z")
how many tags you have configure in ignition i was having around 1500 nos ---
**Author:** ![taglias](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@taglias](https://forum.inductiveautomation.com/u/taglias)\ **Post date:** [May 18, 2017, 7:44am UTC](https://forum.inductiveautomation.com/t/siemens-winlc-rtx-communication-with-ignition/14316/7 "2017-05-18T07:44:47Z")
The number of tags is not a problem, I probably have around 8000. But that depends also on how they are distributed in the PLC. It is better to have them packed in few DBs, if possible, otherwise the driver has to do a lot of queries to the PLC. Maybe you should try to use a real PLC to see if you have the same problem, so the issue is not with WinLC. I had a problem similar to your when I tried to use NetToPLCSim with more than one PLC simulated on the same PC; it seemed like the program NetToPLCSim was too slow to respond to driver requests and the communication continuously switched between good and bad. That’s why I started to use WinLC for simulations (I have used it to simulate 6 PLCs at the same time, with a more than 50k sqltags in Ignition, with no issues other than the logging).