Daughter Board Communication Error

hatchbacKed · Post by **hatchbacKed** » Fri Nov 18, 2005 10:56 am

I'm getting this problem as well. It started a week ago, the CEL also comes off after turning the car off/on. But the Kmanager is throwing out "Daughter Board Communication Error". This just happened without doing anything to the car, used to run without it. So how did you guys fixed this? Can anyone help me solve this? I have attached a datalog with the error. thanks for any help. (K24a on 93vx)

bossman032 · Post by **bossman032** » Fri Nov 18, 2005 11:15 am

hatchbacKed wrote:I'm getting this problem as well. It started a week ago, the CEL also comes off after turning the car off/on. But the Kmanager is throwing out "Daughter Board Communication Error". This just happened without doing anything to the car, used to run without it. So how did you guys fixed this? Can anyone help me solve this? I have attached a datalog with the error. thanks for any help. (K24a on 93vx)

well same thing happened to me I didn't do anything to the car. Hondata is saying my car has wiring issues. yea right... :roll:

when I clear security the car runs like shit..even after I load the hondata map... :roll: a few people are getthing this error..

why will the car thorw a data board error code because of the wiring??
I don't think so common sence say that..my car starts runs fine with the rsx cal file only thing is that it doesn't rev..it was running fine before the data board error code.. :roll:

Post by **Spunkster** » Fri Nov 18, 2005 12:00 pm

are you still receiving the error code?

bossman032 · Post by **bossman032** » Fri Nov 18, 2005 12:04 pm

yes :roll:

Post by **Spunkster** » Fri Nov 18, 2005 12:50 pm

If you are receiving the daughterboard communication error, you can send the ecu to us with a detailed description of the problem.

Bossman, in your case, you have had multiple problems with your wiring due to an engine swap. Your ecu has been replaced once already. Previously you said you cleared security, but did not say you were still receiving an error message...you said that the car ran terribly and ran the same even if you removed half the sensors. Based on this informtation it sounds like there are other issues at hand. Improper wiring can damage the ecu as it has done in your case once already and can also damage the K-Pro Board.

bossman032 · Post by **bossman032** » Fri Nov 18, 2005 1:18 pm

well the problem is this. we have to keep clearing the security. that error goes away. but it comes back on. then we clear security and load the k24a2 map the car runns shitty backfires a lot. then we load the k20a2 cal file the car runs perfect idles right but it bogs when u rev it. with the k24a2 cal it runs very bad, backfires. with the a2 cal file it doesnt backfire. also when we clear secuirty and try to data log with the k24a2 stock cal file it goes offline. but with the rsx cal loaded the car runs fine just it doesn't rev and I can also data log

its not giving no cel codes we disable the obd2 and multiplexter along with the

right now my plan is to get the ecu test in a stock rsx car or swap..
I doudt its my wiring. it won't just kill the ecu.. its probaby a bad sensor on the motor or ecu. Like I said it was running fine for few weeks..

as u see above the other guy had the same problem..the daughter board error just showed up..its not just me..we got get this problem figured out...

hatchbacKed · Post by **hatchbacKed** » Fri Nov 18, 2005 1:43 pm

Spunkster wrote:If you are receiving the daughterboard communication error, you can send the ecu to us with a detailed description of the problem.

Spunkster do you work for hondata? anyway that sounds great. How many days till i get it back? Can I just take it to a nearest hondata dealer? Just wanted to verfiy where to mail it:
Hondata, Inc.
386 Beech Ave
Unit B2
Torrance, CA 90501

thx

bossman032 · Post by **bossman032** » Fri Nov 18, 2005 1:48 pm

hatchbacKed wrote:
Spunkster wrote:If you are receiving the daughterboard communication error, you can send the ecu to us with a detailed description of the problem.
Spunkster do you work for hondata? anyway that sounds great. How many days till i get it back? Can I just take it to a nearest hondata dealer? Just wanted to verfiy where to mail it:
Hondata, Inc.
386 Beech Ave
Unit B2
Torrance, CA 90501

thx

try clearing your security under the online options. if that doesn't work..

brenson · Post by **brenson** » Sat Nov 19, 2005 1:42 am

i have the same problem too.

had KPro in PRB board, it will throw daughterboard comm error after driving around for a bit. sometimes it does it only after driving a bit, sometimes does not do it, sometimes right from the start.

took KPro board out of PRB, put it into another KProed PRC board, it was fine for a while, then after 1-2 days driving, the same error came out!!

what could be the cause for this problem?

hatchbacKed · Post by **hatchbacKed** » Sat Nov 19, 2005 11:52 am

Do I need to load the same calibration again after clearing the security? I don't have my tuned cal file in my computer and I just updated my Kmanager prog. and now I can't seem to download my current calibration from the ecu properly with the new program. I don't see this procedure solving the problem if it is loose board or wires in the hardware... I'll give it a few try and if all fails I'll send it to you guys (Hondata) and have a look at it. thx

bossman032 · Post by **bossman032** » Sat Nov 19, 2005 6:51 pm

they will probably say its your wiring lol.

my car started today only works with the accord k24 cal file..

no cel codes.. I wonder why the stock cal file doesn't work..???
I tired several tsx cal files none of them work..

looks like something to do with the ecu not my wiring.. :roll:

chunky · Post by **chunky** » Wed Oct 18, 2006 12:51 am

Hondata wrote:Typically the cause is the KPro board coming loose, the soldering of the pins into the ECU or the soldering of the two jumper wires on the bottom of the ECU. Sometimes these problems do not occur immediately until either vibration or colder temperatures results in an intermittent connection.

I've just started to get this error intermittently. I've never had any issues with the ECU at all prior to this. This first occured one morning after a rather chilly night. I cleared DTCs and it didn't come back until about a week later. This time I cleared DTCs and it immediately came back. I cleared again and it stayed gone. Since then it has come back intermittently.

So far I see that I need to check the grounds for the ECU, and then I need to check the daughterboard itself as well as the two jumper wires. Is there anything else known about this issue?

Post by **Hondata** » Wed Oct 18, 2006 8:38 am

The daughterboard communication error is caused by very low battery voltage while starting the car.

It is caused by:

- using a smaller capacity battery than stock
- relocating the battery
- using a battery which has been damaged by a deep discharge
- engine swaps with incorrect wiring

chunky · Post by **chunky** » Wed Oct 18, 2006 10:32 pm

Hondata wrote:The daughterboard communication error is caused by very low battery voltage while starting the car.

It is caused by:

- using a smaller capacity battery than stock
- relocating the battery
- using a battery which has been damaged by a deep discharge
- engine swaps with incorrect wiring

thanks for the reponse. I do have a relocated battery, but it's been running fine for well over a year with the k-pro unit. During the last period of inactivity, the battery did become discharged to the point where it would not crank the motor, however it's been about 2 months since the new motor went in and this error has only been occuring for the past couple of weeks. It is the OEM battery that came in the car when I bought it (2002) so it's possible that it is on it's way out. I will check the battery with a multi-meter tomorrow, i'm pretty sure the voltage at the terminals in the engine bay are at >14V with the car running and >12v with the car off.

Post by **Hondata** » Thu Oct 19, 2006 9:31 am

The only voltage which is important is the voltage while cranking the engine. However, it would seem to me that the problem has been diagnosed and identified.