- HMI Model: cmt2108(V2)
- EasyBuilder Pro Version:v6.10.01.259
- EasyDiagnoser
- I’m having problems on a siemens S7 1200 network , I’ve used the EasyDiagnoser to view the tags and see what’s happening. I have some 32 bit float register for real numbers , each states polling all the time . I have no issues with a native Siemens hmi but on the weintek it fails and as stated permanently reads polling . It’s on profinet (port102) and all the other tags seem to be working fine .
Does anyone have any ideas , thanks
Hi, and thank you for contributing to our forum!
To help us better assist you, could you please provide the following information:
- The driver name you are using in EasyBuilder Pro
- The exact controller model (e.g., S7-1200 CPU model)
- A screenshot of the tag that is causing the polling error
This will help us troubleshoot your issue more accurately. Thanks again!
I’m using the Device id:477,Siemens_S7_1500_Ethernet.v33 on absolute addressing. I didn’t really want to but the Siemens S7-1200/S7-1500 (S7commPlus, symbolic addressing) failed , it imports all the tags and they are actually in the project address folder but every one selected states invalid address .
I’m using S7 1200 CPU 1214C AC/DC/Rly CPU’s (X2) and the tags are all 32 bit float registers that sit on polling as can be seen from the picture of the tag library .
I’d dearly love to use symbolic addressing but the tagging seems to fail although it’s imported using the same file as the absolute addressing. The system is in use at the moment so I can’t really experiment more until production stops. As stated I’m already using a Siemens hmi with these tags without any issues . The connection dropping is possibly because of the polling issue I’m guessing.
I’d also be interested in why symbolic addressing fails to be absolutely honest , I can select a tag but then have a ? appear in the data section hence it doesn’t know if it’s a bit or word etc… . I’ve always used absolute addressing but as everything is already operational on the plc , the tags have been written and are running on a Siemens hmi I’m at a bit of a loss why the weintek hmi fails to understand the tags in symbolic format .
Hi @Luckyjonny,
To help us better understand the issue, can you please let us know if at that time both the “Siemens S7-1200/S7-1500 (Absolute Addressing) (Ethernet)” and “Siemens S7-1200/S7-1500 (S7CommPlus, Symbolic Addressing) (Ethernet)” were added within your project?
Also, can you please create a new simple project file to test the “Siemens S7-1200/S7-1500 (S7CommPlus, Symbolic Addressing) (Ethernet)” driver. Within this new project file, please import the .ap file then add a single object such as bit lamp or numeric object and check if this project will compile with just this tag referenced. When finished, can you please let us know if this test was successful?
Yes , this is what I see whenever I try symbolic addressing when I go into project followed by address the tags aren’t present . If I then import them in a csv file I still get the same error .
When I go to select a tag I get the file structure appear and I can select a tag but it then puts a ? Where the data type should be .
It’s a little bit frustrating as the importing tags always is successful according to the software .

This is the tag file structure I have appear which if I then select doesn’t seem to appear as a 32 bit float , it doesn’t work with inputs , outputs either etc…
That’s why I’ve used absolute addressing and have had to basically move dB data to another block that’s not optimized . I already use the block that’s optimized as data on another Siemens hmi .
When using the “Siemens S7-1200/S7-1500 (S7CommPlus, Symbolic Addressing) (Ethernet)” there should not be any tags within the “Address library” after import, so I think their may have been a mistake. Can you please try to create a simple test project as I described and let us know if the issue is resolved?
Yes , a simple tag based program with a couple of tags works fine with get tag info . If I try to load it from ap file it fails , we are in production at the moment so I’ll try and recompile the program I’m working on and try get tag info and hopefully it’s successful. I’ve been doing it from the ap file which seems to be giving me issues for some reason .
Thank you
I am not sure why the .ap file fails to import in this case, but the developer of this driver noted the following wihtin the PLC Connection guide:
Can you please review the instructions in step 2 of this guide and advise if you can import your tags via the [Project] → [Archive] method?
Yes , I’d already tried this method but I can try again and see what the outcome is .
When I use the ap file I can get the tags to import but they are all unusable. I’ll persevere and thank you for your assistance.
Hi @Luckyjonny,
You are most welcome! And, in case you’d like some local assistance I will PM you a point of contact.