0 registered members (),
11
guests, and
3
spiders. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
Forums13
Topics6,515
Posts36,880
Members8,461
|
Most Online117 Jan 16th, 2020
|
|
|
#26652 - 04/19/19 01:43 AM
Tac 50- fault 106, 53, 981
|
Joined: Oct 2015
Posts: 3
TCElevator2
stranger
|
stranger
Joined: Oct 2015
Posts: 3
|
So current state of the car: Was previously running fine, now it will not reach contract speed of 350. However If I change the contract speed in the parameters to 175 it will run to any floor with no issues. But if I place it back at 350 it Consistently everytime throws a 53 fault: safety string error open during run causing an emergency stop. After watching a few times it Seems that as soon as the speed reaches around 200 is when the fault happens... the decel rate is confirmed a proper speed at 120.. Also intermittently thows 981 fault. I have rescanned hoistway and back up scan as well. confirmed etsd, ecnt, edet, ncnt, and all the fixin's on vane in HW are not out of adjustment.. They all activate in IOs proper times at both Term landings. all parameters and adjustments seem to be set properly... Taking a step back to how this all started; arrived onsite and very hungry to multiple 106 faults: DSP battery backup failure. Before replacing the battery and During troubleshooting, the car would ONLY INTERMITTENTLY stop during a high speed run as if opening a safety circuit but not throwing any faults. during this time it would also loose all communication with the IMS program. To me it was Basically indicating power loss to the dsp board or communication board...the 12v dsp battery only had 4volts, so replaced battery. Repowered iOs and CPU checked and verified proper output voltage on All 4 power supplys in cabinet. PS4 seemed a little bit finicky, could've been my meter leads, But ultimately in the it ended up holding the proper voltage consistently at 15v once the new battery was in it stop the communications loss to the IMs system but fault continued and still will not reach contract speed... ANY help or advice at all would be greatly appreciated.... also to answer the question, no I have not adjusted or changed anything in the oscilloscope in reference to acceleration or deceleration and I would appreciate it if i could keep it that way. Thanks in advance
|
|
|
#26661 - 04/20/19 03:18 AM
Re: Tac 50- fault 106, 53, 981
[Re: boomer]
|
Joined: Sep 2015
Posts: 61
TCElevator
journeyman
|
journeyman
Joined: Sep 2015
Posts: 61
|
Sap? Checked and confirmed dsp board fusses
Last edited by TCElevator; 04/20/19 03:25 AM.
|
|
|
#26667 - 04/20/19 05:23 PM
Re: Tac 50- fault 106, 53, 981
[Re: TCElevator2]
|
Joined: Dec 2015
Posts: 1,538
Indirtwetrust
ElevatorPractitioner
|
ElevatorPractitioner
Joined: Dec 2015
Posts: 1,538
Local 18
|
Ok, 908 makes more sense, more like I was thinking anyway. Do you have reduced stroke buffers with physical switches in the hoistway in addition to vanes? They would occupy the first like 8 I/Os ETU1, ETD1, ETU2, ETD2, etc. if you do, make sure all are high when the car is in the middle of the hoistway.
Or You may have some bad data in the DSP for ETS tables. Put car in the middle of the hoistway on inspect. In this order, cycle CPU power, NTSI, ETSI, TBSS, Y, ETSS, Y, cycle CPU power again, NTSI, ETSI, TBSS, Y, ETSS, Y, cycle CPU power again, take car to bottom on inspect, put on auto, do a backup scan.
If that doesn’t work, check the snubbers on NCNT, NDET, ECNT, EDET inputs. If you position encoder is the optical wheel in gov, check alignment and clean wheel.
And it was said above but is worth saying again, make sure there isn’t excessive AC from V+ to VC
|
|
|
#26679 - 04/21/19 09:21 PM
Re: Tac 50- fault 106, 53, 981
[Re: TCElevator2]
|
Joined: Dec 2015
Posts: 1,538
Indirtwetrust
ElevatorPractitioner
|
ElevatorPractitioner
Joined: Dec 2015
Posts: 1,538
Local 18
|
Snubbers are suppressors. They’ll be wired from each input to VC on the controller terminal strip. The print tells you where the PMI module is. Inside the triangle there is an O for Output or an I for Input, then the I/O name, then x-n where x=the PMI card number and n=the module number on that card. It’s best to confirm with the PMI chart or IMS. In IMS you should be using 16 bit ports and there are 48 PMI modules on each card so the first 3 columns are PMI 1, 4-6 are PMI 2, 7-9 are PMI 3 etc. first column is PMIs 1-16, 2nd column is PMIs 17-32, 3rd column is PMIs 33-48. Hope that makes sense. There should also be a chart in the controller door.
|
|
|
|
|