Spontaneous 307 "Operator Abort" <Resolved, chips in K'board>

[RGSparber]

All ran fine yesterday but today I started to see my cursor jumping around on its own as I was setting up for a job. I also had a few spontaneous "307 Operator abort" events.

I figured I might be a missing Windows update so closed CNC12, found updates, installed them, power cycled, and set up for the job again. The cursor was now behaving itself. All was fine until 16 minutes into the run. Then I got another "307 Operator Abort" event. I wasn't touching the machine.

I normally have WiFi turned off since all security software has been disabled.

I have made no changes to the hardware other than to reduce the spindle preload by one click.

Any idea what is going on here?

Thanks,

Rick

[cnckeith]

hello.
to view the Error message logs go to the "URF" zip folder in the report attached and open "msg_log.txt"

(1) 12-28-2021 10:10:53 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:10:54 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:10:54 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:10:58 4032 Reset Cleared
(1) 12-28-2021 10:13:04 FAST_JOG_SELECTED
(4) 12-28-2021 10:14:52 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:14:56 9042 Probe Cleared
(4) 12-28-2021 10:16:33 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:16:34 9042 Probe Cleared
(4) 12-28-2021 10:17:38 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:17:52 9042 Probe Cleared
(4) 12-28-2021 10:19:22 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:19:22 9042 Probe Cleared
(4) 12-28-2021 10:20:17 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:20:28 9042 Probe Cleared
(4) 12-28-2021 10:23:10 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:23:10 9042 Probe Cleared
(4) 12-28-2021 10:23:11 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:23:15 9042 Probe Cleared
(1) 12-28-2021 10:28:12 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:33:45 199 CNC Started
(1) 12-28-2021 10:33:51 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:33:52 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:33:52 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:33:58 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:35:31 199 CNC Started
(4) 12-28-2021 10:35:35 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:35:37 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:35:38 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:35:38 9039 Software Exited, Cycle E-Stop/Reset to Continue
(4) 12-28-2021 10:35:38 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:35:55 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:38:35 199 CNC Started
(1) 12-28-2021 10:38:41 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:38:41 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:38:42 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:38:50 4032 Reset Cleared
(1) 12-28-2021 10:41:07 FAST_JOG_SELECTED
(4) 12-28-2021 10:41:17 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:41:17 4032 Reset Cleared
(4) 12-28-2021 10:44:27 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:44:27 9042 Probe Cleared
(4) 12-28-2021 10:46:12 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:46:13 9042 Probe Cleared
(4) 12-28-2021 10:46:18 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:46:18 9042 Probe Cleared
(4) 12-28-2021 10:47:03 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:47:03 9042 Probe Cleared
(1) 12-28-2021 10:55:09 Tool change: T1 1/4" end mill
(1) 12-28-2021 11:12:08 417 Abnormal end of job
(1) 12-28-2021 11:14:05 Creating report...

the thing that jumps out at me is there are alot of 8040 WARNING: PROBE TRIPPED
to debug your issue, solve the probe tripped issue. easiest way is to remove the probing input definitions from the Acorn inputs using the wizard. and then test the system for other errors. Process of elimination to solve. etc.

[centroidsupport]

Messages can also be accessed directly in CNC12 by going through F7-Utilites -> F9 Logs -> F1 Errors
or F2 Stats

"Errors" will show all the messages in chronological order

"Stats" will show you how many times each error has occurred

[RGSparber]

The probe tripped entries are due to my actions and are understood. The probe was not connected when I hit the 307 error.

Rick

[RGSparber]

hello.
to view the Error message logs go to the "URF" zip folder in the report attached and open "msg_log.txt"

