Ficht diagnostic software problems version 1.42

[jays17pr]

i am working on a 175 ram from 1999 every time y put my laptop with each engine true the data cable it wont let me true pass the program select menu after i press 1 for ffi diagnostic it goes on black and say data error code 22

the engines 1 are e175fpxssr and serial go4784773
engine2 are e175fcxssv and serial go4793608

i got thr program in ebay last week and i have some problems


i need help if some can give me a hand i dont now wat i am doing rong

[ChampioNman]

Try this,, http://www.bbcboards.net/zerothread/205797

[Rude_115]

Are you running this on Windows XP or on an older machine? MUCH easier to get running on Windows 98. Also, have you successufully 'stored' the configuration data file that is needed for the Software to remember what port it is talking out. (Press F3 @ main menu, only need to do on initial use).

BTW did you buy SW from the canadian guy on ebay? Email him for support and see what he says. Please let us know how you make out.

[Laguna Freak]

In reply to the original question:
I recently bought the 1.42b software from the canadian guy on e-bay, that is supposedly for years 2003 and older. My laptop does not have a floppy drive and is loaded with 2007 XP Pro operating system.

I could not get the software from CD loaded with my limited computer literacy. So I called my friendly neighborhood computer guru and paid him $40.00 to come to my office this morning and get the software loaded and functioning without doing the whole DOS boot scenario.

So now after a few keystrokes and changing properties menu for this install program to compatibility with Windows 98, It now appears that I have full access to the program from either CD or my hard drive. What I understand is that XP has the ability recognize and operate older version software programs without going through all of the DOS boot bs to make it work.

I'll be hooking up to my ECU this afternoon to confirm full operation of the sofware. If there are issues, I'll report them here.

Hope this info is helpful to y'all.

[SEAHORSE]

version 1.42 had problems, but they were cured in version 1.42b

Make sure you are not running Windows XP or Vista, it only works well in 98, 95, 3.1, or DOS without a lot of modifications.

Also be sure the correct serial port is chosen and that there isn't a modem on the same one.

Since you bought it on Ebay, it may be a bootleg copy and who knows what is on it. Does it have a factory label on the disk with the OMC logo?

[Laguna Freak]

It has no factory label.

My computer guru set up XP to run this program with Windows 98 compatibility.

Currently I know that the program opens from my hard drive and will allow me to proceed until it detects that there is no com to the ECU. When I get it home tonight, I'll connect to my onboard ECU and take it from there. I do have the serial port identified as COM1. So far all screens appear to be the same as illustrated in the accompanying User Manual.

Having not connected to the engine yet, it appears that everything is ready to go.

[chumleydoo]

I have 1.42 software also. for 2000 175 ficht. loaded on Gateway solo Laptop w/ windows 98. Set for correct port (Com 1). Get to communication screen and says no communication?? Battery switch is on, Key is on, batteries are 100%, 95% charged, cables are clean and tight, but still no communication??

HELP!!!

[wv21ss]

thats what mine does, i got it from e-bay a few years ago and never got it to work.

[chumleydoo]

I got mine from e-bay, everything loaded well, but just won't communicate w/ each other. Could it be a bad cable??

[SEAHORSE]

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by jays17pr &raquo;</TD></TR><TR><TD CLASS="quote">

i got thr program in ebay last week and i have some problems
</TD></TR></TABLE>


<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Laguna Freak &raquo;</TD></TR><TR><TD CLASS="quote">
I recently bought the 1.42b software from the canadian guy on e-bay,
</TD></TR></TABLE>


<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by wv21ss &raquo;</TD></TR><TR><TD CLASS="quote"> i got it from e-bay a few years ago and never got it to work.</TD></TR></TABLE>


<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by chumleydoo &raquo;</TD></TR><TR><TD CLASS="quote">I got mine from e-bay, everything loaded well, but just won't communicate w/ each other. </TD></TR></TABLE>


What's the common denominator here ?

[Laguna Freak]

Seahorse, good point. However because I know these FICHT engines to be complicated, I would ask for your knowledgeable feedback on the following.

So here goes...

I have a '99 E175FPLEEC with 387hrs on a 2000 powerhead replacement and full fuel mapping/software upgrades. Battery voltage and all power connections/grounds/wires/terminals are clean and tight. Prior to purchasing the software, a tech at DFI indicated that the symptoms I explained to him were indicative of ECU failure. Specifically, the only circuit identifiable as faulty with a DVOM was the "Fuel Pump Control by ECU". e.g. With key on after initial 10 second pressurization of the circulation pump, the fuel pump relay begins rapidly cycling on and off and the voltage at the PDP wire harness fluctuates rapidly from 10.6 to 13.2 on this circuit. At the same time, all warning lights except low oil flash in cadence with fuel pump relay switching. With engine running at idle speed to 1000 rpm, this same circuit reads no voltage and lights do not flash. Can't get beyond 1000 rpm because it stalls. This entire scenario is somewhat intermittent in that as the engine and ECU warm, it stalls more readily and it has gotten progressively worse since the day I almost had to get my 20' flats boat towed 3 miles in a 3' Lower Laguna Madre' chop. Then after it cools, it behaves better (relatively speaking). Pressure tests reveal 7 psi on low pressure and 24 psi on high pressure fuel circuits and low pressure pulse pump passes static test.

