#L32e tag export for kepware how to#
#L32e tag export for kepware Patch#
#L32e tag export for kepware simulator#

Launch the OPC Quick Client, and open the group. Select next through all settings, keeping the defaultsД¦.

#L32e tag export for kepware simulator#

Select the Simulator Driver, and select Next through all other settings to keep them at defaultД¤. In the KEPServerEX Configuration, create a new ChannelДў. Here are the steps you will want to follow to do this:ДЎ. The easiest method is to use the Simulator Driver. Thanks for you help and sorry this was so long I just wanted to state everything i see that might be of help to you guys.Greetings are a few different ways to achieve this in KEPServerEX. This might have been helped out by me bumping up the overhead time slice to 50% in all the l32e at the belts since they are not controlling anything and are mainly used to get data from underground to the studio project outside. I say 6 minutes but I think it may be down to 4 the last time we restarted. We have a 6 minute delay from the time it is shutdown to the time we start displaying tag values on studio displays. Because another issue arises once we shut linx down and restart.

#L32e tag export for kepware how to#

Hopefully someone has seen this before and can tell me how to handle putting these back on the network without running into this issue or knowing a fix for linx.

The l32e then shows active instead of unkeyed and the tags stop coming and going. To fix the issue until the next time it occurs, we shutdown and restart linx. We have 7 units and 25 of the plc cabinets we place at the belts.ДҐ. Like i said this is always with a l32e and is not always the same plc. I can go online with the processor using logix5000 just fine and seems like all is ok there. Once on the network, rslinx shows the l32e in the unkeyed state and this is when we start losing some but not all the tags we have setup in studio/intellution. More often then not we tend to see this issue more with moving plc from old belts to new belts since there might be days to weeks between times it is taken off and put back on the network.Д¤.

If for some reason it is off the network longer, say that the move on a Saturday night and we don't get the fiber hook up till Monday, then this is when we see the issue on the unit's plc. This issue doesn't occur under that short of time.

Normally the unit's plc is only disconnected for a couple of hours. е…ѓ2e gets reconnected to the network either after the unit moves up or when the unit goes on a new conveyor belt. Either the l32e gets disconnected from the network due to the coal mining unit advancing or when the unit moves off a conveyor belt.ДЈ. е…ѓ2e compactlogix controller running for days on end on the ethernet network.Дў. The exact steps during this issue are as follows:ДЎ. I did this last Saturday and the problem still exists.

#L32e tag export for kepware Patch#

Rockwell support suggested updating linx from 2.50 to 2.53 and installing a patch that was suppose to avoid hang ups and crashing of linx. We are certain this is not a studio se issue because we had the same thing occuring when we were using intellution. We get the warning 'communication error has been detected for 'topic ag' and perhaps others. Once a plc is taken off the network and then put back on usually after a day or so we see some tags in that plc come and go within the studio se display.