We use technical and security cookies and, only if you accept, analytics with no cross-site tracking. More in the Cookie policy and Privacy policy.
We use first-party cookies and technical storage to make the site work, Google reCAPTCHA security technology and, only if you accept, Vercel analytics (no cookies, no cross-site tracking). You can accept or reject analytics; both options are equivalent and you can change your choice at any time. More info: Cookie policy, Privacy policy, Legal notice and Terms and conditions.
The control is asking for a power cycle so a change takes effect, or warning that a PMC input address is not correctly assigned. The first is routine after touching certain parameters; the second means the machine's signal configuration does not add up, and that is not fixed by restarting.
For reference only: alarms change with the manufacturer, the control and the machine PLC. Check the full code in the official manual before doing anything. Legal notice.
Always, if PMC X/skip is involved or the change is unknown.
Turn off and on again; if it returns, restore documented parameters.
Choose the manual matching your control series, software version and machine builder. A support portal is a starting point; it does not establish applicability to every model.
Some parameters are only read by the control at start-up, because it uses them to build internal structures it cannot rebuild on the fly: axis configuration, signal assignment, interface definition. When one of them is modified, the control accepts the new value but warns that a power cycle is needed for it to be effective. That notice is normal and expected. The second case is of a different nature. Certain input signals reaching the PMC have to be declared in parameters so the control software knows which address to read them at; each axis's reference return deceleration signal is the classic example. If that assignment is missing or points at an address that does not match the installed hardware, the control cannot complete functions that depend on it and it flags that. That assignment is machine specific, defined by the builder, and it turns up wrong for very specific reasons: an incomplete parameter restore or one from another machine, a change in the I/O module configuration, or somebody who modified assignment parameters while trying to fix something else. So the right question here is not what value to enter, but what was changed and what the good state was, and that is why the builder's backup decides whether this is solved in an hour or in a day.
In order, from the fastest and cheapest check to the most expensive.
01Tell whether it is a restart request or an assignment warning
If the message asks for a power cycle after somebody changed a parameter, it is routine: power down by the procedure and check it starts cleanly. If the message points at a PMC input address, do not restart hoping it will fix itself: it will not go away.
02Stop changing parameters immediately
Every additional modification takes the machine further from the last known good state and makes going back harder. Write down what has been touched so far, with previous values if they are known, and stop there.
03Reconstruct the intervention
Who, when, which parameters, which backup was loaded, whether any I/O card or module was replaced. An assignment warning appearing right after a parameter restore is almost certainly a restore from the wrong machine or an incomplete one.
04Compare against the machine's own backup
The correct parameter set is the one for this specific machine, with its serial number, not a sister machine's. Compare the current state against that copy and find the differences. If no copy exists, it has to be requested from the builder: that is the correct route even though it is slower.
05Do not invent signal assignment values
PMC signal addresses depend on that machine's physical module configuration. Entering a plausible value can make the control read an input that is actually something else, with consequences ranging from homing that does not work to a safety condition that is not evaluated properly.
06Correction and validation by maintenance
Restore the correct parameters, power down and up, and then validate functions: reference return on every axis, machine sequences and anything that depended on the affected signal. All of that with a backup of the current state taken first and with the builder's documentation.
The I/O configuration is not identical between the two. Confirm it by comparing both sets and the module configuration. It is solved by restoring the machine's own backup; if none exists, by requesting it from the builder with the serial number.
Expected behaviour for parameters that are only read at start-up. It is confirmed because it does not return after the power cycle. It is worth noting the change in the machine log.
That axis's deceleration signal is not correctly assigned. It is confirmed because the axis does not decelerate on entering the reference area. It needs the correct assignment restored from the builder's documentation, by maintenance.
A complete parameter backup per machine, dated, identified by serial number and stored off the machine. A written record of every parameter change: date, reason, old and new value. Always restore the machine's own copy and never a similar machine's. Documentation of the I/O module configuration filed with the electrical drawings. And one simple rule: configuration parameters are not touched without a backup and without knowing what the previous value was.
Fanuc requests power cycle or reports PMC X address (typically *DEC) not assigned correctly. It is an alarm from the PLC/machine area, and in the catalog it is listed as “Shutdown required / PMC X address incorrectly assigned”. On the machine you notice it like this: Machine is not ready, Requests power off, Appears after modifying parameters 3012/3013/3019.
On the shop floor it almost always comes from one of these causes: Modified parameter that requires reboot, Incorrect *DEC or skip signal assignment, Incomplete backup/restore, OEM configuration change. Rule out the most likely one on your machine first, before touching parameters or swapping anything.
Turn off and on again; if it returns, restore documented parameters. Resetting without fixing the cause first only hides the problem: PW0000/PW0001 trips again and, in the meantime, you keep working with the machine in bad shape.
With the machine stopped and in a safe state, start with these checks: Do not keep changing parameters, Compare with the OEM backup, Note modified parameter. That alone will tell you whether it is the program or whether you need to raise a maintenance job.
With PW0000/PW0001 active, avoid this: Do not modify parameters 3012/3013/3019 without documentation, Do not restore partial parameters without understanding the impact. Skipping any of these points is what turns a minor stop into an expensive breakdown.
Always, if PMC X/skip is involved or the change is unknown. If you are not sure how far it goes, stop the machine and report it: a repeat alarm always works out cheaper than a crash.
It is critical: there is a real risk of damage to the machine, the tool or a person. Leave the machine stopped, do not keep resetting it to see if it goes away, and call maintenance before producing again. Guidance reference. Always confirm the full text in the exact machine/control manual.
List of G and M Codes for CNC Programming. Search and filter ISO commands by control, machine or function.
CNC IDE: editing with G/M tooltips, line inspector, conversion between controls and 2D/3D toolpath.
Estimate CNC turning and milling cycle time from G-code. Calculate parts per hour with a breakdown of cutting, rapids, canned cycles and tool changes.
