how to fix Metcal MX-5000 cartridge not detected when SmartHeat handle is seated
| Controller | Soldering and Rework Station Error Codes. Hakko, Weller, JBC, Metcal, 2026 |
|---|---|
| Category | Industrial Error Codes |
| Guide type | Procedure |
| Skill level | Beginner to intermediate field service tech |
| Time | 5 - 30 minutes including verification |
When how to fix Metcal MX-5000 cartridge not detected when SmartHeat handle is seated hits you on Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 mid-shift, the first instinct is to cycle power on the controller or hit the master reset. Most of the time you do not have to. The steps below are what a maintenance engineer would do at the cell panel before escalating to the OEM hotline - I keep a fault-history notebook per machine so the working state and parameter set are always reproducible.
What how to fix metcal mx-5000 cartridge not detected when smartheat handle is seated actually involves on Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026
On Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 the kit I reach for first includes DMM in low-ohm mode to measure tip heater resistance (Hakko T18 spec 8 ohm), thermal IR camera for handle/cartridge hotspot, Weller WCU calibration unit. Each of these surfaces a different layer of the fault - keep at least the first one in your fault-history notebook so the next time this happens you do not start cold.
For verification on Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026, the methods that survive contact with a real second-shift production workload are measure tip heater resistance with handle disconnected (Hakko T18 spec: 8 ohm +/-10 percent at room temp) and run Weller WE1010 calibration via OFFSET menu against a calibrated thermometer. Anything less than that and you are shipping on vibes.
Authoritative sources for Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 that I cross-reference before committing to a fix: weller-tools.com/us/en/industrial/service, okinternational.com (Metcal parent), jbctools.com/troubleshooting-soldering-station.html. OEM marketing brochures and trade-press writeups are signal, not ground truth.
The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the cabinet.
Diagnose first, fix second
Seventh: run the dedicated diagnostic option for whichever subsystem the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 alarm points at. Drive suspected? Force a servo discharge and re-energize from the drive panel, then check the drive status LEDs for the green ready signal and the last-fault timestamp. Encoder suspected? Power down fully (lockout-tagout), check the encoder battery voltage at the back of the controller, re-home the axis on power-up. Cable suspected? Pin-check the encoder cable continuity end-to-end with a meter (EtherCAT or Profinet drop = use a cable tester, look for an LED link light at both ends). Each of these surfaces config that the controller silently inherits from a previous session, and 90 percent of "this used to work yesterday" reports trace to a stale parameter or a vibrated-loose connector. Capture the result of each step in your notes alongside the timestamp so you do not redo the discovery the next time.
Eighth: diff the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 setup against its last known good state. Ask the obvious question - what changed in the 72 hours before the fault started? Did the controller take a firmware update overnight (check the About panel for the firmware revision vs the previous version you wrote down in your notes)? Did you swap a drive, a motor, an encoder cable, or a fieldbus drop? Did you change a tool offset, a work offset, a vision job, or a recipe? Did the maintenance team push a new PM checklist, swap a lube reservoir, or change a coolant concentration? Use the in-controller audit trail (Fanuc PARAM history, KUKA KRC log, Cognex In-Sight job version) to anchor "before vs after" so you are not guessing. Cross-check the OEM service bulletin and the OEM community forum for the exact firmware revision - if a regression hit a batch of cells in the same week, the community catches it before the official bulletin admits it. Record the suspect ranking, then disprove suspects one at a time with the cheapest test first (parameter restore before drive swap, encoder battery check before encoder swap).
Fifth: replay the failing run against a second axis or a second controller on the same Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 cell. The point is to isolate "this drive" from "this controller" from "the whole cell." If a teammate identical sister-machine works but yours does not, the failure is local to the parameter set or the encoder cable. If the same program faults on every controller in the same cell, you have a cell-wide config change or an OEM-side firmware quirk. Pin the controller firmware version explicitly while you do this: the controller About panel, the firmware hash in the parameter dump, or the system version returned by a SCPI *IDN? query. The version pin is what isolates "the OEM update broke us" from "this machine is on an older firmware than the rest of the cell."
Field notes from real Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 callouts
I keep oscilloscope on heater drive line for PWM dropout capture in my service kit whenever I am on a Soldering and Rework Station Error Codes call; nothing beats a known-good reading taken at the terminal block. On any Electronics fault inside Soldering and Rework Station Error Codes, the first three questions I ask are: which firmware rev, which I/O card, and what was the last commissioning change. Defaults drift between releases.
The verification step I never skip on Soldering and Rework Station Error Codes work is `run Weller WE1010 calibration via OFFSET menu against a calibrated thermometer`; the HMI will happily show "Normal" while the field device is still latched in fault. For Electronics jobs I keep a battered field notebook of "what bit me on Soldering and Rework Station Error Codes and how I cleared it", writing it down the first time has saved me a dozen overnight returns.
Tools I actually reach for
For most Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 faults I start with DMM in low-ohm mode to measure tip heater resistance (Hakko T18 spec 8 ohm), fall back to Hakko FG-102 tip thermometer with logger, Weller WCU calibration unit, JBC TM-1A tip thermometer, thermal IR camera for handle/cartridge hotspot when DMM in low-ohm mode to measure tip heater resistance (Hakko T18 spec 8 ohm) cannot surface the answer, and keep Hakko FG-101 thermometer for tip temperature verification handy for the cases where neither answers. That ordering is not academic - it matches the layers of the fault as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the alarm screen is still open, not after I have already cycled controller power.
Verification I run before I call it fixed
Before I mark a Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 fault resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.
check JBC handle metal contacts with isopropyl alcohol before re-cradlingIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
log idle-to-setpoint recovery time and compare to spec sheetIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
run Weller WE1010 calibration via OFFSET menu against a calibrated thermometerIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
verify Metcal SmartHeat cartridge by swapping into a known-good handpieceOnly when every line above runs clean do I close the loop and update my fault-history notebook with the timestamps.
Where I check first when the docs disagree
When two sources contradict each other on a Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 detail, the disambiguation order I lean on is stable. I usually check weller-tools.com/us/en/industrial/service for the ground-truth view on this part of Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026. I usually check metcal.com/support for the ground-truth view on this part of Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026. I usually check hakko.com/english/support/maintenance for the ground-truth view on this part of Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026. I usually check jbctools.com/troubleshooting-soldering-station.html for the ground-truth view on this part of Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026. OEM marketing brochures and trade-press writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.
Solution-focused remediation path
If the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 symptom started after an overnight firmware update, a drive swap, or a parameter edit, treat firmware and parameter set as the prime suspect. Roll the controller back to the previous firmware if the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 OEM supports rollback (most do via the maintenance bootloader). Restore the saved parameter set from your last known good backup (Fanuc all-parameter PUNCH OUT, KUKA archive, Cognex In-Sight job export) and rerun the program. If both rolled-back firmware and restored parameter set still fault with the same alarm and the same drive, you have a hardware-level or wiring issue. Decision point: if the rolled-back firmware still faults and the cell is under an OEM service contract, open the OEM hotline with the alarm history dump; on an out-of-warranty cell the path is the OEM forum or r/soldering with a minimal reproduction. Save the working firmware revision to your notes so the next rollback is a one-line "pin to firmware X."
If the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller is slow, faulting on cached errors, or HMI-locked, work the cache and parameter stack in order. Cycle controller power per the OEM lockout procedure (master disconnect off, wait 60 seconds for bus discharge, master disconnect on), reboot, and re-home the axes. Clear the local fault history (most controllers expose this under Maintenance -> Clear faults, or Setup -> Reset alarms). Re-load the saved parameter set with the OEM utility (Fanuc PARAM RESTORE, KUKA archive restore) to bypass any local parameter drift. Always capture timing before the cycle: time how long the failing cycle takes three times, write it down, then repeat after the parameter restore so the delta is provable in your notes. Decision point: managed-cell issues go through your controls engineering team for a cell-wide config push; standalone-cell issues go through the OEM diagnostic utility before you escalate to the OEM hotline.
Before any destructive step on a Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 cell, slow down and stage rollback. Snapshot the current firmware revision, the current parameter set (PARAM PUNCH OUT, KUKA archive, Cognex job export), the current ladder and HMI screens, the current I/O mapping, and the current member-roster of teach pendants registered to the cell to a notes entry first. Capture the failing photo, the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 alarm history dump, and the timestamp window. Photograph the cell from two angles: the controller HMI showing the alarm, and the cabinet showing the drive status LEDs. Then do the destructive step (clear a parameter, swap a drive, remove a teach pendant, restore a backup) inside a maintenance mode or a sister cell first, never the production cell directly. Capture the firmware revision, the safety-PLC permissions, the connected-pendant list, the cell operator roster, and the relevant fieldbus log snapshot to your notes before the destructive step. Decision point: if the cell is under an OEM service contract, the cheapest correct path is almost always to open the OEM hotline in parallel with the rollback - the OEM service engineer can confirm whether an OEM-side firmware push is responsible while you are still staging the change, which avoids a needless parameter edit if the fix is in the next firmware revision.
Automate this fix so you do not do it twice
Scrape Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller alarm history + fieldbus log via scheduled job
For the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026, cell faults usually surface as drive alarms, fieldbus dropouts, or vision-trigger misses before a full line stoppage. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with firmware updates, parameter edits, and OEM bulletins without staring at the HMI live. Register the task via cron on a plant-floor logger PC (Linux IPC), Windows Task Scheduler (schtasks /create /XML) on an engineering workstation, or a GitHub Actions schedule against a cell-controller API, then write the CSV to a plant file share or the fab MES for retention. Subscribe a simple dashboard (Grafana with a CSV source, Ignition with a tag history, the fab MES OEE report) to the same bucket so alarm events from every Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller converge on a single view without per-cell HMI clicking.
# Export the controller alarm history via the OEM API (if supported)
curl -X POST https://controller.plant.local/api/v1/alarm_history \ -H "Authorization: Bearer $CONTROLLER_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-25","end_date":"2026-06-01"}' \ -o soldering-alarm-history.json
# Export the cycle history for the last 7 days
curl -G https://controller.plant.local/api/v1/cycles \ -H "Authorization: Bearer $CONTROLLER_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o soldering-cycles.jsonMulti-cell rate-limit + retry policy via shared client wrapper
When the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 integration runs across multiple cells or controller types, every consumer needs the same backoff, jitter, and idempotency behavior or one noisy cell will starve the rest of the MES poller. Wrap the OEM SDK or fetch call in a thin client that reads the rate-limit headers (X-RateLimit-Remaining, Retry-After, x-ratelimit-reset), applies full jitter (base 200ms, cap 30s, max 5 retries), and de-dupes writes by a stable key (the controller cycle id, the fieldbus drop external id, the destination MES record id). Emit simple log lines tagged with the cell id so a fieldbus burst on one cell shows up in the same log as the downstream cascade.
# Python - soldering controller API wrapper with full-jitter retry
from tenacity import retry, wait_random_exponential, stop_after_attempt, retry_if_exception_type
import requests class RateLimited(Exception): pass @retry( wait=wait_random_exponential(multiplier=0.2, max=30), stop=stop_after_attempt(5), retry=retry_if_exception_type(RateLimited),
)
def call_soldering(method, path, token, payload=None): r = requests.request(method, f"https://controller.plant.local{path}", headers={"Authorization": f"Bearer {token}"}, json=payload, timeout=10) if r.status_code == 429: raise RateLimited(r.headers.get("Retry-After")) r.raise_for_status() return r.json()
Monitor + alert via Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 OEM diagnostic reports, alarm history, and plant dashboard ingestion
For the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026, the most useful long-running telemetry is the OEM diagnostic reports + alarm history shipped to a plant dashboard (Grafana with a CSV source, Ignition with a tag history, the fab MES OEE per SEMI E10, a Notion database via the API) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing cycle or runs the failing test sequence every 5 minutes from at least two cells) so a fleet-level regression lights up before teammates report it. Subscribe the on-call inbox or a private Teams channel to the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 OEM service bulletin (Atom/RSS or vendor portal webhook) plus the OEM service-status handle so an open bulletin self-correlates with the synthetic failures.
# Tiny synthetic monitor - hit the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://controller.plant.local/api/v1/me \ >> /var/log/soldering-synth.log sleep 300
done
Common pitfalls and what to watch for
Read-only validation before any write is the single step most Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Photograph every existing parameter page (the axis parameters, the spindle parameters, the safety parameters, the I/O mapping, the recipe library), capture the failing photo in a notes entry, export the relevant log to CSV if the controller supports it (the OEM diagnostic tool fault-history export, the PMC log download), and photograph the HMI alarm history showing the failing window before any change. On Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 cells with multiple operating modes (manual jog, MDI, auto) record the firmware revision, the parameter state, and the I/O mapping in each before toggling anything, because a "fix" pushed only to manual mode is a known regression vector when auto mode has a different interlock set.
The mirror-image mistake is confusing a cell-level symptom with an OEM fault on Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026. A persistent SRVO-023 is often a workpiece-level change pushed by the production team rather than a Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 bug. A "program not loading" can be a renamed program rather than a deleted one. A "trigger not firing" is frequently a vibrated-loose sensor cable or a contaminated lens rather than an OEM-side regression.
Verify the fix worked
- Reproduce the original faulting cycle against Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 on the same cell AND a sister cell with the same recipe. If the alarm or fault code still surfaces on any cell, you have not fixed it.
- Watch for 24 to 48 hours via the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller alarm history + the fieldbus log + your fault-history notebook. Cached fault states and stale fieldbus link state mask slow-burn drift and intermittent fieldbus issues.
- Smoke-test under realistic load: replay the cycle against a test workpiece for at least 30 minutes at your normal production feedrate, log success / alarm and the timestamp per attempt to a notes file.
- Capture the new state in a fault-history notebook entry so the next time this happens you do not rediscover it. Note firmware revision + parameter set + I/O mapping + failing photo + verbatim alarm string + fix applied. Push to a plant-wide maintenance wiki if your plant uses one.
- If the fix involved a maintenance-token rotation or a parameter set change, commit the new token to your password manager and photograph the parameter dump for archival.
Safety, rollback, blast radius
- Test in a Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 maintenance mode or on a sister cell first before any change that touches the production cell. Snapshot the firmware revision, the parameter set, the I/O mapping, and the safety-PLC permissions before changing anything.
- Apply the principle of least surprise when granting teach-pendant access or safety-PLC permissions. Review the operator roster against the people who actually need access - extra teach pendants are extra blast radius.
- Use idempotent cycles where the Soldering and Rework Station Error Codes, Hakko, Weller, JBC, Metcal, 2026 controller supports it (the OEM cycle-id de-dupe, external id keys on MES records) so a re-run cycle does not double-count parts or duplicate scrap records.
- Know your rollback path. Firmware rollback is a one-line OEM utility load; a maintenance-token rotation is reversible if you kept the old token in the password manager during cutover; a parameter set change is reversible only if you saved the previous archive.
- For cell-wide or plant-wide changes, line up a maintenance window with production scheduling before pushing through the OEM utility.
FAQ
References
- OEM service manual for Soldering and Rework Station Error Codes. Hakko, Weller, JBC, Metcal, 2026 (official service bulletins, alarm code reference, safety case)
- Controls-community forums (r/PLC, r/Robotics, r/CNC, r/Fanuc, r/KUKA, r/Cognex, r/labview, OEM community)
- In-controller diagnostic help and the Soldering and Rework Station Error Codes: Hakko, Weller, JBC, Metcal, 2026 firmware release notes
- OEM service-status portals and OEM hotline post-mortem reports
Related fixes
Related guides worth a look while you sort this one out:
- how to clear Metcal MX-5000 'OFL' over-limit fault during sustained heavy soldering
- how to fix Hakko FM-2027 handle sensor error when tip resistance reads 8 ohms
- how to fix Hakko FX-888D HEA tip heater open error with new T18 cartridge
- how to fix JBC CDB tool detection error when handle metal contacts are clean
- how to repair Metcal CV-5210 power module fault and red LED steady-on condition
- how to resolve JBC HDE hot air station short-circuit error on cartridge replacement