Industrial RS485 Modbus to Wi-Fi Converter
Modbus RTU to MQTT Gateway & Datalogger for Your Existing Wi-Fi


MacSync WX1 polls your Modbus RTU meters, PLCs and drives over RS485 and publishes the values to any MQTT broker
No Gateway, No SIM, No New Cable — Just the Wi-Fi You Already Have.
No Gateway, No SIM, No New Cable —
Just the Wi-Fi You Already Have.
MacSync WX1
Explore the highlights

Polls holding and input registers from 20 to 32 slave devices on one RS485 line, on its own schedule.
Sends values to any broker — on-premise or cloud — with TLS on port 8883 and server certificate validation.
Dual-band 802.11 b/g/n/ac Wi-Fi on 2.4 and 5 GHz, WPA2-PSK and WPA3, DHCP or static IP. No gateway, hub or SIM.
Stores up to 30,000 records through a Wi-Fi or server outage and forwards them when the link returns.
A 19 Ah cell where there is no supply, or 9–36 V DC for continuous, high-rate reporting.
A JSON command on the subscribe topic writes a register or coil, or requests a one-time read.
Wi-Fi, broker and register map are set in the Maya app over Bluetooth — no web UI, no AT commands.
Two switchable channels for 4–20 mA, 0–10 V or digital inputs, used in place of RS485 when the instrument has no serial port.
Designed and manufactured in Pune. WPC compliant, RoHS conforming, supported in Indian Standard Time.
In plain terms
What Is a Modbus to MQTT Converter?
The short answer
A Modbus to MQTT converter is a device that acts as a Modbus RTU master on an RS485 line, polls the registers of existing equipment such as energy meters, PLCs and drives, and publishes the values as messages to an MQTT broker over the network. This one uses the Wi-Fi your site already has, so there is no gateway to install, no SIM and no new cable back to a control room.
Modbus role
- RTU master
Modbus role on one RS485 port
- 20–32
Slave devices on the line
- 125
Consecutive registers per read
Publishes to
- MQTT
Any MQTT broker
- HTTPS
HTTP and HTTPS endpoints
- AWS · Azure
IoT Core, IoT Hub, private or on-premise
Wi-Fi
- 2.4 / 5 GHz
IEEE 802.11 b/g/n/ac
- 2.4 / 5 GHz
Dual-band
- WPA2 / WPA3
With DHCP or static IP
Security
- TLS
Encrypted MQTT
- Port 8883
With server certificate validation
- AES-256
Data encryption
Logging
- 30,000
Records stored through an outage
- 3 modes
Time, threshold or sampling based
- 2 triggers
Thresholds with minimum and maximum limits
Power
- 19 Ah
Battery variant, Li-SOCl₂ cell
- ~2.5 years
Estimated life at 15-minute uploads
- 9–36 V
DC-powered variant

MacSync WX1
The MacSync WX1 is not a serial server. A serial server passes raw serial bytes across the network and still needs a SCADA or PLC master to poll through it; the WX1 does the polling itself, on its own schedule, and delivers finished values to your broker.
Modbus RTU master on one RS485 port, reading holding and input registers from 20 to 32 slave devices on the line.
Any MQTT broker, plus HTTP and HTTPS endpoints — on-premise, private cloud, AWS IoT Core or Azure IoT Hub.
IEEE 802.11 b/g/n/ac, dual-band 2.4 GHz and 5 GHz, WPA2-PSK and WPA3, DHCP or static IP.
TLS-encrypted MQTT on port 8883, with server certificate validation and username and password authentication. Client certificates are a firmware option on orders of 1,000 devices.
Store-and-forward buffering of 30,000 records through Wi-Fi or server outages.
Battery variant on a 19 Ah cell, estimated at about 2.5 years on 15-minute uploads, or a 9–36 V DC variant, in an IP65 enclosure with an IP67 option.
It is often searched for as an RS485 to Wi-Fi converter or a Modbus Wi-Fi gateway. If the Wi-Fi or the server goes down, it stores up to 30,000 records and forwards them when the link returns.
Get a quote
Need a quote for the MacSync WX1?
Tell us how many you need and where they are going. A product engineer replies within one working day with availability, lead time and the right variant for your site.
- Reply within one working day
- Designed and built in Pune, India
- WPC compliant, RoHS conformant
Downloads
Everything You Need to Get Building
Datasheets, drawings, firmware, and tools — all in one place.
Engineered for
Built for the Plant Floor, Not the Server Rack
A sealed glass-filled nylon enclosure rated IP65, with an IP67 option, for mounting beside the equipment rather than inside a panel.

