Control locking up?

[Moose]

Ok my guy had homed the machine when I was away for a while
I had went into the pc files to look at the thumb drive and when going back that's when I it was stalled

Hard to keep track of everything going on when your busy and going in 5 directions at once

[Moose]

Just tried running the same program again

This time with the door closed I had no problems using cycle stop or esc but when it got to line N0010 it stalled

[martyscncgarage]

Just tried running the same program again

This time with the door closed I had no problems using cycle stop or esc but when it got to line N0010 it stalled

Dont care about the program either post the CNC12 screen with the error or a report.
Marty

[martyscncgarage]

Please tell us what brand model servo motors you have on all axis, post the motor labels if you can.

[Moose]

Can't find labels, gone or worn off

When I said "stall" I meant lock up like before. Sorry!!!
Can jog with pendant only, DRO does not change until it unlocks or begins responding again
Takes about a minute or less

Before now it would also lockup when using cycle stop or esc button

[Moose]

Screen shows 301 or 302 while locked up

[martyscncgarage]

Screen shows 301 or 302 while locked up

Take a picture of the full CNC11 screen with your phone showing the errors.
301 is Stopped
302 is moving

Post another fresh report please so we can see the latest logs.

Marty

[martyscncgarage]

When you say "Locked up" can you exit CNC11 back to Windows?

[cncsnw]

The message "SV_STALL ERROR Reported by CNC11!!!" was an ill-advised attempt to shame the software developers into ensuring that every stall condition (notably ones due to encoder errors) was accompanied by a meaningful message. It has long outlived its usefulness.

The problem with it is that CNC11 and CNC12 consider it a "stall" if the PLC program removes SV_MASTER_ENABLE while one or more axes are enabled. Since all standard PLC programs remove SV_MASTER_ENABLE whenever any Fault condition occurs (anything which sets SV_STOP), the effect is that the "SV_STALL ERROR Reported by CNC11!!!" message appears any time a Fault occurs with axes enabled. This has nothing to do with conditions that would normally be considered "stalls", such as "410 ... position error", "411 ... full power without motion", "412 ... encoder differential error", etc..

In nearly all of the examples that Marty posted from the message log, "SV_STALL ERROR Reported by CNC11!!!" is immediately preceded by "9039 Software Ready Fault". This is a fault, triggered by the PLC, in response to loss of communication from CNC11 on the PC. It is the MPU11 component on the Allin1DC telling us the same thing you already told us: the PC software has gone non-responsive for an extended period.

I suspect either a heat issue (more heat buildup in a closed cabinet); an interference issue (closing the door moves the computer closer to noisy components); or a connection issue (closing the door moves and flexes the cables, possibly shifting plugs).

One thing that stands out is the large coil of CAT5 cable, with an extra loop around the PC power cord for good measure. You might consider buying a 5' or 6' long shielded CAT5e cable, and running it from the PC to the Allin1DC with a minimum of detours (but of course, with just enough slack to allow the door to open and close).

[Moose]

When I look at the location of the CAT5 connection point on the drive there is no real clear route to avoid electrical components like transformers, fuses, VFD, etc.

If I was starting from scratch building the cabinet I would change up some things to improve the situation

I am thinking about relocating the pc outside the main cabinet in its own cabinet

I have a local legitimate PC repair guy that can check/scan the pc for any problems with cpu, ram, cards, etc.
At least this will hopefully eliminate pc hardware and performance issues