(1) 12-28-2021 10:10:53 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:10:54 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:10:54 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:10:58 4032 Reset Cleared
(1) 12-28-2021 10:13:04 FAST_JOG_SELECTED
(4) 12-28-2021 10:14:52 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:14:56 9042 Probe Cleared
(4) 12-28-2021 10:16:33 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:16:34 9042 Probe Cleared
(4) 12-28-2021 10:17:38 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:17:52 9042 Probe Cleared
(4) 12-28-2021 10:19:22 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:19:22 9042 Probe Cleared
(4) 12-28-2021 10:20:17 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:20:28 9042 Probe Cleared
(4) 12-28-2021 10:23:10 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:23:10 9042 Probe Cleared
(4) 12-28-2021 10:23:11 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:23:15 9042 Probe Cleared
(1) 12-28-2021 10:28:12 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:33:45 199 CNC Started
(1) 12-28-2021 10:33:51 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:33:52 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:33:52 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:33:58 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:35:31 199 CNC Started
(4) 12-28-2021 10:35:35 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:35:37 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:35:38 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:35:38 9039 Software Exited, Cycle E-Stop/Reset to Continue
(4) 12-28-2021 10:35:38 9033 Reset Initiated, Press Reset to Clear
(1) 12-28-2021 10:35:55 204 Exiting CNC...Normal Exit (66)
(1) 12-28-2021 10:38:35 199 CNC Started
(1) 12-28-2021 10:38:41 Warning: X Axis screw comp table does not match travel limits
(1) 12-28-2021 10:38:41 CNC12 Acorn Mill v4.64
(4) 12-28-2021 10:38:42 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:38:50 4032 Reset Cleared
(1) 12-28-2021 10:41:07 FAST_JOG_SELECTED
(4) 12-28-2021 10:41:17 9033 Reset Initiated, Press Reset to Clear
(4) 12-28-2021 10:41:17 4032 Reset Cleared
(4) 12-28-2021 10:44:27 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:44:27 9042 Probe Cleared
(4) 12-28-2021 10:46:12 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:46:13 9042 Probe Cleared
(4) 12-28-2021 10:46:18 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:46:18 9042 Probe Cleared
(4) 12-28-2021 10:47:03 8040 WARNING: PROBE TRIPPED
(4) 12-28-2021 10:47:03 9042 Probe Cleared
(1) 12-28-2021 10:55:09 Tool change: T1 1/4" end mill
(1) 12-28-2021 11:12:08 417 Abnormal end of job
(1) 12-28-2021 11:14:05 Creating report...

the thing that jumps out at me is there are alot of 8040 WARNING: PROBE TRIPPED
to debug your issue, solve the probe tripped issue. easiest way is to remove the probing input definitions from the Acorn inputs using the wizard. and then test the system for other errors. Process of elimination to solve. etc.

I did disturb my X-axis home position a few days ago so am not surprised that my screw mapping comp table is broken. I'll have to run X axis calibration again.

I'll disable my probe inputs via the Wizard and see if I still get the 307 fault.

Rick

[centroidsupport]

Any chance you have a chip in your keyboard? Touch screen contaminated? How often is the error occurring? If you just go into MDI, don't move anything
or start anything, just let it sit at the MDI prompt. If so, how long did it sit before the error occurred?

We are going to need another report

[RGSparber]

Any chance you have a chip in your keyboard? Touch screen contaminated? How often is the error occurring? If you just go into MDI, don't move anything
or start anything, just let it sit at the MDI prompt. If so, how long did it sit before the error occurred?

We are going to need another report

I think you nailed it! I turned over the keyboard and very fine flakes of aluminum rained down. After replacing the keyboard with a new one and moving it far away from the mill, the job ran just fine to completion.

I also found that my screw mapping went out to x = 13 but I had my soft limit at 12. Easy fix.

One odd but benign event - Windows switched to the login screen while I was running. No harm to the program but what parameter did I not set right?


Lesson learned - cover the keyboard before starting the spindle.

Secondary lesson - no matter how solid the software and hardware, swarf in the keyboard, or some other crazy problem like it, can make the system act in unexpected ways. This is exactly why I won't let the software control my spindle motor.

Thanks to all for their help,

Rick

[centroidsupport]

Glad we could help.

Windows switching to the login screen is strictly a Windows thing. I can't think of anything you could do in Windows that would cause that. I suppose you could double check to make sure all your power saving features are turned off but I don't see how any of those could put you at a login screen.

Unfortunately, we don't have a parameter that can prevent that. lol

[tblough]

Check the Windows screen saver settings. One option is to lock the workspace when the screen saver activates. That sounds like what happened. Disable the screen saver completely!

I prefer WetKeys waterproof keyboards for machine use. Completely sealed in silicone and available with built-in touchpads. No chip or coolant splash problems, and they can be washed with hot soapy water when dirty.

https://www.wetkeys.com/Touchpad-Plus-W ... 06t-bk.htm

[RGSparber]

Tom,

I found the offending option in the screen saver section. Hopefully, this solves the problem since I thought I had completely disabled the screen saver feature but clearly missed something.

That is a nice keyboard but a bit beyond my budget. I did take apart the keyboard that caused my problems and found that inside, it was a single, sealed silicone slab. So maybe it wasn't so bad after all. I used compressed air to blow out the plastic keys assembly and then blow out around this silicone slab. Not much more to it. I'll put it back in service but will keep an eye out for more odd behavior plus will keep it covered from now on when the spindle is running.

Thanks,

Rick