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's program memory is full and there is no room for what you are trying to register or receive. There is no fault: you have to make space. The only delicate part is that the quick way to make space, deleting carelessly, is also the quick way to lose programs you needed.
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.
If the memory reports a size smaller than the actual one or does not free after deleting.
Reset after freeing up space or canceling the operation.
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.
The control reserves a fixed amount of memory for programs, and that amount is set by the series and the options purchased, not by the size of any computer's disk. Besides the total space, there is usually a limit on the number of registered programs, and the two limits are independent: you can run out of room with plenty of space free if you have hit the maximum number of programs, or the other way round. When the control tries to register a new one and it does not fit in either sense, it aborts and warns. One detail confuses a lot of people: the size a program occupies in the control's memory does not match the file size on the PC, because the control stores it in its own internal format. So working out whether it fits is done by looking at what the control itself reports as free memory, not at what the file weighs on the server. Another typical situation is silent accumulation: test programs, old versions of the same job, orphaned subprograms and backups somebody left there three years ago. A machine that is never cleaned up ends up in this state, and the clean-up is always done in the same order: full backup first, then the cull.
In order, from the fastest and cheapest check to the most expensive.
01Check how much free memory and how many programs are left
The control reports free space and the number of registered programs against the maximum. Check both: if what has run out is the program count, deleting one huge program solves nothing and you have to delete several small ones.
02Take a full directory backup before deleting anything
Every program out to the server or a card, verifying the transfer completed correctly. This step is not optional: nearly every story about lost programs starts with somebody who needed space in a hurry. If the transfer fails, sort that out before going any further.
03List and classify what is there
Go through the directory identifying jobs in progress, finished jobs, tests and the shop's common subprograms. Common subprograms are never deleted, however old they look, because several jobs call them and their disappearance is noticed later and at the worst moment.
04Delete what is backed up and not in progress
Start with old versions and tests, which are the ones nobody will miss. Delete deliberately, one at a time, checking that each one is in the backup. Never use a bulk delete or a format to get by.
05Check whether a memory card or external execution is available
Many machines can run from a card or over DNC, which takes the pressure off internal memory for large programs. If the machine has it, that is the real answer for parts with long programs, instead of deleting every week.
06If free memory does not add up or does not release when you delete, tell maintenance
If free memory does not increase after deleting programs, or the control reports a smaller total size than it should, there may be a memory or internal structure problem. That is not fixed by deleting more: it is diagnosed, with a backup in hand.
The maximum number of registered programs has been reached, not the space. Confirm it by comparing the program counter against the machine's maximum. It is solved by deleting several small programs that are already backed up.
The program exceeds what internal memory can hold. It is confirmed because it always happens with that job. It is solved by running from a card or over DNC, or by rethinking the program with subprograms and cycles instead of a huge list of points.
Accumulation of versions and tests. Confirm it by listing the directory and counting how many are variants of the same job. Fix it with a monthly clean-up routine with a backup taken first, and a naming convention that distinguishes production from tests.
Periodic automatic backup of each machine's programs to the server, so deleting is never frightening. A numbering convention separating common subprograms, production jobs and tests, so you can see at a glance what can be deleted. Scheduled clean-ups, not emergency ones. Execution from card or DNC for parts with long programs. And a visible list at the machine of the common subprograms that are never deleted.
Fanuc cannot register/load a program because the program memory is full. It is an alarm from the Program area, and in the catalog it is listed as “No program space in memory”. On the machine you notice it like this: Cannot register a new program, Fails when receiving over DNC/USB, The control warns that memory is full.
On the shop floor it almost always comes from one of these causes: Too many stored programs, Forgotten test programs or backups, Limited memory on that Fanuc series. Rule out the most likely one on your machine first, before touching parameters or swapping anything.
Reset after freeing up space or canceling the operation. Resetting without fixing the cause first only hides the problem: PS0070 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: Make a backup before deleting, List programs and delete unused ones, Check the memory/CF card if applicable. That alone will tell you whether it is the program or whether you need to raise a maintenance job.
With PS0070 active, avoid this: Do not delete programs without backup, Do not format memory without confirming backup, Do not interrupt transfers in progress. Skipping any of these points is what turns a minor stop into an expensive breakdown.
If the memory reports a size smaller than the actual one or does not free after deleting. 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 a warning: the machine carries on, but it is flagging something that will get worse if you let it go. Deal with it between parts, not at the end of the shift. 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.
