VRF System Throwing a Fault Code: Field Troubleshooting and Logging It Against the Equipment
A VRF system flashing a fault code on the wired controller is rarely a "swap the board and go" job—the same code can mean a clogged EEV, a low refrigerant charge, a comms fault on the F1/F2 line, or a single overloaded fan motor across an 8-unit network. R-Pro's field app walks you from the code on the screen to the real cause and the repair steps, working fully offline in a mechanical room with no signal. The same job—labor, the replaced sensor, the gas you added—then flows straight into the office ERP for the quote, the tax invoice, and the accounting, with no re-typing back at the truck.
On site: decode the code and trace it to the failed unit
- Read the fault code off the wired remote or the outdoor PCB 7-segment display, then use R-Pro's AI diagnosis (built on 600+ real HVAC & refrigeration cases) to turn that code into likely causes—EEV stuck, sensor out of range, high/low pressure trip, inverter compressor overcurrent—and the step-by-step checks for each.
- Pin the fault to the right box: VRF strings dozens of indoor units off one or two outdoor condensers, so note whether the code came from the master controller, a specific indoor cassette, or the outdoor unit address—the field app keeps separate equipment records so you log against the unit that actually failed, not 'the system'.
- Scan the outdoor unit nameplate with the camera to auto-fill model, refrigerant type (R410A vs R32), and serial—no squinting at a faded label and hand-typing it while balanced on a ladder.
- Verify before you condemn a part: confirm F1/F2 communication voltage, check subcooling/superheat against the displayed sensor readings, and rule out a simple address conflict or dip-switch error—all captured as you go, even with zero signal in the riser.
- Drop a voice memo while your hands are dirty ('IDU #4 ball-3 throwing E6, EEV coil reads open, swapping coil') so nothing gets lost between the roof and the paperwork.
Back at the office: quote the repair, invoice it, and book the parts
- Turn the diagnosis into a proper quote in the ERP—itemize the replacement EEV coil or pressure sensor, the recovered/added refrigerant by weight, and labor hours, with an itemized construction-style quote if the customer wants a line-by-line breakdown.
- Raise an invoice or a proper tax invoice using your OWN country's tax setup—set the tax name and rate yourself (VAT, GST, sales tax) so the document is correct whether you're in Seoul, Sydney, or Sharjah.
- Pull the replaced sensor or PCB out of inventory and log the consumption, so your parts count for VRF spares is accurate and you know when to reorder before the next call.
- Record the refrigerant added against the job for accounting—sales, purchases, expenses, and net profit all roll up automatically, so the gas cost isn't quietly eating your margin.
- File the supplier and purchase order for any board you had to special-order from the VRF manufacturer, and keep it tied to this customer's ledger for warranty and follow-up.
The connection: one fault, logged once, used everywhere
- The unit you scanned, the code you cleared, and the part you swapped become a permanent service-history entry under that customer and that specific outdoor/indoor unit—so the next tech sees 'this E6 came back twice on IDU #4' instead of starting blind.
- Field work flows into the office books automatically: the parts, gas, and labor you logged on the roof populate the quote, invoice, and accounting with no double entry back at the desk.
- Issue a receipt to the customer on site the moment the system clears and runs—then the same numbers are already waiting in the ERP, so the field record and the office record can never drift apart.
- Recurring VRF fault patterns build into searchable history per site, so a building with a chronic comms fault or a flooding EEV is obvious before you quote the next 'mystery' callback.
- Both tools speak 10 languages on one subscription, so a multilingual crew can diagnose in the field and run the books in the office in whatever language each person works in.
Diagnose the VRF fault in the field. Bill and book it in the office.
R-Pro is two strong tools on one subscription: a field app that decodes the fault code, traces it to the failed unit, and logs the fix per equipment fully offline—and an office ERP that turns that same job into the quote, tax invoice, parts draw, and accounting with no double entry. One VRF callback, captured once, working everywhere. Available in 10 languages.
Get R-Pro →FAQ
The same VRF fault code shows on two different indoor units—how do I keep the records straight?
Log against each unit separately. R-Pro keeps an individual equipment record per indoor and outdoor unit, so an E6 (or comms fault) on IDU #4 and the same code on IDU #7 are two distinct history entries under one customer. When one keeps recurring, you'll see it immediately instead of treating the whole system as one blob.
Can I diagnose and log a VRF fault in a mechanical room with no cell signal?
Yes. The field app's AI diagnosis, nameplate scanning, voice memos, and per-unit service history all run fully offline. You can decode the code, trace the cause, record the part swapped, and even issue a receipt on site. Everything syncs to the office books once you're back in range—no signal required to do the work.
How does the refrigerant I added during the repair end up in my invoice and accounting?
You record it once on site as part of the job—weight of gas added, the EEV coil or sensor replaced, labor hours. That data flows into the ERP automatically, so it populates the quote and the tax invoice and books to your accounting (expenses and net profit). No second round of typing back at the desk, and the gas cost can't slip through unbilled.
Is the office ERP just a billing add-on, or a real business tool?
It's a full office system in its own right—quotes and itemized construction estimates, invoices and tax invoices with your own country's tax name and rate, accounting (sales, purchases, expenses, net profit), inventory, suppliers, purchase orders, customer ledger, and reports. The field app and the ERP are two equal tools; you happen to use them together so one VRF job is captured once and used everywhere.