0
Under review

S7 interface - no signal values even though address is correct and connection can be made

Andrea 2 days ago in General Questions updated 1 day ago 2

I'm currently working on a project with a 1518TF-4 CPU which we activated on an IPC. I can establish a connection between Unity and the PLC but the signals then doesn't recieve any values and stay 0 or FALSE.

The signals I need access for are inside a DB. I've created the Signals in the S7 interface by hand and I made sure the address is correct. 
Example of a signal I created:

Image 1299

I also made sure, that all the settings specified here S7 TCP | realvirtual.io are done. So that there's full access and PUT/GET communication is allowed. I tried establishing a connection to signals inside a DB and Q signals. My only goal is to read signals, no need to write them. 

I've tried it with realvirtual 2022.19.6148 and 2022.15.5414. The Unity version I'm using is 2022.3.39. I also tried a simple test siemens project but that also didn't work. 

I know that it already worked at some point last year, but I can't figure out why it doesn't anymore. 

This is what my S7 config looks like: 

Image 1300

I've also tried all kinds of varieties of settings, so different values for max pdu length, with reverse high low bytes and more. 

I don't know if this has any relevance but I did notice that sometimes, when reverse high low bytes is activated, some Bool signals randomly jump between FALSE and TRUE, some Ints sometimes jump to 265 and back to 0 and Floats will do the same to 2.350989E-38.

Does anyone have an idea, why I cannot get the signal values in Unity? I've run out of ideas. 





Under review

Hi Andrea,

That does sound like unusual behavior. Since nothing has changed on the interface code side, it's a bit tricky to pinpoint the root cause.

Would it be possible for you to test this with a minimal project setup? For instance, you could use PLCSim Advanced with the TCP/IP interface to check if the same issue persists. This approach could help isolate whether the problem lies within your current project or the interface itself.

Let us know what you find!

Best regards,
Thomas

I'll be on vacation until February so I'll try it when I'm back. A coworker has pointed out that the addresses could be wrong though, so I will also have a look at that when I'm back.