Ask our team:
  • Phone: +86 181 0690 9650
  • E-Mail sales1@apterpower.com
  • Lifecycle status

    Discontinued / Obsolete by OEM
    Apter Power supports exact-spare review and Plant Loop migration scoping.

INLIM03

/ 4.9
1001 reviews | Need a Specific Revision?
ABB INLIM03 is a legacy Bailey Loop Interface Module used with the INBIM02 bus interface in Plant Loop communication arrangements.
In Stock
Ships by Wednesday, October 28
Fast Shipping Available
Get a quick price for INLIM03
Quantity
*E-mail
Company
*Mobile
*Content
Upload (gif, jpg, jpeg, png, bmp, doc, docx, xls, xlsx, ppt, pdf, csv)

Technical specifications for INLIM03

  • Manufacturer:
    ABB
  • Part Number:
    INLIM03
  • Product Family:
    ABB Bailey
  • Product Type:
    Loop Interface Module
  • Stock:
    1
  • Communication role:
    Plant Loop interface
  • Companion module:
    INBIM02
  • ABB migration path:
    INNIS01 with INNPM12 in Plant Loop mode
  • System family:
    Bailey Plant Loop
  • Weight:
    0.4 kg
  • Estimated shipping dimensions:
    3.5x31x17.6cm
  • Tariff Code:
    8537101190
  • Country of origin:
    Sweden
  • Place of shipment:
    Xiamen,Fujian,China
By purchasing this item, you agree to the Terms & Conditions, ApterPower is not an authorized distributor for listed manufacturers or tradenames and therefore the manufacturer's warranty does not apply. All our products come with ApterPower's 1-year warranty.

More Information

Overview Manuals Loop Architecture Migration Path Fault Isolation Product Applications

Features:

  • Path-level diagnosis: encourages the loop interface and its companion hardware to be evaluated as one communication chain.
  • Architecture-aware sourcing: distinguishes an exact repair from a migration that changes more than one module.
  • Node-continuity planning: keeps addresses, cabling, and redundancy behavior visible during an outage decision.
This module becomes the relevant service target when a legacy node loses its Plant Loop path while local controller and I/O functions remain otherwise identifiable.

A purchase decision should distinguish two different outcomes: restoring the existing paired interface or engineering the later communication architecture; a one-board visual substitution does not establish either result.

Before committing to repair or migration, the team should define the complete node boundary and the acceptance test for loop recovery, reducing the risk of receiving correct hardware for an incomplete solution.

Apter Power supports legacy-system sourcing and migration-scope review for the ABB INLIM03 Loop Interface Module, with the complete communication path considered before quotation.
ABB INLIM03 Loop Interface Module Manuals,Datasheets,Link Important Notice: No qualified exact-model English PDF is attached. Use the complete product model in every document request.
  • Plant Loop role: connects the node to the legacy communication highway.
  • Paired interface: works with INBIM02 in the original arrangement.
  • Node boundary: retain the relationship between interface hardware and controller node.
  • Network records: preserve loop addressing and redundancy details.
  • ABB mapping: INNIS01 and INNPM12 are identified as the later Plant Loop-mode path.
  • Two-module scope: migration concerns both legacy interface roles.
  • Configuration work: addresses and communication settings require engineering review.
  • Validation: prove node communication and redundancy before decommissioning the old pair.
  • Primary status: compare loop indication and node visibility.
  • Paired hardware: separate INLIM03 symptoms from INBIM02 or cabling faults.
  • Media check: inspect connectors and the documented loop path.
  • Recovery decision: choose repair or migration only after the failure boundary is located.
  • Legacy Plant Loop nodes: maintenance of the installed loop-interface arrangement.
  • Communication recovery: restoration after exact hardware and media diagnosis.
  • Migration engineering: transition to the ABB-defined later interface architecture.
  • Spare evaluation: exact-model sourcing for a documented INLIM03 and INBIM02 pair.
Description
The INLIM03 is an ABB Bailey Loop Interface Module used in the legacy Plant Loop communication architecture. Its role is tied to the companion INBIM02 bus interface rather than to a standalone field-I/O or controller function.

ABB identifies an INNIS01 network interface together with an INNPM12 operating in Plant Loop mode as the later replacement path for INLIM03 and INBIM02. That mapping is an architecture migration, not permission to exchange one board without reviewing the paired interface and configuration.

When maintaining INLIM03, preserve loop addresses, paired-module identity, cable routing, redundancy information, and node communication behavior. These records define whether an exact repair or an engineered migration is the lower-risk route.
Alternative Names
INLIM 03 Bailey INLIM03
Technical notes
The INLIM03 forms a Plant Loop interface together with INBIM02, while ABB identifies INNIS01 plus INNPM12 in Plant Loop mode as the later architecture. Do not replace only one element by name; record the pair, loop address, redundancy, cabling, and node configuration, then stop if the migration boundary is incomplete.
Exceptional Service

Our Mission

  • 100% Satisfaction

    We believe expertise is priceless. With over 20 years of experience, and top engineers on staff, we can help you solve or avoid problems that threaten your business.
  • Trust Guaranteed

    Not only do we have a vast inventory, our team makes sure every piece of equipment is in working condition. Your purchases are also backed by our Warranty.
  • Expertise

    Time is money, especially when your equipment is down. We work quickly to get your equipment on its way so you can get it back up and running.

FAQS

The following is a list of questions commonly asked by our customers. Please contact us if you have a question about our process that is not answered below.
Why must an engineer review INBIM02 when planning an INLIM03 replacement?
The original Plant Loop function is a paired interface, so changing one module without the companion role and configuration can leave the node communication path incomplete.
What does ABB require before moving from INLIM03 to the later Plant Loop architecture?
Treat the change as an INNIS01 plus INNPM12 migration, then reconcile loop mode, addresses, cabling, redundancy, and system configuration.
How should a technician diagnose intermittent communication around INLIM03?
Separate module status, companion INBIM02 behavior, loop media, connector condition, and node visibility before deciding which component has failed.
Can INLIM03 be replaced with INNIS01 as a one-for-one board exchange?
No. ABB describes a combined later interface path, so a single-board swap is not established by that replacement statement.
What procurement evidence reduces risk when sourcing an INLIM03 spare?
Require exact model identity, board and connector condition, repair traceability, and confirmation that the offered item is not an adjacent bus-interface module.
How should INLIM03 communication be accepted after repair?
Confirm loop address, node visibility, message stability, redundant-path behavior where fitted, and recovery after the approved restart sequence.