The BRD-355 has been designed to support applications such as leased line replacement, analogue/dial-up modem replacement, operating broadband over ISDN and providing broadband for utilities. The BRD-355 provides a fixed broadband connection via ADSL or VDSL. Recent broadband protocol technology changes by telecommunication carriers has forced the industrial communications industry to adapt their solutions. The unit therefore supports most ADSL/VDSL2 communication standards including ADSL Annex J and VDSL2 Vectoring. VDSL2 Vectoring enables data rates to be doubled, helping users to achieve up to 100 Mbit/s over copper cables. This is particularly useful when fibre infrastructure is unavailable.
The cyber security features of the BRD-355 prevent unauthorised access and secure the communication for Internet-enabled applications. An easy-to-use built-in firewall filters incoming traffic, allowing only approved data packets to pass through the device. To inter-connect units securely over the Internet, multiple encrypted VPN technologies are supported, including IPsec and OpenVPN.
Because most automation devices are now equipped with an Ethernet port for communications, the BRD-355 has a built-in two-port Ethernet switch. However, to support the need to connect to legacy equipment with serial outputs, the unit also features an RS-232-port. Serial to Ethernet conversion and intelligent modem replacement features help to simplify upgrading these legacy solutions to be part of an IP-enabled network.
For easy integration into existing industrial applications, the compact unit has a robust design and can be installed on a DIN rail. All connectors and LEDs have been positioned at the front, providing the user with easy access and fast status feedback. The unit is energy efficient, helping to minimise power consumption, and can be powered from a wide input range from 10 to 60 VDC. An isolated power supply increases immunity against electromagnetic interference and provides greater communication reliability.
@Westermo #PAuto @HHC_Lewis
No comments:
Post a Comment