Toshiba ASD-G9ETH Manuale Utente

Pagina di 106
 
  
7
ICC 
2.  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. 
 
Supported Protocols 
The interface currently provides server support for the following fieldbus 
protocols: 
• Modbus 
TCP 
• EtherNet/IP 
• PCCC 
• BACnet/IP 
• Profinet 
IO 
 
Note that use of Profinet IO is mutually exclusive of the other supported 
protocols.  In order to use Profinet IO, a separate application firmware file must 
be loaded into the interface (refer to section 12). 
 
Macromedia® Flash-Enabled Embedded Web Server 
Interface configuration and real-time drive parameter monitoring & control are 
provided via an embedded web server.  The interface’s web server feature 
provides direct data access and control via standard web browsers such as 
Microsoft Internet Explorer and Mozilla Firefox.  The latest version of 
Macromedia Flash Player browser plug-in is required.  Refer to section 9. 
 
XML Configuration File Upload/Download 
All interface configuration files are stored in the unit’s internal filesystem in XML 
format.  These files can be transferred to/from a PC via the FTP protocol, which 
provides the capability for PC-based file backup and easy configuration copying 
to multiple units.  Configuration files can also be viewed and edited via standard 
text editors, XML editors and web browsers.  Refer to section 11. 
 
Email-Based Alarm Notifications 
Up to 20 configurable alarm conditions can be programmed into the interface.  
Value, logical comparison and time-based conditions can be provided for the 
interface to autonomously monitor any available drive register.  When an alarm 
condition is triggered, a notification email can be sent to up to four destination 
email addresses.  Refer to section 10.9. 
 
Network Timeout Action 
A configurable network timeout action can be programmed that allows 
parameters to have their own unique "fail-safe" conditions in the event of a 
network interruption.  Refer to section 10.7.4.