Essentially no. Each tag can have up to 1000 events per second (more if multiple events share the same timestamp, where we create an internal array of the data). The only real limit will be imposed by the storage space available. […]
FAQ Category: Data Collection
FAQs relating to the collection of data into a RAPID database
Does RAPID support Alarm & Condition data ?
Yes, RAPID supports insertion of both continuous and A&E data. There is a specific schema for A&E data that is based on the OPC specification and there are a number of agent plugins that support the collection of A&E data (OPC, SQL etc). This schema also supports vendor defined attributes. […]
Does RAPID support Store and Forward data collection ?
If store and forward is required then a RAPID Data Agent can be installed local to the data source (OPC, MODBUS, MQTT etc) and this will collect data from the source independently of the state of the RAPID system or its network connection. During normal operation the Agent sends the data to RAPID over a […]
Am I restricted to the tag name provided by an OPC server ?
No, RAPID must use the name from the OPC server to collect data from it, but also supports 2 additional naming fields for each tag. These are ‘Alias’ which is typically a shorter name for the data and ‘Description’ which is a longer name. For data sources where there is no specific item names, the […]
Can I create my own data collection plugins ?
The RAPID Data Agent supports plugin data interfaces via simple DLL’s. It is possible to create custom plugins using Visual Studio with the supplied libraries. These can be developed in both C# and VB. […]
