|
0 registered members (),
17
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,521
Posts36,905
Members8,461
|
Most Online117 Jan 16th, 2020
|
|
|
#7243 - 05/31/13 11:57 PM
Re: MiProm 21 firing all car calls
[Re: john jay]
|
Joined: Jan 2012
Posts: 419
Broke_Sheave
addict
|
addict
Joined: Jan 2012
Posts: 419
|
I didn't see anywhere in the thread that he was talking about VP 10's I took the fault reading to be 18 in the motion error log and VP 10's in the drive error. Whatever the case if you check the motion error log and see a list of errors the one with the asterisk is the 1st one. So if you see a 23 motion Error, (Drive Fault) with the asterisk, followed by a VP 10 in the drive log, then you can assume the drive fault started the whole routine. Vice versa 18 asterisk then 23, ST to P relay opened while in flight. As for the calls firing remove DO17 upstairs to simulate and check car call inputs on debug.
Last edited by Broke_Sheave; 05/31/13 11:58 PM.
|
|
|
|
|
|
|