The same instrutions as with Kawi ecu work also with 2006 busa ecu.
Verification that everything works can be done by: 1) Ensuring that +5v is present after applying 12v 2) Checking from gauge data presense, that ensures even with an ecu that has nothing connected that the processor is running
Below what the gauge data looks like as a TTL signal (appr 7kb/s, about 8 bytes, 8,n,1)
__________________
When asking a question, you can also consider posting it to facebook:
You are right - so lets clarify: Gauge data stream has not changed its still in 33. The 29 is programming TX. I have not yet seen 29 to output anything, but 33 gaugedata (marked tech on the board) gives a hartbeat to instrument cluster. If that hartbeat is missing the FI light on cluster will be lit up. (EDIT - but you reminded me about one important thing. As I had dremeled one of the resesistors on line to 29 I can get the value for the missing resistor from the cpu to harness line 33 )
1
2
3
4
5
6
7
8
9
35
36
37
38
39
40
41
ig1
ig2
ig3
#11
#21
#31
#41
sol
fp
e1
n-
g+
oxh
txck
afc
htb
10
11
12
13
14
15
16
17
42
43
44
45
46
47
ig4
exs
sol2
sck
md1
cos1
cos2
b+
vm
n+
g-
ox
avf
htf
18
19
20
21
22
23
24
25
48
49
50
51
52
53
e02
clt
nt
ms
ts
cov1
cov2
cov3
vcc
vta
tha
thw
pa
at
26
27
28
29
30
31
32
33
34
54
55
56
57
58
59
60
e03
e01
sta
txd1
rxd1
sds
fwe
tech
rct
e2
taco
code
gp
pm
don
gndh
-- Edited by PetriK at 06:57, 2007-10-30
-- Edited by PetriK at 07:01, 2007-10-30
__________________
When asking a question, you can also consider posting it to facebook:
To make things even more clear it appears the 32 bit CPU requires no external programming voltage. After looking through the data sheet I haven't found any pin or reference to any type of programming voltage.
So the function of pin 29 on the older 16 bit ECUs was not moved to a different pin on the newer ECU, it was removed as it was no longer needed.
I wouldn't worry about that amount of noise. I'd be willing to bet if you put your probe on a ground point somewhere on the ECU board you'd see pretty much the same signal
Yep - dont really worry bearing in mind the amount of noise that injection, ignition and charger introduces, just limiting the potential reasons why programming does not initialize.
The measurement points were as close to the processor as possible (next to a pin) and Vcc on the harness connector. Same ground though.
__________________
When asking a question, you can also consider posting it to facebook: