The history of this software is fascinating. In the days of the FANUC System 6 and System 0 (legendary CNC systems), the "Starting System" was rigid. It was burned onto chips. If you needed to upgrade the boot software, you physically replaced computer boards.
Today, with controllers like the Series 30i or the R-30i Plus, the Starting System has evolved into a sophisticated operating environment. It now supports features like:
The next time you see a FANUC robot spring into action, moving with fluid, hydraulic-like grace, remember the few seconds before the movement. Listen for the click of the contactors and the initialization sequence.
Stuck at "Starting System Software. Please Wait": A Troubleshooting Guide for Fanuc Controllers If your Fanuc controller is stuck on the "Starting System Software. Please Wait"
screen, you are not alone. This common hang-up usually indicates that the boot process has stalled before the main operating system can take over, often due to corrupted memory or hardware communication failures.
Below is a guide to help you diagnose and resolve this issue, ranging from simple resets to hardware checks. 1. Identify the Point of Failure 7-segment LED display on the main CPU board inside the controller cabinet. If the display shows a '0' or is blank: This often points to a parity alarm or a failure in the DRAM/CPU. Status Indicators:
On many R-30iB controllers, the top two LEDs should be solid and the bottom two should blink. If they look different, the main board may not be booting correctly. 2. Immediate Software Fixes
Before replacing expensive boards, try these software-level recovery steps: Perform an INIT Start:
This will clear the SRAM and essentially factory reset the unit. Hold down the
keys (or PREVIOUS and NEXT on some models) while powering on to enter the Boot Monitor (BMON) menu. Select INIT Start This will wipe your settings, so you must have an "All of the Above" (AOA) Image backup ready to restore. Restore an Image Backup:
If an INIT start doesn’t work, use a known good image backup from a USB or PCMCIA card to re-flash the system software. 3. Basic Hardware Checks
Hardware issues are frequent culprits when software remains unresponsive:
Seeing the message "Starting System Software Please Wait" frozen on your Fanuc controller can be frustrating, especially when it stalls your entire production line. This status typically appears during the initial boot phase where the hardware handshakes with the system software. If your screen has been stuck for more than a few minutes, 1. Immediate Troubleshooting: The "Power Cycle"
Before diving into hardware, try a clean restart. A simple power flicker can sometimes cause the software to hang during its initialization. Turn off the controller power.
Wait at least 2 minutes to allow the capacitors to drain completely.
Disconnect external devices: Unplug any USB drives, memory cards, or Ethernet cables, as these can sometimes cause the bootloader to hang.
Power on again and observe if it progresses past the "Please Wait" screen. 2. Check for Hardware Communication Issues
If a simple restart doesn't work, the problem often lies in a physical connection that isn't reporting back to the main CPU.
Reseat Daughter Boards: On many Fanuc CNC controls (like the 16i/18i), daughter boards for graphics or motion control can vibrate loose over time. Open the yellow case behind the screen and carefully reseat these boards.
Swap the Teach Pendant/Cable: If you are using a robotic controller (R-30iA/B), a faulty teach pendant or a frayed cable can prevent the system from completing its boot sequence. Try swapping with a known working pendant if available.
Verify 24V Power Supplies: A "lazy" power supply that takes too long to reach full voltage can cause a "race condition," leaving the software waiting for a signal that arrived too late. Check if your 24VDC supplies are consistent. 3. Software Corruption & Boot Monitor (BMON)
If the hardware is healthy, the system software or SRAM data may be corrupted, often due to a dead backup battery or an improper shutdown during a write cycle. Accessing the Boot Monitor Facebook·FANUC Robot Programmers
The "Starting System Software" file stored on the Flash ROM has become damaged. This can happen due to:
Solution: This usually requires a System Reload.
In the high-stakes world of computer numerical control (CNC) manufacturing, time is the ultimate currency. Every second a machine sits idle translates directly into lost revenue and delayed production schedules. For operators of Fanuc-controlled machine tools, few sights are as common—or as potentially anxiety-inducing—as the stark, unadorned message on the amber-tinted display: "Fanuc Starting System Software Please Wait." Far from a simple status update, this message serves as a critical digital gatekeeper, representing the complex, layered handshake between hardware, firmware, and application software that defines modern industrial automation.
At its core, the "Please Wait" message signals the boot process of the Fanuc CNC’s proprietary operating system. Unlike a personal computer that loads a general-purpose OS like Windows or Linux, a Fanuc controller runs a real-time, highly specialized operating system. When the machine is powered on, the control does not simply "wake up." It performs a meticulous, pre-programmed ritual. First, the hardware initializes—checking power supplies, the main CPU, and memory integrity. Then, the bootloader retrieves the compressed system software from a flash ROM or solid-state drive and decompresses it into working RAM. The message appears during this phase, indicating that the kernel of the Fanuc software is loading, along with critical real-time extensions that will govern axis movement, spindle synchronization, and ladder logic (the PLC program for machine-side functions like coolant and tool changers). This is not a delay; it is a controlled detonation of digital readiness.
The duration of this "wait" state is a diagnostic goldmine for an experienced technician. Under normal circumstances, depending on the Fanuc series (from the legacy Series 0 to the modern 30i-B or 31i-B), the boot process should take between 30 seconds and two minutes. A normal, predictable wait indicates a healthy system. However, an unexpectedly prolonged wait—or an infinite loop of the message—signals deeper trouble. Common culprits include a corrupted system software file, a failing memory module on the main board, a depleted backup battery that has caused parameter or program loss, or even a hardware failure in the boot device itself. In these pathological cases, the "Please Wait" message transforms from a mundane status into a cry for help, often requiring the restoration of "from SRAM" data or a complete clean installation of the executive software.
Crucially, this message underscores a fundamental tension in industrial design: robustness versus responsiveness. Fanuc prioritizes deterministic, crash-proof behavior over rapid boot times. Every byte loaded during the "Please Wait" phase is verified, often with checksums and cyclic redundancy checks (CRCs), to ensure that the software controlling a multi-ton machining center has not been corrupted. The alternative—a faster boot that skips integrity checks—risks catastrophic results, such as a tool plunging into a vice or an axis runaway. Thus, the waiting period is a conscious safety feature. It is the controller’s way of ensuring that when the axes finally energize and the "Ready" light illuminates, every line of G-code will be executed with absolute fidelity.
For the machine operator, the message is a lesson in patience and procedure. The cardinal rule is simple: never interrupt the boot cycle. Forcefully cycling power while the message is displayed is the most common cause of software corruption, as it can leave the flash memory in an inconsistent state. A skilled operator knows that this "Please Wait" is not an error, but an invitation to observe—listening for the characteristic clunk of the electromagnetic contactors and watching for the transition to the coordinate position display. In some older Fanuc models, the wait might be followed by a "NOT READY" alarm, which simply means the operator must press a cycle start or reset button. In modern controls, it fades silently into the main interface, its job complete.
In conclusion, the seemingly innocuous phrase "Fanuc Starting System Software Please Wait" is a profound reminder of the hidden complexity behind industrial automation. It demarcates the boundary between lifeless hardware and a functioning, intelligent machine tool. It is a brief period of enforced humility in a world obsessed with speed—a few seconds where the controller checks its own pulse before commanding immense forces. For those who understand it, the message is not an obstacle but a reassurance: the digital brain is booting, the checks are passing, and production is about to resume. All it asks for, in return for its precision and power, is a moment of your patience.
FANUC controls use a lithium battery (usually a BR-2/3A or BR-AGCF2W) to maintain SRAM contents while the main power is off. The SRAM holds CNC parameters, pitch error compensation, part programs, and tool offsets. The system ROM contains the boot software.
Here is the trap: If the battery voltage drops below 2.7V, the SRAM becomes unstable. On the next power cycle, the control attempts to validate the SRAM checksum. When it fails, the boot process can freeze at the "starting system software" screen because the control is unsure if it has a valid environment to load into.
If "Please Wait" persists beyond 5 minutes, the system is likely stalled.
When a FANUC CNC displays "Starting system software please wait" (or similar), the controller is initializing firmware, loading system software modules, or performing a firmware/self-check after power-on or a reboot. It can be normal for several seconds to a few minutes, but extended or repeated hangs indicate a problem.
A healthy FANUC CNC should cycle through the following stages in under two minutes:
The message "FANUC STARTING SYSTEM SOFTWARE PLEASE WAIT" appears during stage #3. It indicates that the Boot Monitor has successfully handed over control to the System Software loader, but the loader is stuck—unable to complete the transition to the operational CNC state.