Buy anything from 5,000+ international stores. One checkout price. No surprise fees. Join 2M+ shoppers on Desertcart.
Desertcart purchases this item on your behalf and handles shipping, customs, and support to Tunisia.
Overview This is a RS485 device data acquisitor / IoT gateway designed for industrial environment. It combines multi functions in one, including serial server, Modbus gateway, MQTT gateway, RS485 to JSON, etc. The module features RS485 and Ethernet ports, uses screw terminals for power input, supports 924V wide range power supply. Rail-mount flame-retardant case design, small in size, easy to install. It is suitable for applications like data acquisition, IoT gateway, safety & security IoT, and intelligent instrument monitoring.etc. Specifications 1.Primary Introduction Product Type--- Serial server, Modbus Gateway, MQTT Gateway Basic Function--- Bi-directional transparent data transmission between RS485 and Ethernet Communication interface --- RS485 port x 1, Ethernet port x 1 Power supply --- 9 24V DC screw terminal 2.Communication Ethernet--- common network port, 10 / 100M auto-negotiation RJ45 connector, 2 KV surge protection. Serial port--- RS485. 3.Serial specification Baudrate---300 115200 bps Parity bit--- none, odd, even, mark, space Data bit--- 5 9 bits 4.Software Protocol--- ETHERNET, IP, TCP, UDP, HTTP, ARP, ICMP, DHCP, DNS Configuration--- host, web browser, device management functions library Communication method--- TCP/IP direct communication, VCOM Operating mode--- TCP server, TCP client (coexisting with TCP server), UDP, UDP multicas 5.Environment requirement Operating temperature--- -40℃ 85℃ Storage temperature: -45℃ 125℃ Humidity range--- 5% 95% relative humidity Dimensions --- L x W x H--- 87x 36 x 59 mm Online Document/How to use: //bit.ly/3rWrjyz Package Content RS485 TO ETH (B) x1 Review: I'm working on a personal project with the Modbus functionality. The device I'm working on was tested with the Serial to RS485 dongle and working fine. I added the RS485 to the RJ45 Ethernet Module (waveshare), enabled the Modbus TCP to RTU mode, set the device address, and sent the following command: `modbus 192.168.6.35:2020 -s213 h@13` The "waveshare" is able to transmit data to my device, and my device successfully processes the command responding with the correct Modbus response: [23:50:09][D][uart_debug:114]: >> D5:03:02:08:27:CF:8C However, the "waveshare" device, seems, to either have a defective RX port or can not transmit the response back. I tried modbus_cli and ModbusMechanics. Both fail with the "waveshare" device but work with the USB458 dongle. *Correction*: Looks like it was a subtle bug with the particular Modbus library on my device and/or the device(s). Even though the USB dongle works correctly, another device from a different vendor behaves the same way. Setting 2 stop bits helped. I assume the "waveshare" device would work perfectly with this setup. Sorry for the initial negative review. Review: We have some devices using MODBUS-RTU and have employed these to remotely monitor those devices across our network to the NOC via MODBUS-TCP as a basic gateway. They are compact and easily configured, but lack TLS or any other network security that some networks may require.
| ASIN | B09MBW9WFL |
| Brand | Waveshare |
| Color | RS485 TO ETH (B) |
| Customer Reviews | 4.4 4.4 out of 5 stars (21) |
| Item Weight | 0.01 Kilograms |
| Manufacturer | Waveshare |
| Mfr Part Number | RS485 to ETH RJ45 (B) |
| Model Number | RS485 to ETH RJ45 (B) |
| Unit Count | 1 Count |
Y**V
I'm working on a personal project with the Modbus functionality. The device I'm working on was tested with the Serial to RS485 dongle and working fine. I added the RS485 to the RJ45 Ethernet Module (waveshare), enabled the Modbus TCP to RTU mode, set the device address, and sent the following command: `modbus 192.168.6.35:2020 -s213 h@13` The "waveshare" is able to transmit data to my device, and my device successfully processes the command responding with the correct Modbus response: [23:50:09][D][uart_debug:114]: <<< D5:03:00:0D:00:01:07:DD [23:50:09][D][uart_debug:114]: >>> D5:03:02:08:27:CF:8C However, the "waveshare" device, seems, to either have a defective RX port or can not transmit the response back. I tried modbus_cli and ModbusMechanics. Both fail with the "waveshare" device but work with the USB458 dongle. *Correction*: Looks like it was a subtle bug with the particular Modbus library on my device and/or the device(s). Even though the USB dongle works correctly, another device from a different vendor behaves the same way. Setting 2 stop bits helped. I assume the "waveshare" device would work perfectly with this setup. Sorry for the initial negative review.
J**H
We have some devices using MODBUS-RTU and have employed these to remotely monitor those devices across our network to the NOC via MODBUS-TCP as a basic gateway. They are compact and easily configured, but lack TLS or any other network security that some networks may require.
A**Y
Works great. The web UI is good, so dip switches are required to change baud rate, and you can do all sorts of configuration with the config page. The default addr is 192.168.1.254, it was unfortunate the same as my gateway, so I had to hard wire to it to change the IP address. Other than that, it is very easy to use. I hooked up a thermostat and humidity sensor to it and created an IOT app.
A**1
Allows comms in one direction, no issue.
R**T
Immediately there's one problem, and I don't understand why Chinese manufacturers do this: The IP address is set statically at 192.168.1.254 rather than using DHCP. Even when set to DHCP, it does not properly pull DNS servers from DHCP and has it set statically to 192.168.1.3, which doesn't matter much because it doesn't need DNS, but still. It's such a weird default that the rest of the world does not use. Ethernet devices should start with DHCP, and they should always pull DNS from DHCP unless set statically after DHCP config. After that, everything is excellent. Just beware that the ground plug on top of this is not the same as the negative of the input voltage. Make sure your modbus sensor/device is powered the same way this is powered. Honestly, a great device and exactly what I needed for testing a modbus TCP implementation.
Trustpilot
2 days ago
2 months ago