Key Technical Specifications
| Parameter | Specification |
|---|---|
| Manufacturer | IBA AG |
| Model | SM128V |
| Product Type | VMEbus fiber-optic signal interface module |
| Platform | ibaPDA / ibaLink VME-based acquisition system |
| Fiber-Optic Links | 2 output links (Tx) |
| Signal Capacity | 64 analog + 64 digital per link (128 total per link) |
| Bus Interface | VMEbus |
| Typical Use | Process data export from VME control systems to ibaPDA recorder |
| Compatible Receiver | ibaFOB-io, ibaFOB-4i(-S) fiber-optic input cards |
| ibaPDA Software Note | ibaPDA ≥ 5.20 requires assigning module type “SM128” per link for scaling support |
| Configuration | Defined in ibaPDA server I/O configuration |
| Status Indicators | Front-panel LEDs for link and module status |
Product Introduction
The IBA SM128V is one of those modules you find in older turbine halls, rolling mills, and test benches where ibaPDA was originally deployed on a VME chassis. It is not a standalone analog input card. Its actual job is to sit on the VME backplane, read a process image from the control system, and push up to 128 signals out over two fiber-optic links into the ibaPDA recorder.Engineers keep this module in service because replacing it means touching the entire acquisition chain: VME slot assignment, fiber-optic cabling, ibaFOB receiver cards, and the ibaPDA I/O configuration. The module itself is usually reliable. The problems come when someone swaps it without verifying the ibaPDA module type assignment. On ibaPDA 5.20 and later, each fiber link must be assigned to module type “SM128” if you want gain/offset scaling in real format. Use the older “ibaLink-SM-64-io” type and you lose that scaling capability entirely.
Quality SOP & Tech Pitfalls
The Lab Report (SOP)
- Visual inspection: VME front panel, fiber-optic connectors, backplane pins, and nameplate.
- Part-number verification: SM128V, hardware revision, and serial number.
- Counterfeit check: label quality, connector finish, and PCB build consistency.
- Insert into a known-good VME chassis for power-up.
- LED status check for module initialization and fiber link activity.
- Fiber-optic output verification using an ibaFOB receiver card and ibaPDA server.
- Signal count verification: confirm 64A + 64D per link in the ibaPDA I/O manager.
- Scaling test: verify gain/offset behavior when module type is set to “SM128.”
- Configuration comparison against the existing ibaPDA backup.
- Anti-static packaging with photographed serial numbers and fiber port labels.
The Engineer’s Warning (Pitfalls)
The biggest mistake is treating the SM128V as a generic “128-channel analog input module.” It is not. It is a fiber-optic bridge between a VME control system and ibaPDA. If the source system no longer writes the correct process image, the SM128V will happily transmit garbage — or nothing at all.The second mistake is ignoring the ibaPDA software version. On ibaPDA 5.20+, assigning the wrong module type (“ibaLink-SM-64-io” instead of “SM128”) disables real-format scaling. I have seen engineers spend two days chasing a “bad module” when the real problem was a single dropdown selection in the I/O configuration.
Installation & Configuration Guide
- Pre-Installation ⚠️
Follow plant safety procedures. Export the current ibaPDA server configuration. Photograph VME slot positions, fiber-optic cable routing, ibaFOB receiver card assignments, and existing I/O module settings in ibaPDA. - Removal
Label both fiber-optic cables (Link 1 and Link 2). Note the VME slot number. Power down the VME chassis if required by site procedure. Remove the module carefully and inspect backplane pins. - Installation
Install the SM128V into the same VME slot. Reconnect fiber-optic cables to the correct Tx ports. Verify that the receiving ibaFOB card is seated properly. Confirm the ibaPDA server I/O configuration matches the physical link assignment. - Power-On & Testing
Power up the VME chassis. Check front-panel LEDs for module status. Open ibaPDA server and verify signal presence on both links. Confirm analog scaling and digital state mapping. Run a live trend comparison against known process values. Only return to full recording after validation.
Compatible Replacement Models
- ✅ IBA SM128V (same hardware revision) — True drop-in if the VME slot, fiber links, and ibaPDA configuration match.
- ⚠️ IBA SM128V (different revision) — May require ibaPDA module type reassignment and scaling verification. Allow 1–2 hours for validation.
- ⚠️ IBA ibaNet-based acquisition modules (newer platform) — Functionally equivalent for ibaPDA recording but require Ethernet/ibaNet infrastructure, new configuration, and potentially new receiver hardware. Not a drop-in replacement.
- ❌ Generic VME analog input cards — Not compatible. The SM128V is an iba-proprietary fiber-optic interface, not a standard VME I/O module.
Frequently Asked Questions (FAQ)
Is the SM128V still produced by IBA?
No. It is a legacy VME-era module. IBA has moved to Ethernet/ibaNet-based acquisition hardware for new installations. Treat it as a legacy spare.Can I use it with modern ibaPDA versions?
Yes, but ibaPDA 5.20 and later require assigning module type “SM128” per fiber link to enable gain/offset scaling. Older versions use “ibaLink-SM-64-io” without scaling support.Does it accept analog sensors directly?
No. The SM128V does not condition field sensors. It reads a process image from the VME backplane and transmits it over fiber optics to ibaPDA. The actual analog/digital signals come from the control system, not from field wiring on the SM128V itself.What happens if I swap the two fiber cables?
The signal mapping will be wrong. Link 1 and Link 2 carry separate 64A + 64D groups. Swapping them will shift every signal by 128 positions in the ibaPDA server.What fails most often on these modules?
Fiber-optic connector contamination, incorrect ibaPDA module type assignment, VME backplane pin damage, and lost configuration after server migration. The hardware itself is generally solid.Can I replace it with an Ethernet-based iba module?
Functionally yes, but it is not a drop-in swap. You would need new ibaNet hardware, new fiber or Ethernet cabling, and a full ibaPDA I/O reconfiguration. Plan for a proper migration project, not a hot swap.
