Combining RS485 with Wifi TCP/IP. Buy converter or ???

Communication and networks are not my forte and I'm still wrapping my head around most of this.
We've made a sensor that can be communicated with in 3 ways: serial cable (4pins, Rx, Tx), Modbus RS485 cable, and wifi. We have a collaborating partner that's asking for Modbus TCP/IP via ethernet cable.
Should we buy a gateway (like the ones from Moxa) that converts RS485 to TCP?
Or is there a way to combine what's already written for wifi with an ethernet cable/port?
Any other ideas
 
The most common solution is to use a Modbus/TCP to Modbus RTU gateway. The added benefit of using a gateway is that, depending on the gateway, other communication protocols may be included as well. For example, ICC's ETH-1000 could be used to bring your sensor's data in via Modbus RTU and expose it to Modbus/TCP, BACnet/IP, EtherNet/IP, PROFINET, and any other supported protocol by loading a single configuration onto the unit.
http://www.iccdesigns.com/millennium-series/10-eth-1000.html

Another option is integrating ICC's "gateway on a chip" called the PicoPort, or the upcoming Ethernet version the PicoPort-E, directly onto your sensor's PCB. The core concept of these communication chips are the same as an external gateway. One port communicates Modbus RTU to your sensor's CPU and the other port(s) communicate to a customer's network. The PicoPort converts between two serial protocols, but the upcoming PicoPort-E can convert serial to serial as well as serial to Ethernet.
http://www.iccdesigns.com/single-chip-modules/30-picoport.html

If your sensor already supports Modbus/TCP communication via WiFi, then a customer could use a wireless access point or wireless router to convert the WiFi signal to Ethernet. However, you may find that many customers that require Modbus/TCP are uncomfortable using WiFi in this manner, whether it be due to reliability issues, complexity, etc.

Full Disclaimer: In case it's not apparent I do work for ICC. I am the product specialist for the products mentioned above. If you have any questions on those products, please feel free to email me directly or submit a support ticket on our website.
 
The most common solution is to use a Modbus/TCP to Modbus RTU gateway. The added benefit of using a gateway is that, depending on the gateway, other communication protocols may be included as well. For example, ICC's ETH-1000 could be used to bring your sensor's data in via Modbus RTU and expose it to Modbus/TCP, BACnet/IP, EtherNet/IP, PROFINET, and any other supported protocol by loading a single configuration onto the unit.
http://www.iccdesigns.com/millennium-series/10-eth-1000.html

Another option is integrating ICC's "gateway on a chip" called the PicoPort, or the upcoming Ethernet version the PicoPort-E, directly onto your sensor's PCB. The core concept of these communication chips are the same as an external gateway. One port communicates Modbus RTU to your sensor's CPU and the other port(s) communicate to a customer's network. The PicoPort converts between two serial protocols, but the upcoming PicoPort-E can convert serial to serial as well as serial to Ethernet.
http://www.iccdesigns.com/single-chip-modules/30-picoport.html

If your sensor already supports Modbus/TCP communication via WiFi, then a customer could use a wireless access point or wireless router to convert the WiFi signal to Ethernet. However, you may find that many customers that require Modbus/TCP are uncomfortable using WiFi in this manner, whether it be due to reliability issues, complexity, etc.

Full Disclaimer: In case it's not apparent I do work for ICC. I am the product specialist for the products mentioned above. If you have any questions on those products, please feel free to email me directly or submit a support ticket on our website.
That's great! Thank you for the explanation. It seems the gateway is the fastest and easiest way forward, but integrating the chip would be a natural next step. Also a great point about WiFi, I had never thought about it from the customers' perspective and the reliability/security issues.
 
You could also use this, I used that many times. They work great and reliable (built with automotive electronics specifications) and not expensive.
We can deliver them quite fast.
See: https://www.proconel.com/product/mmtcpbconv-tcp-rs232rs485-ethernet-serial-converter/
Thanks for the link. Most of the gateways I've seen have been around 200-500 (USD or EUR) for the base model and then go up in price with increasing number of ports. Would you say this one is around the same price? Or is it less expensive by an order of magnitude, like less than 100 (USD or EUR)?
 
I just looked and I have 4 pieces MMTCPBCONV220 of the 220 volt power supply version (also works on 230V) on stock.
Can be shipped via UPS quickly if order received before 1200hrs (our local time Rotterdam) because then the UPS guy comes for the daily pickup.
Price ex. works is Euro 240,- a piece.
Good, simple, reliable and quick solution. I use lots of them, work great.
Just send the order to [email protected]
and see our website here: https://cascade.net/
MMTCPBCONV 220.JPG
 
Top