Red X on Pop Up launch

[MCC_max]

I have used data tables to create common pop-up panels that are used for several identical pieces of equipment. This works well with one exception. If you launch the pop-up looking at one piece of equipment, then close it and launch the same pop-up for another piece of equipment, the pop-up panel briefly displays data for the previous device and then all links go to red Xes for a few seconds before being populated with new data. The alarm window tends to show a "no response from socket" for the PLC in question whenever this happens. The device is an RTU that is connected to Lookout as a Modbus Ethernet slave.

I can deal with a slight delay on loading data for the new device, but I'd like to avoid the red Xes and error message. Something about switching to a different row in the data table causes this to happen. The red Xes do not appear the first time you open the pop-up panel and they don't seem to appear if it has been a few minutes since you opened it. However, it is common to need to change settings on several similar devices in rapid succession and then we see this issue.

Any ideas on settings for the panel or the Modbus driver to avoid this problem would be appreciated.

Thanks,

Max

[Mike@Forshock]

I use a datatable to multiplex panels as well and have not seen the red X problem.

Have a small demo process?  If i get a chance I will simplofy mine and post it.

Mike

[MCC_max]

Thanks for the reply, Mike.

I don't have a small demo of it, but could probably make one. It is pretty weird behavior.  After playing with it, I find that I get the issue the first time after starting the process that I open the pop-up for a particular device. After that it seems to work, but I will sometimes see the issue come back again if no one has looked at one of the pop-ups for several hours. Each time it happens, all links to the driver go to Red X mode and there is a "no response on socket" message in the alarm summary. The red Xes are there for less than a minute and then everything returns to normal and the alarm clears.

Cheers,

Max

[Mike@Forshock]

Here is how I did mine for my Pump Control Panels, trying to explain a large panel, will try to make a quick demo.

- - - 

Each item is in a unique folder, with many objects below:

Well 17 = \\.\Server\Pumps\Well17

Each pump has a "DisplayPBOpen" pushbutton (\\.\Client\Pumps\Well17\DisplayPBOpen)

Inside the Control Panel area (\\.\Client\CON_Pumps\)

I have a Sequencer object with connections to "Goto...":  Goto1 = \\.\Client\Pumps\Well17\DisplayPBOpen

The sequencer has the label of each folder (Step 1 is "Well17" in this example)

I have a symbolic link (ServerSL)with a dymamic expression:  "\\"&..\Setup\Server&"\Server\Pumps\"&ItemList.Label

Inside the panel, each object connects to the symbloic link connection

Switch with Remote connection:  "[ServerSL]\SettingDT.B1.logical"

Which comes out as "\\ServerName\Server\Pumps\Well17\SettingDT.B1.Logical"

Well18 would be step 2 (Goto2), so the link becomes "\\ServerName\Server\Pumps\Well18\SettingDT.B1.Logical"

On the panel we have additional logic to store the last know Sequencer value, and if it is different we activate the panel and adjust displays as needed (Well vs Booster, etc.)