Help Please! MSG PM Following Error Limit Exceeded?

[Cellar Dweller]

Help Please! MSG PM Following Error Limit Exceeded?

Have DX-32 controller on 1995 Discovery 308. I thought I had the problem worked out but no.

At the end of a tool path I get "MSG PM Following Error Limit Exceeded" I preceded to the "main page" and it is indicated as error "#83 Lube Pump Interval" with a value setting of 0.000000.

The Description reads:
"The time, in seconds of axis motion, between activations of the lubrication pump. A value of zero specifies always on."

I clean and check out the lube pump. It is working and sends oil the the linear guide way bearings.

So what else should I look at and how the heck does the controller KNOW when the pump as run or not. Also I cannot get into parameters because of a password problem. I thought I read about that in a different post. I will search.

All help will be greatly appreciated, making parts, need to keep machine moving.

Thanks,
CD

[MetalicGlow]

Originally Posted by Cellar Dweller Help Please! MSG PM Following Error Limit Exceeded? Have DX-32 controller on 1995 Discovery 308. I thought I had the problem worked out but no. At the end of a tool path I get "MSG PM Following Error Limit Exceeded" I preceded to the "main page" and it is indicated as error "#83 Lube Pump Interval" with a value setting of 0.000000. The Description reads: "The time, in seconds of axis motion, between activations of the lubrication pump. A value of zero specifies always on." I clean and check out the lube pump. It is working and sends oil the the linear guide way bearings. So what else should I look at and how the heck does the controller KNOW when the pump as run or not. Also I cannot get into parameters because of a password problem. I thought I read about that in a different post. I will search. All help will be greatly appreciated, making parts, need to keep machine moving. Thanks, CD

I get the same following error on my DX32, except it always does it when the X axis homes at or near 0.0000". I turn off the machine, unplug/plug in the BMDC board a few times to clean the contacts, then reboot. The problem goes away for a few more weeks (lol). The contacts tarn on the board and a good connection is lost. At least that seems to be what causes the problem on my machine.

[Cellar Dweller]

Update: I changed the parameters to run the oil pump once an hour, just to get help with trouble shooting and see if my machine would run the entire part. But the machine threw an error in the same exact spot, BUT this time it gave me a #84 (the next in line) error with regard to how much time to let pass once the oil pump is on to initiate a pressure test.

I found my password in a forum search. So others can write it down of find it easily in a search. The password for my DX32 DX-32 is 111257. This is the password to access the parameters on a 1995 Bridgeport discovery 308 w/ DX-32 controller.

Does ANYBODY know how the controller knows what the pressure is and how often it runs? How does the controller compare the parameters to what actually happens?

MetalicGlow,
Thanks, I will give that a try.
BTW, do you know were the pressure sensor for the oiling system is?

Thanks,
CD

[Cellar Dweller]

Update: Well my problem has nothing to do with a #83 or #84 error. It is a programming problem. I guess I should say it's a Post processors and or the machine controllers capabilities problem. Way to go Bridgeport! Post a oil pump error when the controller does not know what to do!!

Anyway, the machine stops (shuts the drives, coolant, and spindle off) at the end of a tool path. If I skip the line it stalls on then it will run, but I have input an addtional S code for the spindle to turn on then it stalls again in the same place. The operation is a ramp contour with 4 passes. It stalls at the end of each contour. Here is a small bit of the code. From here I am going to the mastercam forum and giving the guy who wrote the PP a call. So I guess the lesson learned for me is, always test the machine with a program you know it runs properly before paying to close attention to any errors.

Thanks,
CD

N1370 G99 X1.1038 Y-.727 Z-.898
N1380 G99 X.2316 Y-.727
N1390 G99 X-.21 Y-.6491
N1400 G99 X-.21 Y.21
N1410 G99 X1.16 Y.21
N1420 G99 X2.744 Y.21
N1430 G99 X2.744 Y-.362
N1440 G99 X2.744 Y-.4395
N1450 G99 G3 X3.494 Y-1.1895 I3.494 J-.4395
N1460 G99 G1 X4.244 Y-1.1895
N1470 G99 X4.244 Y-1.1895 Z-.798 F6.4 (STOPS HERE)
N1480 G0 Z.25 (WILL NOT RUN) (IF I JUMP TO THIS LINE AND INPUT A SPINDLE SPEED, IT WORKS)
N1490 G0 X4.194 Y.3105
N1500 G0 Z.127
N1510 G99 G1 X4.194 Y.3105 Z.027
N1520 G41 G48 X4.194 Y.3105 F18.3
N1530 X4.194 Y.3105
N1540 G99 X3.444 Y.3105

[machintek]

I believe this machine uses a cam style oil pump so the pump on on/off timers are irrelevant.
Looking at line 1450 a feed rate move is commanded with no feedrate. It may be necessary.
Same for line 1460.
Check programming manual.

George

[md63825]

Did you ever get that issue resolved? I am getting that error message on my Z axis. Usually happens when machine goes to make a Z rapid move.

[Cellar Dweller]

Yes, I did. But, its been a few years, and I don’t remember all the details.

So here are some facts, as best I can remember, hopefully they’ll help you out.
I used Mastercam X3 at the time.
The problem was not my machine, that is to say, I did not “fix” anything, like a faulty connection, bad onboard PC, controller boards, etc.

The problem was in the way certain selections in Mastercam created a post that was formatted differently than other posts. In other words, my problem was specific to that posting. Either MC or my PP is output in a slightly different format depending upon, tool path, speed, drill, tap, ramp, comp, etc.

I just changed the routine to something else and it worked great. As I am typing this I am starting to remember that it was related to the “look forward” it “saw” something in the upcoming code, and it did not compute. LOL I think it may have been, drill verse drillpeck, or mill, etc. It was something simple, I just can’t remember. Hopefully, you already have a solution. But, if not I would look at what “type” of command you have coming for that z move, and change it to something else and see if the post will run. Start narrowing down which “call” or “block” is not computing.

Sorry I can’t be more specific.

Also, review my post in this thread of 09-28-2009, 07:15pm, maybe the gcode may give you a clue as to what is going on.

Thanks,
CD