Tail sheave looks ok, did not see anything there to indicate any slippage for the governor. the call came in with this same symptom. I believe the floor table got lost with all the swapping around of boards and parts off and on of power countless times.
I looked back through my old notes, I had a Mod throwing 27 error's because I didn't have enough field currant. Try checking out the field parameters, and bump up the field parameter. While your at it check out motor for connections, brushes and and such.
I have not checked the motor field parameters. I will do that and compare to the other car. I did meg the armature and fields for integrity. I did swap the CN6 ribbon cable when we swapped the MSU board.
What if you just try to scale it in at inspect speed with the PPR adjustment in Motion Adjust. Not that it’s a real fix but it would be interesting to see if it would run consistently. Maybe you could even get it to take a scan. And if would run with MVEL over 150 fpm you could see if the 150 fpm ETS sensor board is reading the speed from the Encoder correctly.
At this point I would try swapping the Motion Adapter Bd. They are plug and play. Also have you tried a reinit? It will tell you if one of the drive parameters is mismatched with the Miprom parameters.
Is the new governor encoder the same rpm rating? What does the Debug Screen show under Motion Excuses while the unit is faulted? Dragging/sluggish brake (already mentioned) will cause a 27. Flakey brake switch (if used) will generate a 27/26 fault. Bad contacts, broken wires at Brake relays (SB, SB2 I think).
Faulty Brake Pick issues typically appear in Motion Region 2 or 3.
make sure motor encoder rpm is set to encoder rpm under msu adjust motion adjust. this is one parameter that is not listed in the miprom 21 black book, but i have had this a couple of times. have had a couple cars that will only change this parameter if the power goes out, or if you do not shut down the switches before main line. motor encoder not position encoder.
Good morning all. I can finally breathe a sigh of relief! We had success yesterday!!! Here's what happened.
Bottomed out I_DRV_VEL to lowest setting of 30 FPM and car ran in one direction without fault. I could then get a better reading on screen 3 in Motion info to compare the Vcmd, Vfb & Venc. car was still reading about 7 FPM higher on Venc = 34 compared to Vcmd.= 27. Compared to another car running same I_DRV_VEL speeds were only 1-2 FPM different.
Thanks to all of your suggestions I began looking at motor parameters, specifically the PPR of the motor encoder, which was set correctly according to the job parameter sheets, and param 558 ME Base Speed. I first tried changing the encoder PPR param 609 higher and lower but it didn't seem to have much affect. Granted I didn' make extreme changes as I didn't want to set the car on the safeties if I could help it. So I changed it back and lowered ME Base Speed from 850 to 700 and the car ran up and down on inspection without fault! I gradually brought the RPM higher until it faulted again and left it in a happy medium at 750. At that point we were able to get a floor table scan and run the car on automatic for the first time in a long time.
Here's where it gets even more interesting. On automatic the car was running in the high 370's with a M_VEL set at 350 and yes just clipping the over speed switch on the governor. Dropped M_VEL down to 325 and car still running high 350's. Dropped M_VEL to 300 car is running in the mid to high 330's. The other thing I notice is that the car seems to be overshooting the pattern a bit, not really noticeable in the car but you can hear it in the machine.
Put the car on a heat run, top to bottom for an hour or so to get things warmed up. Car ran fine, not overshooting floors or logging any faults. For now I am happy the car is running but I would like to get to the bottom of why I had to make those changes! My gut is telling me that even though the encoder tag says 2048 on the motor and 240 on the governor there is some difference between them and the original ones! I could probably make some more adjustments to param 609 and maybe get the car running a little better but not going to mess with it for now.
Anyone have any thoughts on this? I REALLY appreciate all the help and suggestions along the way.
ADC Scale 1 is usually set at 2.5v if the motor RPM is the actual RPM of the car. You can adjust this lower to decrease speed then adjust your PPR to attain the proper contract speed. The drive and the MSU must have the same ME Base speed which is usually the motor nameplate. The PPR adjustments must also be the same in both places.
what was the motor encoder rpm set to under MSU ADJUST. looks like you are only looking at the drive adjustments as john jay says above make sure the MSU adjustment s are correct as well
Thanks john jay and Vatorgator I did double check those parameters you suggested. ADC scale is at about 2.57V and I made sure that the RPMs are the same in both MSU and drive.
The car started to run into the overhead! This is only happening on a one floor run from the floor below. If we ran it from multiple floors below the top or bottom to top it would come in fine . It would not run into the pit or thru the bottom landing. It's not overshooting any of the other floors in either direction. Please correct me if I'm wrong but If we have a good floor table the MSU is calculating the slowdown distances at all the landings? with terminal interference from the limits how does the car run into the overhead on a one floor run? Could the top landing mag switch be faulty? I can see that we may or may not get both speed switches on the ETS board on a one floor run, in either direction depending on the floor height but we get both every time on a one floor run into the top landing. It seems like the car is trying to get to full speed on that one floor run. Is there a parameter for an alternate profile for a one floor run? I found ALT PL1 & 2 PROFILE but that looks like it has to do with load weighing. We do not have any load weighing device. Thoughts?
First off, 2.57 is too high. Lower ADC to2.5 volts, then check to make sure the ME Base speed is the same RPM as the Motor Nameplate, in the Drive and MSU. Then raise or lower your speed with the PPR parameters, again in MSU and the Drive. Use the motion averages screen to see when you have attained contract speed.. Also to see when the speed switches are picking. As for the going into the overhead, you may be tripping your ETS switch. Get the speeds correct then see what happens on the one floor run.
Good morning all, john jay you hit the nail on the head! First thing I did was lower ADC Scale to 2.50 and the car immediately responded. I moved the RPM and PPR settings in the drive and MSU to achieve the most stable speeds I could and the car has been running since Tuesday. My natural curious side wants to know what must have changed in the system that necessitated the change in that parameter that was set from the day the car was adjusted 25+ years ago? I am very thankful that the damn thing is running! Thank you all very much for your help with this!
Glad to hear it. It must be those pesky Gremlins again. It would be hard for that unit to run with the ADC at 2.57 unless all the associated parameters, ME Base speed, and the PPR's were jacked also.
