The main attribute of our RMC system is its modular structure, this allows for properties as:
Robustness
- every system and application component is independent program module (exe)
- program error in one module cannot compromise functionality of whole system,
and failing module is automatically restarted by RMC system services
Independence of user interface from working modules
- user interface and core logic functionality are implemented in separate modules
- no ‘window’ on desktop is needed for RMC node to perform its function
Flexible interprocess protocol
- modules communicate by exchanging messages either in asynchronous mode (using subscription/notification system) or synchronous mode (using request/reply system)
Rapid development of modules
- application is designed as a cluster of working and user interface modules
- each module has well-defined focused functionality which leads to more simple
transparent and understandable code
Software maintenance without application shutdown
- program modules in RMC node can be upgraded on the fly, node shutdown is not needed
- node configuration can be modified by adding or removing modules without node shutdown
HOW RMC SYSTEMS WORK?
Common set of system services
Every RMC application utilizes standard system services which allows application developers to focus on solving target domain problems instead of reimplementing common functions of
- state and configuration storage
- alarm signaling and handling
- event logging, with filtering, export and archivation
- system backup and restore
- event scheduler
Web interface
- access to application functions and selected devices via web browser
- multiuser access to single RMC node
Distributed applications
A single RMC system is called ‘node’. Nodes can be connected to form distributed RMC system using custom application protocol based on UDP/IP with various levels of relations between modules:
- direct message exchange between modules in different nodes
- local access to remote module data and events using RMC mirroring service
Hot-standby dual system
- connection of two RMC nodes with identical application configuration
- only one RMC node is active at any given time, with manual or automatic switchover in case of failure
- single IP address access configurable for web access to active RMC node
| Communication protocols | RS232, RS485, MODBUS, UDP/IP, TCP/IP, SNMP v1/2/3, GB2PP |
| Max. modules per node | 100 |
| Max. nodes per application | unlimited |
| Intermodule message throughput | cca 1500 msg/sec |
| Event log message throughput | cca 50 events/sec with queue buffer for 10000 events |
| CMS cooperation | SNMP v1/2/3 agent module with up to 10 trap addresses |
Partial list:
| ATC Radios | Rohde & Schwarz series 4100, 4200, 4400, 5200 Rohde & Schwarz series 200 Rohde & Schwarz series GB4000V |
| Network | EtherWAN 63000, MOXA EDS 508, MOXA EDS 518, Mikrotik |
| Multiplexer | Keymile UMUX 1200/1500, RadMUX |
| Power | AXAM. EltekDC, Eta UPS, IMCO POWER |
| TV | TV vysielače Rohde & Schwarz ATV DD 7000/8000 |
| ATC with CAA SR type approval LPZ-S-006/2011, Military ATC with MAA SR type approval UVL-SPLPZ-010/2007 Conformance to ATC SWAL 3 |
|
| Intelligent Buliding Management | |
| Communication Server (RDS) | |
| TV Transmitter Monitoring and Control | |
| Parking Control System |
| Operating system Microsoft Windows XP, 7, 8, 10, 11 | |
| Minimum HD space 10 GB, minimum RAM 4 GB | |
| Processor Intel Pentium class or higher |
These are minimal system requirements for basic RMC configuration up to five device driver modules.
Minimal requirements for HD space, RAM and processor have to be evaluated specifically for each RMC application.