Notifications
Clear all
Topic starter
29/05/2015 5:05 am
Have a 311. Car at bottom would only run up a foot or so. Gets software direction
Limit error. 2609. I disable software direction limit. And can run the car on inspect
And normal. Was told to do a learn trip. I get the learn trip enabled. Car runs down
But stops just shy of botttom floor and gets error. No bottom floor i can run it on inspect to bottom and all idz odz ntt ntb etb etc inputs are working. There are no directional limit switches any ideas as to what imissing here
Tried slowing down car on learn run.
Limit error. 2609. I disable software direction limit. And can run the car on inspect
And normal. Was told to do a learn trip. I get the learn trip enabled. Car runs down
But stops just shy of botttom floor and gets error. No bottom floor i can run it on inspect to bottom and all idz odz ntt ntb etb etc inputs are working. There are no directional limit switches any ideas as to what imissing here
Tried slowing down car on learn run.
29/05/2015 12:18 pm
Check to make sure your encoder (pvt) is counting and the position is changing. During the learn run you may need to jump out the final.
Topic starter
30/05/2015 3:01 am
Encoder is counting. Stops when ld comes on. Fault is 1ls distance
Is to large. Distance from ntb activation to bottom floor is to large
I tried setting 1ls2ls to max which is 3000. Same outcome
If move vane down. I get a no 1ls at bot floor error. while looking at count while doing learn run pvt count is 38800 then it switches to 2000 and counts up to around 45000 which is ntb off point. It turns around. Says down1ls hits ntb and switches to down bfl. It continues until count reaches 2100 or so and that is when it gets a no bottom floor error. Seems like it stops exactly the count that is the estimated ntsd zone length which is 2325. I kind of subtracted count from ntsb activation to when the car aborts the learn run it is the approximate value of the estimated ntsd zone length. Not an expert on 311 and this is just my thoughts not sure where to go now. Is it the pvt not counting properly ? Not sure of that be ause when i first deactivated software direction limit i was able to run the car from the bottom to the next floor and it did run up ok. Then it did run down. Then i started learn run procedure and here i am. Any help would be appreciated
As i am now lost as to where to go from here
Is to large. Distance from ntb activation to bottom floor is to large
I tried setting 1ls2ls to max which is 3000. Same outcome
If move vane down. I get a no 1ls at bot floor error. while looking at count while doing learn run pvt count is 38800 then it switches to 2000 and counts up to around 45000 which is ntb off point. It turns around. Says down1ls hits ntb and switches to down bfl. It continues until count reaches 2100 or so and that is when it gets a no bottom floor error. Seems like it stops exactly the count that is the estimated ntsd zone length which is 2325. I kind of subtracted count from ntsb activation to when the car aborts the learn run it is the approximate value of the estimated ntsd zone length. Not an expert on 311 and this is just my thoughts not sure where to go now. Is it the pvt not counting properly ? Not sure of that be ause when i first deactivated software direction limit i was able to run the car from the bottom to the next floor and it did run up ok. Then it did run down. Then i started learn run procedure and here i am. Any help would be appreciated
As i am now lost as to where to go from here
30/05/2015 10:42 am
If it will still run on controller inspection, run it and watch the count. If It is jumping around or counting fine in one direction and not in the other, then you encoder is bad. If you change the encoder and it is still jumping then the motion control board is bad. You shouldn't have to move the vanes once they are set unless something moved. And you shouldn't have to change the other perimeter. Also where are you turning the directional limits off. On a 311 there are two places. One is in the safety test area and the other is in the perimeters.(NY limit en)
30/05/2015 10:56 am
Are you using an Otis service tool or a laptop? If using otis tool go to 2-4-2 to see the count. The count on the learn run is only where the vanes are. Start your learn run just off ntb. Run it up till ntb gos low. Then start the learn run. Don't forget to jump the final limit out too. Some vintages of 311 you had too, some you didn't. Depended on the software version. Also the learn run doesn't overwrite till it's completed so the original is still on the EPROM.
Topic starter
30/05/2015 11:57 am
thanks for the replies magic, i thought maybe the encoder was bad, so i did check
M242, and ran the car up a floor, and back down to the exact spot i started, and the count was nearly exact, off a couple counts due to not stopping exact same point. at this point i knew the encoder was working, i was originally starting learn run just above ntb as you indicated, but decided to start it with car level at bottom floor, that is where i noticed in the learn run window, that the value to the right of the A: which i assume is actual started at 38800 or close to that, then the car would start running up and the count would change to 2000 and then count up to 4500 which is where ntb fell off, then run down and fail with NO BOTTOM error.
I have only worked on this unit a couple of times in the last 10 years, so i was not sure if this was normal. it just did not seem correct. so i decided to turn off main line, and remove the battery on the mcss board to see if i could get the stored pvt position count to start at 0 again. i waited a few minutes put battery back in and tried again. same outcome. now I'm starting to get frustrated, but still thinking something about that 38800 starting count is just not right. so this time i turned off unit, unplugged battery, shorted the 2 pins together, this time when i started the learn run, the A: value was 00000 and the car started counting up to ntsb which was around 2400 stopped came down and completed the entire learn and all was well. this was a really strange one car is running fine now. not sure what happened here why did the pvt count get so hi, pvt failure? mcss spike?
I did get to learn quite a bit in the last 2 days though.
M242, and ran the car up a floor, and back down to the exact spot i started, and the count was nearly exact, off a couple counts due to not stopping exact same point. at this point i knew the encoder was working, i was originally starting learn run just above ntb as you indicated, but decided to start it with car level at bottom floor, that is where i noticed in the learn run window, that the value to the right of the A: which i assume is actual started at 38800 or close to that, then the car would start running up and the count would change to 2000 and then count up to 4500 which is where ntb fell off, then run down and fail with NO BOTTOM error.
I have only worked on this unit a couple of times in the last 10 years, so i was not sure if this was normal. it just did not seem correct. so i decided to turn off main line, and remove the battery on the mcss board to see if i could get the stored pvt position count to start at 0 again. i waited a few minutes put battery back in and tried again. same outcome. now I'm starting to get frustrated, but still thinking something about that 38800 starting count is just not right. so this time i turned off unit, unplugged battery, shorted the 2 pins together, this time when i started the learn run, the A: value was 00000 and the car started counting up to ntsb which was around 2400 stopped came down and completed the entire learn and all was well. this was a really strange one car is running fine now. not sure what happened here why did the pvt count get so hi, pvt failure? mcss spike?
I did get to learn quite a bit in the last 2 days though.
31/05/2015 12:03 pm
Sounds like your motion control board(mcss) locked up. Glad you got it going. I might would replace that battery. FYI if it ever starts going on fire service for no reason replace the one on the ring car board too. Had a four car group and only one of them would go on fire service and it turned out to be that battery.