Multiple Ethernet hosts on a single NS terminal

[PdL 71]

I was wondering if anyone has a trick to overcome the problem that when one or more Ethernet hosts setup in a single NS terminal go offline, the terminal becomes pretty much inoperable, due to the great lag and communication errors. Especially when trying to navigate trough screens where objects direct to the offline host, the performance is extremely slow. I know about the comm auto return and timeout parameters but they don't seem to help much, although retry is set to 0 and comm auto return to ON, it keeps trying to connect to the offline host when navigating screens. Sure the screen has to try to reconnect but it should not influence the performance as much as it does now. How do you guys handle this?

[ECSI 17]

Hey PdL did you ever find a solution for this problem?

[PdL 71]

No not really... or really not. One would be to not have the NS poll data in the hosts but to write all data from the host to internal memory, but that would make it very hard to maintain the program. We are moving away from using NS terminals or NS runtime which has the same problem for projects with multiple ethernet hosts. Using more SCADA or other HMI brands to overcome this.