For information on accessing the HTTP Interface through a browser, whether your gateway is communicating with iMonnit or not, see the following articles: This interface can be enabled from iMonnit, or locally. The local interface is accessible from a web browser on the same local network. If you need to modify these configurations, you can do it under the Modbus sub-tab that now appears in the gateway settings.Īctivate the Modbus TCP Interface Using the HTTP Interface (local configuration page)Īnother way of adjusting your Modbus TCP settings is through the gateway’s HTTP Interface (local configuration page) through a browser. With the default configuration, the TCP Timeout Minutes is 5 minutes, and the Port number is 502. The Interface will be enabled on the next gateway check-in and can be polled to retrieve Modbus data. Toggle the switch for “ Activate MODBUS Interface” to On.Select the Interface sub-tab (in the gray area toward the center of the screen).Select the Settings tab (gear icon) in the top navigation bar.Select the gateway to activate the Modbus TCP Interface.Select Gateways from the primary left-hand menu.These steps assume that your gateway is in your iMonnit account. Therefore you’ll need to configure your gateway to operate with a static IP address.Īctivate the Modbus TCP Interface Using iMonnit Note: To effectively use your gateway with the Modbus TCP Interface, you’ll need to poll your gateway at the same IP address. You can activate it through iMonnit or locally using the HTTP Interface (local configuration page). There are two ways to activate the interface. The Modbus TCP Interface on an Ethernet Gateway is inactive by default. Using the Ethernet Gateway 4 on a private MODBUS TCP or SNMP Network.
MODBUS SERVER AND DEVICE NOT COMMUNICATING SOFTWARE
If you are using the Modbus TCP Interface in conjunction with iMonnit Software (such as ), there’s no need to unlock your gateway. Please review the article below for details on using the gateway on a private network with the Default Server Interface disabled. Important When operating an ALTA Ethernet Gateway on a private network without iMonnit, the gateway must be unlocked, and there are certain limitations in configuring sensors. Therefore there is no way to send data or configure the gateway or sensors through the Modbus TCP Interface. Note: The Modbus TCP Interface is read-only. The Interface’s standalone configuration enables the gateway on a local private network without iMonnit by polling the gateway via Modbus TCP requests. This interface can be used without the Default Server Interface (iMonnit Software) active or as a standalone interface. Modbus TCP is the Modbus remote terminal unit (RTU) protocol with a TCP interface that operates over Ethernet. The Monnit ALTA Ethernet Gateway 4 offers a Modbus Transmission Control Protocol (TCP) Interface to access gateway and sensor information directly via Modbus TCP poll requests. There are slight differences in the Modbus TCP Interface of the Ethernet Gateway 3. Note: This article is for the ALTA Ethernet Gateway 4.
0 kommentar(er)
