
The replacement decision begins with what each channel must do, not with whether a candidate looks newer. The current OEM datasheet describes speed, speed-band, zero-speed, rotor-acceleration, and reverse-rotation channel options. It also states that the 3500/50M is not an independent speed-control or overspeed-protection device. That boundary affects engineering approval before any part comparison begins.
Use the current 3500/50M datasheet as the controlled reference for these functions, limits, ordering options, and warnings. Record its document number 141538 and revision with the project file instead of relying on an undated catalog excerpt.
| Required Duty | Evidence to Capture | Replacement Consequence |
|---|---|---|
| Speed or speed-band alarming | Full-scale rpm, events per revolution, alert setpoints, delays, recorder scaling, sensor type | Candidate must reproduce the range, pulse interpretation, alarm behavior, and outputs. |
| Rotor acceleration | rpm/min range, event count, alarm level and delay, peak value use | Acceptance must include both speed and acceleration response, not only a steady rpm point. |
| Zero Speed | Two-channel configuration, proximity-probe evidence, zero-speed threshold, start/stop sequence | Reject magnetic-pickup use for this channel type under the current OEM warning. |
| Reverse Rotation | Two probes, physical order around the shaft, channel assignment, forward direction, reverse logic | Swapping channels or probe order can reverse the conclusion; preserve the complete relationship. |
| Conditioned Keyphasor to rack backplane | Enabled state, dependent monitor slots, System 1 or other diagnostic use, phase-reference requirement | The review expands from one module to every downstream consumer of the conditioned signal. |
| Speed control or overspeed trip | Control narrative, cause-and-effect, trip voting, safety requirement | Reject the 3500/50M as the sole control or overspeed-protection solution and route to the approved protection architecture. |
Maintenance should own the installed hardware photographs and field history. Instrumentation or controls engineering should own the channel configuration, sensor signal, relay logic, and Keyphasor dependency map. Reliability engineering should own the measurement duty and acceptance criteria. Procurement should own candidate identity, condition, source, commercial lead time, and document package. Any missing field remains Unknown until its owner closes it; a supplier assumption is not an engineering record.
A tachometer card is one element in a signal chain. Photograph and record the target feature on the shaft, the transducer, field wiring, rear I/O, front monitor, rack interface, alarm path, buffered or recorder output, and backplane consumers. This prevents a candidate from passing a label comparison while failing the actual application.
Record whether each channel receives a proximity transducer signal or a magnetic pickup, the sensor model, its power source, mounting location, pulse target, normal amplitude, polarity, threshold method, hysteresis, and events per revolution. The current datasheet permits up to two transducer inputs, but the permitted channel function is not identical for every sensor type. OEM stop rule: Do not use magnetic pickups for the Reverse Rotation or Zero Speed options. The OEM warns that their low-speed edge behavior can produce false direction indications. A magnetic pickup that works for ordinary speed measurement is therefore not evidence that it is acceptable for these two duties.
Zero Speed and Reverse Rotation use both channels, so the approval record must retain channel-to-probe identity rather than merely listing two sensors. For direction, include a shaft-view sketch showing the defined forward direction, the physical order of Probe A and Probe B, terminal numbers, and their channel assignments. For zero speed, retain the operating sequence and threshold evidence. If either relationship is uncertain, do not infer it from wire color or terminal proximity.
| Chain Element | Installed Evidence | Owner | Status / Trigger |
|---|---|---|---|
| Machine duty | Machine tag, train, shaft, normal and transient speed range | Reliability | Reopen after process or driver change |
| Pulse target | Notch/tooth count, events per revolution, forward direction sketch | Mechanical / Reliability | Reopen after rotor work |
| Transducer | Model, proximity or magnetic, supply, waveform or amplitude record | Instrumentation | Reopen after sensor replacement |
| Field wiring | Cable ID, shield, polarity, channel terminals, isolation or barrier path | Instrumentation | Reopen after rewiring |
| Rear I/O | Complete number, termination type, barrier status, rear-slot photo | Maintenance | Unknown blocks approval |
| Front monitor | 3500/50 or 3500/50M, complete number, hardware and firmware | Maintenance / Controls | Unknown blocks direct-replacement claim |
| Rack context | Slot, 3500/20 or 3500/22M, rack configuration and software versions | Controls | Reopen after interface or software change |
| Consumers | Relays, gateways, recorder outputs, System 1, backplane Keyphasor users | Controls / Reliability | Reopen after logic or monitoring change |
The comparison must use full part numbers and controlled documents for both the installed and candidate assemblies. The 3500/50 family name does not identify the front hardware revision, rear I/O type, termination architecture, approval option, or firmware. The OEM's product history notes that the 3500/50M was released with waveform support, but that historical difference is not a blanket replacement approval.
The OEM 3500 evolution timeline records the M-series waveform milestone. The current datasheet separately defines today's 3500/50M ordering and system-version requirements. Use both sources for context, but use the controlled project and OEM documents applicable to the installed unit for the actual disposition.
The current OEM spare-parts table identifies 136703-01 as the Discrete Internal Barrier I/O Module with Internal Terminations. It is not a generic rear I/O for every 3500/50 or 3500/50M installation. A candidate using 136703-01 requires evidence that the installed application was designed for the internal-barrier architecture, that the associated field circuit and grounding meet the controlled installation drawing, and that project hazardous-area approvals remain valid.
Consult the OEM internal-barrier datasheet and the project-specific certified drawings before accepting this option. Physical fit or connector similarity is not sufficient evidence.
| Comparison Field | Installed Assembly | Candidate Assembly | Operational or Procurement Impact |
|---|---|---|---|
| Front identity | Complete 3500/50 or 3500/50M part number; revision | Complete part number; revision | A series name alone cannot establish equivalence. |
| Rear I/O | Complete number; internal, external, TMR, or internal barrier | Complete number and matching architecture | May require I/O, ET blocks, cables, drawings, and recertification. |
| Measurement duty | Speed, band, acceleration, zero speed, reverse rotation | Supported configured channel type | Wrong duty changes alarms, measured values, and test method. |
| Transducer path | Sensor type, supply, pulse amplitude, events/rev | Permitted input and conditioning | Magnetic pickup is prohibited for reverse or zero speed. |
| Rack interface | 3500/20 or 3500/22M plus firmware | Required interface and firmware | Current 3500/50M is not compatible with any 3500/20 version. |
| Configuration tools | Software versions and backup file | Required versions and conversion path | Unknown versions require engineering review, not an automatic upgrade recommendation. |
| Backplane Keyphasor | Enabled state and dependent slots | Equivalent conditioned signal and tested consumers | A missing or changed reference can affect synchronous measurements elsewhere in the rack. |
| Outputs and approvals | Buffered, recorder, alarms, hazardous-area evidence | Equivalent outputs and current approvals | May change wiring, data paths, FAT/SAT scope, or purchase package. |
| Status | Use It Only When | Required Output |
|---|---|---|
| Acceptable | Every installed and candidate field is documented, OEM requirements are met, and no function, I/O, interface, approval, or dependency changes | Approved comparison record and test plan |
| Conditional | A defined change such as rear I/O, termination hardware, software, firmware, or configuration is permitted and fully engineered | Change list, owner, rollback plan, and approval signatures |
| Engineering Review | Any part number, rack interface, firmware, sensor path, Keyphasor consumer, safety role, or approval remains Unknown | Open-question register and responsible engineer |
| Reject | The candidate conflicts with an OEM warning, required measurement, 3500/20 compatibility, sensor restriction, barrier architecture, or project certification | Recorded rejection reason; do not purchase |
The 3500/50M can be configured to place conditioned Keyphasor signals on the rack backplane for other monitors. That capability may eliminate the need for a separate Keyphasor module in a specific design, but it also means a tachometer replacement can affect more than speed indication. Approval requires a consumer map, not a yes-or-no checkbox.
The 3500 system datasheet describes the tachometer's place in the protection system and repeats the warning that the module is not intended for overspeed protection. Use the rack configuration and project drawings to identify the actual consumers in the installed rack.
Stop condition: If the team cannot identify who consumes the conditioned backplane signal, classify the replacement as Engineering Review. Do not disable the output, add a separate Keyphasor module, or change channel assignments merely to make the candidate fit.
A successful hardware fit can still change the measurement if configuration evidence is incomplete. Save the readable rack configuration, screenshots or exports of both channels, firmware and software versions, alarm logic references, and the current peak-hold values before work begins. A printed summary alone is not a substitute for a restorable configuration backup.
| Configuration Record | What Must Be Preserved | Acceptance Evidence |
|---|---|---|
| Channel type | Speed, Speed Band, Rotor Acceleration, Zero Speed, or Reverse Rotation | Installed and restored selections match the approved design |
| Input conditioning | Auto/manual threshold, hysteresis, events per revolution, full-scale rpm | Traceable input crosses the expected points without false counts |
| Alarm behavior | Setpoints, delays, latching or relay associations, bypass state | Alarm and downstream logic operate at documented test points |
| Direction logic | Probe order, channel assignment, defined forward direction | Forward and reverse simulations produce the correct state |
| Zero-speed logic | Threshold, transition behavior, operating sequence | Run-down or approved simulation proves the intended indication |
| Peak hold | Highest speed, reverse peak, or reverse rotation count; reset authority | Pre-change values archived and post-test reset documented if authorized |
| Outputs | Buffered transducer and 4 to 20 mA recorder scaling where used | Measured output agrees with the configured value and downstream display |
| Backplane output | Conditioned Keyphasor enablement and consumer assignment | Each dependent monitor or system receives valid data |
For adding the current 3500/50M to an existing system, the current OEM datasheet lists 3500/22M firmware revision 1.70, 3500/01 Configuration Software 4.20 or later, 3500/02 Data Acquisition Software 2.52 or later, 3500/03 Display Software 1.52 or later, and 3500/50M firmware revision 5.30 or later. It also states that the 3500/50M is not compatible with any version of the 3500/20.
Treat those values as documented gates for the current product, not as permission to perform an unplanned software or firmware upgrade. If the installed versions are unknown or outside the stated requirements, record the gap, identify the controlled upgrade or alternate-replacement path, and obtain engineering approval before procurement.
The purchase request should contain enough evidence for a supplier to identify the candidate and enough engineering context for the plant to approve it. Amikon Limited supports current and legacy industrial automation sourcing, but our quote cannot replace the customer's compatibility and safety approval. Availability, condition, lead time, warranty scope, and included accessories must be confirmed in the current quotation.
Use Amikon technical resources to organize front/rear identification, review the 3500 System category, and send the completed evidence package to the Amikon contact team. Do not send only '3500/50' or '136703-01' and ask for a guaranteed match.
| Approval Gate | Required Evidence | Owner | Decision |
|---|---|---|---|
| 1. Duty | Channel function, machine range, alarm or annunciation role, explicit overspeed boundary | Reliability | Pass / Fail / Open |
| 2. Input | Transducer type, pulse geometry, signal evidence, two-channel relationship | Instrumentation | Pass / Fail / Open |
| 3. Assembly | Front and rear photos, complete numbers, I/O and barrier architecture | Maintenance | Pass / Fail / Open |
| 4. Platform | 3500/20 or 3500/22M, firmware, configuration software, rack backup | Controls | Pass / Fail / Open |
| 5. Dependencies | Backplane Keyphasor consumer map, relays, recorder, gateway and System 1 paths | Controls / Reliability | Pass / Fail / Open |
| 6. Commercial | Candidate photos, revision, condition, quantity, included I/O/accessories, lead time and warranty | Procurement | Pass / Fail / Open |
| 7. Execution | Approved procedure, permits, bypass plan, rollback part, test equipment and witnesses | Operations / EHS | Pass / Fail / Open |
Commissioning must prove the configured measurement and every affected output, not merely an OK LED. Testing should be executed under the site's approved electrical, machinery-protection, bypass, and return-to-service procedures.
| Test | Acceptance Evidence | Result / Record |
|---|---|---|
| Module health | OK, TX/RX, bypass state, rack alarms, diagnostics and communication are normal | Pass / Fail; screenshot and timestamp |
| Input identity | Each traceable input appears on the intended channel with correct polarity and event count | Pass / Fail; equipment ID and calibration due date |
| Speed range | Indicated rpm and recorder value agree at approved low, normal, and high test points | Measured versus expected values |
| Acceleration or speed band | Dynamic input crosses the configured condition and produces the expected measurement and alarm | Trend or test curve plus alarm log |
| Zero speed | Approved transition test proves the intended threshold and indication without false state | Time-stamped transition record |
| Direction | Two-channel simulation proves forward and reverse states and the defined shaft direction | Channel/probe map plus state record |
| Alarm and relay chain | Alert, Danger or configured annunciation and downstream relay/DCS behavior match cause-and-effect | Witnessed functional result |
| Buffered and recorder outputs | Front/rear buffered signals and 4 to 20 mA outputs match configuration where used | Measured output and load |
| Backplane consumers | Every dependent monitor, gateway, display or System 1 path receives valid speed/phase data | Consumer-by-consumer signoff |
| Peak hold and restoration | Peak values, reset action if authorized, bypass restoration and final configuration checksum are recorded | Final signed SAT record |
Define failure and rollback criteria before the test. Any unexpected direction state, missing Keyphasor-dependent value, altered alarm behavior, unexplained diagnostic, or inability to restore the approved configuration is a failed acceptance, even if the tachometer displays plausible speed.
No. The current OEM spare-parts table identifies 136703-01 as a discrete internal-barrier I/O module with internal terminations. It is suitable only when the complete installed design, field circuit, grounding, controlled drawing, and approvals support that architecture. Compare the exact installed rear I/O before requesting it.
No under the current OEM guidance. The 3500/50M datasheet warns against magnetic pickups for Reverse Rotation and Zero Speed because their low-speed signal edge can cause false direction indications. Confirm a permitted proximity-transducer arrangement and the required two-channel relationship instead.
It can in a correctly engineered configuration because the 3500/50M can supply conditioned Keyphasor signals to the rack backplane. That capability is not automatic proof of equivalence. Confirm the enabled channel, signal quality, all backplane consumers, rack interface, configuration, and consumer-level acceptance tests.
No according to the current 3500/50M datasheet, which states that the module is not compatible with any version of the 3500/20. Record the installed rack interface before purchasing. A change to the rack interface is a separate engineered scope, not a minor tachometer swap.
No. The OK LED supports module-health assessment but does not prove channel identity, rpm accuracy, direction, zero-speed logic, alarms, relay behavior, buffered or recorder outputs, or conditioned Keyphasor delivery. Acceptance requires traceable functional evidence and signatures for every affected path.
Before requesting a 3500/50 or 3500/50M replacement, assemble front and rear photographs, complete part numbers, rack interface and firmware, transducer and pulse details, both channel assignments, the configuration backup, Keyphasor consumer map, required approvals, and the acceptance plan. Mark every gap Unknown and assign an owner. Amikon Limited can then quote the identified hardware and commercial terms while your engineering team retains the compatibility and return-to-service decision.


Need an automation or control part quickly?
Copyright Notice © 2004-2026 AMIKON is operated by Amikon Limited. Amikong.com is the company's official website and primary domain.
Disclaimer: Amikon Limited is an independent supplier and is not authorized by or affiliated with any manufacturer. Products may have older date codes, and OEM warranties do not apply. Firmware is not guaranteed; customers are responsible for obtaining any required firmware or licenses and complying with applicable End-User License Agreements.
Cookies
Individual privacy preferences
We use cookies and similar technologies on our website and process your personal data (e.g. IP address), for example, to personalize content and ads, to integrate media from third-party providers or to analyze traffic on our website. Data processing may also happen as a result of cookies being set. We share this data with third parties that we name in the privacy settings.
The data processing may take place with your consent or on the basis of a legitimate interest, which you can object to in the privacy settings. You have the right not to consent and to change or revoke your consent at a later time. This revocation takes effect immediately but does not affect data already processed. For more information on the use of your data, please visit our privacy policy.
Below you will find an overview of all services used by this website. You can view detailed information about each service and agree to them individually or exercise your right to object.
You are under 14 years old? Then you cannot consent to optional services. Ask your parents or legal guardians to agree to these services with you.
Leave Your Comment