 |
 |
The TOSVERT-300MVi Multiprotocol Ethernet and Modbus RTU Interface allows information to be transferred seamlessly between the drive and various fieldbus networks with minimal configuration requirements. In addition to the connection to the ASD, the unit provides a 10/100BaseT Ethernet port, one RS485 port, and one RS232 port. These various communication ports operate independently, and are configurable along with the unit's internal point database via a standard web browser.
The ASD-MVETHERNET currently provides support for the following protocols:
 Modbus RTU (RS485 master and slave)
Modbus RTU (RS232 master and slave)
Modbus TCP/IP (slave)
Ethernet/IP (server)
The TOSVERT-300MVi Multiprotocol Ethernet and Modbus RTU Interface provides simultaneous support for many different communication protocols, allowing complex interchanges of data between otherwise incompatible networks. At the heart of the interface is an element called the "point database". The point database is entirely user-configurable, and provides the mapping information that allows requests from the various supported networks to be interpreted and stored in a common format. This allows data to be routed from any supported network to any other supported network.
|
|
| Documents |
|
|
|
|
| Firmware |
|
 ASD-MVETHERNET V1.100 BSP |
This BSP (Board Support Package) contains:
ASD-MVETHERNET V1.100 application firmware file (.bin file for use with the Rabbit Field Utility)
ASD-MVETHERNET V1.100 User's Manual (in Adobe Acrobat .PDF format)
ASD-MVETHERNET Version Info (in Adobe Acrobat .PDF format)
ASD-MVETHERNET EDS File |
|
|
| Features |
|
Ethernet Port
IEEE 802.3 10/100BaseT Ethernet compliant. Shielded RJ45 connector accepts standard CAT5-type 8-conductor unshielded twisted-pair (UTP) patch cables. Supports multiple simultaneous protocols. |
RS485 Port
One optically-isolated half-duplex 2-wire RS485 port (A / B / Signal Ground /
Shield). This port allows a selection of various master and slave protocols. |
RS232 Port
One RS232 port that can be used to configure the unit, update the internal
firmware, upload/download configuration files or act as a control protocol port. |
Supported Protocols
Modbus RTU (RS485 master and slave)
Modbus RTU (RS232 master and slave)
Modbus TCP/IP (slave)
Ethernet/IP (server) |
Indicators
1 green "LNK" LED that is on whenever a valid Ethernet connection is detected.
1 green "SPD" LED that is on whenever a 100BaseT Ethernet connection is established.
1 amber "ACT" LED that flashes whenever data is transferred across the Ethernet network.
1 bicolor red/green "MS" LED that indicates module status information.
1 bicolor red/green "NS" LED that indicates network status information.
1 green "TX" and 1 "RX" LED on the RS232 port, which indicates RS485
port activity. |
|
Text-Based Console Configuration
Basic unit configuration is performed via a text-based console interface, available locally over the RS232 port via a standard PC terminal program such as Microsoft Windows HyperTerminal®, or over Ethernet via a Telnet session. The unit also provides initial configuration access via ICMP ("ping") configuration. |
Macromedia® Flash-Enabled Embedded Web Server
Advanced unit configuration and point monitoring/control are also provided via an embedded web server using the HTTP protocol. The unit's web server feature provides direct data access and control via standard web browsers such as Microsoft Internet Explorer and Netscape Navigator. The latest version of Macromedia Flash Player browser plug-in is required. |
Configuration File Upload/Download
A unit's configuration can be uploaded from / downloaded to a PC, which provides the capability for PC-based file backup and easy configuration copying to multiple units. |
Network Timeout Action
A per-port and per-point 2-level configurable network timeout action can be programmed that allows each internal point to have its own unique "fail-safe" condition in the event of a network interruption. |
Field-Upgradeable
As new firmware becomes available, the unit can be upgraded in the field by the end-user. |
|
|
|
|
|
