# Siemens Enhanced Driver stuck in ReconnectWait **URL:** \ **Category:** Ignition\ **Created:** [January 14, 2026, 3:48pm UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288 "2026-01-14T15:48:44Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Baskar\_Arumugam](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@Baskar\_Arumugam](https://forum.inductiveautomation.com/u/Baskar_Arumugam)\ **Post date:** [January 14, 2026, 3:48pm UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288/1 "2026-01-14T15:48:44Z")
Hello everyone, I’m facing an issue with **Ignition 8.3.0** while connecting to a **Siemens PLC** using the **Siemens Enhanced Driver**. **Problem description:** - When I configure the PLC using the **Siemens Enhanced Driver** , the device status always remains **ReconnectWait** - No tags come online - No clear error messages are shown in the gateway logs (only reconnect attempts) **What works:** - Using the **Standard Siemens S7 driver** , the **same PLC** , **same IP** , and **same network** , the connection works without any issue - Communication is stable and tags read correctly **Environment:** - Ignition version: 8.3.0 - PLC: Siemens S7 (tested on the same hardware) - Network: No firewall changes, same subnet - Port 102 is reachable and confirmed open ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/4/f4cdd75c350eb326a44cdec7a7e0a45657374b0a.png) A known limitation or bug in Ignition 8.3? - Related to specific PLC firmware versions? - Caused by connection limits or TSAP / optimized block access settings? Any guidance or confirmation would be appreciated. Thanks in advance. ---
**Author:** ![Cody\_Morgan](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cody\_Morgan](https://forum.inductiveautomation.com/u/Cody_Morgan)\ **Post date:** [January 14, 2026, 4:00pm UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288/2 "2026-01-14T16:00:40Z")
There should be a reason for being unable to connect in your logs. You might have to turn on debug level logs for the Siemens loggers, though. I'll edit this post in a moment with the names of the relevant loggers. FYI, If you use "Absolute" address type, that will connect more similarly to the older S7-1200 driver. "Symbolic" uses a different connection type. You probably want to use symbolic. If you don't want to share them via the forum, you can upload them to my dropbox, but sharing on the forum helps others who stumble in the future: > **[Dropbox](https://www.dropbox.com/request/ilZgcCn8hJgcWdrPPEfi)** EDIT: Setting these two loggers two debug should get everything related to the driver. You should see a little arrow to expand relevant log messages. - drivers.SiemensSymbolic - com.inductiveautomation.ignition.drivers.siemens ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/b/7b4a40b2396e07c8d2465c5cf7a1e6e765cf0af1.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/0/70c43744d34fba481615eb0131755491f8f7ffb4.png) ---
**Author:** ![Baskar\_Arumugam](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@Baskar\_Arumugam](https://forum.inductiveautomation.com/u/Baskar_Arumugam)\ **Post date:** [January 17, 2026, 10:58am UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288/3 "2026-01-17T10:58:23Z")
Thank you for taking the time to reply to my post. The logs below are repeatedly generated and are related to my device connection. I hope this information helps you better understand the communication issue I am facing. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/e/ce950230d3b49ee9a043e653b7b2629d68a16cfc.png) For your information, when I select the **Address Type** as **Absolute** , the device status changes to **Connected**. However, when I select **Symbolic** addressing, the device status remains in **Reconnect Wait** (or) **Connecting**. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/e/be0598ab4d125ae4bc24a2fa0895c28664331240.png) Thank you in advance for your support. ---
**Author:** ![Cody\_Morgan](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cody\_Morgan](https://forum.inductiveautomation.com/u/Cody_Morgan)\ **Post date:** [January 29, 2026, 7:41pm UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288/4 "2026-01-29T19:41:21Z")
I'll have to reach out to support from our vendor about that error message. It comes directly from the third party library we use, and I cannot find any documentation about it. What firmware version are you using? If I had to guess, this would be some sort of configuration error. Something not configured properly on the PLC or possibly something that is mismatched in the gateway settings. ---
**Author:** ![Baskar\_Arumugam](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@Baskar\_Arumugam](https://forum.inductiveautomation.com/u/Baskar_Arumugam)\ **Post date:** [February 2, 2026, 7:59am UTC](https://forum.inductiveautomation.com/t/siemens-enhanced-driver-stuck-in-reconnectwait/113288/5 "2026-02-02T07:59:59Z")
Thank you very much for taking the time to respond to my post — I truly appreciate your support. The issue has now been resolved. I would like to share a couple of observations for reference. Initially, while testing symbolic communication, there was a network issue that caused communication problems. At that time, since I was new to symbolic communication, I was unsure whether the issue was related to the network or the symbolic driver configuration. To isolate the problem, I attempted to establish communication using **NetToPLC** instead of connecting directly to the physical PLC. In this case, the absolute addressing worked correctly, but symbolic communication was not successful. Later, I realized that NetToPLC does not support symbolic browsing. After resolving the network issue, I reconnected to the physical PLC and tested symbolic communication again. This time, it worked properly. Thanks again for your guidance.