Technical articles
Model-specific references for FANUC CNC systems, maintenance records and fault diagnosis.
“FANUC system” alone is not enough to select maintenance documentation. Using the 0i-F configuration screens, this guide explains how to record hardware, software series and editions, and associate screenshots with the machine nameplate and fault time.
Read article →Alarm history retains alarms; operation history can show some surrounding events. Neither replaces the other. Based on the 0i-D manual, this guide explains how to preserve times, axis identifiers and operator actions before clearing away diagnostic clues.
Read article →Before investigating FSSB faults, save the line, slave and axis relationships recognized by the system. For 30i/31i/32i-B, this article explains the connection-status screen and its comparison with cabinet locations, without automatic setting or parameter writing.
Read article →A PING response does not guarantee file transfer. Using the Fast Ethernet/Data Server functions documented in B-64014EN/03, distinguish physical connections, IP reachability and file services, and avoid changing several settings in one test.
Read article →Network connectivity and suitability for direct external access require separate checks. Using FANUC’s published embedded-Ethernet advisory, this article explains product-scope checks, version records and access restrictions coordinated with network administrators.
Read article →A quotation request naming only a “FANUC drive” or an incomplete model can omit the interface, specification and owning machine. This guide organizes machine, component and replacement records without treating visual similarity as proof of direct interchangeability.
Read article →A FANUC 16 display showed ghosting. Comparing IO boards and tracing display signals revealed an open connection at a CPU pin; the display returned to normal after repair. Board traces and photos are retained, with pin details limited to the board examined at the time.
Read article →A Tornos deco sigma 20 with FANUC 31i-MODEL A would not start and had no display. The original record located a short circuit in the mainboard power section. This revision separates observations from suspected supply instability and explains why historical fuse trials are not selection advice.
Read article →An A06B-6093-H112 had no indicator lights and damaged chips. After chip and fuse replacement it powered up normally, but a misconnected cable remained an unconfirmed suspicion. The comparison measurement and original photos are retained; interface data cannot be transferred between models.
Read article →A TSUGAMI B020-V developed intermittent alarm 9083 during main/subspindle synchronization. Comparisons of the drive, cable and sensors showed the alarm moving with the sensor. This revision adds interpretation and scope limits while retaining the recorded tests and photos.
Read article →