Apexi Pfc, Copilot, And Pc Interface

[Don Dada]

my testing was on windows xp and it was sweeet no issues

i have heard vista is generally ass and i wouldnt touch vista with a 10ft pole

I'm taking it that you used Fc edit right?

If so under setup what "Fc-box" do you select for it to recognize Fc Hako?

Also Paul i could of sworn that there was a list of widebands that were compatible with Fc edit/datalogit in the faq but i had a look again and didnt see anything...

or it was probably somewhere else i read it but..

Does it matter the brand of the wideband or will any one be compatible with Fc hako once it has a 5V output?

Btw...nice work guys

[STATUS]

Just upgrade to Windows 7. I've been using it on my laptop for 2 years with three different USB to Serial convertors (all running at once on the same machine at times) and it's worked flawlessly.

no go as lot of the Motec stuff is DOS based.

[STATUS]

you have a toughbook! you lucky man.... how good are they! my dell c400 does me fine for now.

if your seriuos dude, they are the only thing that interfaces with every different tuning interface with 100% reliability.... ive spent 10000000's on flash laptops, top of the range this and that with all the different windows and honestly the TOUGHBOOK ON XP eats every thing... i love it and i have a killer supplier now for them.

im looking to upgrade (new model) so when i get rid of this one i will let you know it will go CHEAP.

[paulr33]

if using FC HAKO and fc edit you leave it on defaults and set the right com port and it works

[Don Dada]

FC-HAKO includes USB interface, rather than using a USB-to-RS232 converter cable which then gets converted to TTL levels with a MAX232 or similar chip.

Not sure if people use more than 2 analog inputs or the 4 switch outputs. Those are not supported.

It also supports official software (FC-Pro JP only, including analog inputs), and third party software.

It also supports firmware updating, if any bug fixes or new features need to be added to the hardware in the future.

So will it work if i hook up my Aem uego wideband 0-5v output to the analog inputs for logging?

Will it have any issues with calibration?

[_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.

[_bk_]

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.

[urtwhistle]

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.

Hey mate, Im in perth with a ER34 pfc and your FC hako. The 1.01 firm ware made it alot easier to get it log for me. yet I still get the odd glitch with FC edit locking up.

Were do I get the model code? can I view it with the commander or do I need remove the fc and read it off the sticker???

Chris

[JonnoHR31]

i'm in perth aswell and pretty sure i've got the older type, will check tommorow.

[Don Dada]

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?)

BK>>>>>>

When you say it works with Windows 7 (32bit) are u referring to Windows 7 Professional 32bit or Windows 7 Home Premium 32bit ???

Or does it work with both???

I need to know so i can buy my new laptop asap.....well... and of course the hako

I've been looking for weeks now for one with xp pro but had no luck so this is excellent news...just need to know EXACTLY which version of Windows 7 i need now

Are there any other guys who can confirm it works with 7 (32bit)???

Btw you need to update this to the faq on your site...it is contradicting what u said here

Edited November 23, 2010 by Don Dada

[STATUS]

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.

Sweet, it turned out the old usb to serial drivers that were supplied literally screwed all my USB connectivity for other products, i had to do a full FTDI clean / erase. hopefully the new driver eliminates all the issues.

[_bk_]

Hey mate, Im in perth with a ER34 pfc and your FC hako. The 1.01 firm ware made it alot easier to get it log for me. yet I still get the odd glitch with FC edit locking up.

Were do I get the model code? can I view it with the commander or do I need remove the fc and read it off the sticker???

Chris

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.

[_bk_]

When you say it works with Windows 7 (32bit) are u referring to Windows 7 Professional 32bit or Windows 7 Home Premium 32bit ???

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

Btw you need to update this to the faq on your site...it is contradicting what u said here

Updated.

[_bk_]

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.

Edited November 24, 2010 by _bk_

[_bk_]

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.

[_bk_]

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! :-)

[W0rp3D]

Ever thought of porting this to mobile devices just as a disply thing, if you have i believe the android OS should be the first one to get it

[_bk_]

Ever thought of porting this to mobile devices just as a disply thing, if you have i believe the android OS should be the first one to get it

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.

[W0rp3D]

Via serial or bluetooth?

Anyway... it's not really my intended market now or in the future.

i guess its pointless answering the first question then, i thinkit would sell tho, especially bluetooth, i like to be able to see the hand controller but so do the switched on TMU, would be good to have it display on the phone and be able to turn it off if you get pulled over.

[JonnoHR31]

i'm in perth aswell and pretty sure i've got the older type, will check tommorow.

nvm, its a ecr33 one. my bad