_bk_

4k7 ohm resistor, to switched +12V.

Apexi MAP sensor is 1.7 bar (at ~4.5V) boost pressure sensor. You can connect any MAP sensor, as long as: 1) you have the right connectors on both ends when making custom wiring harness. 2) know the sensor parameters. See http://1jzmerc.com/hks-faq/hardware/#map for a list of MAP sensors and parameters. D-Jetro RB25DET PowerFC (4E14BN32 and 4E14BN33) is legit - but limited to Power Excel workshops - according to http://www.apexi.co.jp/pdf/products/p_fc.pdf

Up for sale is package suitable for Stagea NM35 VQ25DET. Includes: * HKS F-CON V Pro ECU, v3.24 firmware. * NP5-15 harness (these are close to impossible to find as the OEM connectors are not made any more) * software & serial cable. It can be tuned in one of the following ways: 1) Airflow meter (airflow voltage map needs to be reverse engineered) 2) OEM MAP / IAT sensor (voltage map needs to be reverse engineered) 3) HKS MAP / IAT sensor (easiest solution / items not provided) 1700$AU for the package. Photos: (click for larger photo)

Any offers? No one wants to be unique?

Up for grabs is an obscure (but 100% functional) piece of kit. Includes: * HKS F-CON V gold v3.1 ECU. (major software version differences are superficial minor updates that 99.9% of tunes dont use anyway) * Custom-made F-CONV-to-ECR33 harness, with 2 optional switch outputs used (fuel pump relay, NVCS / cam shaft switch / solenoid) * 3 bar (43 psi boost) MAP sensor, and IAT sensor, together with sensor harness. * 100% english software, with hardware dongle and serial comms cable. * Support from me, so I won't leave you in the lurch after the sale. Features: * 32x32 fuel / ignition maps. * integrated self-learning target AFR map. * more tuning tables than your Apexi PowerFC. * ignition cut. * double-spark (this is not a well-known feature of the HKS ECUs) * switchable maps, so you can switch between E85 and PULP. For more feature details, check out: http://1jzmerc.com/h...-con-v-pro-gold I'm selling it as I bought the ECU as an extra - I have more than one - for testing purposes, and to demystify anything and everything about HKS ECUs and their variants. It is 100% functional and confirmed working and tested on an RB25DET. It can also work on an RB20DET or RB26DETT with minor harness / software modifications. a few more wires on the RB26, and different software settings (engine volume, injector flow rate) for AFM, or different injector pulse width for MAP tables. The only other thing you need to do is to wire the fuel pump into full speed mode. I will also provide _confirmed_ working maps that can either be used for RB25 AFM or 3 bar MAP sensor. It will only need a quick 1 hour tune on the dyno to refine it to your engine / turbo / injectors / cams. That's how long it took to tune (+1 hour for setup) with the 1JZ by a tuner who has never touched a 1JZ, and never tuned a HKS ECU before. Yes I have a 1JZ, and yes I did have an RB25 in the merc (that's another story in itself). but now it lives in the R32. $1300 for the lot. or $1150 without MAP + IAT sensor + sensor harness. Photos (click for larger):

Selling comms cable suitable for Power FC. Couple of limitations: * will only work with FCC3-compatible Power FCs. * will only work with FC-Pro software. * hardware does not support analog inputs. $125 buy now or start bidding from $99 plus postage - http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&item=250831753337

Guys, I've decided to start an unofficial FAQ for the HKS F-CON ECUs since there is a huge mystery around these ECUs. http://1jzmerc.com/hks-faq/ Any questions or if you have some information that is worth adding to the FAQ, please send them my way. Enjoy. David (BK)

Sold!

Selling this as a package: * Apexi Power FC to suit Nissan Skyline GTR R32 or R33. * Apexi FC Hand Controller to suit Nissan-based Power FC. * PC-interface hardware - works with CoPilot, FC-Pro (Power Excel software) and FC-Edit. I'm selling this on ebay as item #250798029895 - bids start from $850

Some more news / updates: 1) FC-HAKO now works with Toyota JZX100 auto (v3.43) as there is a PowerFC firmware bug. I guess it doesn't matter for the Nissan / Skyline crew Massive thanks to the Russian who was very patient in helping me debug and resolve the issue. Without people like him, it's very hard to resolve obscure technical problems. With english not his primary language, it was even more impressive that he managed to comprehend my instructions flawlessly 2) Repaired another PowerFC (Subaru WRX), this time a communications port failure. So it's legitimate what Apexi advise to NOT disconnect and reconnect HC (and other devices) while the PowerFC is powered up. Eventually the PowerFC comms port will fail. 3) Apparently Copilot development will cease. 4) Apparently Apexi (or AP Engineering) attempted to do a PowerFC for the VG30DETT as evident in this screenshot 5) FC-HAKO works no problems with RB26DETT D-Jetro PowerFC. 6) Haven't sold one FC-HAKO to a Nissan Silvia owner in Australia yet. Hmm. BK. http://fc-hako.com/

Sounds like a good idea to be able to change tunes without the laptop. What settings are different? I might be able to implement this without a PC involved, and allowing the hand controller to be connected to the FC-HAKO. I could make it that if you do a specific function on the hand controller that the FC-HAKO will read / write TUNE 1 or TUNE 2. I think that is a more elegant solution.

