ABB NPBA-02 Profibus DP Adapter Module – ACS400/ACS500/ACS600 Spare, ODVA-PROFIBUS Conformant

Description

Technical Specifications

Main Features and Advantages

DP-V0 cyclic I/O with ABB Drives Profile overlay.​ The NPBA-02​ (58976024G) implements the PROFIBUS DP-V0 slave state machine — cyclic data exchange only, no acyclic services (no DP-V1 alarm/diagnosis, no acyclic parameter read/write). For the majority of drive integrations, this is sufficient: PPO type 2 (2-word control + 2-word status, the ABB default) gives the PLC a 16-bit Control Word (bits 0=OFF1, 1=OFF2, 2=OFF3, 3=Enable op, 7=ACK fault — same bit semantics across ABB’s FBA family), a 16-bit Reference (speed/torque % or rpm, scaled via drive params 11.02–11.06), a 16-bit Status Word (ready/running/fault/warning/alarm per bit), and a 16-bit Actual Value (motor speed default, switchable to current/torque via Group 51). PPO types 3, 4, 5 extend this to 4/4 or more words for multi-drive telegrams. A Siemens PLC programmer using SFC14/SFC15 (DP RD_REC/WR_REC) or the TIA Portal “ABB_Drive” GSD-derived FB can have a NPBA-02​ node live in an afternoon — the GSD file (ABB_08xx.gse / Vendor ID 0x0003) imports into STEP 7 / TIA, the scanner sees the node, PPO type is selected, and the I/O address range lands in the PLC’s PI/PQ image.Group 51 configuration, no DIP switches.​ Like its FBA siblings (NDNA-02​ DeviceNet, NETA-02​ Modbus TCP), the NPBA-02​ carries zero user-DIPs — everything is drive-parameterized. Group 51.01 = node address (1–125, must be unique on the Profibus trunk). Group 51.02 = PPO type (1–5). Group 51.03 = number of PPO words in the telegram (auto-filled by PPO type, but can be trimmed if the PLC wants fewer words). Group 51.04+ = optional extended mapping (some drive firmware revisions allow Actual Value source selection — speed/current/torque/frequency — through Group 51 rather than the main drive params). This means a NPBA-02​ bought today drops into an ACS600 commissioned in 2001 and an ACS800 commissioned in 2012 with no compatibility issue — the FBA 40-pin interface on RMIO has been stable, and Group 51 has been present since the earliest ACS600 FBA-supporting firmware. The only watch-out: very early ACS400 firmware (v1.x) had FBA bugs with PPO-5; ABB PCN recommended firmware ≥v2.2 for NPBA-02​ on ACS400 — a detail the spare buyer should confirm if the plant still runs early ACS400.BF/SF LED diagnostics per PROFIBUS standard.​ The two LEDs on the NPBA-02​ fascia follow the PROFIBUS specification: BF (Bus Function) blinks green at power-up while the scanner hasn’t assigned the node, goes solid green when the DP cyclic exchange is active (the “data exchange” state), and goes red on bus faults (trunk disconnected, 220 Ω terminator missing at one or both ends, baud mismatch, node-address conflict with another slave). SF (System Failure) is green when the NPBA-02​ itself is healthy (5 V present, FBA ribbon seated, no internal fault) and red when the module has detected an internal error (rare — the NPBA-02​ is mostly passive PHY + DP-V0 ASIC) or when the drive signals a “FieldBus fault” upstream (e.g., the PLC sent a PPO with wrong length, or the drive’s Group 51 mapping conflicts with the scanner’s configuration). A Siemens-trained maintenance tech can triage a NPBA-02​ node in 30 seconds at the drive door: “BF red, SF green” → check trunk terminators and node address duplicate; “BF green, SF red” → NPBA-02​ internal or drive-side Group 51 mismatch; “both red” → 5 V absent (NPOW/RMIO issue, not NPBA-02​ itself).Auto-baud across the full PROFIBUS envelope.​ The NPBA-02​ (58976024G) listens on the DB9 pins at power-up, detects the baud from the scanner’s preamble (the repeating “Request_FDL_Status” or the live token-pass pattern), and locks — no DIPs to mis-set when moving a spare from a 1.5 Mbps line (typical S7-400H PCS 7 cell) to a 12 Mbps line (S7-1500 + ET 200SP-IM). The DB9 pinout follows IEC 61158-2: Pin 3 = B (Data B, negative-going), Pin 8 = A (Data A, positive-going), Pin 5 = shield drain, Pins 6+9 often looped for the 220 Ω termination resistor + switch in some connector shells (though on NPBA-02​ the terminator lives on the Profibus trunk topology, not on the drive — the drive is a mid-trunk droop, not an endpoint, unless it’s the last node, in which case a 220 Ω terminator must be plugged onto the T-connector or built into the last T-piece). Maximum trunk length follows PROFIBUS spec: 1200 m at 9.6–93.75 kbps, 400 m at 500 kbps, 200 m at 1.5 Mbps, 100 m at 3–12 Mbps — the NPBA-02​ itself doesn’t limit this; it’s the trunk physics.Kit variant for retrofit (NPBA-02 + mounting).​ Like NDNA-02, the NPBA-02​ can be ordered as a module-only (for drives originally ordered with FBA, where the door already has the DB9 cutout) or as a kit (cover plate with DB9 cutout + mounting frame + FBA ribbon) for retrofitting into a drive that shipped without FBA. The 58976024G article is the module itself; the kit article would be a different order number (ABB’s kit numbering for FBA modules typically appends “-KIT” or a separate 3BSE… code). For plants auditing spares: if the drives on the floor are “FBA-ready” (door cutout present), stock NPBA-02​ (58976024G) modules only; if some drives are bare (no cutout), also stock the kit-frame + ribbon for that drive form (ACS400 door, ACS800-04 door, ACS800-01 bookcase — each has a different frame). The NPBA-02​ module itself is the same across all kits.Upgrade path to NPBA-12.​ The NPBA-02​ (58976024G) is DP-V0 only — no acyclic. If a plant later decides they want to read drive parameters (fault code 31.xx, motor temp, energy counters) or write parameters (change accel time, speed trim) from the PLC without stopping the drive, they need DP-V1 acyclic services, which means swapping the NPBA-02​ for an NPBA-12. The swap is drop-in — same 40-pin FBA, same Group 51 addressing, same DB9, same BF/SF LEDs — the NPBA-12​ just adds the DP-V1 state machine and a larger ASIC. The NPBA-02​ (58976024G) remains the right-cost choice for pumps, fans, conveyors, compressors where the PLC only needs Run/Ref/Status — which is roughly 70 % of ABB drive nodes in a typical plant.