Babel Buster MX-61-V3 Modbus to SNMP Gateway

        Babel Buster MX-61-V3 Modbus to SNMP Gateway

        Control Solutions’ Babel Buster® MX-61-V3 is a Modbus to SNMP Gateway used to connect Modbus RTU or Modbus TCP devices to your SNMP network. 

        • $549.00
         
        OR

        Control Solutions’ Babel Buster MX-61-V3 is a Modbus to SNMP Gateway used to connect Modbus RTU or Modbus TCP devices to your SNMP network. The SNMP manager can use SNMP Get to retrieve contents of any mapped Modbus register. In addition, the BB3-6101 uses threshold rule templates to continuously monitor Modbus data and generate SNMP Traps upon sensing of “alarm” conditions.

        The MX-61-V3 supports SNMPv3 as well as SNMPv2 and SNMPv1. User credentials for SNMPv3 access are entered via the built-in secure web user interface.

        Feature Highlights
        • Connect Modbus RTU and Modbus TCP Devices to SNMP v1, v2c, v3
        • Higher point count, up to 1,000 MIB variables typical
        • User defined register map for Modbus
        • CSV import of register maps for client/master configuration
        • Modbus RTU RS-485 Master or Slave
        • Modbus TCP Client and Server
        • SNMP Get/Set access to all data points
        • SNMP trap generation, user programmable criteria
        • User HTML support for adding custom web pages
        • Configured via secure (https) internal web server
        • 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.

        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.

        • SNMPv3 in addition to SNMPv1/v2
        • SNMP Get/Set access to all data points
        • SNMP trap generation, user programmable criteria
        • MD5/DES support for Get/Set, encrypted traps not supported
        • Supports MIB size of 1,000 variables typical
        • Up to 2,000 Modbus registers
        • Support for multi-register 32-bit, 64-bit data and character strings
        • Local registers accessible as any Modbus register type
        • Modbus coils, discrete inputs, input registers, holding registers
        • Modbus register mapping configured via web interface
        • Built-in data scaling for units conversion
        • Support for packed holding registers
        • Modbus RTU Master or Slave
        • Modbus TCP Client and Server
        • 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 with XML configuration files
        • Includes “10X” configuration file capacity
        • Direct import of CSV configuration files
        • Hardened RS-485 transceiver for Modbus RTU
        • 10/100BaseT Ethernet
        • DHCP or static IP address
        • Field upgradeable firmware upload via ftp
        • 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-V3

        MX-61-V3 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

        Footer navigation