I bought the software to rule out other possibilities prior to sending the ECU to DFI. So this afternoon I connect to ECU. Com is intermittent but successful enough for me to:

1) read and clear the same trouble codes that I retrieved via the check engine light prior to flashing in cadence with fuel pump relay.
2) verify ECU software ID, model no., engine hrs at 387, etc, etc
3) review rpm graph which read 100% at 1000 rpm (very strange and inconsistent with prior report)

It would not maintain COM when attempting to conduct static EMMDIAG tests on fuel pump and injectors and COM became increasingly worse after warming engine and attempting to check for hard codes after clearing. Incidentally the trouble codes were malfunctioning AT Sensor, TP Sensor below range, WT switch activation. Both AT sensor and WT switch were indicated by check engine light diagnostic code reading and tests revealed them to be responding to temperature changes in the inverse of what a negative temperature coefficient thermistor should. Essentially resistance for both increased with temperature and WT switch activated at 165 upon re-heat after heating to initial activation at 213 and then cooling to deactivation at 155. They were both replaced prior to establishing COM and the codes remained cleared after clearing and running the engine today.

So because my initial diagnostics led me to the fuel supply circuit and then the DVOM revealed the only discrepancy to be in the pump control electrical circuit plus the other symptoms and EMMDIAG results all seem to be pointing me to a faulty ECU.

Can you offer any sage advice on this that would contradict a faulty ECU?

Thanks for your time and thought. I really appreciate it.

[SEAHORSE]

A bad ECU or EMM can have connection problems with a laptop, and from your description, it sounds like a bad one.

I haven't used ver. 1.42b in so many years that I've forgotten what a lot of it is like. It always had problems with the newer Windows operatiing system on some laptops. With serial port adapters, it was even more finicky. The factory diagnostic CD that works with Windows and on all FICHTS and E-TECs is all I have now.

[Laguna Freak]

Thanks Seahorse. That helps to put my mind at ease that I'm diagnosing correctly. One more question if you don't mind.

I have previously seen on the internet a more recent version of the diagnostic software for all Evinrude DI engines including E-TEC sold for about $50.00 from other marine dealers, not on e-bay. When I contacted on of them they had a superseding part number that was $750.00 and required an activation code. So my question is; do you know where I could find this or similar upgraded software at a much more reasonable price than $750.00?

Thanks again!

[SEAHORSE]

$750 - Wow, that's outrageous

Google FICHT software and there are a few companies that pop up that sell the programs, they are several hundred $$ but no where near $700

[Laguna Freak]

Re: Ficht diagnostic software problems version 1.42 (wv21ss) (chumleydoo)

I got mine from e-bay, everything loaded well, but just won't communicate w/ each other. Could it be a bad cable??

chumleydoo and wv21ss,

You haven't provided enough info for me to be able to offer an opinion or suggestion based on anything other than conjecture. But, I would say that because my software appears to be communicating and Seahorse has indicated that a faulty ECU can interupt COM, you may have ECU issues. I would do everything I could to rule that out before spending the cash for ECU re-build.

The other issue may be how the program compatibility is configured in your laptop.
I had to have an "expert" load and configure mine to get XP operating system to operate it in Windows 98 compatibility mode. Also consistent with what Seahorse said; I do not have a serial adaptor to USB or other. My COM cable is connected directly to the serial port on my computer. I did have to re-set my com port and re-boot my computer to get it to communicate.

Hope this helps.

[chumleydoo]

Using Gateway Solo Laptop. Windows 98.
Copied files/program to hard drive of laptop.
States in manual it performs better when loaded to hard drive.
Loaded and set up to operate in DOS mode as prescribed.
Cable is connected directly into 9 pin serial port in laptop.
Connected to ECU port, then turn on Main Battery switch, then turn on key/ignition.
When I attempt to go int #1 - Ficht Diagnostics, I go thry 2 screens and then arive at the non-communication screen.
Then I'm stuck !!!!!!

[SEAHORSE]

You have the ignition key ON, right?

[chumleydoo]

YES SIR

[Laguna Freak]

How does the engine perform? What symptoms are you attempting to diagnose? To your knowledge, is the ECU/EMM functioning properly?

Check all of your program files properties menus and make sure all are operating in Windows 98 compatibility. I'm just guessing here but if some are set to Windows 98 and/or some are set to DOS or the computer has conflicting compatibility modes checked that could cause a problem.

My underestanding is that if your operating system is Windows 95 or 98, you do not need to operate in DOS or DOS mode.

Let us know.

[chumleydoo]

Engine 2000 E175FPXSSV - was/had what sounded like an octane knock, and was losing/gaing RPM while under power. Spitting and Puttering. So I put it on the trailer. Had the compression checked in all cylinders (100 PSI - in all cylinders). That is why I bought the Diagnostic Software to Diagnose engine. We no longer have an Evinrude dealer in the area, But I have an Evinrude/Johnson/Mercury skilled mechanic to do the work. He just did not have the diagnostic software.