Current Version: 5.0
RTMC real-time monitoring and control software is bundled with our LoggerNet, LoggerNet Admin, and RTDAQ software. Please note that RTMC cannot be purchased separately. This software graphically displays data, sets input locations, and toggles ports and flags. A simple yet powerful user interface allows RTMC to use components such as alarms, sliders, graphs, toggles, tables, and gauges to design custom multitab displays. For more alarms, switches, graphs, gauges, and layout components, see RTMCPro.
Read MoreRTMC Real-time Monitoring and Control Software is bundled with our LoggerNet, LoggerNet Admin, and RTDAQ software. It graphically displays data, sets input locations, and toggles ports and flags. A simple yet powerful user interface allows RTMC to use components such as alarms, sliders, graphs, toggles, tables, and gauges to design custom multi-tab displays.
RTMC's bitmap-based display system provides the tools used to tailor your displays. It can simultaneously display data from any number of data loggers in the network. RTMC can access statistical data reported by the server, including the current state of your data logger network and system-critical information used to trigger alarms. All of RTMC's functions are available when connected as a client to a server on a remote PC. RTMC also includes a sophisticated real-time mathematical compiler for performing real-time calculations. With its point-and-click interface, RTMC is a simple solution for generating real-time displays.
Current Version | 5.0 |
Operating System | Windows 11, 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.) |
Purchased Separately | No (Bundled with LoggerNet, LoggerNet Admin, and RTDAQ software) |
Software Level | Entry |
Real-Time Updates | Yes |
Alarms | Real-time, visual, audible |
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
Product | Compatible | Note |
---|---|---|
21X (retired) | ||
CR10 (retired) | ||
CR1000 (retired) | ||
CR1000X | ||
CR10X (retired) | RTMC is compatible with the mixed array, PakBus, and TD data logger operating systems for the CR510, CR10X, and CR23X dataloggers. | |
CR200X (retired) | ||
CR211X (retired) | ||
CR216X (retired) | ||
CR23X (retired) | RTMC is compatible with the mixed array, PakBus, and TD data logger operating systems for the CR510, CR10X, and CR23X dataloggers. | |
CR300 | ||
CR3000 (retired) | ||
CR310 | ||
CR350 | ||
CR500 (retired) | ||
CR5000 (retired) | ||
CR510 (retired) | RTMC is compatible with the mixed array, PakBus, and TD data logger operating systems for the CR510, CR10X, and CR23X dataloggers. | |
CR6 | ||
CR800 (retired) | ||
CR800 (retired) | ||
CR850 (retired) | ||
CR850 (retired) | ||
CR850 (retired) | ||
CR850 (retired) | ||
CR9000 (retired) | ||
CR9000X (retired) |
RTMC runs on Windows 10 and 11. RTMC runs on both 32-bit and 64-bit versions of these operating systems.
Number of FAQs related to RTMC: 21
Expand AllCollapse All
Value forwarders can be used to keep all of the values synchronized. Use the switch to set the value in one datalogger, and then use multiple value forwarders to read this value and forward it on to the other dataloggers. The value forwarders can be set as hidden so that they don’t show up in runtime.
The RTMC chart is more customizable, but the Connect screen is easier to set up.
A network may need to be loaded into LoggerNet from a backup file. If there was no backup, an identical network must be set up in the LoggerNet Setup for the RTMC project to run.
Assuming the data structure is the same between the two files, the data from the BACKUP file can be cut and pasted into the DAT file.
The project needs to be designed in RTMC Pro using the development environment. The project can then be run within the development environment or by using RTMC Run-Time.
RTMC uses the LoggerNet server for its data source. RTMC Pro, on the other hand, can also use a DAT file.
Yes. In RTMC, there is a Value Forwarder component that can be used to read a value from one datalogger and send it to another.
Access the Public table in the datalogger to use SetPoint. By changing the station setup to retrieve the Public table, it should show up in RTMC as being able to read/write to.
The easiest way to get the data into LNDB is to store the information in the LoggerNet data cache (or, for the information to be in a format that looks like a datalogger data file to LNDB so that it can be imported).
Custom Collection exists solely to collect data directly from the datalogger and to write those data to one or more data files. Because of this, the data are not stored permanently in the data cache of LoggerNet. The only way (with RTMC Pro) to get this data into RTMC is to define a data file data source.