I guess I have to question 'Has to be merge'. You already know the downside, what is the perceived benefit of merging?I've had a single plant that exceeded the max tag count, so we split the application in two and used two I/O servers.
Wonderware Intouch Demo License
Later expansions caused us to hit the max tag count again, and we split to four I/O servers. The limit is for InTouch. Any one InTouch application has the limit, but that doesn't mean your plant has to fit in that limit.In the example I worked on, we ended up with four I/O servers to handle 9 lines. The I/O servers were where the tag limit mattered in our case.
The clients used remote references and had very low tag counts. The clients could access all four I/O servers.We did have to manage several InTouch applications, which complicated matters. But it was workable. Oakley,If you don't mind me asking,I use Intouch windowmaker and windowviewer at my plant. What exactly does Archestra do and how does it help?Meanwhile I'm stuck with a stand alone 64 tags license.:smas:ArchestrA is object based and has a Integrated Development Environment. It makes it alot easier to develop new gear for your plant. Where one would normally use Smartsymbols all symbols are now contained in the object.
It has a parent-child hierarchy that shows derivation of the objects.You can still use smartsymbols with the objects or do away with them completely. Automatic referencing is made easy. High Level Diagnostics standard as part of object viewer.You can even convert your current application and use it within system platform.64k Is the maximum Intouch Count but with System Platform you can go much much higher than 64k. I recall a system where we at 150k+. ArchestrA is object based and has a Integrated Development Environment.
It makes it alot easier to develop new gear for your plant. Where one would normally use Smartsymbols all symbols are now contained in the object. It has a parent-child hierarchy that shows derivation of the objects.You can still use smartsymbols with the objects or do away with them completely. Automatic referencing is made easy. High Level Diagnostics standard as part of object viewer.You can even convert your current application and use it within system platform.64k Is the maximum Intouch Count but with System Platform you can go much much higher than 64k. I recall a system where we at 150k+.Galaxy??Sir, how about our Stand Alone applications? Can we just import it into the SystemPlatform?
How about the tags?Thanks! We have three stand alone applications ('HVAC','ELECTRICAL' and 'MAIN') our client wants us to put it into 1 application. Where in we can navigate all the 3 areas.wonderware has given us credit for old licenses when upgrading in the past.
You may want to talk with them about your project and ask them about letting you trade in the old licenses toward the new license.If it were me, I would get away from wonderware. The support is terrible(along with the price of it) and the licensing is from the 80's, along with most of the technology.
Another advantage of ArchestrA is that with a galaxy of objects, you can have multiple managed InTouch apps. Say a specific application for one area, and a totally different application for another. Additionally, since you can create object symbols within the object template, you have have consistent graphics between the applications.Speaking of the graphics. This would be one stop shopping for the object graphics.Example: if you have an analog device template, you could use the analog graphic in the template everywhere you have an analog device. Now lets say you want to add a button on the faceplate of the analog device to pull up a trend of the object from the historian.
Change the template and deploy. No need to go through the entire application and change every instance to add this functionality.Additionally, if you are using WW Historian, one nice feature is store and forward. If your historian goes off line for any reason, the AOS (Application Object Server) will store the data until the historian is available, then push the data to it. We have three stand alone applications ('HVAC','ELECTRICAL' and 'MAIN') our client wants us to put it into 1 application. Where in we can navigate all the 3 areas.There is always upgrading associated with transferring from a stand alone system to the system platform architecture. For one you might require additional platforms for your GR ect.
Wonderware Demo License Verification
There is other alternatives which are more low risk.Try this link (Not knowing what your system looks like this lets you do application management so you could effectively have all the application on a typical multi monitor operator system. To transition between them is pretty much seamless.
It would also not affect your current setup so it is very low risk. Downside some thin client hardware required.Hope this help.
I guess I have to question 'Has to be merge'. You already know the downside, what is the perceived benefit of merging?I've had a single plant that exceeded the max tag count, so we split the application in two and used two I/O servers. Later expansions caused us to hit the max tag count again, and we split to four I/O servers. The limit is for InTouch.
Any one InTouch application has the limit, but that doesn't mean your plant has to fit in that limit.In the example I worked on, we ended up with four I/O servers to handle 9 lines. The I/O servers were where the tag limit mattered in our case. The clients used remote references and had very low tag counts.
The clients could access all four I/O servers.We did have to manage several InTouch applications, which complicated matters. But it was workable.Hi, are I/O servers have I/O points limit? Cause were experiencing right now a delay on update, we have 60,131 tags in 1 DASABCIP.4 I/O server.The I/O server Diagnostics always Hang up on the SMC.And in Wonderware,What are the possible downside if we maximized the number of tags; Having a large number of tags 60,131 out of 61,402(license limit).Does it has a direct effect on DASABCIP.4?And can we directly pick an item from DASABCIP.4 and show it in Wonderware Application?, like remote tag (WW application into another WW application).Cause in FactoryTalk I notice that some connections were directly connected to the I/O server. Does WW can do that also?Thanks and Regards,Vryle.
Apologies for jumping in a bit late on this. Been on holiday.With the amount of Tags you are using i would move away from the DAS server all together and go for a product like Topserver from SoftwareToolbox. You can get most common driver and use either the DDESuitelink or the OPC object. I had similar issues in the past using DAS.
And it was a 2 part solution. Firstly i swopped out the DAS for topserver and secondly did optimization of the scan engines.So the rule i normally have is that i will set the scantime on a engine to minimum of 500ms. What you can do is monitor your CPU.Start Deploying objects in groups, You want to have 1 CPU at +-15-20% load. This is a good indication to create a new engine and to deploy the objects on your new engine.Also look at your scanovverrun of engine in object viewer this is a good indication that there are to many objects vs what you have set your scantime to be. Scanoverun indicates that the engine could not fully process all the objects.This does cause a 'delay' in updates.You can have 2 engines per CPU in your AOS. Keep in mind the load your server will have when redundancy kicks in.I would also reccomend having a Slow - Medium and Fast groups not all data always has to be polled at 1s i normally break this down in 1s/3s/5s.Hope it helps.
Wonderware License Crack
What i saw here was 3 Groups are in 1 PC and the another 5 groups came from another PC.Ill suggest that Topserver, Another thing is DAS always hang up. Do the number of device items affect the performance of server?In our case we have 60,000 + items.ThanksIt definitely affects your update time.
I have done tests in the past on 50000+ IO going to topserver took off half the delay time again you need to look at how many objects are deployed under each scanengine and what results the scanengine returns. If there are overruns you might see delays in data.Maybe you can elaborate on how many objects you have allocated and post your object viewer results.The engine attributes i would look at isEngine.Schedular.ScantimeEngine.Schedular.ScanoverrunsCntEngine.Schedular.ScanoverrunsConsecCntEngine.Schedular.TimeIdleAvgEngine.Schedular.Objectcnt.