Moxa MGate Alternative: the Wiman WE62C

No. Wiman is an independent industrial hardware manufacturer based in Chennai. We are not affiliated with, authorised by or endorsed by Moxa Inc., and we neither distribute nor resell their products. Moxa, MGate and NPort are trade marks of Moxa Inc., referenced on this page only descriptively, to identify the products a buyer is comparing against.

Logically and electrically, in many cases yes — but check the details before you order rather than assume them. The WE62C is a bidirectional Modbus TCP ⇄ Modbus RTU converter with one RJ45 LAN port, one RS-485 Modbus port and a separate utility/config port, running from 12–24 V DC. Two things do change. Configuration is done from a browser through the WE62C's built-in web portal. And the enclosure and terminal layout are ours, so check the mechanical fit and the DIN-rail space — or send us a photo of the panel and we will check it for you. On addressing: send us the operating mode you plan to run and your existing point map, and we will confirm in writing how slave IDs and register addresses will present to your SCADA before you commit to the swap.

The WE62C has a transparent RS-232/RS-485 mode alongside its two Modbus conversion modes, but we do not publish a Real-COM-style Windows driver that maps a remote serial port to a local COM number, and we publish no driver stack for Linux, macOS or legacy UNIX. If your application must see a local COM port, a serial device server from a vendor that ships and maintains that driver stack is the correct choice, and we will tell you so on the call rather than sell you the wrong box.

We do not publish a concurrent-client figure on the WE62C brief, and we are not going to invent one for a comparison page. For reference, Moxa publishes up to 16 simultaneous Modbus TCP masters on the MGate MB3180/MB3280/MB3480 — we simply have not published an equivalent figure, and we would rather say that than match it with a number we have not measured. Send us your poll architecture — how many masters, poll interval, registers per poll, and whether writes are involved — and we will confirm against the firmware build you would actually receive. If the answer is not good enough for your application, we will say that too.

It depends on how the two masters talk, and it is worth being precise about it. If both are Modbus RTU sharing one RS-485 bus, that is a bus-arbitration problem rather than a protocol-conversion one, and it needs the WT20C: two independent Modbus RTU masters and one downstream slave on 3 × RS-485 half-duplex ports (two masters, one slave), arbitrated transparently at under 50 ms per master query, with inbuilt CRC-16 error correction. Baud is 2400–115200 bps set per port, power is 12–24 V DC with reverse-polarity protection, and it operates from −20 to +70 °C. If instead both masters can speak Modbus TCP, the answer may be a TCP gateway that supports multiple simultaneous TCP masters — including imported gateways that publish a supported client count for this case. Tell us which situation you are in and we will point you at the right one.

Yes, and it is a routine request here rather than an exception — non-standard register maps, a meter that bends the Modbus spec, a byte order your historian insists on, a site-specific uplink format, your branding on the label and in the firmware identity. We scope it, quote it and give you a date on a call. To be clear, we are only stating what we will do; we make no claim about what any other manufacturer will or will not agree to.

For standard WE62C and WT20C configurations we build in Chennai and hold finished stock, so we quote against real inventory and commit to a dispatch date. Customised firmware or private-label builds carry a scoped lead time that we put in writing before you raise the purchase order. For phased rollouts we can allocate production capacity and buffer stock against your forecast. Component markets do move — the 2025-26 memory shortage affected manufacturers across the industry, ourselves included — and when it affects a date you will hear it directly from us.

It logs, and it is configured like a networked device rather than a dumb adaptor. The inbuilt data logger stores readings through a link outage and forwards them on reconnect, and configuration is through a built-in web portal with server-IP commands and OTA firmware updates. It is a protocol converter, not an edge client: it does not publish to MQTT or a cloud API. If you need that, it is one of our gateways you want, and we will tell you so.

The converters are manufactured at our Chennai facility, so we can support Make in India and local-content documentation in a tender submission. Send us the exact clause wording before you bid and we will confirm in writing whether we meet it, including when we do not. Whether any particular imported product qualifies under a given clause is a question for that supplier and the tender authority, not one for us to answer on their behalf.

Yes, and we would prefer you did. Start with the free WIMNET Modbus Scanner to confirm slave IDs, register ranges and byte order on your existing bus, and use the browser-based hex converter to check how your meter encodes floats. If the register map still looks doubtful after that, send us a capture and we will read it with you. For qualifying projects we can arrange an evaluation unit — ask on the enquiry form.