Description
3. Product Introduction & Engineering Value
Anyone who’s had to bolt custom logic or a protocol gateway onto an aging ControlLogix system knows the appeal of a SAM module: instead of building an external PC-based interface with its own cabling and failure points, you get a program running right in the rack with direct backplane access to the controller’s data — no separate network hop required for that connection.
The 56SAM-810 is OLDI’s Special Application Module built around Windows CE with 64MB of CompactFlash storage, and it slots into the same 1756 chassis as your ControlLogix processor and I/O. Per OLDI/Softing’s own description of the SAM line, these modules provide two Ethernet ports for communicating out to enterprise systems or HMI panels, while keeping the fastest read/write path — the backplane itself — reserved for talking to the ControlLogix controller directly.
4. Technical Specifications
Verified/documented parameters:
- Operating system: Windows CE
- Storage: 64MB CompactFlash
- Chassis compatibility: Allen-Bradley ControlLogix 1756 rack (backplane-based module)
- Manufacturer: Online Development Inc. (OLDI) — acquired by Softing; module family now marketed under Softing.us
- Network interfaces (SAM family, per manufacturer): Two Ethernet ports for external communications, separate from backplane data path
- Primary use case: Custom application hosting with direct ControlLogix backplane data access, commonly used by OEMs, systems integrators, and advanced end users
- Product status: Discontinued by manufacturer — sourced today via repair/refurbished channels
- Distinct from: Rockwell’s own native 1756-CMS-series Compute Modules (e.g., 1756-CMS1B1), which are a separate, Rockwell-manufactured product line with their own CPU/storage specifications — do not assume shared internals between these two module families
Not independently verified for this exact variant: processor type/speed, RAM capacity, backplane current draw, and physical module dimensions. If you have the OLDI 56SAM-810 datasheet or a nameplate photo, I’ll complete these accurately rather than estimating from the unrelated Rockwell CMS-series specs.
5. Field Application & The “Trench” Experience
Illustrative scenario — not a specific reported incident:
A common situation with legacy SAM modules: a facility running an older ControlLogix system needs to add a custom data-logging or protocol-translation function, and someone assumes any “ControlLogix compute module” will do, ordering a Rockwell-native 1756-CMS unit instead of matching the existing OLDI SAM programming environment already in use elsewhere in the plant. The two aren’t running the same software stack or programming model, so code written for one doesn’t simply transfer to the other — worth confirming which module family your existing custom applications actually target before assuming compatibility.
Specific application scenarios:
- Legacy protocol gateway duty, translating between an older serial-based subsystem and the ControlLogix backplane without adding external PC hardware to the panel
- Custom data historian/logging tasks running directly in the chassis, reducing the network round-trip needed to pull data for enterprise reporting systems
- HMI data-bridging in facilities where a lightweight in-chassis application is preferable to a full external server for a single-purpose data feed
56SAM-810
56SAM-810
6. Transparency SOP: QA & Testing
Generic verification framework for a used/refurbished SAM module:
- Visual and connector inspection — backplane connector condition, Ethernet port condition, CompactFlash card seating
- Power-up and OS boot verification — confirm the module boots into Windows CE correctly and completes its startup sequence
- Backplane communication test — verify the module establishes communication with a ControlLogix controller on a test rack
- CompactFlash integrity check — confirm the 64MB CF card reads/writes correctly, since this is the module’s only onboard storage
(General framework — substitute your actual documented QA process where it differs.)
7. The Veteran’s Tech Trap Guide
⚠️ Don’t confuse OLDI SAM modules with Rockwell’s native Compute Modules. They occupy a similar physical role (custom program execution in a 1756 chassis) but are different products from different manufacturers with different programming environments. Code and configuration aren’t interchangeable between them.
⚠️ 64MB of CompactFlash is a real constraint by modern standards. If you’re planning to run anything beyond the lightweight application this module was originally sized for, confirm your program and data storage needs fit comfortably within that limit before deploying.
PRO TIP: Since this part is discontinued and now supported through Softing (as OLDI’s successor) rather than the original manufacturer directly, confirm current support/repair channels before assuming legacy OLDI documentation or firmware sources are still actively maintained.
⚠️ Windows CE end-of-support considerations: Microsoft’s support lifecycle for Windows CE has long since ended industry-wide. If this module handles anything network-facing, treat it with the same network-isolation caution you’d apply to any other unsupported embedded OS still in service.
8. Dynamic FAQ
Q: Is this the same as a Rockwell 1756-CMS1B1 compute module?
No — the 56SAM-810 is a third-party module from Online Development Inc. (OLDI, now Softing), a separate product line from Rockwell’s own native ControlLogix Compute Modules. They serve a similar role but aren’t interchangeable.
Q: What operating system does this module run?
Windows CE, with 64MB of CompactFlash storage for the OS and application.
Q: Is this part still manufactured?
No — it’s discontinued. Current sourcing is through repair/refurbished channels; OLDI’s product line and support now fall under Softing.
Q: What warranty applies to a repaired/refurbished unit?
Varies by seller — some resellers list 2-year warranties on repaired stock; confirm the specific term with whoever you’re purchasing from.
Q: Does this module need special programming tools different from standard ControlLogix development?
Likely yes, given it’s a separate manufacturer’s module — confirm with Softing/OLDI documentation or your existing SAM-based applications before assuming standard Studio 5000 programming covers this module’s custom application layer.
Q: Can I upgrade the CompactFlash capacity on this module?
Not confirmed from available sources — check with Softing/OLDI support directly rather than assuming the CF card is user-upgradable, since some chassis-based modules from this era have fixed or vendor-specific storage configurations.
Start Chat