01 / 04
Applications
What are the Applications of the RS485 Modbus to Wi-Fi Converter?

Factory Energy Sub-Metering
Read Modbus energy meters on every feeder and publish kWh, demand and power factor to your dashboard over the plant Wi-Fi, with no cable back to the panel room.
Read case studiesDG Set Monitoring (Genset Controllers, Run Hours): Pull run hours, load and alarms from a generator controller's RS485 port and see every genset on one screen.
HVAC & Chiller Plant (BMS Retrofit, BTU Meters): Bring chillers, AHUs and BTU meters into the building dashboard without rewiring the plant room, using the Wi-Fi already serving the building.
Compressors & Utilities (Compressed Air, Load Hours): Log pressure, load and unload hours and energy from compressor controllers to find the cost of leaks and idle running.
Solar Inverter Rooms (Inverters, String Data): Read string inverters daisy-chained on RS485 and publish generation and fault data to your monitoring platform.
Cold Rooms & Refrigeration (Controllers, Alarms): Collect temperatures, defrost status and alarms from refrigeration controllers, buffered through any Wi-Fi dropout.
Water & Effluent Plants (Flow Meters, Totalisers): Publish flow rate and totaliser values from Modbus flow meters across a treatment plant covered by site Wi-Fi.
Data Centres & Server Rooms (Power Meters, On-Premise): Log power and energy from rack and feeder meters to a broker inside your own network, with nothing sent off site.
Machine Monitoring (PLCs & Drives, OEE): Read status and counters from PLCs and variable frequency drives to track uptime without touching the control program.
Commercial Buildings (Tenant Metering, Billing): Meter each floor or tenant from existing Modbus meters and send billing-grade readings on a fixed interval.
Warehouses & Logistics (Indoor Sites, No Cabling): Monitor power and equipment across a large indoor site using the Wi-Fi that already covers the floor.
Process Instruments (4–20 mA, 0–10 V): Switch the unit to analog mode to read pressure, level and flow transmitters that have no serial port.
Laboratories & Pharma (Local Data, Audit Trail): Keep equipment and utility data on a local server for plants that need data ownership and a complete record.
Browse all 13 applications
01 / 13
Works with
Modbus RTU to MQTT, Without a Gateway or a Polling Application
A Modbus master that polls your equipment and publishes straight to your broker over the Wi-Fi you already run.A Modbus master that polls your equipment and publishes straight to your broker over the Wi-Fi you already run.


Where it fits
From Meter Rooms to Machine Halls, Wherever Wi-Fi Already Reaches
Energy & Utility Metering
Modbus energy, water and gas meters published to a dashboard or billing system, feeder by feeder and tenant by tenant.

Plant Equipment & Machines
PLCs, drives, compressors and generator controllers read over RS485 without changing a line of control code.

Buildings & Cold Storage
Chillers, AHUs, BTU meters and refrigeration controllers brought into one platform, using the building's own network.


Energy & Utility Metering
Modbus energy, water and gas meters published to a dashboard or billing system, feeder by feeder and tenant by tenant.

Plant Equipment & Machines
PLCs, drives, compressors and generator controllers read over RS485 without changing a line of control code.

Buildings & Cold Storage
Chillers, AHUs, BTU meters and refrigeration controllers brought into one platform, using the building's own network.
Why Macnman
Do You Need a Gateway to Send Modbus Data over Wi-Fi?
No. The MacSync WX1 joins your existing Wi-Fi as an ordinary client and connects to the broker directly, so there is no gateway, hub or SIM between the meter and your platform. It polls the Modbus registers itself, publishes the values over MQTT or HTTPS, and buffers up to 30,000 records if the network or the server is unavailable.


