Need help to identify ABB Master 800xa system
Yes, it's possible to consult an expert, but the old and often updated system is so old...
Anyway, the existing system contains 2 redundant 'Aspect/Conn. server', each is with 2 screens for the operators and a client computer for the 'engineering' station. That's it, and a 'AC450controller'.
Computers are located in the operators room and the ABB Master is located in the switch room. Between them is a fiberoptic cable (50meters). This network is stand alone.
As built documentation isn't our strength, so I guess that a MB300 network is installed, right?
Now the main point. I'd like to store all process data, but the very limited data are only for some hours available. Is it possible to install a historic data server? Can I install a hist server on a new computer by myself? Is it plug and play?
Voted best answer
Storing data require Basic History plus possibly TTD Data and Config services to be created in the aspect system. The two later must run on the node acting as AC400 connectivity server, i.e. having the PU515 or PU410 RTA box connected.
Basic History can run in any server node; it logs data to disk so the OperateITData folder need to be able to grow if you are adding new logs to this system.
You seem to have TTDs running in the controller so next step would be to ensure that you have TTD Data and Config sources pointing to these services that need to exist in the service structure. The source aspect is typically located on the MB300 network object itself.
You also need to have a History Source aspect at the same place pointing to the Basic History service.
Once this is all set (services running, source aspects in order, disk space on server) you perform TTD Upload from the TTD Synchronization aspect on each controller object.
For each primary log found (secondary logs are skipped) a log in Basic History is created with Log Period 2x the TTD length. This initial size can be extended to whatever your disk will fit. Just adjust the storage setting on the Log Template aspects to fit your need. Secondary logs (to make long trend scopes to open faster need to be added; but that is a few clicks on the Log Template - just be sure to keep an eye on the disk space so you don't fill the disk).
OPC logs can be added where TTD is missing. Just be sure to read the performance chapter so that you know why logging on 10s, 30s or 1 minute is a waste and why only a subset of properties are possible to subscribe to via controller generic subscriptions (e.g. MB300 AI's VALUE property but NOT Process Section).
Last; perform RTA Board ANPER analysis (task load + channel load) to ensure you are operating within the stipulated limits of what an RTA and MB300 OPC server can deliver.
Feel free to post more questions if you like.
If I understand your question correct...
If you have an Advant 450 controller, you surely have an MB300 network between the controller and the connectivity server(s). If you also have an engineering station with AdvaBuild, this station is probably also connected to the MB300 network.
History data can be stored in different ways. The Advant controller can store history data as TTD (time tagged data). It all depends on what your configuration looks like, but the storage capacity is, as, you say, limited. You can increase the number of storage points by extending the storage in your servers, OPC data logs.
Wether or not you need to install a history server, depends on the amount of data and the number of storage points. For a rather small system you normally do not need an Information Manager (history server). Check the available disk space in your servers, and calculate the size needed for your purposes. Maybe you have the possibility to install more diskspace within your servers? Installing an IM is of course the best solution, but I would not call it plug-n-play.
In order to save space, you can also set up hierarchical logs.
Thank you for answering. Your first assumption is right, but I don't know what 'AdvaBuild' is. I attached a file with installed software.
I'm storing historic data in 9 different 'TTD Log' groups. With the storage capacity you mean the physical harddisk, right?
Is the historic server (IM) an active node that stressed the MB300 network?
Do I save storage capacity after implementation of IM?
Does IM needs a buffered power supply?