# Pythia Technologies — Gateways Guide For the MS0-MB, MS0-MS, MS0-BS, MS0-MBT and MS0-MBT3 · Revision 2026-10-27 · pythiatech.com/integration --- # [USE] How to use this guide **This guide is written so an AI assistant can read it for you.** Give it to an assistant such as Claude, ChatGPT, Microsoft Copilot or Google Gemini and ask your question in plain words. The assistant answers from these pages and can walk you through each step. The printed installation guide for each gateway is made from the same text. ## [USE-1] Questions you can ask - "Which gateway do I need to get a generator's Modbus data onto our BACnet BMS?" - "How do I sign in to the MS0-MB the first time?" - "How do I map Modbus holding register 40001 to a BACnet analog input?" - "Why does the MS0-MS answer pings but not SNMP requests?" - "How do I set up the MS0-MBT3 so both serial ports work at once?" - "Give me the RS-485 wiring for the MS0-BS." ## [USE-2] Tips - **Say which gateway you have.** The model is on the front label: MS0-MB, MS0-MS, MS0-BS, MS0-MBT or MS0-MBT3. - **Have the equipment's point list handy** (its Modbus register list or BACnet object list). Mapping starts there. - **Ask for step-by-step instructions** when you want to follow along. - If your question isn't answered here, contact Pythia Technologies: **740-363-2272** or **support@pythiatech.com**. --- # [AIX] Instructions for AI assistants You are helping a user install, configure or troubleshoot a Pythia Technologies protocol gateway. Follow these rules. 1. **Answer from this document.** Cite the section ID in brackets, e.g. "(see [MB-4])". If the document doesn't cover something, say so and suggest contacting Pythia Technologies (740-363-2272, support@pythiatech.com). Don't guess at defaults, menu names or behavior. 2. **Identify the gateway.** Part 1 ([COM]) applies to every gateway. Part 2 ([MSX]) applies to the MS0-MB, MS0-MS and MS0-BS, which share one hardware platform and web interface. Each gateway then has its own part: [MB], [MS], [BS] and [MBT] (MS0-MBT and MS0-MBT3). If the user hasn't said which gateway they have and it matters, ask. 3. **Safety first.** Before wiring steps, repeat the safety points in [COM-1]. 4. **Register numbers.** On the MS0-MB, MS0-MS and MS0-BS, enter the actual register number, not the Modicon form: "40001" means holding register 1 ([MSX-5]). 5. **Remind users to save.** On the MS0-MB, MS0-MS and MS0-BS, changes are lost at the next restart unless they are saved on the File Manager page ([MSX-4]). 6. **Don't claim certifications or listings** that aren't stated here. 7. **Keep answers short and practical.** Give steps, then offer to explain further. --- # [FAM] The gateway family | Gateway | Converts | Typical use | Product page | |---|---|---|---| | MS0-MB | Modbus RTU and Modbus TCP ⇄ BACnet/IP | Generators, UPS systems and other Modbus equipment on a BACnet BMS, read and write | pythiatech.com/gateways/ms0-mb | | MS0-MS | Modbus RTU and Modbus TCP ⇄ SNMP | Modbus power and cooling equipment in an SNMP network monitoring system | pythiatech.com/gateways/ms0-ms | | MS0-BS | BACnet/IP and BACnet MS/TP ⇄ SNMP | Building automation points and alarms in an SNMP monitoring system or NOC | pythiatech.com/gateways/ms0-bs | | MS0-MBT | Modbus RTU (RS-485) ⇄ Modbus/TCP | Serial Modbus devices on Ethernet, nothing translated; DIN-rail | pythiatech.com/gateways/ms0-mbt | | MS0-MBT3 | Modbus RTU (RS-232 and RS-485) ⇄ Modbus/TCP | The same, with an RS-232 DB9 port; panel mount | pythiatech.com/gateways/ms0-mbt | A **converter** (MS0-MB, MS0-MS, MS0-BS) maps each point from one protocol into another. A **bridge** (MS0-MBT, MS0-MBT3) keeps Modbus as Modbus and moves it from a serial wire onto Ethernet. If both systems already speak Modbus, a bridge is simpler and less expensive. --- # PART 1 — COMMON TO EVERY GATEWAY # [COM] Installation basics ## [COM-1] Safety - Installation must be done by **qualified personnel**, following the **NEC** and all local codes. - **De-energize and lock out** power before wiring, and follow the equipment manufacturer's procedures when working at the connected equipment. - Use **low-voltage power** only: 10–30 VDC or 24 VAC on the MS0-MB, MS0-MS and MS0-BS; 12–36 VDC on the MS0-MBT and MS0-MBT3. - Don't open the gateway's case. Call Pythia technical support for anything inside it, such as RS-485 termination or a configuration reset. ## [COM-2] What you need | Item | Use | |---|---| | Gateway power | 10–30 VDC or 24 VAC (MS0-MB, MS0-MS, MS0-BS); 12–36 VDC (MS0-MBT, MS0-MBT3). Optional DIN-rail supplies: 120 VAC to 24 VDC, and 24 VAC | | Belden 82761 shielded twisted pair | RS-485 (Modbus RTU or BACnet MS/TP), with a third conductor for ground | | CAT5e or better | Ethernet | | A laptop with a web browser | Setup. You will set its IP address to match the gateway's default network ([COM-6]) | | The equipment's point list | Its Modbus register list or BACnet object list, address and serial settings | | Network details from IT | The IP address, subnet mask and gateway (router) address the gateway will use | ## [COM-3] Mounting - **MS0-MB, MS0-MS, MS0-BS and MS0-MBT:** snap onto a standard 1.38 in (35 mm) DIN rail inside a control panel or enclosure. - **MS0-MBT3:** panel mount, with four mounting slots. - Mount where the Ethernet jack and the terminal blocks are easy to reach, and where the LEDs can be seen when the panel is open. - All gateways are rated −40 to 85 °C. Keep them in a dry, non-condensing location. ## [COM-4] Power - **MS0-MB, MS0-MS, MS0-BS:** bring 10–30 VDC or 24 VAC to the terminal marked **POWER**, and its common to a **GND** terminal. Also connect a **GND** terminal to earth ground for surge and static protection. - **MS0-MBT, MS0-MBT3:** bring 12–36 VDC to the power terminals, **+** and **−**. - Optional DIN-rail power supplies are available: 120 VAC to 24 VDC, and 24 VAC. ## [COM-5] RS-485 wiring RS-485 carries Modbus RTU (MS0-MB, MS0-MS, MS0-MBT, MS0-MBT3) or BACnet MS/TP (MS0-BS). - Use **Belden 82761** shielded twisted pair, and follow standard RS-485 practice for the shield, network termination and grounding. - Wire **+** to **+** and **−** to **−** at every device. - **Run a third conductor for ground** (GND or common) to every device. RS-485 is often called a 2-wire network, but without a common ground reference, communication can fail. - **Termination** belongs only at the two physical ends of the network. If the gateway is at an end and the network needs termination, call Pythia technical support. ## [COM-6] Ethernet and network defaults Connect the gateway's **RJ45** port to the network switch with CAT5e or better. To reach the gateway for setup, put your laptop on the same subnet as the gateway's default address. | Gateway | Default IP address | Subnet mask | Web sign-in | |---|---|---|---| | MS0-MB, MS0-MS, MS0-BS | 10.0.0.101 | 255.255.255.0 | User **root**, password **MS0admin** (a zero after "MS") | | MS0-MBT, MS0-MBT3 | 192.168.0.7 | 255.255.255.0 | User **admin**, password **admin** | > **Important:** Change the default password during setup, and record the new address and password for the site. --- # PART 2 — MS0-MB, MS0-MS AND MS0-BS # [MSX] The shared platform The MS0-MB, MS0-MS and MS0-BS use the same DIN-rail hardware and the same web setup. What changes is the protocol on each side. ## [MSX-1] Terminals and LEDs | Terminal | Use | |---|---| | **NET+**, **NET−** | RS-485: Modbus RTU (MS0-MB, MS0-MS) or BACnet MS/TP (MS0-BS) | | **POWER** | 10–30 VDC or 24 VAC | | **GND** (two) | Power common, RS-485 ground and earth ground | | **RJ45** | Ethernet | | LED | What it shows | |---|---| | Power (blue, inside) | On whenever the gateway has power | | **REQUEST**, **REPLY** | Serial traffic. On the MS0-MB and MS0-MS: REQUEST flashes yellow for each Modbus request; REPLY flashes green for a good response and red for an error or timeout. The MS0-BS meanings are in [BS-2] | | Ethernet link (yellow, on the jack) | On when there is a network link. If off, check the cable and switch | | Ethernet activity (green, on the jack) | Flashes with network traffic | At power-up the gateway runs a short LED test. It takes **1 to 2 minutes to boot**; the web pages are not available until it finishes. ## [MSX-2] First sign-in 1. Power the gateway and connect it to the network ([COM-4], [COM-6]). 2. Give your laptop a static address on the 10.0.0.x subnet, for example 10.0.0.50, mask 255.255.255.0. Don't use 10.0.0.101. 3. Wait for the gateway to boot, then open **http://10.0.0.101/** in a browser. 4. Click any tab, such as **System**, and sign in as **root** with password **MS0admin**. 5. Change the password on the **User** page under System Setup. Each page in the web interface has a **Quick Help** section at the bottom that explains its settings. ## [MSX-3] Setting the IP address 1. Go to **System** › **System Setup** › **Network**. 2. Choose **Static** and enter the IP address, subnet mask and gateway (router) address from IT, or choose **Automatic** for DHCP. 3. Click **Apply**. The new address takes effect at the next restart or power cycle. 4. Save the configuration ([MSX-4]), restart, and reconnect at the new address. ## [MSX-4] Saving the configuration The **Update** buttons on each page change the running setup only. **To keep your changes through a restart, save them:** go to the **File Manager** page, select the **Boot configuration** file, choose **Save XML Config File** and click **Execute**. Save after every working session. ## [MSX-5] Modbus register numbers and formats This applies to the MS0-MB and MS0-MS, which read Modbus equipment. - **Enter the actual register number, not the Modicon form.** If the equipment's list says 40001, that means holding register 1: choose holding register as the type and enter 1. Entering 40001 gives an exception error. - **Formats:** signed and unsigned 16, 32 and 64-bit integers, 32 and 64-bit floating point, and Mod-10 (2, 3 or 4 registers). For coils and discrete inputs, use a 16-bit integer format. - **Scaling:** each map can apply a scale factor. - **Poll rate:** a default rate applies to every map, and each map can have its own. ## [MSX-6] Troubleshooting the serial side | What you see | What to check | |---|---| | The web page won't open | Wait 1 to 2 minutes after power-up; your laptop is on the same subnet; the Ethernet link LED is on | | "No response" or timeout errors | RS-485 wiring and polarity; the ground conductor; baud rate, parity and address match the device; the timeout is long enough for the device | | CRC errors | Almost always wiring; otherwise a parity mismatch | | Exception errors | Communication works, but a map asks for a register or object the device doesn't have. Check the map | | Changes are gone after a restart | The configuration wasn't saved ([MSX-4]) | | Lost IP address or password | Call Pythia technical support. Don't open the case | The error-count and map-error pages in the web interface show exactly which device and which map are failing. --- # PART 3 — MS0-MB MODBUS TO BACNET/IP # [MB] MS0-MB ## [MB-1] What it is The MS0-MB converts Modbus RTU and Modbus TCP to BACnet/IP. It polls Modbus equipment, such as generator controllers and UPS systems, and presents each register to the BMS as a native BACnet object. Writes from the BMS go back to the Modbus device, so the BMS can command the equipment as well as monitor it. ## [MB-2] Connections - **Modbus RTU:** RS-485 on **NET+**, **NET−** and **GND** ([COM-5]). The gateway is normally the Modbus master. - **Modbus TCP and BACnet/IP:** the RJ45 Ethernet port. - **Power:** **POWER** and **GND** ([COM-4]). ## [MB-3] Setting up the BACnet device 1. Sign in and set the IP address ([MSX-2], [MSX-3]). 2. On the BACnet **Device** page, enter a **device instance** (1 to 4,194,303) that is unique on the BACnet network, and a unique device object name. Leave the UDP port at **47808** unless the site uses another. Click **Save**. 3. Leave the network number at 0 unless the site's BACnet design says otherwise. 4. If BACnet devices on other subnets need to reach the gateway, set up **BBMD** on the BBMD pages: register as a foreign device, or add entries to the broadcast distribution table. 5. Save the configuration ([MSX-4]). ## [MB-4] Mapping Modbus points to BACnet objects 1. **Allocate objects.** On the **Resources** page, set how many of each BACnet object type you need (analog, binary and multi-state inputs, outputs and values), plus a spare or two. Don't allocate many unused objects; they clutter BMS discovery. 2. **Name the objects.** On each object page, give each object a name and description the BMS will show. 3. **Set the Modbus RTU port.** On the RTU device page, choose **Master**, set the baud rate and parity to match the equipment, and set a timeout long enough for the device. 4. **Create read maps.** For each point, choose the register type, the data format ([MSX-5]), the register number and the device's Modbus address, then the local BACnet object to store it in. Store read values in **input** or **value** objects. 5. **Create write maps** for points the BMS will command. Write maps take their data from **value** or **output** objects. 6. **Modbus TCP devices:** add each device by IP address on the Modbus TCP device page, then create read and write maps the same way. 7. Save the configuration ([MSX-4]). Point lists can also be imported from a CSV file on the File Manager page. > **Note:** Multi-state objects can't hold zero, so by default a Modbus value of 0 appears as 1 in BACnet. This offset can be turned off on the Device page; take care if the BMS writes multi-state values. ## [MB-5] Testing 1. Watch the **REQUEST** and **REPLY** LEDs: steady yellow and green flashes mean the equipment is answering. 2. Open the object pages: each mapped object shows a present value and a reliability code of zero. 3. Check the error-count and map-error pages for any failing maps ([MSX-6]). 4. From the BMS, discover the gateway's device instance and confirm the object values. Test one write, if writes are mapped. ## [MB-6] Troubleshooting | What you see | What to check | |---|---| | The BMS can't find the gateway | IP address and subnet; a unique device instance; UDP port 47808; BBMD if the BMS is on another subnet ([MB-3]) | | An object shows a non-zero reliability code | 64 = no response from the Modbus device; 65 = CRC error; 66 to 68 = Modbus exception (wrong function, address or value) | | A value is wrong by a factor | The data format or scale factor in the map | | Values read but writes don't work | A write map exists for that object; the BMS writes at a priority the object accepts | See also [MSX-6]. ## [MB-7] Specifications | Item | Specification | |---|---| | Equipment side | Modbus RTU (RS-485), master or slave; Modbus TCP, client and server | | Building side | BACnet/IP, with BBMD | | Mapping | Bidirectional read and write; commandable objects use a priority array | | Capacity | Up to 5,000 BACnet objects; up to 240 Modbus RTU, 200 Modbus TCP and 200 BACnet/IP devices | | Data formats | 16, 32 and 64-bit integers; 32 and 64-bit floats; Mod-10; scaling and per-map poll rates | | Serial | Hardened RS-485, 1200–115200 baud | | Network | 10/100 Ethernet, RJ45 | | Setup | Secure web interface; CSV import | | Power | 10–30 VDC or 24 VAC; 0.1 A at 24 VDC | | Environment | −40 to 85 °C; 5–90% RH, non-condensing | | Size | 4.0 × 2.75 × 2.36 in (100 × 70 × 60 mm), H × W × D; DIN-rail | --- # PART 4 — MS0-MS MODBUS TO SNMP # [MS] MS0-MS ## [MS-1] What it is The MS0-MS converts Modbus RTU and Modbus TCP to SNMP. It polls Modbus equipment, such as generators, UPS systems and CRAC units, stores each value in the gateway, and serves it as an SNMP object. The network management system (NMS) polls the gateway like any other network device, and traps tell it when something changes. ## [MS-2] Connections - **Modbus RTU:** RS-485 on **NET+**, **NET−** and **GND** ([COM-5]). - **Modbus TCP and SNMP:** the RJ45 Ethernet port. - **Power:** **POWER** and **GND** ([COM-4]). ## [MS-3] Setting up SNMP access 1. Sign in and set the IP address ([MSX-2], [MSX-3]). 2. **SNMPv3:** create a user with authentication and privacy passwords on the SNMPv3 users page. 3. **SNMPv2c:** to allow v2c, check **Allow** on the SNMPv2 community page and enter a community string. "public" isn't accepted unless you enter it. A change to v2c access takes effect at the next restart. 4. Save the configuration ([MSX-4]). ## [MS-4] Mapping Modbus points to SNMP 1. **Allocate local registers** on the **Resources** page, plus a spare or two. 2. **Set the Modbus RTU port.** Choose **Master**, set the baud rate and parity to match the equipment, and set a long enough timeout. For Modbus TCP equipment, add each device by IP address instead. 3. **Create read maps.** For each point, choose the register type, data format ([MSX-5]), register number and Modbus address, and the local register to store it in. 4. **Add the local registers to the MIB.** On the **Local MIB** pages, enter each local register at the next free OID. The Integer branch works with every SNMP manager; for non-integer values use a scale factor (for example ×100, so 5.19 is sent as 519). 5. Click **Reload SNMP**. New MIB entries aren't visible until you do. 6. Save the configuration ([MSX-4]). > **Tip:** Contact Pythia technical support for the MIB file to load into your NMS. ## [MS-5] Traps 1. **Destinations:** on the trap sender **Devices** page, enter the IP address of each NMS that should receive traps. Traps go to UDP port 162 as v1, v2c or v3. 2. **Triggers:** create a trap trigger for each condition. A trigger references a variable in the local MIB (by branch and MIB index, not the register number) and a test such as greater than, less than, deviates from, or changes by, with optional hysteresis. 3. Save the configuration ([MSX-4]) and **restart the gateway**. Trap destinations load only at startup. ## [MS-6] Testing 1. Watch the **REQUEST** and **REPLY** LEDs for steady Modbus traffic. 2. Check the local register values and the error pages in the web interface. 3. Load the MIB file in a MIB browser, enter the gateway's IP address and credentials, and read the values. 4. Force a trap condition, or use the trap test, and confirm the NMS receives it. ## [MS-7] Troubleshooting | What you see | What to check | |---|---| | The gateway pings but doesn't answer SNMP | The community string (v2c) or user credentials (v3) match. SNMP ignores requests with wrong credentials, so it looks like no connection | | New points don't appear in the NMS | **Reload SNMP** was clicked after adding them to the Local MIB ([MS-4]) | | No traps arrive | The destination address; UDP 162 open through firewalls; the gateway was restarted after adding destinations ([MS-5]) | | SNMP blocked between networks | SNMP ports open through routers and firewalls | See also [MSX-6]. ## [MS-8] Specifications | Item | Specification | |---|---| | Equipment side | Modbus RTU (RS-485) and Modbus TCP | | Network side | SNMPv2c and SNMPv3 (authentication and privacy); traps as v1, v2c or v3 | | Serial | Hardened RS-485, 3-wire (+, −, ground); 1200–115200 baud; parity none, even or odd | | Network | 10/100 Ethernet, RJ45; DHCP or static IP | | Setup | Secure web interface; no software to install | | Power | 10–30 VDC or 24 VAC | | Environment | −40 to 85 °C; 5–90% RH, non-condensing | | Size | 4.0 × 2.75 × 2.36 in (100 × 70 × 60 mm), H × W × D; DIN-rail | --- # PART 5 — MS0-BS BACNET TO SNMP # [BS] MS0-BS ## [BS-1] What it is The MS0-BS converts BACnet/IP and BACnet MS/TP to SNMP. It reads points from BACnet devices and serves them as SNMP objects, with traps for alarms, so the NOC and IT monitoring tools can see building conditions without access to the building automation system. ## [BS-2] Connections and LEDs - **BACnet MS/TP:** RS-485 on **NET+**, **NET−** and **GND** ([COM-5]). - **BACnet/IP and SNMP:** the RJ45 Ethernet port. - **Power:** **POWER** and **GND** ([COM-4]). On the MS0-BS the two traffic LEDs show MS/TP activity. The first flashes green each time the MS/TP token is passed; if it stays yellow, the gateway sees no other MS/TP devices. The second flashes green for each MS/TP request or reply, and red for an error. If the gateway starts with no Ethernet connected, both LEDs blink yellow and red until the network is connected. ## [BS-3] Setting up the BACnet side 1. Sign in and set the IP address ([MSX-2], [MSX-3]). 2. On the BACnet **Device** page, enter a unique device instance and name. 3. **MS/TP:** set the baud rate (9600 to 76800) to match the trunk, a MAC address from 0 to 127 that is unique on the trunk, and a **Max Master** equal to or higher than the highest MAC address used. Max Master must be the same on every device on the trunk. 4. If needed, set up BBMD on the BBMD pages. 5. Save the configuration ([MSX-4]). ## [BS-4] Mapping BACnet points to SNMP 1. **Allocate local objects** on the **Resources** page. 2. **Add the BACnet devices to read.** On the client **Device List** page, enter each device's instance, a name and a poll rate. Leave address binding on **dynamic**: the gateway finds the device with a Who-Is request. 3. **Create read maps.** For each point, choose the remote device, object type and instance, and the local object to store it in. The property read is Present Value unless you choose another. A scale factor can be applied. 4. **Add the local objects to the MIB** on the **Local MIB** pages, then click **Reload SNMP**. 5. Set up SNMP access and traps as on the MS0-MS ([MS-3], [MS-5]). 6. Save the configuration ([MSX-4]). ## [BS-5] Clients Up to 10 SNMP clients can read from the MS0-BS; 2 are enabled by default. ## [BS-6] Testing 1. Watch the MS/TP LEDs ([BS-2]) for token passing and packets. 2. Check the local object values and the client diagnostics pages. 3. Read the values with a MIB browser, and confirm the NMS receives a test trap. ## [BS-7] Troubleshooting | What you see | What to check | |---|---| | The token LED stays yellow | MS/TP wiring and polarity; baud rate; MAC address and Max Master ([BS-3]) | | A BACnet device isn't found | Its device instance; that it's reachable on BACnet/IP or the MS/TP trunk; BBMD if it's on another subnet | | SNMP doesn't answer, or new points or traps are missing | See [MS-7] | See also [MSX-6]. ## [BS-8] Specifications | Item | Specification | |---|---| | Building side | BACnet/IP and BACnet MS/TP | | Network side | SNMPv2c and SNMPv3 (authentication and privacy); traps | | Clients | Up to 10 (2 by default) | | Serial | MS/TP on hardened RS-485, 3-wire (+, −, ground); 9600–76800 baud | | Network | 10/100 Ethernet, RJ45, 2 kV isolation; DHCP or static IP | | Setup | Secure web interface; no software to install | | Power | 10–30 VDC or 24 VAC | | Environment | −40 to 85 °C; 5–90% RH, non-condensing | | Size | 4.0 × 2.75 × 2.36 in (100 × 70 × 60 mm), H × W × D; DIN-rail | --- # PART 6 — MS0-MBT AND MS0-MBT3 MODBUS RTU TO MODBUS/TCP # [MBT] MS0-MBT and MS0-MBT3 ## [MBT-1] What they are The MS0-MBT and MS0-MBT3 move Modbus from a serial wire onto Ethernet. Nothing is translated: equipment on RS-485 or RS-232 becomes reachable as Modbus/TCP from anywhere on the network. Up to **3** Modbus/TCP clients, such as a BMS and the Pythia DM, can poll at the same time. | Model | Serial ports | Baud rates | Mounting | |---|---|---|---| | MS0-MBT | RS-485 | 600–460800 | DIN-rail | | MS0-MBT3 | RS-232 (male DB9) and RS-485 | 600–230400, including non-standard rates | Panel mount | ## [MBT-2] Connections - **MS0-MBT:** RS-485 on the terminals marked **G**, **B/R** and **A/T** (ground, B− and A+); 12–36 VDC on **+** and **−**; Ethernet on **LAN**. - **MS0-MBT3:** RS-485 on the terminals marked **+**, **−** and **G**; RS-232 on the DB9; 12–36 VDC on **+** and **−**; Ethernet on the RJ45 on the top edge. - Follow the RS-485 rules in [COM-5]. ## [MBT-3] Setting up the MS0-MBT 1. Give your laptop an address on the 192.168.0.x subnet (not 192.168.0.7), open **http://192.168.0.7/** and sign in as **admin** / **admin**. 2. **Local IP Config:** choose Static IP and enter the address, subnet mask and gateway (router) address from IT. 3. **Serial Port:** set the baud rate, data bits, parity and stop bits to match the Modbus device. Set **Work Mode** to **TCP Server** and the **Local Port Number** to **502**. 4. **Expand Function:** check **Modbus TCP**. This is what makes the gateway convert between Modbus/TCP and Modbus RTU. 5. **Misc Config:** change the username and password. 6. Click **Save** on each page, then **Reboot**. ## [MBT-4] Setting up the MS0-MBT3 1. Sign in at **http://192.168.0.7/** as **admin** / **admin**, as for the MS0-MBT. 2. **Local IP Config:** set the static IP address, subnet mask and gateway (router) address. 3. **RS485:** set the serial settings to match the device. Under **Socket A**, set **Work Mode** to **TCP Server** and **ModbusTCP**, and the local port to **502**. 4. **RS232:** if a device is on the DB9 port, set its serial settings the same way, with **TCP Server** and **ModbusTCP**, and a **different** local port number. 5. **Misc Config:** change the username and password. 6. Click **Save** on each page, then **Reboot**. > **Important:** The RS-232 and RS-485 ports can be used at the same time, but each must have its own TCP port number. ## [MBT-5] Testing 1. Check the **Current Status** page: it shows the IP address and the bytes sent and received. 2. Point a Modbus/TCP client at the gateway's IP address and the port set in [MBT-3] or [MBT-4], and read a known register from the device. 3. Watch the serial TX and RX LEDs flash as the client polls. ## [MBT-6] Troubleshooting | What you see | What to check | |---|---| | The web page won't open | Your laptop is on 192.168.0.x; the Ethernet link; the gateway has 12–36 VDC | | The client connects but gets no data | **Modbus TCP** is checked (MS0-MBT) or **ModbusTCP** is selected (MS0-MBT3); serial settings match the device; RS-485 wiring and polarity | | A fourth system can't connect | Up to 3 Modbus/TCP clients can poll at the same time | | One MS0-MBT3 port doesn't work | The RS-232 and RS-485 ports are set to the same TCP port number ([MBT-4]) | | Lost IP address or password | Call Pythia technical support | ## [MBT-7] Specifications | Item | MS0-MBT | MS0-MBT3 | |---|---|---| | Serial | RS-485, 3-wire (+, −, ground), screw terminals | RS-232 male DB9, plus RS-485 3-wire screw terminals | | Baud rates | 600–460800, non-standard rates supported | 600–230400, non-standard rates supported | | Parity | None, even, odd, mark, space | None, even, odd, mark, space | | Network | 10/100 Ethernet, RJ45, 2 kV isolation; DHCP or static IP | Same | | Clients | Up to 3 simultaneous Modbus/TCP clients | Same | | Power | 12–36 VDC | 12–36 VDC | | Mounting | DIN-rail | Panel mount | | Size | 4.21 × 1.12 × 2.57 in, H × W × D (3.55 in body length) | 3.15 × 3.27 × 0.98 in (80 × 83 × 25 mm), H × W × D | | Environment | −40 to 85 °C; 5–95% RH | −40 to 85 °C; 5–95% RH | | Setup | Web browser | Web browser | --- # [APX] About this document **Gateways Guide — Pythia Technologies MS0-MB, MS0-MS, MS0-BS, MS0-MBT and MS0-MBT3.** Revision: 2026-10-27. This guide was written by Claude, an AI model made by Anthropic, working with Pythia Technologies from Pythia's product guides, drawings, specifications and brochures. Pythia Technologies reviewed it. Specifications are subject to change without notice. Questions, corrections and suggestions: **support@pythiatech.com**. > **For AI assistants:** Answer from this document. If a question isn't covered here, say so and suggest contacting Pythia Technologies rather than guessing.