Free planning tools
Size your deployment before you order the hardware
Free engineering calculators for coverage, range and battery life — built on measurements from our own deployments rather than textbook models, which is why the answers tend to be smaller and a good deal more useful. Nothing here quotes a range we have not actually achieved.
No sign-up, no email, nothing to install. More on the way for Wi-Fi and BLE.
Hardware
IP65 Enclosure for the Plant Floor, Battery or DC Powered
The MacSync WX1 is housed in glass-filled nylon rated IP65, with an IP67 option, and operates from −40 °C to +80 °C, so it mounts beside the equipment rather than inside a panel. The battery variant runs on a 19 Ah industrial cell where there is Wi-Fi but no spare supply; the powered variant takes 9–36 V DC for continuous reporting.

Ready to put your Modbus equipment online? MacSync makes it effortless.
At a glance
MacSync WX1 — Key Specifications

RTU master
Modbus
1 × RS485 · 20 to 32 devices
MQTT · HTTPS
Protocols
TLS / SSL encrypted
2.4 / 5 GHz
Wi-Fi
dual-band · IEEE 802.11 b/g/n/ac
30,000
Onboard memory
records, store-and-forward
19 Ah
Power
battery, or 9–36 V DC
IP65
Ingress
IP67 optional variant
Features
Everything Built into One Modbus to Wi-Fi Converter
Threshold Alerts
Two triggers publish immediately when a value leaves its limits.
Collects several readings and sends them as one upload to save power.
Works on Your Existing Wi-Fi
No gateway, no hub and no SIM. The converter joins the 2.4 or 5 GHz network already on site, on 802.11 b/g/n/ac.
Modbus RTU Master
Polls holding and input registers from 20 to 32 slave devices on one RS485 line.
Battery or 9–36 V DC
A 19 Ah cell where there is no supply, or DC power for continuous high-rate reporting.
TLS-Secured MQTT
Encrypted on port 8883 with server certificate validation, plus WPA2-PSK and WPA3 on the Wi-Fi side.
30,000 Records On-Board
Built-in memory keeps logging through Wi-Fi and server outages, then forwards the backlog.
Analog Inputs Included
Two switchable channels for 4–20 mA, 0–10 V or digital inputs, used in place of RS485 when needed.
Any Broker, Any Platform
MQTT, HTTP and HTTPS to on-premise servers, private cloud, AWS IoT Core or Azure IoT Hub.
Capabilities
On-Board Memory That Never Loses a Reading
Built-in memory stores 30,000 records through a Wi-Fi or server outage and forwards them automatically when the connection returns.

Architecture
Modbus to MQTT over Wi-Fi — Network Architecture


Why it matters
Your Meters Already Speak Modbus. Now They Can Reach the Cloud.
Most plants have years of Modbus equipment and good Wi-Fi, with nothing connecting the two. This closes that gap without a gateway or a rewiring job.
Why it matters
Most plants have years of Modbus equipment and good Wi-Fi, with nothing connecting the two. This closes that gap without a gateway or a rewiring job.
No new infrastructure
It joins the Wi-Fi you already run. There is no gateway to site, no SIM to manage and no cable to pull back to the control room.
Data in the form you want
Finished values arrive on an MQTT topic or HTTPS endpoint, ready for a dashboard, historian or analytics tool.
Keeps IT comfortable
TLS encryption, outbound-only connections and a broker of your choosing, including one that never leaves the site.
Gaps do not become holes
A Wi-Fi dropout or a server restart is buffered on the device and forwarded later, so the history stays complete.
How it works
How Does a Modbus to MQTT Converter Work?
Step 1 of 5
Wire RS485 to the equipment
Two wires, A and B, from the meter, PLC or drive to the converter. 20 to 32 devices can share the line, each with its own slave ID.
Map the registers in the app
In the Maya app, add each value: slave ID, function code, register address and data type. Check shows the live reading.
Connect to Wi-Fi and the broker
Pick the network, enter the broker host, port and topic, and turn on TLS. A test upload confirms the path end to end.
Values go out over MQTT
The converter polls on its schedule and publishes to your topic — or stores the readings if the link is down.
Your platform takes it from there
Dashboards, alerts and analytics run on the broker's data, and commands sent back can write a register.
What lands on your broker
What Does the Converter Publish to Your MQTT Broker?
Integrators ask this first, so here it is. The converter publishes each set of readings to the topic you choose and listens on a second topic for commands. Field names are the parameter names you give each register in the Maya app.
Reading — published to macsync/device001/data
{
"deviceId": "device001",
"timestamp": "2026-01-15T10:15:00Z",
"Energy_Meter_KW": 42.7,
"Voltage_L1": 231.4,
"Current_L1": 61.8,
"Frequency_Hz": 49.98
}Example message: one value per configured Modbus field, under the name you gave it.
Command — sent to macsync/device001/cmd
{
"slaveId": 1,
"numberofreg": 1,
"address": 0,
"value": 223
}Writes the value 223 to register 0 on slave 1. Coil writes and one-time register reads use the same topic.
The reading is an illustrative example: topics and field names are yours to set. The command format is the one in the remote configuration guide. Ask us for the current payload reference before writing a parser.

