Code PMON-009: PMON monitor not found
Problembeschreibung & Sicherheitswarnung
Die Fanuc R-30i Series Robot Controller hat einen kritischen PMON monitor not found-Alarm ausgelöst. Sofortige Aufmerksamkeit durch einen qualifizierten Bediener oder Wartungstechniker ist erforderlich, um Folgeschäden an der Ausrüstung oder verdorbene Teile während des Fertigungszyklus zu vermeiden. Stellen Sie immer sicher, dass standardmäßige Sicherheits- und LOTO-Verfahren befolgt werden, bevor Sie auf Schaltschränke zugreifen.
Offizielle Schritte zur Fehlerbehebung
Cause: The PC Monitor task had an internal monitoring failure. The requested monitor number was not found in the list of monitors. Remedy: Somehow, PMON is out of sync with the PC. In some cases, this may be normal if the PC is attempting to clean up after an internal error. 4.14.5 PNT1 Alarm Code PNT1-001 Unknown PAINTtool error Cause: PaintTool has detected an unknown error. Remedy: Refer to the teach pendant error log for the cause of the error. PNT1-002 Press master reset Cause: The system is in an error condition. Remedy: Press RESET to clear the error. PNT1-003 Reset failure Cause: The reset procedure has failed. Remedy: Correct the error, if any, and try the reset operation again. PNT1-004 Robot Servos Disabled Cause: The robot servo disconnect is on. Remedy: Turn off the robot servo disconnect. PNT1-005 Production mode is disabled Cause: The production mode input is off. Remedy: None. PNT1-006 REMOTE switch must be REMOTE Cause: The remote switch is in the LOCAL position. Remedy: Place the remote switch in the REMOTE position. PNT1-007 Machine lock is ON Cause: The machine lock is on going into production. Remedy: Disable the machine lock on the teach pendant before entering production. PNT1-008 Robot motion is not enabled Cause: The UOP enable input is OFF. Remedy: The UOP enable input must be ON. PNT1-009 Invalid job %s received Cause: An invalid job number was received from the PLC. Remedy: The PLC must initialize the robot with a valid job number. PNT1-010 Invalid tutone %s received Cause: An invalid tutone option was received from the PLC. Remedy: The PLC must initialize the robot with a valid tutone option. PNT1-011 Invalid repair %s received Cause: An invalid repair option was received from the PLC. Remedy: The PLC must initialize the robot with a valid repair option. PNT1-012 Invalid color %s received Cause: An invalid color number was received from the PLC. Remedy: The PLC must initialize the robot with a valid color number. PNT1-013 Job (%s) is not found Cause: The teach pendant JOB program is not loaded, or was not created on the controller. Remedy: A teach pendant JOB program must be created or loaded in the controller before attempting to run it in production. PNT1-014 Invalid job %s in queue Cause: An invalid job number was received from the PLC. Therefore, the robot cannot put the job into the job queue. Remedy: At the PLC, initialize the robot with a valid job number in order to receive a job read acknowledge from the robot. PNT1-015 Invalid color %s in queue Cause: An invalid color number was received from the PLC. The robot cannot put the color into the color queue. Remedy: The PLC must initialize the robot with a valid job number in order to receive a color read acknowledge from the robot. PNT1-016 Job queue is full Cause: The job queue is full. Remedy: Remove unneeded job(s) from the job queue before attempting to add more jobs to the queue. PNT1-017 Color queue is full Cause: The color queue is full. Remedy: Remove color(s) from the color queue before attempting to add more colors to the queue. PNT1-018 Shell aborted or paused Cause: Another task has detected that the main task has aborted or paused. Remedy: Turn off the controller, then turn it on again. PNT1-019 Wait for autoprocessing to finish Cause: Autoprocessing of the last editted program is still in process. 4.ERROR CODES B-83124EN-6/02 Remedy: Wait for autoprocessing to complete before entering production mode. PNT1-020 Invalid job type (%s) received Cause: An invalid job type was received from the PLC. Remedy: The PLC must initialize the robot with a valid job prefix. PNT1-021 System is in error status Cause: There is an alarm that must be cleared before Test Cycle can be run. Remedy: Press RESET to clear all system alarms. PNT1-022 Sync Que-Job passed window Cause: The job is not run and the encoder counts indicate that the part is past the Start switch (plus tolerance). The robot deletes the job from the queue, posts this warning message and continues to operate in production. Remedy: None. PNT1-023 Sync Que-Job before window Cause: The job is not run and the encoder counts indicate that the part has not made it to the Start switch (minus tolerance). The robot will hold onto that job for the next start signal, post this warning message, and will continue to operate in production. Remedy: None. PNT1-024 UOP's assigned but disabled! Cause: The User Operator Panel (UOP) inputs are assigned, but have been disabled! Remedy: If your system requires these UOP signals, you must enable these inputs on the Teach Pendant as follows: 1. Press MENUS. 2. Select SYSTEM. 3. Press F1 [TYPE]. 4. Select Config. 5. Move the cursor to Enable UI signals, and change them from FALSE to TRUE. If your system does not require these UOP signals, unassign these UOP signals in the I/O menu. PNT1-034 Parm %s Value beyond limits Cause: An attempt was made to set an applicator parameter output beyond its min/max value. Remedy: Verify the specified parameter's min/max output setting. PNT1-039 I/O setup verified OK Cause: SETUP Applicators: The I/O information is correct and complete. Remedy: None. PNT1-040 Error attempting to setup I/O Cause: SETUP Applicators: The I/O information for an applicator was changed and is in error. Remedy: Check that the output type, output number, rack and slot number, first bit location, and number of bits are all specified correctly. PNT1-045 Adj. colors table sizes to %s Cause: The application is attempting to adjust the size of the color tables based on the configuration variable setting. Remedy: None. PNT1-046 Adj. color valves table size to %s Cause: The application is attempting to adjust the size of the color valve table based on the configuration variable setting. Remedy: None. PNT1-047 Failed to adj. color table size Cause: There is not enough memory available for the application to adjust the size of the color tables to the match requested setting. Remedy: Use a smaller setting that is within the memory constraints of the controller. PNT1-048 Failed to adj. color valve table size Cause: There is not enough memory available for the application to adjust the size of the color valves table to match the requested setting. Remedy: Use a smaller setting that is within the memory constraints of the controller. PNT1-053 Invalid parameter indicator Cause: An invalid parameter indicator value was sent from the PLC. Remedy: Verfiy that the number of applicator control parameters set up in the robot matches the value sent from the PLC. This value should be between the range of 1 to 4. PNT1-054 No channel/parameter indicated Cause: The PLC sent a parameter indicator value of 0. Remedy: Correct the parameter indicator value at the PLC. PNT1-055 Manual inputs are enabled Cause: On manual mode entry, all PLC manual mode input functions are enabled. Remedy: None. PNT1-056 Manual inputs are disabled Cause: On manual mode exit, all PLC manual mode input functions are disabled. Remedy: None. PNT1-057 Manual enabled during motion Cause: Manual mode is being initiated during robot motion. Remedy: Robot motion must complete before it enters manual mode. PNT1-058 Manual enabled in color cycle Cause: Manual mode is being initiated during a color change cycle. Remedy: The color change cyle must complete before the robot enters manual mode. PNT1-059 TP Enabled in cycle Cause: The teach pendant cannot be enabled when running a remote color change cycle. Remedy: None. PNT1-064 Tracking que exceeded Cause: For continuous line systems, indicates that too many parts have passed the part detect switch within the current boundaries. Remedy: Expand the robot boundaries, or lower the conveyor speed. PNT1-065 Linetracking parameter undefined Cause: For continuous line systems, a line tracking parameter is undefined and is required to run the system. Remedy: Ensure that all tracking parameters have been set up on the SETUP Tracking menu. PNT1-066 Railtrack parameter undefined Cause: For continuous line systems, a rail tracking parameter is undefined and is required to run the system. Remedy: Ensure that all tracking parameters have been set up on the SETUP Tracking menu. PNT1-067 Invalid tracking frame Cause: An attempt was made to use an invalid tracking frame number. Remedy: The current software supports tracking frames 1-6. The tracking frame number must be greater than 0, and less than 7. PNT1-068 Encoder count rollover Cause: For continuous line systems, this warning indicates that the encoder counter has detected a rollover condition. Remedy: None. PNT1-069 Part Detect less than min dist Cause: For continuous line systems, this warning indicates that the trigger distance is less than a pre-determined value. The part detect will be ignored by the robot controller. 4.ERROR CODES B-83124EN-6/02 Remedy: Reduce the minimum distance value to less than the job spacing distance, or replace the old part detect switch. PNT1-070 Conveyor direction incorrect Cause: For continuous line systems, the robot has determined the conveyor is running in the wrong direction. Part detects will be ignored by the robot. Remedy: Swap the leads on the encoder repeater board so that the encoder counts positive pulses instead of negative. PNT1-071 %s skipped-over max travel Cause: For line tracking systems only: This is a warning that the part has tracked too far to be played back. The previous job or color change took too long to play. The robot will ignore this job/color. Remedy: Decrease the cycle time of the job or decrease the color change cycle. PNT1-072 Tracking encoder disconnected Cause: The robot is detecting a problem with the tracking encoder cable. Remedy: Check the encoder cable, and replace it if necessary. PNT1-073 Right-Hand Rule only for this robot Cause: The robot being used is not supported in PaintTool line tracking for a left hand arm type. The robot is not a P-Series robot. Remedy: If the robot library (setup) does not offer a selection for right or left hand robots, then no remedy is required. If the robot has been set up as a left hand robot, change it to a right hand robot. PNT1-074 DAL alarm(Track encoder:1) Cause: The tracking encoder has been disconnected, or is faulty. Remedy: Reconnect the tracking encoder or determine if the encoder connector is faulty. The robot controller power must be turned off, then turned on again before the system is allowed to reset. PNT1-075 Extreme entry position violation Cause: The TCP (Line Tracking) or Extended Axis (Rail Tracking) has been commanded beyond the Entry Limit defined in the System parameter, $LNCFG.$ENTRY_XTRM. Remedy: Adjust the Entry Limit ($LNCFG.$ENTRY_XTRM), or change the Tracking Boundary to be inside of this limit. PNT1-076 Extreme exit position violation Cause: The TCP (Line Tracking) or Extended Axis (Rail Tracking) has been commanded beyond the Exit Limit defined in the System parameter, $LNCFG.$EXIT_XTRM. Remedy: Adjust the Exit Limit ($LNCFG.$EXIT_XTRM) or change the Tracking Boundary to be inside of this limit. PNT1-085 Posn unreachable at line %s Cause: An unreachable position is detected in the adjustment precheck Remedy: Check the alarm log to find out at which position motion error will occur, use CLR_Adj to clear the adj value PNT1-086 PLC e-stop detected Cause: An interlock signal fault or PLC E-stop was detected. Remedy: Correct the source of the fault, and RESET the controller. PNT1-087 Robot overtravel Cause: The mechanical unit went beyond its normal travel limits and reached an overtravel limit switch. Remedy: Follow the overtravel recovery procedure in Electrical Connection and Maintenance Manual. PNT1-088 Release SOP e-stop Cause: The operator panel (SOP) EMERGENCY STOP has been detected. Remedy: Release the SOP EMERGENCY STOP, and press RESET to clear the E-STOP condition. PNT1-089 Release TP e-stop Cause: The teach pendant EMERGENCY STOP has been detected. Remedy: Turn the teach pendant EMERGENCY STOP button, and press RESET to clear the EMERGENCY STOP condition. PNT1-090 TP enabled during production Cause: The teach pendant was enabled during production. Remedy: The teach pendant cannot be enabled during production. Disable the teach pendant. PNT1-091 Disable teach pendant Cause: The teach pendant is enabled. Remedy: Disable the teach pendant to continue the program. PNT1-092 Stop error excess Cause: Refer to SRVO-023 SERVO Stop error excess(G:x A:x) in the Error Code Manual. Remedy: Refer to SRVO-023 SERVO Stop error excess(G:x A:x) in the Error Code Manual. PNT1-093 Move error excess Cause: Refer to SRVO-024 SERVO Move error excess(G:x A:x) in the Error Code Manual. Remedy: Refer to SRVO-024 SERVO Move error excess(G:x A:x) in the Error Code Manual. PNT1-094 DEADMAN switch RELEASED Cause: The DEADMAN switch has been released during an operation. The operation has been discontinued. Remedy: Press and hold the DEADMAN switch to restart the procedure. PNT1-095 Fence open during production Cause: The FENCE1 and FENCE2 circuits are open on the EMG control board. Remedy: Determine the cause of the FENCE1 and FENCE2 open circuits, and correct the problem. PNT1-096 UOP immediate stop detected Cause: The IMSTP (immediate stop) UOP input was not asserted. Remedy: If you are using UOP signals, clear the source of the fault. If you are not using UOP signals, press MENUS, select I/O, and map all UOP signals to zero. Then cycle power on the controller. PNT1-097 HOLD active Cause: A HOLD signal, either from the UOP or the teach pendant, has been activated. Remedy: Remove the HOLD condition, and press RESET. PNT1-098 Track destination gone Cause: Destination out of window error. Remedy: The current cycle must be aborted, and then restarted. PNT1-099 PC serial interface fault Cause: The PLC interface serial link has failed. Remedy: Check the LED status on PLC interface board. Refer to Remote I/O interface for an Allen-Bradley PLC or Genius Network Interface for GE FANUC manual for more information. PNT1-100 OVC alarm Cause: This Alarm is echoed to the PLC when SRVO-046 SERVO OVC alarm (Group:%d Axis:%d) is posted. Refer to the Teach Pendant alarm screen for group and axis number. Refer to SRVO-046 for the cause. Remedy: Refer to SRVO-046 for the remedy. PNT1-101 Limit error Cause: The taught position was outside the normal work envelope of the robot. One of the robot axes could not reach the position. Remedy: Reteach the position. Refer to the MOTN-017 alarm that was triggered before this paint alarm for details on the specific group and axis number. PNT1-102 Position not reachable Cause: This alarm is echoed to the PLC when MOTN-018 STOP Position not reachable is posted. Refer to the MOTN-018 alarm for the cause. Remedy: Refer to the MOTN-018 alarm for the remedy. 4.ERROR CODES B-83124EN-6/02 PNT1-103 Configuration mismatch Cause: This is a pause condition. The configuration (Flip/No-Flip) cannot change during a Cartesian (linear or circular) motion. Remedy: Either reteach the motions using the same configuration (Flip or No-Flip), or use a joint motion to change configurations before proceeding with Cartesian motion. PNT1-104 Planner error Cause: The planner encountered an error. Remedy: Check the error message log for details. PNT1-105 Unitialized position Cause: This is a system software error. Remedy: Document the events that led to the error, record the software version number, and contact your local distributor or your local FANUC representative. You can try to clear the error by turning the controller off, and then on again. PNT1-106 Brake fuse blown Cause: This alarm is echoed to the PLC when SRVO-008 SERVO Brake fuse blown is posted. Refer to SRVO-008 for the cause. Remedy: Refer to SRVO-008 for the remedy. PNT1-107 Robot not mastered Cause: This alarm is echoed to the PLC when SRVO-027 WARN Robot not mastered(Group:%d) is posted. Refer to the Teach Pendant alarm screen for the group number. Refer to the SRVO-027 alarm for the cause. Remedy: Refer to the SRVO-027 alarm for the remedy. PNT1-108 MCC alarm Cause: The servo amplifier magnetic contactor (MCC) is welded closed. Remedy: Refer to the troubleshooting section in the Controller Series Electrical Connection and Maintenance Manual. PNT1-109 Discharge current alarm Cause: This alarm is echoed to the PLC when a SRVO-043 SERVO DCAL alarm(Group:%d Axis:%d) alarm is posted. Refer to the Teach Pendant alarm screen for the group and axis number. Refer to SRVO-043 for the cause. Remedy: Refer to SRVO-043 for the remedy. PNT1-110 High voltage alarm Cause: This alarm is echoed to the PLC when a SRVO-044 SERVO HVAL alarm(Group:%d Axis:%d) alarm is posted. Refer to the Teach Pendant alarm screen for the group and axis number Refer to SRVO-044 for the cause. Remedy: Refer to SRVO-044 for the remedy. PNT1-111 High current alarm Cause: This alarm is echoed to the PLC when a SRVO-045 SERVO HCAL alarm(Group:%d Axis:%d) alarm is posted. Refer to the Teach Pendant alarm screen for the group and axis number Refer to SRVO-045 for the cause. Remedy: Refer to SRVO-045 for the remedy. PNT1-112 Low voltage alarm Cause: This alarm is echoed to the PLC when a SRVO-047 SERVO LVAL alarm(Group:%d Axis:%d) alarm is posted. Refer to the Teach Pendant alarm screen for the group and axis number. Refer to SRVO-047 for the cause. Remedy: Refer to SRVO-047 for the remedy. PNT1-113 Servo amp overheat alarm Cause: This alarm is echoed to the PLC when a SRVO-049 SERVO OHAL1 alarm (Grp:%d Ax:%d) is posted. Refer to the Teach Pendant alarm screen for the group and axis number. Refer to SRVO-049 for the cause. Remedy: Refer to SRVO-049 for the remedy. PNT1-114 Collision alarm Cause: This alarm is echoed to the PLC when a SRVO-050 SERVO Collision Detect alarm (G:%d A:%d) is posted. Refer to the Teach Pendant alarm screen for the group and axis number. Refer to SRVO-050 for the cause. Remedy: Refer to SRVO-050 for the remedy. PNT1-115 Pulse coder battery discon alarm Cause: This alarm is echoed to the PLC when a SRVO-062 SERVO BZAL alarm(Group:%d Axis:%d) alarm is posted. Refer to the teach pendant alarm screen for further information on the SRVO-062 alarm. Refer to the SRVO-062 alarm for the cause. Remedy: Refer to the SRVO-062 alarm for the remedy. PNT1-116 Pulse coder alarm Cause: This alarm is echoed to the PLC when a SRVO-061 SERVO CKAL alarm(Group:%d Axis:%d), SRVO-063 SERVO RCAL alarm(Group:%d Axis:%d), SRVO-064 SERVO PHAL alarm(Group:%d Axis:%d), or SRVO-066 SERVO CSAL alarm (Group:%d Axis:%d) is posted. Refer to the teach pendant alarm screen for further information on the SRVO-061, SRVO-063, SRVO-064, or SRVO-066 alarm. Refer to the SRVO-061, SRVO-063, SRVO-064, or
Source: FANUC Robot R-30iA Alarm Code List Operator's Manual
Last reviewed: 2026-07-01 · Verified against the manufacturer’s official documentation.
Über Fanuc R-30i Series Robot Controller Alarme
Industriesteuerungen von Fanuc verfügen über umfangreiche Diagnosesysteme zum Schutz der internen Schaltkreise und mechanischen Verbindungen. Wenn eine R-30i Series Robot Controller einen Fehlercode wie PMON-009 ausgibt, deutet dies typischerweise auf eine Diskrepanz zwischen befohlenen Werten und tatsächlichem Sensor-Feedback hin.
Vollständige Alarmliste: 6553 Fanuc R-30i Series Robot Controller codes.
Have a better solution?
Help the industrial community by sharing your repair experience for code PMON-009.
Need a searchable reference for more Fanuc R-30i Series Robot Controller manuals?
We structure equipment manuals into searchable code, title, cause, solution, safety note, and source-reference data. Send a PDF and example searched codes when you need public pages, private search, or structured exports.
Space reserved for Google AdSense / Industrial Affiliate Links
Monetization target for 2026