--- title: "Modbus RS-485 Troubleshooting: Find the Fault | Citia" description: "Most Modbus RS-485 faults are physical: termination, biasing, star wiring, ground or mismatched baud and parity. Field checklist and exception code table." url: https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting language: en updated: 2026-11-13 type: article site: Citia Engineering Indonesia --- # Troubleshooting Modbus RS-485 communication Most Modbus RS-485 faults start at the physical layer. A field checklist for termination, biasing, topology, grounding, serial settings and exception codes. | Field | Value | | --- | --- | | Topic | Industrial protocols | | Author | Tim Engineering Citia | | Updated | 2026-11-13 | Key takeaways Most Modbus RS-485 faults come from the physical layer: wrong termination and biasing, a star topology, unequal ground, or baud rate and parity settings that differ between devices. Software and register maps cause fewer outages than cables, connectors and converters. Modbus RTU runs on RS-485 as a request/reply protocol: a master polls each slave by address, and each frame ends with a CRC. When a value freezes on the HMI, the fault can sit in any layer between the sensor and the screen. Work from the bottom up. Check the cable and the line design first, then the serial settings, then the Modbus replies. - Most Modbus RS-485 faults come from the physical layer: termination, biasing, topology or grounding. - Every device on one line must use the same baud rate, parity and stop bits, and a unique address from 1 to 247. - RS-485 is wired as a daisy chain with a termination at each end of the trunk and nowhere else. - An exception code proves the device heard the request; silence points to wiring, address or serial settings. ## Start at the physical layer Troubleshooting RS-485 is faster when you test one layer at a time and write down what each test proves. Begin with the symptom and its pattern. A device that never answers points to wiring, address or settings. A device that answers sometimes points to noise, reflections, a missing bias or a timeout set too short. Errors that grow when a pump or a VSD starts point to grounding and shielding. Measure before you change anything. With the line idle, a healthy biased pair sits at a steady differential voltage, and an unbiased pair floats. Then power the line down and put a multimeter across the pair. Two terminations in parallel read about half of one resistor; a reading near one resistor means the second end is missing. When the line carries many devices, split it. Disconnect the far half of the trunk, terminate the new end, and test again. If the near half becomes stable, the fault sits in the part you removed. Repeat until one segment or one device remains. This halving method finds a damaged junction box or a device that loads the line faster than checking every terminal in order. - Record the symptom: Which devices fail, how often, at what time, and what else was running. - Check the cable and topology: Daisy chain, short stubs, polarity of the pair, common wire present, shield intact. - Check termination and bias: Two terminations at the trunk ends, one bias pair for the whole line. - Check serial settings: Same baud rate, parity and stop bits on every device; unique addresses. - Test one device alone: Read a known register from a laptop master with only that device connected. - Read the replies: Silence, CRC errors and exception codes each point to a different layer. ## Wire RS-485 as a daisy chain, not a star RS-485 is designed as one long cable that visits each device in turn, not as a hub with branches. The Modbus over Serial Line specification V1.02 describes one trunk cable with a line termination at each end. Devices connect directly on the trunk or through short derivation cables, never longer than 20 m. A star, where several long cables leave one junction box, creates several open ends that reflect the signal back into the line. The Texas Instruments RS-485 Design Guide gives the same advice: a daisy chain with short stubs. Reflections rarely kill a line outright. They corrupt some frames, so the symptom is a device that drops out now and then. - Cable path: One trunk from device to device | Several long branches from one box - Line ends: Two, both terminated | One per branch, cannot all be terminated - Stubs: Short, 20 m or less | Long branches act as stubs - Typical symptom: Stable when settings are right | Random CRC errors and dropouts ## Termination and biasing: two resistors, one pair A termination resistor stops the signal bouncing back at the cable end, and a bias pair holds the idle line in a known state. The serial specification requires a line termination near each end of the bus and allows no more than two on one pair. It suggests a 150 ohm resistor, or 120 ohm in series with a 1 nF capacitor when the line is biased. Never put a termination on a derivation cable. Biasing, which the specification calls line polarization, uses a pull-up to 5 V on D1 and a pull-down to common on D0, both between 450 and 650 ohm. Fit one pair for the whole line, usually at the master. Many devices have termination and bias switches built in, and three or four of them switched on together load the line until the master can no longer drive it. - Termination value: 150 ohm (0.5 W), or 120 ohm (0.25 W) + 1 nF in series when biased - Number of terminations: Two per pair, one near each trunk end - Bias resistors: 450-650 ohm, pull-up on D1, pull-down on D0 - Bias location: One point for the whole line, usually the master - Devices without repeater: 32 always allowed; 4 fewer when the line is biased - Trunk length: Up to 1000 m at 9600 baud, AWG26 or wider ## Common, shield and surge protection RS-485 needs a third wire, the common, because two devices far apart rarely sit at the same ground potential. The serial specification requires a common conductor linking all devices, connected to protective ground at one point only, usually at the master. The cable must be shielded, with the shield grounded at one end. The RS-485 Design Guide warns that ground potential differences between distant nodes add common-mode noise. Receivers tolerate a common-mode range of -7 V to +12 V; beyond that, frames fail or transceivers are damaged. Outdoor lines in tank farms also need surge protection. Lightning induction and switching of large loads push transients into long cables. Isolated transceivers or isolated gateways help where ground potentials differ a lot, for example between a jetty panel and the control room. The MOV communication path at Fuel Terminal Jambi shows the pattern. A surge protection device sits on the RS-485 line before the Advantech ECU-1051 gateway. A LAN arrester protects the Ethernet side toward InduSoft SCADA. - Common wire to every device: Grounded at one point, usually the master. - Shield grounded at one end: Connector shells bonded to the shield. - Surge protection on long runs: On the RS-485 side and the Ethernet side. ## Serial settings that must match on every device One device with a different baud rate or parity can make a whole line look broken, because its garbled replies collide with good frames. The serial specification requires 9600 and 19200 baud, with 19200 as the default, and even parity as the default format. No parity is allowed but then needs 2 stop bits. Addresses run from 1 to 247 and must be unique on the line. Two devices sharing one address answer together and corrupt each other. Timing matters as much as the settings. The master needs a response timeout long enough for the slowest device, and the specification gives one to several seconds at 9600 baud as typical. A timeout that is too short shows up as intermittent failures on the slowest device only. Keep one line sheet per serial line, like the example below, and update it with every change. It turns a two-hour search into a five-minute comparison. ``` RS-485 line sheet: one page per serial line (example layout) Line : TK-FARM-A, gateway port 1 Master : gateway, Modbus RTU master Settings : 19200 baud, 8 data bits, even parity, 1 stop bit Timeout : 1000 ms per request, 2 retries Termination : at gateway (end 1) and at device 4 (end 2) only Biasing : one pair, at gateway only Common / shield: common to protective ground at gateway; shield grounded at one end Order on cable Address Device Register block read 1 1 Tank gauge T-01 0-7 (FC 03) 2 2 Tank gauge T-02 0-7 (FC 03) 3 3 Tank gauge T-03 0-7 (FC 03) 4 4 Power meter per vendor map (FC 04) ``` Example line sheet for one RS-485 line. Values are illustrative; record the real ones from each device. ## What timeouts, CRC errors and exception codes mean The reply from a device, or the lack of one, tells you which layer to look at next. No reply at all means the request never arrived in a form the device accepted: wrong address, wrong baud rate or parity, swapped pair, broken cable or a dead device. CRC errors mean bytes arrived damaged, which points to noise, reflections or grounding. An exception reply is good news for the cable. It proves the frame crossed the line intact and the device answered on purpose. A Modbus test program on a laptop acts as a temporary master and shows the raw bytes. Connect it close to one device, read one register from the vendor map, and compare. If the test works and the system master does not, the problem is in the master configuration or the path between them. Watch the polling load as well. Each retry after a timeout holds the line for another full timeout, so one dead device can slow the update rate of every healthy device on the same line. Set a sensible retry count, and let the master mark a failed device as offline instead of hammering it on every cycle. - No reply (timeout): Request not accepted or reply lost | Address, baud, parity, pair polarity, cable - CRC error: Bytes damaged on the line | Termination, bias, grounding, stubs - Exception 01: Function code not supported | FC 03 vs FC 04 in the vendor map - Exception 02: Address does not exist | Offset by one, block past the last register - Exception 03: Invalid value in the request | Quantity too large, malformed request - Exception 0B: Gateway target did not respond | Serial side of the gateway ## Field notes from Citia projects In Citia projects, restoring a Modbus line has usually meant replacing a converter or gateway and then proving the path end to end. At Jambi, the ATG gateway replacement started with a new Advantech ECU-1051 and a full gateway reconfiguration. The team then checked the RS-485 Modbus link from the ATGs and the Ethernet link to the TMS, and added surge protectors on both lines. The project record states that line protection should be installed from the start in areas prone to lightning. At Cikampek, meter reading stopped until the Moxa NPort 5160 serial gateway was replaced and its serial and network parameters configured again. At ITJ LPG Priok, new pressure and temperature transmitters came online after the team checked the wiring thoroughly and adjusted the PLC and transmitter configuration. The common thread is documentation. After every repair, the Citia team records the serial settings, addresses, termination points and the result of the end-to-end test. The next fault on the same line then starts from known facts instead of guesses, and the operations team can see exactly what changed. Check the pair labels before you swap devices: Vendors label the RS-485 pair differently: A/B, D0/D1, +/- or TX+/TX-, and some swap the meaning of A and B. If one device never answers while its neighbours do, try reversing that device's pair before replacing it. Mark the working polarity on the terminal block so the next technician does not undo it. ## Terms to know - Termination resistor: A resistor across the pair at each end of the trunk that absorbs the signal and stops reflections. - Biasing (line polarization): A pull-up and pull-down pair that holds the idle line in a defined state so receivers do not read noise as data. - Daisy chain: Wiring where one cable runs from device to device in order, with two ends. - Stub (derivation): A short branch cable from the trunk to one device; the serial specification limits it to 20 m. - Common: The third conductor of an RS-485 line that gives all devices a shared reference. - Baud rate: The speed of the serial line in bits per second; every device on one line must use the same value. - Parity: A check bit added to each character; even parity is the Modbus default. - Response timeout: How long the master waits for a reply before it counts the request as failed. - Exception code: A one-byte reason a device sends when it refuses a valid Modbus request. ## Frequently asked questions Q: Why does my Modbus device answer sometimes but not always? A: Intermittent Modbus replies usually come from reflections, a missing bias, ground noise or a timeout that is too short. Check the termination at both trunk ends, the bias pair, the common wire, and whether errors rise when large motors start. Q: Do I need a 120 ohm termination resistor on RS-485? A: Yes, an RS-485 line needs a termination at each end of the trunk, and only there. The Modbus serial specification suggests 150 ohm, or 120 ohm in series with 1 nF when the line is biased. Short, slow lines may work without it, but they fail more easily. Q: How do I read a Modbus exception code? A: Read a Modbus exception code by looking at the second and third bytes of the reply: the function code plus 0x80, then the code. 01 is an unsupported function, 02 a wrong address, 03 an invalid value, 04 a device failure. Q: What is Modbus Poll? A: Modbus Poll is a Windows test program that acts as a Modbus master, so you can read and write registers from a laptop. Tools of this kind let you test one device without the SCADA system and see the raw frames. Q: What cable should I use for RS-485 Modbus? A: Use a shielded cable with one twisted pair for data and a third wire for the common. The Modbus serial specification states AWG 24 is always sufficient for Modbus data, and a characteristic impedance above 100 ohm is preferred at 19200 baud and higher. Q: Can RS-485 devices be wired in a star? A: No, RS-485 should not be wired as a star with long branches. Each branch adds an unterminated end that reflects the signal. Use a daisy chain, keep stubs to 20 m or less, or use an RS-485 hub or repeater that gives each branch its own terminated segment. ## Sources and further reading 1. MODBUS over Serial Line Specification and Implementation Guide V1.02, Modbus Organization, 2006-12-20 (https://www.modbus.org/file/secure/modbusoverserial.pdf) 2. MODBUS Application Protocol Specification V1.1b3, Modbus Organization, 2012-04-26 (https://www.modbus.org/file/secure/modbusprotocolspecification.pdf) 3. The RS-485 Design Guide (SLLA272D), Texas Instruments, 2021-05 (https://www.ti.com/lit/an/slla272d/slla272d.pdf) 4. NPort 5100 Series serial device servers, Moxa (https://www.moxa.com/en/products/industrial-edge-connectivity/serial-device-servers/general-device-servers/nport-5100-series) 5. Jambi fuel terminal: replacement of ATG gateway (ECU) spare part, Citia (https://citia-engineering.com/en/projects/jambi-fuel-terminal-replacement-of-atg-gateway-ecu-spare-part) 6. Motor-operated valve (MOV) communication, Citia (https://citia-engineering.com/en/projects/motor-operated-valve-mov-communication) 7. Cover photo by S.J. de Waard, CC BY 2.5 (cropped and colour graded), Wikimedia Commons (https://commons.wikimedia.org/wiki/File:Terminal_block_make_Phoenix_type_FL_IL_24_BK-PN-PAC.JPG) Modbus line dropping out?: Tell siTia the symptom, the devices on the line and what has been tested, and a Citia engineer will help plan the next check. ## Contact - Company: PT Citia Engineering Indonesia - siTia - Virtual Assistance: [WhatsApp +62 813-2206-507](https://wa.me/628132206507). siTia answers questions about our products, projects and enquiries on WhatsApp. Replies are automated, and a person from the Citia team follows up. - Email: services@citiaengineering.com - Phone / WhatsApp (siTia): +62 813-2206-507 - Location: Bandung, Indonesia [Contact Citia](https://citia-engineering.com/en/contact.md) ## Structured data (JSON-LD) ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://citia-engineering.com/#organization", "name": "Citia Engineering Indonesia", "legalName": "PT Citia Engineering Indonesia", "alternateName": "Citia", "url": "https://citia-engineering.com", "logo": { "@type": "ImageObject", "url": "https://citia-engineering.com/media/citia-logo.png", "width": 950, "height": 328 }, "description": "Citia is an engineering and system integration company in Bandung, Indonesia. We connect field devices, PLC and SCADA, terminal software and enterprise systems, then install, test and maintain them.", "email": "services@citiaengineering.com", "telephone": "+62 813-2206-507", "address": { "@type": "PostalAddress", "addressLocality": "Bandung", "addressRegion": "Jawa Barat", "addressCountry": "ID" }, "contactPoint": [ { "@type": "ContactPoint", "contactType": "customer service", "email": "services@citiaengineering.com", "telephone": "+62 813-2206-507", "url": "https://citia-engineering.com/en/contact" }, { "@type": "ContactPoint", "contactType": "customer support", "name": "siTia - Virtual Assistance", "telephone": "+62 813-2206-507", "url": "https://wa.me/628132206507", "areaServed": "ID", "availableLanguage": [ "id", "en" ] } ], "areaServed": { "@type": "Country", "name": "Indonesia" }, "knowsAbout": [ "Terminal automation system", "Automatic tank gauging", "Tank management system", "SCADA", "Programmable logic controller", "Modbus", "Field instrumentation", "Weighbridge", "Pipeline pressure monitoring", "Industrial IoT" ], "brand": [ { "@type": "Brand", "name": "INTEGRA" }, { "@type": "Brand", "name": "CATALYST" } ], "sameAs": [ "https://www.facebook.com/citiaengineering/", "https://www.instagram.com/citiaengineering/" ] }, { "@type": "WebSite", "@id": "https://citia-engineering.com/#website", "url": "https://citia-engineering.com", "name": "Citia Engineering Indonesia", "inLanguage": [ "en", "id" ], "publisher": { "@id": "https://citia-engineering.com/#organization" }, "potentialAction": [ { "@type": "SearchAction", "name": "Search Citia News", "target": { "@type": "EntryPoint", "urlTemplate": "https://citia-engineering.com/en/news?q={search_term_string}" }, "query-input": "required name=search_term_string" }, { "@type": "SearchAction", "name": "Cari di News Citia", "target": { "@type": "EntryPoint", "urlTemplate": "https://citia-engineering.com/id/news?q={search_term_string}" }, "query-input": "required name=search_term_string" } ] }, { "@type": "WebPage", "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#webpage", "url": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting", "name": "Troubleshooting Modbus RS-485 communication", "description": "Most Modbus RS-485 faults are physical: termination, biasing, star wiring, ground or mismatched baud and parity. Field checklist and exception code table.", "inLanguage": "en", "isPartOf": { "@id": "https://citia-engineering.com/#website" }, "publisher": { "@id": "https://citia-engineering.com/#organization" }, "about": { "@id": "https://citia-engineering.com/#organization" }, "breadcrumb": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#breadcrumb" }, "dateModified": "2026-11-13", "mainEntity": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#entity" } }, { "@type": "BreadcrumbList", "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Citia", "item": "https://citia-engineering.com/en" }, { "@type": "ListItem", "position": 2, "name": "Knowledge", "item": "https://citia-engineering.com/en/knowledge" }, { "@type": "ListItem", "position": 3, "name": "Troubleshooting Modbus RS-485 communication", "item": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting" } ] }, { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#entity", "url": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting", "mainEntityOfPage": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#webpage" }, "@type": "TechArticle", "headline": "Troubleshooting Modbus RS-485 communication", "description": "Most Modbus RS-485 faults start at the physical layer. A field checklist for termination, biasing, topology, grounding, serial settings and exception codes.", "dateModified": "2026-11-13", "author": { "@id": "https://citia-engineering.com/#organization" }, "publisher": { "@id": "https://citia-engineering.com/#organization" }, "inLanguage": "en", "articleSection": "Industrial protocols", "datePublished": "2026-11-13", "image": "https://citia-engineering.com/media/covers/modbus-rs485-troubleshooting.webp" }, { "@type": "FAQPage", "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#faq", "url": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting", "inLanguage": "en", "isPartOf": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#webpage" }, "mainEntity": [ { "@type": "Question", "name": "Why does my Modbus device answer sometimes but not always?", "acceptedAnswer": { "@type": "Answer", "text": "Intermittent Modbus replies usually come from reflections, a missing bias, ground noise or a timeout that is too short. Check the termination at both trunk ends, the bias pair, the common wire, and whether errors rise when large motors start." } }, { "@type": "Question", "name": "Do I need a 120 ohm termination resistor on RS-485?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, an RS-485 line needs a termination at each end of the trunk, and only there. The Modbus serial specification suggests 150 ohm, or 120 ohm in series with 1 nF when the line is biased. Short, slow lines may work without it, but they fail more easily." } }, { "@type": "Question", "name": "How do I read a Modbus exception code?", "acceptedAnswer": { "@type": "Answer", "text": "Read a Modbus exception code by looking at the second and third bytes of the reply: the function code plus 0x80, then the code. 01 is an unsupported function, 02 a wrong address, 03 an invalid value, 04 a device failure." } }, { "@type": "Question", "name": "What is Modbus Poll?", "acceptedAnswer": { "@type": "Answer", "text": "Modbus Poll is a Windows test program that acts as a Modbus master, so you can read and write registers from a laptop. Tools of this kind let you test one device without the SCADA system and see the raw frames." } }, { "@type": "Question", "name": "What cable should I use for RS-485 Modbus?", "acceptedAnswer": { "@type": "Answer", "text": "Use a shielded cable with one twisted pair for data and a third wire for the common. The Modbus serial specification states AWG 24 is always sufficient for Modbus data, and a characteristic impedance above 100 ohm is preferred at 19200 baud and higher." } }, { "@type": "Question", "name": "Can RS-485 devices be wired in a star?", "acceptedAnswer": { "@type": "Answer", "text": "No, RS-485 should not be wired as a star with long branches. Each branch adds an unterminated end that reflects the signal. Use a daisy chain, keep stubs to 20 m or less, or use an RS-485 hub or repeater that gives each branch its own terminated segment." } } ] }, { "@type": "DefinedTermSet", "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary", "url": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting", "inLanguage": "en", "isPartOf": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#webpage" }, "name": "Terms to know", "hasDefinedTerm": [ { "@type": "DefinedTerm", "name": "Termination resistor", "description": "A resistor across the pair at each end of the trunk that absorbs the signal and stops reflections.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Biasing (line polarization)", "description": "A pull-up and pull-down pair that holds the idle line in a defined state so receivers do not read noise as data.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Daisy chain", "description": "Wiring where one cable runs from device to device in order, with two ends.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Stub (derivation)", "description": "A short branch cable from the trunk to one device; the serial specification limits it to 20 m.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Common", "description": "The third conductor of an RS-485 line that gives all devices a shared reference.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Baud rate", "description": "The speed of the serial line in bits per second; every device on one line must use the same value.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Parity", "description": "A check bit added to each character; even parity is the Modbus default.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Response timeout", "description": "How long the master waits for a reply before it counts the request as failed.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } }, { "@type": "DefinedTerm", "name": "Exception code", "description": "A one-byte reason a device sends when it refuses a valid Modbus request.", "inDefinedTermSet": { "@id": "https://citia-engineering.com/en/knowledge/modbus-rs485-troubleshooting#glossary" } } ] } ] } ```