Babel Buster MX-61-V2C SNMP to Modbus Gateway

$549.00

Control Solutions’ Babel Buster® MX-61-V2C is used to connect SNMP v1 and v2c devices to Modbus RTU and TCP.

SKU: MX-61-V2C Categories: ,

Overview

Control Solutions’ Babel Buster® MX-61-V2C is used to connect SNMP v1 and v2c devices to Modbus RTU and TCP. The MX-61-V2C includes an SNMP client that can read and write MIB variables in other SNMP devices. When reading, the remote device’s data will be stored in a local register. When writing, data will be taken from a local register and sent to the remote SNMP device via SNMP Set.

The MX-61-V2C includes an automatic table walker with multiple algorithms making it suitable for walking the sparse alarm table found in UPS systems implementing RFC 1628. The table walker can easily translate the alarm table into a series of Modbus coils for easy access by a PLC.

Feature Highlights
• Connect SNMPv1/v2c Devices to Modbus Network
• Modbus RTU RS-485 Master or Slave
• Modbus TCP Client and Server
• SNMP v2c client and server
• SNMP Get/Set access to all data points
• SNMP trap generation, user programmable criteria
• Configured via secure web server
• User HTML support for adding custom web pages
• Supports IPv4 and IPv6
• FCC, CE Mark
• Software Included, No Drivers to Buy

Full product information, data sheet, online user guide, tutorial videos, and more available by clicking here.

Description

Control Solutions’ Babel Buster® MX-61-V2C is used to connect SNMP v1 and v2c devices to Modbus RTU and TCP. The MX-61-V2C includes an SNMP client that can read and write MIB variables in other SNMP devices. When reading, the remote device’s data will be stored in a local register. When writing, data will be taken from a local register and sent to the remote SNMP device via SNMP Set.

The MX-61-V2C includes an automatic table walker with multiple algorithms making it suitable for walking the sparse alarm table found in UPS systems implementing RFC 1628. The table walker can easily translate the alarm table into a series of Modbus coils for easy access by a PLC.

The MX-61-V2C includes a trap receiver supporting both v1 and v2c traps. The template driven trap receiver provides multiple algorithms for recognizing traps, and can easily place trap information into holding registers for Modbus access.

The MX-61-V2C allows you to create your own Modbus register map. The “registers” can be 16, 32, or 64 bit integer, or IEEE 754 floating point. The MX-61-V2C also supports ASCII character strings as a series of registers.

The MX-61-V2C can be Modbus RTU master or slave (user selectable), and Modbus TCP client and server (concurrently). When configured as a master, maps created via templates in the MX-61-V2C’s web UI will read and write other Modbus devices, copying their data to local registers when read, or sending data from local registers to those devices when written.

The MX-61 is a significant enhancement over its predecessor, the SPX. The hardware includes a faster processor and hardware encryption engine for efficient rendering of secure web pages. The software includes numerous enhancements.

• IPv6 support
• Secure (HTTPS) web server
• Higher point count, up to 1,000 MIB variables typical
• CSV import of register maps for client/master configuration
• Menu options to clear part or all of configuration

Configuration of the gateway is done via the secure web pages served by the internal web server. The user simply fills in templates. The entire configuration is saved in the internal Flash file system in XML format. This file may be exported to replicate additional copies of the configured device, or for backup.

The MX-61-V2C includes template based rules for simple calculations and data tests. These can be used for simple data manipulation. Reformatting from one register type to another is automatic. Therefore, a simple copy rule will transform a number into an ASCII string for use in sending traps.

Full product information, data sheet, online user guide, tutorial videos, and more available by clicking here.

 

Specifications

• Modbus RTU RS-485 Master or Slave
• Modbus TCP Client and Server
• Modbus TCP over Ethernet 10/100BaseT
• SNMP v1, v2c Get/Set access to all data points
• SNMP v1, v2c table walker
• SNMP v1, v2c trap receiver
• SNMP v1, v2c trap generation, user programmable criteria
• Up to 2000 local registers
• Supports MIB size of 1,000 variables typical
• 16, 32, 64-bit integer, 32 or 64-bit IEEE 754 floating point, Mod10
• ASCII character string support (UTF-8)
• Supports Modbus “coils”, input registers, holding registers
• Modbus register mapping configured via web interface
• Modbus (master) polling interval configurable per point
• Configure via secure web pages with password protection
• TLS 1.2
• RSA-1024/SHA-256 self-generated certificates
• Supports externally generated certificates
• Flash file system, 10X capacity, for XML configuration files
• Direct import of CSV configuration files
• Online help, Quick Help section at bottom of every web page
• Field upgradeable firmware upload via ftp
• DHCP or static IP address
• Hardened EIA-485 transceiver for Modbus RTU
• Powered by 10-30VDC or 24VAC 50/60 Hz
• Power Consumption: 0.1A @ 24VDC
• Panel mount, 70mm H x 131mm W x 38mm D
• Pluggable screw terminal block for power & RTU network
• Operating temperature -20°C to +75°C
• Humidity 5% to 90% non-condensing
• FCC Class A, CE Mark

Maximum Object Counts and System Capacities for MX-61-V2C

 MX-61-V2C allows user allocation of memory resources. Memory capacity will not support maximum counts of everything possible, but maximum count limits are set high so that you can allocate resources where you need them.

• Maximum Modbus registers 2000

• Maximum Modbus RTU device count 240
• Modbus RTU read map count 1000
• Modbus RTU write map count 1000

• Maximum Modbus TCP device count 200
• Modbus TCP Client read mapcount 1000
• Modbus TCP Client write map count 1000

• Maximum MIB Size: 2000 Variables, Integer branch
• Maximum MIB Size: 1000 Variables, other branches

• Maximum SNMP Client device count 200
• SNMP Client read map count 1000
• SNMP Client write map count 1000

• Maximum SNMP trap destinations 5
• Maximum SNMP trap receive sources 50
• Maximum SNMP trap receive rules 500