Updates over the last month: FC-HAKO will now transparently resend commands to the PowerFC if it receives bad (or no) data from the PowerFC. This will be attempted 3 times before failing over to software/application layer resend. FC-HAKO can now switch between all supported software without physical reconnection required, and now works without dropping the first packet of data (eg: CoPilot and PFCPing). Website has been overhauled and relaunched. (modern web browsers only) Paypal buy-it-now option is now available. Firmware update tool is now written in C and is available as an EXE. Just download the exe and bin files then run. Thanks to those who have provided their time and patience for technical testing in order to resolve really obscure comms problems. For those with HKS ECUs, you have not been left out. I'll release some info in the near future in addition to what has been recently released on the FC-HAKO website. David @ FC-HAKO

I will NOT give you two-for-the-price-of-one, to an address that is NOT yours, to a paypal account NOT in your name.

Has anyone tried FC-HAKO hardware on Windows 7 (any edition) (32-bit or 64-bit)? Or is it one of those long-standing rumours when something doesn't work, it sticks? "My PowerFC isn't a PRO! but it has a FC Pro sticker on it!!!"

I'd be happy to do the hardware side of things, together with a proof of concept software client (PC only). But it's low on my priority list. Hmmm... on second thoughts, that would solve the embedded logging box problem, too.

Via serial or bluetooth? FastHatch (Andre) was supposed to release his PSP-like modified hand controller device which would communicate with the PowerFC. He's already written the software and made pre-production hardware modifications... it's a matter of modifying the hardware, selling it as a package and supporting it But I doubt it will go anywhere apart from a once-off prototype, since his primary aim is to use this project as part of his masters degree. Anyway... it's not really my intended market now or in the future.

It's funny that everyone else has managed to update the FC-HAKO firmware no problem. But I had one guy - with 15 years serial communications programming experience - have the most amount of problems I have ever seen. Another guy, also with 20+ years software development experience, had forgotten to check the most obvious - if all the cables are connected - after spending 2 days trying to figure out what was the problem. So if you're a software developer, especially with serial comms experience, please don't ask me for help, and just be a normal user for once! :-)

A few weeks ago, I did update the FC-HAKO firmware on Windows 7 Ultimate 64-bit CPU. That was no problem for me. I couldn't haul that desktop computer to the car to test The most important thing is to NOT use Win7 64-bit "XP-mode" virtualisation. I had an American ex-pat guy in Japan do this, and he said it rarely worked successfully with PFCPing. Not only that, I think he also tried to connect within the first 10 seconds of connection, hence it "failed". And I think he also tried to use FC-Edit with auto-com detect mode, which is NOT supported. Hope that helps.

The most important thing with the FC-HAKO, or rather the USB-to-serial cable, is to allow _absolutely_ minimum 10 seconds after physical connection before you initiate connection with the PowerFC. It takes 10 seconds for the PC to detect and add the com port of the USB-to-serial device. A couple of times I carelessly tried to connect too early whilst testing and thought wtf was wrong. So it is best to allow 15 seconds. It's also recommended that you stick to the same USB port that it was initially detected on, especially for WinXP.

I only have Windows 7 Ultimate, installed on a 32-bit CPU. Updated.

Should be on the case itself. Or tell me which hand commander you have (FCC2 NT or FCC3) ER34 was apparently the "older" designed ones... but it appears to use the newer comms protocol. This is the same for the ECR33 PowerFC: old chip - hence not in production any more - but newer comms. yeah, v1.00 was a bit problematic over 5minutes+. v1.01 should have resolved it. I've tried it on the 1JZ + 15 minutes of logging, no problems whatsoever, considering the protocol used for the 1JZ / 2JZ is 6x quicker (~160 kHz) than all the other protocols (20-30 kHz) to the PowerFC.

I've personally tried and confirm the FC-HAKO works on: * Windows XP Pro * Windows 7 (32 bit) I know for sure it does NOT work on: * Windows XP Home (prolific drivers aren't detected) * Windows 7 (64 bit, in "XP-mode" virtualisation, barely works?) I released FC-HAKO firmware v1.01 the last few weeks to address some initial / continuing connectivity issues. v1.02 will be forthcoming later in the week to address corner-case SW & HW auto-detection issues, aswell as addressing support for all legacy PowerFCs. Weirdly enough, the 1JZ / 2JZ PowerFC is a special case with its own communications protocol (different speed). I would appreciate if there is anyone in Perth with an older PowerFC (with FCC2 NT hand controller) so I can verify it indeed works. The PowerFC model must be in the format of: * PFC ER34 9901-0123 * PFC RB25 9703-0515 * PFC RB26 9609-0351 Thanks. BK.

Don Dada: It's calibrated in the tuning software. FC-HAKO plays no part in the calibration process other than converting analog 0-5V input to an 8bit digital number.

Those that have used the FC-HAKO: Are you connecting the cable directly to the PFC without an extension cable? Is the plug a tight fit? If so, that could be part of the issue as it should go in much farther. If you have an extension cable, please utilise that. Also, are you removing the cable by pulling on the actual cable, rather than on the connector? Please do not do this. If it is a tight fit or does not work any more, I'm happy to send out a replacement cable, or get it replaced in person (by John) if you're in Perth. Send an email to [email protected] and we'll organise it from there. Or if you're happy to do it, modify the connector like: One other possibility is that the laptop may be in power-saving mode, where it might place USB devices into a lower power state after X amount of minutes of non-usage. But I am not sure if this could be causing it. I've only had it properly tested with XP, so I am not sure when it comes to Vista / 7. Sorry about the issues. I'm trying to figure out what is exactly causing them. David.

I've sold more overseas than to those in Australia! That would also explain why apexi stop making ecr33 PowerFCs... everyone wants one, but no one wants to buy one :-) David. (fc-hako.com)