The Enless receiver behaves like a server and can only accept one client at a time. Being requested by another Modbus device can disrupt Modbus communication with the current TCP client.
Related Articles
- [Proprietary mode] How to reset the receiver to factory settings
- [Proprietary mode] What is the default IP address of the receiver ?
- [Proprietary mode] What is the maximum pulse count ?
- [Proprietary mode] Why is there a red reloading icon next to my transmitter on the IP server of the receiver ?
- [Proprietary mode] What is the receiver's power consumption ?
- [Proprietary mode] How to decode the contact status of the TX CONTACT in the Modbus table
- [Proprietary mode] How to decode the battery status in the Modbus table
- [Proprietary mode] How to decode the battery status in the Bacnet objects
- [Proprietary Mode] Maximum frequency of Modbus requests
- [LoRaWAN] I can't connect my transmitter to the network
- [LoRaWAN] ADR management
- [LoRaWAN] Which port should downlinks be sent to ?
- [LoRaWAN] Behaviour of Joins and LinkChecks
- [LoRaWAN] Minimum transmission periodicity
- [LoRaWAN] LoRaWAN version
- Transmitters calibration
- VOC monitoring-related questions
- Maximum length of the cable on pulse transmitters
- Products warranty duration
- Data Encryption
- TX Pulse wiring
- TX 4-20mA wiring
- [Proprietary Mode] How to change the IP address of the receiver ?
- [Proprietary Mode] Read the total number of Pulses of a Pulse transmitter in BACnet objects
- [LoRaWAN] How to switch from one LoRaWAN network to another ?
- Managing and resetting the index of a Pulse transmitter
- [LoRaWAN] How to change the transmission period of a transmitter in LoRaWAN?
- Compatibility between smart metering transmitters and meters :
- Fixed orange LED on my sensor
- TX contact wiring