Connects a supported RX3i controller to PROFINET devices and scanners.
Key Information
IC695PNC001-BFBE is an Emerson PACSystems RX3i PROFINET Controller. It provides the controller-side PROFINET interface for supported RX3i systems and distributed PROFINET I/O.
Emerson release information identifies IC695PNC001-BFBE as firmware 3.21, released in August 2022 for manufacturing-component updates. The exact BFBE suffix is therefore part of the controlled hardware and firmware identity.
Configuration, device names, network topology, MRP settings and controller compatibility should be preserved from the approved PAC Machine Edition project before exchange.
Functions
Maintains configured PROFINET device names, addresses and topology in the controller project.
Supports the diagnostics and network-management functions documented for the installed PNC001 firmware.
Keeps firmware 3.21 and the BFBE hardware identity traceable during replacement.
Specifications
| Manufacturer | Emerson |
|---|---|
| Exact model | IC695PNC001-BFBE |
| Platform | PACSystems RX3i |
| Module function | PROFINET Controller |
| Documented firmware | 3.21 |
| Release date | August 2022 |
| Release note | Manufacturing-component updates |
| Module family | IC695PNC001-Bxxx |
| Engineering environment | PAC Machine Edition; confirm project-version support |
| Revision control | BFBE suffix must remain on the quotation and replacement record |
Installation
- Export the controller project and record the PNC slot, LAN addressing, device names, MRP role and cable routing.
- Confirm the installed CPU firmware and PAC Machine Edition release support IC695PNC001-BFBE.
- Install only after control power, network consequences and remote-output states are covered by the approved procedure.
- Restore the approved configuration, then verify every configured device, alarm and redundancy path.
Lifecycle
- Retain the full BFBE label and firmware record with the project archive.
- Review Emerson release notes before moving between PNC001 suffixes.
- Preserve switch, ring and device-name records so a network fault is not introduced during exchange.
- Archive post-startup diagnostics and the final topology check.
About IndustryParts
https://www.industryparts.com/PROFINET identity stays linked to the approved project
IndustryParts handles IC695PNC001-BFBE with its firmware release, RX3i host and network topology visible from enquiry through acceptance.
- BFBE release retained
- CPU compatibility reviewed
- Topology evidence requested
Related Models
| 37CXL4G5I1 | MCS-325 | Entrelec 18-410051-001CC |
| CRN4-100 A-P-G-BUBE | CTA Center Tech BFL DN65 44607 001 PS16 | KH77B CT100LS4/BMG/HF/TF/ES1S |
| C2C-SA16510A10000 | PSI-MOS-RS232/FO | SFAM-90-10000L-TG1-2SA-M12 |
| 6DS1601-8BA | PNOZ s4.1 | 170M5149 |
| C200HE-CPU42-E | X20 AO 4622 Rev. N3 | TMSR-380-33-U-SB |
| PSR-SPP-24UC/ESAM4 | MN 452-11y-t-M20 | S75 |
| MX21747-040-00 | EL6631-0010 | 901-H510-WW00 |
| PCS245-NB-D24 | VLM-000-SIE | TK 355-20z |
| 045700 | 6FC5110-0BB01-0AA2 | E160X01 |
| 4574821 | BL0T3CW0H2 | SEW CMP50L/KY/AK0H/SM1 BSHF202 |
FAQ
Q01Can IC695PNC001-BFBE be ordered as IC695PNC001 alone?
Use the complete IC695PNC001-BFBE identity. The BFBE suffix maps to firmware 3.21 and should remain traceable in the quote, spare record and commissioning report.
Q02What evidence should accompany an IC695PNC001-BFBE enquiry?
Send the front and side labels, RX3i CPU and firmware, slot, PAC Machine Edition release, network drawing, MRP role, device count and required quantity.
Q03Can a later PNC001 revision replace IC695PNC001-BFBE without engineering review?
Do not assume it can. Compare Emerson release notes, CPU and project compatibility, firmware behavior, certifications and the approved network design.
Q04What network information must be protected before changing IC695PNC001-BFBE?
Protect the controller project, device names, IP settings, topology, ring configuration, alarm mapping and any application logic that reads network status.
Q05What proves IC695PNC001-BFBE is ready for service?
Confirm the exact release, clean module diagnostics, all configured devices connected, expected MRP state, stable I/O exchange and an approved control-response test.