Reporting
Three Ways to Report, Chosen by What You Are Watching For.
A reading published on a fixed interval. Predictable data for trends, billing and energy reports.
Note: Shorter intervals suit the DC-powered variant.
Two configurable triggers watch a chosen field and publish immediately when the value leaves its minimum and maximum limits. Note: Use it for alarms: over-current, low level, high temperature.
The device takes several readings at a set gap, stores them, and sends them together as one upload. Note: Keeps the detail while cutting Wi-Fi wake-ups, which is what extends battery life.
Cloud & LNS
Publishes to Any MQTT Broker or HTTPS Endpoint
On-Premise, Private Cloud, AWS IoT Core & Azure IoT Hub
MacSync WX1 converters publish Modbus values to any standard MQTT broker or HTTPS endpoint — a server on your own network, a private cloud, AWS IoT Core or Azure IoT Hub — with TLS encryption and no vendor platform in between.


Installation
On the network in minutes, with nothing new to install.

Mount and wire
Fix the unit to a wall or pole near the equipment and connect RS485 A to A and B to B.

Map the registers
Add each field in the Maya app and press Check to confirm the value against the meter's display.

Join Wi-Fi and the broker
Select the network, enter the MQTT host, port and topics, and enable TLS for an encrypted connection.

Test before you leave
Send Uplink checks connectivity, reports Wi-Fi signal strength and confirms the message reached the broker.
Range & reliability
Reliable Wi-Fi Connectivity, Built for Industrial Sites
Dependable 2.4 / 5 GHz Wi-Fi with 30,000-record on-board buffering through outages
The MacSync WX1 is a dual-band 802.11 b/g/n/ac Wi-Fi device that works on both 2.4 GHz and 5 GHz, reaching up to about 100 m indoors from an access point depending on the building. The Maya app reports signal strength at the mounting point before you commit, and anything missed during a dropout is stored and forwarded.

