Главная
Skipped breadcrumb items
RM-1050-T
Инструкция по эксплуатации Страница: 46

Главная
Moxa
RM-1050-T
Инструкция по эксплуатации Страница: 46

Moxa RM-1050-T — обзор программного обеспечения для сбора данных RTU [46/52]

Превью страниц Страница 46 / 52

ioPAC RTU Software RTU Data Acquisition

5-2

I/O Data Access

ioPAC RTU controllers support many kinds of I/O modules that collect physical data from sensors. For ioPAC

8500 series, users can use modularized 85M series I/O modules.

Moxa provides C/C++ programming tools for users to develop their own project for data acquisition. C/C++

library and APIs can be found under C/C++ Sample Code Programming Guide for ioPAC RTU Controllers

 Files  io, io_event, and misc.

One important function of the current analog input module is the Burn Out function. Users can use the

MX_RTU_Module_AI_Burnout_Value_Set API to configure the Burn Out mode. If a module is burned out

or a wire is disconnected, the LED will turn RED.

Battery Backup SRAM

ioPAC RTU controllers support battery backup SRAM which is an important part of applications that require any

kind of data backup in the event of a power failure. The size is 128 KB and users can use the APIs

MX_RTU_SRAM_Read and MX_RTU_SRAM_Write to access the SRAM. For more detailed information and

examples, please refer to C/C++ Sample Code Programming Guide for ioPAC RTU Controllers

 Files

 misc.

Millisecond Timestamp

A timestamp is a sequence of characters or encoded information identifying when a certain event occurred,

usually expressing the date and time of day and sometimes accurate to a small fraction of a second. The ioPAC

85M-1602-T and 85M-3801/11-T support modules have a dual CPU architecture, which means each I/O

module has its own CPU that can easily record events in milliseconds. Using this function enables the ioPAC to

collect data more accurately by providing millisecond timestamps for event and historical data analysis. Thanks

to the millisecond timestamp function, operators can distinguish the sequence of data and know how to handle

this event accordingly.

Users can use the APIs MX_RTU_Module_DI_Value_Get, MX_RTU_Module_AI_Raw_Value_Get, and

MX_RTU_Module_AI_Eng_Value_Get to retrieve the timestamp information from I/O modules. For more

detailed information and examples, please refer to C/C++ Sample Code Programming Guide for ioPAC

RTU Controllers

 Files.

Active OPC Server

Active OPC (AOPC) Server is a software package provided by Moxa that operates as an OPC driver for an HMI

or SCADA system. It offers seamless connection from Moxa's ioLogik series products to SCADA systems. Active

OPC Server meets the latest standard of OPC DA 3.0, which allows connections to various kinds of devices and

host OPC machines.

Moxa has pioneered the concept of “active type” OPC software in the automation industry. The patented Active

OPC Server offers non-polling architecture alongside the standard OPC protocol, giving users the alternative of

active, push-based communication from Moxa’s RTUs and remote I/O devices. This adaptation of “push”

technology means that I/O status will be updated at the Active OPC Server only when there is an I/O status

change, a pre-configured interval is reached, or when a request is issued by a user. This application of push

technology cuts metadata overhead, resulting in faster I/O response times and more accurate data collection

than traditional pull-based architectures. With Moxa’s “active technology” advantage, users can now instantly

receive alarms and real-time updates allowing for timely risk response.

Use the AOPC APIs to configure and access the AOPC tag information. For more detailed information and

examples, please refer to C/C++ Sample Code Programming Guide for ioPAC RTU Controllers

 Files

 aopc.

Moxa RM-1050-T — обзор программного обеспечения для сбора данных RTU [46/52]

Содержание

Похожие устройства