Independent CNC repair and technical reference Contact

FANUC 0i-F diagnosis 308/309: why check the Pulsecoder when the winding is cooler?

Published Updated

Diagnosis 308 and 309 report servo winding and Pulsecoder board temperatures. Record both for the same axis with the complete alarm and sampling times, rather than confusing different measuring points or post-stop readings.

Contents
  1. Scope and the two readings
  2. Build a comparable record first
  3. Use readings to choose the next investigation
  4. Hypothetical analysis: 308 at 92°C and 309 at 101°C
  5. Maintenance boundaries and handover
  6. Source and limitations

After a servo-axis overheat alarm, looking at just one “motor temperature” can misdirect the investigation. The winding and encoder board are different measuring points. A reading taken after stopping also cannot automatically represent conditions at the alarm. This article explains how to organize those two pieces of evidence, not how to select a replacement part from a temperature display.

Scope and the two readings

The reference is FANUC Series 0i-MODEL F Maintenance Manual B-64605EN/01, §1.3.2, printed p.19. This applies to configurations covered by that manual which actually support the temperature information. Identify the CNC, servo motor and Pulsecoder models first; do not transfer these definitions to other generations, spindles or arbitrary external detectors.

DiagnosisMeasuring pointAlarm temperature stated in this edition
308Servo motor winding140°C
309Printed circuit board inside the Pulsecoder100°C; the manual notes approximately 85°C for the air inside the encoder

Both readings use °C. The manual specifies temperature-information errors of ±5°C over 50–160°C and ±10°C over 160–180°C, and an alarm operating-temperature error of up to 5°C. These are manual specifications, not user-adjustable settings or permission to operate up to those temperatures. Approximately 85°C is neither a substitute alarm threshold for the 309 display nor an allowable cabinet or workshop ambient temperature.

Build a comparable record first

  1. Make safe before gathering evidence. Follow the machine builder’s alarm and safe-stop procedure. Save information only when safe and the display remains readable; do not delay stopping for a screenshot. Record the complete alarm number and text, axis, time and operation underway.
  2. Pair readings from the same axis. Save 308 and 309 with screenshots. If changing pages creates a time gap, record each time. Do not pair X-axis 308 with Z-axis 309, or substitute how the housing feels for an internal reading.
  3. Label the sampling stage. Distinguish alarm-time, post-stop and cooled-down records. If the first screenshot was taken minutes after stopping, explicitly mark the alarm-time temperature as unknown. Without a historical trend, do not reconstruct a peak.
  4. Attach existing operating records. Collect the preceding machining cycle, available load and environmental records, and recent maintenance, noting whether they cover the same period. Do not add load or repeatedly reset to reproduce the alarm.

Use readings to choose the next investigation

If 309 stands out while 308 is relatively low during the same period, first define the inspection scope around the encoder measuring point and its thermal environment. This does not prove failed encoder electronics. If 308 stands out, existing load, duty-cycle and heat-dissipation information become the next evidence to verify. If both are elevated, their common rise alone cannot identify a failed fan, bearing or cable. These are editorial suggestions for organizing evidence, not a manufacturer fault-isolation table.

For abrupt, missing or alarm-inconsistent readings, treat data validity as a separate question: check model applicability, selected axis, screenshot timing and accompanying alarms before qualified personnel decide whether the sensing path requires inspection. Do not record a blank or unsupported item as 0°C. Two low post-stop readings do not establish that the original alarm was false.

Hypothetical analysis: 308 at 92°C and 309 at 101°C

Suppose an axis on an applicable configuration reports overheating and, during the safe stop, 308=92°C and 309=101°C are recorded. These invented readings illustrate reasoning; they are not a field case or test results. Although 92°C is below the manual’s winding alarm temperature, 101°C is around the encoder-board alarm region. The conclusion “the winding is not hot, so the alarm must be false” is therefore unjustified.

Retain both readings and the complete alarm, verify sampling times, and focus further investigation on encoder temperature and the validity of its measurement. Given the stated errors, 101°C also does not prove an actual board temperature of exactly 101°C or justify replacing the encoder. A later decrease in 309 documents a change after cooling, not proof that the cause has been removed.

Maintenance boundaries and handover

Separate observations, hypotheses and open questions in the handover: for example, “309 elevated at stop; alarm-time peak unknown; thermal environment and sensing path need verification.” This is read-only diagnostic guidance. Do not alter protective parameters, bridge temperature circuits, connect or disconnect feedback wiring while energized or open the encoder. Cabinet access, electrical measurements, dismantling and return-to-service checks belong to qualified personnel following the machine builder’s procedure, including energy isolation and discharge requirements. A cleared alarm or lower temperature does not authorize machining to resume.

Source and limitations

FANUC Series 0i-MODEL F Maintenance Manual, B-64605EN/01, §1.3.2, printed p.19, “Motor temperature information.” This is a third-party public mirror of a FANUC-authored manual, not an official FANUC download site. Definitions and errors come from that edition; the recording method, investigation sequence and hypothetical analysis are editorial work. No machine testing was performed. Actual support and maintenance or restart requirements depend on the applicable model documentation and machine builder.

Related technical articles

FANUC 0i-F APZ loss: interpreting the cause records in diagnosis 310/311FANUC 0i-F automatic backup diagnosis 1016: completion is not recovery readinessFANUC 0i-F stalled automatic cycles: why diagnosis 0 is not the old 000–015 table