Two devices, one search term
RS485 to Wi-Fi Converter: Modbus to MQTT Gateway or Serial Server?
Both get sold as an "RS485 to Wi-Fi converter", and they do opposite jobs. Picking the wrong one is the most common mistake in this category, so here is the difference.
| Compare | Modbus to MQTT converter — MacSync WX1 | RS485 to Wi-Fi serial server |
|---|---|---|
| What it does | Polls Modbus registers itself and publishes the values | Passes raw serial bytes across the network unchanged |
| Who is the Modbus master | The converter | Your SCADA, PLC or PC software |
| What arrives at the other end | Named values on an MQTT topic or HTTPS endpoint | A Modbus RTU or Modbus TCP stream on a network port |
| Needs a master polling it | No — it reports on its own schedule | Yes — the master must stay connected and keep polling |
| If the Wi-Fi drops | Stores up to 30,000 records and forwards them later | Polls time out and that period's data is lost |
| Typical power | 19 Ah battery or 9–36 V DC | DC supply only |
| Choose it for | Dashboards, MQTT brokers, energy analytics, cloud and on-premise platforms | An existing SCADA or HMI that already speaks Modbus TCP |
If you need a virtual COM port or a Modbus TCP connection for an existing SCADA master, a serial server is the right tool and the MacSync WX1 is not. If you want readings delivered to a broker or platform without building a polling application, this is the device.
Battery life
How Long Does the Battery Last on Wi-Fi?
It depends almost entirely on how often the converter connects. These are estimates from the model behind the Macnman Wi-Fi battery life calculator, for the battery variant on its 19 Ah cell with one Modbus read and one TLS connection per upload.
| Upload interval | DHCP address | Static IP address |
|---|---|---|
| Every 5 minutes | About 0.9 years | About 1.4 years |
| Every 10 minutes | About 1.7 years | About 2.5 years |
| Every 15 minutes | About 2.5 years | About 3.5 years |
| Every 30 minutes | About 4.3 years | About 5.7 years |
| Every hour | About 6.7 years | About 8.2 years |
| 5-minute readings, uploaded hourly (sampling mode) | About 5.0 years | About 5.8 years |
Estimated, not guaranteed: a sensor powered from the converter and a weak Wi-Fi signal both shorten battery life. Sampling mode stores readings and sends them together, so the converter pays for one Wi-Fi connection instead of twelve. For reporting faster than every few minutes, use the 9–36 V DC variant. Try your own settings in the Wi-Fi battery life calculator under Network Planning Tools.
Choosing a network
Wi-Fi or LoRaWAN for Your Modbus Data?
Macnman builds this converter for both networks, so the honest answer depends on where the equipment sits and how much data you need from it.
| Compare | MacSync WX1 — Wi-Fi | MacSync LX1 — LoRaWAN |
|---|---|---|
| Network it needs | The Wi-Fi already on site | A LoRaWAN gateway |
| Reach | Up to about 100 m indoors from an access point | Kilometres from a gateway |
| Data per message | Full messages — many registers at once | 51 to 222 bytes per uplink |
| Route to your platform | Direct, over MQTT or HTTPS | Through a LoRaWAN network server |
| Remote writes | Commands arrive on an MQTT topic | Downlinks wait for the next uplink in Class A |
| Choose it when | Equipment is inside Wi-Fi coverage and you want rich or frequent data | Equipment is spread across a large site or beyond Wi-Fi reach |
Inside a plant, building or campus with good Wi-Fi, the WX1 is simpler: no gateway and no network server. Across a wide site, outdoors, or where Wi-Fi does not reach, the LoRaWAN version covers the distance with one gateway.
FAQ
Frequently asked questions
Wire the equipment's RS485 A and B terminals to the MacSync WX1, then open the Maya app over Bluetooth. Add each value as a field: slave ID, function code, register address, data type and how many registers to read. Join the device to your Wi-Fi, enter the broker's host and port, and set a publish topic such as macsync/device001/data. From then on the converter polls the registers on its own schedule and publishes the values to that topic. The Check button shows a live reading for each field, so the register map can be verified before you leave site.
Each upload is published to the topic you set, for example macsync/device001/data, and carries the values of the fields you configured under the parameter names you gave them in the Maya app, such as Energy_Meter_KW. Commands travel the other way as JSON on the subscribe topic: a message with the slave ID, register address and value writes a register on the connected equipment. The sample on this page shows an example of both; ask us for the current payload reference before you write a parser.
No, and the difference matters. A serial server is a transparent bridge: it passes raw serial bytes across the network and relies on a SCADA or PLC master to do the polling through it. The MacSync WX1 is the Modbus master itself. It polls your equipment, converts the registers into values and publishes them to a broker or HTTPS endpoint. If you need a virtual COM port or Modbus TCP for an existing SCADA system, buy a serial server. If you want data delivered to a platform without writing a polling application, this is the right device.
MQTT always runs through a broker, and the MacSync WX1 works with any standard one, such as Mosquitto, EMQX or HiveMQ, whether it runs in your own server room or in the cloud. You enter a hostname or an IP address, so a local broker on the plant network works exactly like a hosted one. The datasheet also lists AWS IoT Core, Microsoft Azure IoT Hub and Google Cloud, alongside on-premise servers, private cloud, REST APIs, webhooks, SCADA and BMS platforms. Where there is no broker, the device can post to an HTTP or HTTPS endpoint instead. The standard firmware signs in with a username and password, so a platform that expects a client certificate on every device, as AWS IoT Core does by default, needs the client-certificate firmware option, which is offered on orders of 1,000 devices or more.
Yes. Turn on TLS in the MQTT settings and use port 8883 for an encrypted connection, with a toggle to validate the broker's server certificate. Plain MQTT on port 1883 remains available for a closed local network. In the standard firmware, authentication is by username and password. Client-certificate authentication (mutual TLS) and a change to the MQTT QoS level are firmware customisations, available on orders of 1,000 devices or more. On the Wi-Fi side the device supports WPA2-PSK and WPA3, and firmware is protected by secure boot and signed over-the-air updates. The converter only makes outbound connections to your broker, so no inbound ports need opening on the plant firewall.
Yes, as a firmware customisation. The standard MacSync WX1 firmware signs in with a username and password over TLS and validates the broker's server certificate. If your platform needs a client certificate on each device (mutual TLS), or a specific MQTT QoS level, we build that into the firmware for orders of 1,000 devices or more. Tell us the broker and its authentication requirements when you enquire.
Nothing is lost. The MacSync WX1 keeps polling the Modbus equipment and stores the readings in onboard memory, up to 30,000 records, then forwards them once the connection returns. At one record every five minutes that is roughly 100 days of cover. That store-and-forward behaviour is one of the practical differences from a transparent serial server, where a dropped link simply means the master's polls time out and that period is missing from your history.
Yes to both bands. The MacSync WX1 is dual-band and supports IEEE 802.11 b/g/n/ac, so it joins Wi-Fi 4 and Wi-Fi 5 access points, and connects to Wi-Fi 6 access points as an 802.11ac client since those remain backward compatible. Many low-cost RS485 to Wi-Fi converters are 2.4 GHz only. In a plant, 2.4 GHz usually reaches further and passes through walls and machinery better, while 5 GHz has more clean channels where access points are close by. The battery variant uses Wi-Fi Power Save Mode between uploads to cut idle power. The Maya app scans for networks and shows signal strength for each, and a hidden network can be added manually with the band chosen explicitly.
The supported security modes are WPA2-PSK and WPA3, with DHCP or a static IP address. If your corporate network uses 802.1X enterprise authentication with per-user certificates, ask us before ordering. In practice most IT teams place devices like this on a separate IoT network or VLAN with its own passphrase, which also keeps plant-floor equipment away from office systems. The converter needs only an outbound connection to the broker.
For scheduled polling, function code 03 (Read Holding Registers) and 04 (Read Input Registers). Values can be read as INT16, UINT16, INT32 or FLOAT32, with either word order for the 32-bit types, and several consecutive registers can be read as one group. Each field has its own slave ID, so one RS485 line can carry multiple devices. Serial settings cover the common baud rates up to 115200 bps with none, even or odd parity.
Yes. The converter subscribes to a command topic, and a JSON message containing the slave ID, register address and value writes a register on the connected equipment. Coils can be written the same way, and a one-time read of any register can be requested on demand. Because the device holds an MQTT connection rather than waiting for a radio window, commands reach a powered unit promptly. On the battery variant, commands are picked up when the device next wakes.
It can, and the upload interval decides how many. A Wi-Fi connection costs far more energy than a LoRaWAN transmission, so the MacSync WX1-BO sleeps at around 100 µA between readings, wakes briefly to poll and transmit, and goes back to sleep. On the 19 Ah cell, the Macnman Wi-Fi battery life calculator estimates about 0.9 years at 5-minute uploads, 2.5 years at 15 minutes, 4.3 years at 30 minutes and 6.7 years at hourly uploads, with DHCP, a TLS connection and one Modbus read each time. A static IP shortens every connection and raises those figures to about 3.5 years at 15 minutes and 8.2 years hourly. Sampling mode helps more: reading every 5 minutes but uploading the 12 readings once an hour gives about 5 years. The device also supports Wi-Fi Power Save Mode on any access point. These are estimates; a sensor powered from the converter and a weak Wi-Fi signal both shorten them. For reporting every few seconds, choose the 9–36 V DC variant, and where battery life matters most, the LoRaWAN version of this converter lasts longer on the same cell.
No. The converter joins your existing Wi-Fi as an ordinary client and talks to the broker directly. There is no gateway or hub to buy, no SIM and no monthly data plan per device. That makes it the simplest option wherever the equipment already sits inside Wi-Fi coverage.
Yes. The broker can be a machine on your local network, entered by IP address, so readings never have to leave the site. The device supports on-premise servers and private cloud as well as public platforms, which suits plants that need local data ownership or have no outbound internet access from the production network.
Choose Wi-Fi when the equipment is inside reliable Wi-Fi coverage and you want frequent or detailed data: there is no gateway, messages can carry many registers at once, and commands arrive quickly. Choose LoRaWAN when the equipment is spread across a large site, outdoors, or beyond the reach of your access points: one gateway covers kilometres, at the cost of smaller messages and slower updates. Macnman builds the converter for both, as the MacSync WX1 for Wi-Fi and the MacSync LX1 for LoRaWAN.
Yes, with one limit you should know about. The MacSync WX1 has two switchable channels, each set to 4–20 mA, 0–10 V or digital input, with 12-bit resolution, but the RS485 and analog inputs share the same terminals, so the device runs in either RS485 mode or analog mode, not both at once. A site with a Modbus meter and an analog transmitter side by side needs two units, or a transmitter with a Modbus output.
From an Android phone, using the Maya app over Bluetooth, with no programming and no web interface to find. The app scans for Wi-Fi networks, takes the MQTT settings and the Modbus field list, and has a Send Uplink test that checks network connectivity, measures Wi-Fi signal strength and confirms that a message reached the broker. Settings can be changed later from the server by sending JSON commands.
Yes. Macnman Technologies designs and manufactures the MacSync WX1 in Pune, Maharashtra. It is WPC compliant and conforms to the RoHS directive, and support comes directly from the engineering team in Indian Standard Time.
Modbus RTU and Modbus TCP are the same request-and-response protocol on different wires: a master asks and a slave answers, over RS485 for RTU or over a network for TCP. MQTT works differently. A device publishes a message to a broker whenever it has data, and any number of applications can subscribe to it. Converting RTU to TCP only changes the cable, and something still has to keep polling. Converting RTU to MQTT changes who starts the conversation and where the data can go, which is why it suits dashboards and cloud platforms.
One RS485 line carries 20 to 32 Modbus devices, 32 being the standard RS485 limit without a repeater. Each value you configure carries its own slave ID, in the Modbus range of 1 to 247, and a single read can cover up to 125 consecutive registers. All devices on the line must share the same baud rate and parity. Send us your device list and register map and we will confirm the configuration.
Six things. The device joins Wi-Fi as an ordinary client using WPA2-PSK or WPA3, on 2.4 or 5 GHz. It takes an address by DHCP or a static IP. It makes one outbound connection to the broker, on port 8883 for TLS or 1883 for plain MQTT, so no inbound port or port-forward is needed. Traffic can be encrypted with TLS and the broker's certificate validated. It signs in to the broker with a username and password; client-certificate authentication is a firmware option on orders of 1,000 devices or more. And the broker can sit inside your own network, so no data has to leave the site. Most IT teams place it on a separate IoT network or VLAN.
More from Macnman
What Else Do We Build at Macnman
Let‘s make it easy - reach out now!
Let’s bring it to life!
Let‘s Make it Easy
Reach Out Now
We are always ready
to help and
answer your
questions
Call
+91 7972856163
+91 9096830856
Location
Office-15 Bibwewadi, Pune, Maharashtra 411037
Get in Touch
Define your goals and all to value your time
Use of this website and purchase of Macnman products are subject to our Terms and Conditions.




