Description
Key Technical Specifications
| Parameter | Specification |
|---|---|
| Manufacturer | ABB / Bailey |
| Model | NTLS01 |
| Product Type | Network Link Slave Module |
| System Compatibility | Bailey INFI 90 / Symphony DCS |
| Network Protocol | INFI-NET communication highway |
| Form Factor | Single-slot module for INFI 90 Module Mounting Unit (MMU) |
| Front Panel Diagnostics | LED status indicators for link health and fault identification |
| Mounting | DIN-rail style MMU chassis slot |
| Communication Role | Slave node on INFI-NET loop |
| Condition | New surplus / tested used (verify per unit) |
Product Introduction
If you’ve ever walked into a control room where the INFI-NET loop was chattering with intermittent faults, you know the panic that sets in when a network module starts blinking red. The NTLS01 is one of those unheralded workhorses — it doesn’t do flashy math or run PID loops. It just keeps the loop talking. And in a DCS, that’s everything.I’ve pulled these out of racks that had been running since the late ’90s. The hardware itself is straightforward: a single-board module that slots into the MMU, connects to the INFI-NET coax or twinax, and acts as a slave node for whatever local controller or I/O cluster it’s serving. No firmware updates to chase. No software licenses. It either talks or it doesn’t. That simplicity is why these things lasted decades. The revision you get matters — some early boards are finicky about termination and grounding. But when it’s matched correctly, it’s dead reliable.
Quality SOP & Tech Pitfalls
The Lab Report (SOP):
Every unit goes through the same gauntlet before it ships. Visual inspection first — I’m looking for burned traces, corroded connectors, or reworked solder joints that scream “field repair.” Then a counterfeit check against known Bailey part markings. Live test on an INFI 90 test rack: verify the module seats, powers up, and registers on the loop. Insulation resistance check with a Fluke 1507. Firmware/revision logged. Finally, anti-static bag with desiccant, sealed with a tamper label.The Engineer’s Warning (Pitfalls):
Here’s where people get burned. They swap an NTLS01 without checking the loop address dip switches or the termination jumper on the adjacent module. I once watched a plant lose half their loop because someone yanked a slave module and forgot that the loop needed to be re-terminated at the new endpoint. The whole network went into a reflection nightmare. Thirty minutes of downtime for a five-second jumper check. Also: don’t assume all NTLS01 revisions are identical. Some handle loop baud rates differently. Verify before you hot-swap.
Installation & Configuration Guide
1. Pre-Installation ⚠️
- Shut down the affected loop segment if hot-swapping is not supported by your system configuration.
- Photograph everything: dip switch positions, jumper settings, cable labels, and the module nameplate.
- Verify loop address — write it down. This is the number one cause of post-swap communication failures.
2. Removal
- Label each cable before disconnecting.
- Release the MMU locking screws or DIN clips carefully — these old racks are brittle.
- Slide the module straight out. Don’t wiggle it. The backplane pins bend easily.
3. Installation
- Copy all dip switch and jumper settings from the old module to the new one. This step alone prevents the vast majority of startup failures.
- Seat the module firmly into the MMU slot. You should feel the backplane connector engage.
- Reinstall locking screws. Reconnect cables per your labels.
4. Power-On & Testing
- Restore power to the MMU.
- Watch the LED sequence: power LED first, then link status. A steady green means you’re good. Flashing or red means check your address and termination.
- Verify communication from the operator station. Confirm the node appears on the loop map.
- Run a loop health check if your system supports it.
Compatible Replacement Models
| Model | Compatibility Tier | Notes |
|---|---|---|
| NTLS01 (same revision) | ✅ Drop-in Replacement | Exact match. Verify revision code on nameplate. |
| NTLS02 | ⚠️ Verify Compatibility | Later revision in the same family. May require loop address reconfiguration. Confirm with OEM documentation. |
| INNIS01 / INNIS21 | ❌ Not a Direct Replacement | These are Network Interface Slave modules with a different role in the INFI 90 architecture. Do not substitute without engineering review. |
Frequently Asked Questions (FAQ)
Can I hot-swap an NTLS01?
It depends on your loop configuration. INFI-NET was designed with some hot-swap capability, but pulling a slave node can still cause a momentary loop disturbance. If the loop is carrying critical control data, schedule the swap during a maintenance window. Better safe than sorry.How do I know if my NTLS01 is bad?
Front-panel LEDs are your first clue. No power LED means check the MMU slot and backplane. Link LED flashing or off means check your loop address, termination, and cabling. If the module powers up but doesn’t appear on the loop, try a different MMU slot first — rule out the chassis before condemning the board.Is the NTLS01 still available new from ABB?
No. It’s been obsolete for years. What’s on the market is new surplus (factory sealed, old stock) or tested used/refurbished. Always ask for the revision code and a photo of the nameplate before buying.What’s the difference between NTLS01 and NTCL01?
Completely different animals. NTLS01 is a Network Link Slave module. NTCL01 is a Communication Link Termination Unit — it terminates the end of an INFI-NET loop. Swapping one for the other will not work. Don’t do it.Do I need to reconfigure the loop after replacing an NTLS01?
If you copied the dip switch settings correctly, no. The loop should see the new module as the same node. If communication doesn’t restore, double-check the address switches and the termination jumper on neighboring modules.What warranty do you offer?
Standard is one year on new surplus and tested units. Refurbished or as-is units may carry a shorter warranty. Confirm before ordering.




Tel:
Email:
WhatsApp: 
