Jump to content


  • Content Count

  • Joined

  • Last visited

About 007

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you. I'll try this with the pull up resistor. The other method didn't seem to work.
  2. Thank you. I'm located in India, but should be able to find some time when the car isn't going to be used and ship the ECU over.
  3. 007

    Honda CAN protocol

    The only info from the ECU they expect are RPM and VSS. The HDS scanner also expects a repeating VIN frame to be able to connect. Because no other modules are touched, they remain happy and chatty as usual. There are two major issues here 1. the cluster expects a speedo pulse from the ECU once every 10 meters to keep the odo ticking 2. The last byte of each frame is like a checksum, which must be valid, or the cluster rejects the entire frame and everything goes haywire. I've managed to figure out enough of the logic to have the Macchina compute this byte and keep the cluster alive. Besides these, everything else is fairly straightforward.
  4. 007

    Honda CAN protocol

    Hello. I've spent a considerable amount of time analyzing the CAN data for a Civic FD2 in order to retain the stock cluster functionality. Now I can operate it with a G4+ Thunder and without requiring the stock ECU to be present on the CAN bus. There are some quirks of the Honda protocol that cannot be defined using CAN Manager, so I use CAN Manager to put the bulk of the data on the bus, pick it up with a Macchina M2, do the required transformation and retransmit. I was wondering if you would be Keen to incorporate this logic into the Thunder directly. This will hold good for a lot of Honda's with CAN driven clusters.
  5. Thank you for the response Simon. What you say makes sense, but do you reckon that the nice and round threshold at 55C is coincidental? I've disabled ECU Hold Power for now by using he same switched ignition output to A5 and C2. Would it be possible for the team there to recreate the issue in the lab by putting a Thunder under a hot air blower? I don't have another unit with me at the moment, or I'd have tested that one in the bench myself. In case there's a suspect joint, would it be worth the effort for me to take the case off and visually inspect the board?
  6. I haven't been able to find a way to generate a high side driven PWM output. I'd like to use this to implement alternator output control. Since the entire unit is grounded to the chassis, low side driven PWM isn't an option. Using GP Output and setting a threshold voltage causes the output to keep thrashing on and off, and makes the idle really lumpy and the lights flicker.
  7. It's been a while, but the build is finally alive once again, and this time, I have concrete information. The issue is most definitely with the ECU and not the wiring. There are no problems below ECU temp 55*C. When the temp crosses 55, the ignition signal input (pin C2) stops registering key off, and instead reads Active. When this was happening, I even snipped the wire going to C2 clean off and probed the voltage from the ECU, and it read 3V. I left things untouched and let the ECU cool down, with C2 still snipped off and the moment the temp dropped below 55, the ignition input correctly changed to inactive and the ECU turned itself off. I'd really appreciate if if someone could look into the matter and hopefully come up with a fix. This behavior doesn't look random to me, and I suspect should be reproducible in a lab.
  8. After everything's been installed, there's hardly any room to fit even a pinky finger around the ECU. So I'll try to completely wrap it in heat reflective tape and have a tiny opening facing the firewall. I don't think a diagonal sheet will do much good once the hot air from the fan diffuses everywhere in the engine bay. Summer temps here nudge 50*C. Thanks for the confirmation Simon. I must compliment you guys on this ECU. Even above 80*C, it handled itself like a champ. I had previously installed a Haltech Elite 1500 in a similar position, and that thing would start going into limp mode the moment internal temps crossed 60. I was finally forced to relocate it inside.
  9. Thank you for your response. To your points: The engine isn't self idling. The ECU isn't powering down. It isn't a sticky relay.I triple checked, and once when this was going on, pulled the relay clean off and the ECU still wouldn't power down. Pretty much impossible because the line that goes to the ECU's ignition signal pin is the only thing aforementioned relay controls. The low power side is wired to the ignition key, and the high power side to the ECU and nothing else. When I turn off the key, everything else in the the car that is on ignition power goes dark, except the ECU. Also, when this happens, the Runtime Value for Ignition Signal remains ON. I've wired up the Main Relay controls, and everything on the engine draws power from one of three relays that are controlled by the ECU's Main Relay Out. If this was something to do with flywheeling diodes, this would happen all the time. Every single time this has happened has been after a crawl through traffic. I wasn't able to log unfortunately, but I was keeping an eye on ECU internal temperature while a friend was driving through some pretty thick traffic after a long drive. There was no headwind to evacuate the engine bay, and the radiator fan venting all the hot air inside the engine bay drove up the ECU temp to a really alarming 85*C by the time we reached home, and I rushed out and pulled the C connector to kill the engine, which is what I always do when the ECU fails to shut down. This was the point when I decided to Thermaflect sleeve the ECU to prevent it from heating up. If that does not work, cabin mount is the only thing left to do. I really hope it doesn't come to that.
  10. Hello. I've been running a Thunder on a build I did recently. This ECU is installed in the engine bay like shown in the attached image. For the most part, the ECU doesn't seem to mind this at all but I did notice one glitch that would repeat consistently after some crawling through traffic. The ECU would not recognize the ignition key being turned off and would continue to idle the engine even after the key was removed. This doesn't happen when the engine bay is relatively cool. I haven't been able to identify the exact threshold past which this takes place, but I'd guess around 70*C ECU temperature. Any ideas why this might be the case? On to the second question, I plan to do something about keeping the ECU cool. While the obvious solution is to move the entire unit inside the car, that's something I'm considering as a last resort option. The current idea is to get a Thermaflect sleeve and wrap the ECU in it. That should prevent direct blasts from the radiator fan which is what seems to be sending ECU temperatures to 80*C and above. What I'm not sure about, however, is how this will affect the ECU's ability to dissipate its own generated heat. Can somebody from Link chime in to and let me know whether or not this is a good idea?
  11. 007

    Odo tick in User Defined CAN

    Hey Adam. The ABS module provides individual wheel speeds in a 8 byte frame. However, the speed displayed on the gauge and the odo tick information comes from the ECU utilizing input from the vehicle speed sensor mounted on the gearbox. I understand that it will take a lot of generic CAN functions to cover all possible OEM strategies, but in the meanwhile, would it not be possible to add a wheel revolution counter for either one or all four wheels, similar to the engine revolution counter that is already available? I feel that is a generic enough function for this purpose. I would really appreciate it if you could add this in. It is the only fly in an otherwise perfect ointment. Good to know that you are working on a plugin solution for this platform. I have reverse engineered a fair bit of the CAN structure to drive the gauge cluster, and would be happy to share that information if that will be of any help to you.
  12. Hi. I'm going to be building a FD2 Civic with a K24 engine and a Link G4+ Thunder. I plan to drive the gauge cluster using the User Defined CAN feature. I've managed to figure out everything except a tiny detail related to the digital odometer. Honda sends an "odo tick" once every 10 meters to the cluster. This is a 1 byte value that counts up every tick and cycles back to 0 after 255 and repeats. Every 10 ticks, the cluster increments the odo by 0.1. I've searched all the available data items to send in a CAN frame and haven't found a speedo pulse count or anything I could use to enable this feature. I see only speedo out (status), but that won't do. See the attached graphical representation of the CAN data. Am I missing something here? If not, could this feature be added in a future firmware update? Thanks in advance.
  13. Solved! Again, it was the default settings that did me in. The max and min clamps in the IACV settings were holding the commanded duty cycle back. The IACV works as I guessed before. Unpowered, the shutter is halfway open and that is where it returns to rest once any applied signal is removed. Grounding the IACVP pin rotates the shutter one way and grounding IACVN rotates it the other way. 50% duty cycle keeps the shutter at its default position. Anything above or below 50% either increases or decreases idle depending on how IACVP and IACVN are wired.
  14. I believe this IACV requires a PWM ground signal on both pins besides the +12V pin to move the shutter in opposite directions. Let me try to scope the stock ECU's control signals versus the Link and revert.
  15. Hello Scott. I finally managed get my engine running smoothly with my G4 Xtreme, but there's still a fly in the ointment. I'm trying to use a 3 wire Honda RACV that looks like this: http://i130.photobucket.com/albums/p254/bazwouterze/Honda Civic/DSC00876.jpg To do this, I set Aux Out 1 to ISC Sol Slave and Aux Out 2 to ISC Solenoid, with a frequency of 500 Hz. With Idle Control in Open loop, nothing that I enter in the Duty Cycle table has any effect. The engine idles really high like the RACV is fully open. I kept changing ISC Solenoid frequency all the way from 20 to 500 Hz, and nothing worked. Connected another RACV that I had lying around to see how the shutter behaved, and for frequencies above 20 Hz, I don't hear or feel the solenoid buzz like it should. Even when it clicks rapidly at 20 Hz, it is unable to control idle. I have a good mind to fix a 2 wire IACV there, but would really like to run the RACV. Any suggestions?
  • Create New...