The software ibaHD-Server is divided in a client and a server component. The server component runs as a service under Windows on an ibaPDA computer as well as on a separate server computer in the network.
Note |
|
|---|---|
|
Considering the large data volume which will be stored over the years, we recommend the use of a separate computer for ibaHD-Server with the correspondent hard disk capacity. |
|
ibaPDA (server) continuously provides ibaHD-Server with measured data which is stored over weeks, months or years in a special file structure. The data is organized and stored in so-called HD stores on ibaHD-Server. The term HD store designates the physical (hard disk) storage area which is sized and reserved for an HD data store.
Different types of HD stores exist depending on whether signals (time- or length-based) or events shall be stored.
Together with the HD data store in ibaPDA, an assignment is established between the signals or events to be recorded and the HD store (file location).
Signals or events can be assigned individually to each HD data store. So, data can be distributed, e.g. according to technological functions or subjects like production or maintenance.
An ibaHD-Server can manage several HD stores including HD data stores. An ibaPDA system can provide several HD data stores with data on one ibaHD-Server as shown in the next picture.
An ibaPDA system can write different HD data stores to different ibaHD-Servers, too. Also multiple ibaPDA systems can write their data by means of multiple HD data stores on the same ibaHD-Server but into different HD stores. The only exception is the event storage, because multiple ibaPDA systems can write on the same event store of an ibaHD-Server. The example shows how multiple ibaPDA systems write into different HD stores on one ibaHD-Server.
Note |
|
|---|---|
|
This means: every HD data store needs a different HD store. It is not possible to write with several data stores into the same HD store. |
|
The ibaHD-Server is operated and configured via the client component. The HD client component is completely integrated in the ibaPDA client. Moreover, the client component makes available the display function of the historical data in the ibaPDA client.
Note |
|
|---|---|
|
An ibaPDA client can only connect to one ibaHD-Server at a time! On the other hand, multiple ibaPDA clients may display the data of the same ibaHD-Server. Their number is limited by the number of HD client licenses. |
|
The signals in the ibaPDA client are dragged and dropped out of a special HD signal tree into a special HD trend graph. Dedicated control elements, zoom and jump functions support the navigation along the time or length axis.
Events are dragged in the ibaPDA client out of the HD signal tree and dropped in an HD event table. It is possible to search special events via filter and a query assistant. The display mode of the relevant line in the event table can be modified dynamically. HD signal displays (trend graphs) can be coupled to an event table. In this way, the historical signal trend graph around an event can be displayed by double clicking on the event line.
Another example for a configuration can be found in the appendix.


