Dan

Show:

What's happening?

  • 89Corvette Protocol Broken

    The 89 Corvette protocol and parser are broken in the release version. The symptoms are that the Interact mode won't sync up with the ECU. I'm in the process of modifying the sources to fully support this protocol. Dan.

    2005-04-16 20:22:04 UTC in FreeScan

  • Followup: RE: Compiling Win32 in 2005

    FreeScan now runs without crashing. I have basic 89Corvette functionality working. The next step is refining the displays to fcomplete the mapping of the 89Corvette. I should also be able to add the 86-88 TPI Corvette,Camaro Z28 and Pontiac Firebird to the list.

    2005-04-16 13:05:07 UTC in FreeScan

  • Followup: RE: Compiling Win32 in 2005

    I've made some good progress. I can now compile and execute FeeScan without crashes. One source of crashes was a unregistered control that is registered by the Windows Install. I need to get more information to close that loop. The other crash that affected me was a couple of coding errors in the 89Corvette protocol module that I'm using. Array sizes were set incorrectliy. It appears the...

    2005-04-15 00:19:04 UTC in FreeScan

  • Followup: RE: This project has spawn a new it seems.

    The Freediag program is an OBD II scanner. FreeScan is for vehicles that are pre OBD II. So this one (FreeScan) may have some life left in it. Dan.

    2005-04-13 16:31:05 UTC in FreeScan

  • Followup: RE: Compiling Win32 in 2005

    OK, I've been massaging the case of the includes source so it compiles now under WinXP and Visual C++ 6.0. The environment I'm in is case sensitive. Now I've got to figure out why the exe crashes when it executes! I'm also from the linux/unix world, so this development world is a bit foreign to me. I'll be adding a MAF based 1227165 ECU - TPI Camaros, Firebirds, and Corvettes. Dan.

    2005-04-13 16:23:56 UTC in FreeScan

  • Followup: Compiling Win32 in 2005 (part II)

    Also have found that the folder protocols is referenced as "protocols" and "Protocols". This is also providing compile time errors. Dan.

    2005-04-13 02:55:07 UTC in FreeScan

  • Compiling Win32 in 2005

    Ok, I'll admit I'm not well versed in Visual C and maybe there is a quick workaround, but on the surface it appears that the source in the current form has not been compiled in WIn32. Why? The includesin the source files are lower case and the filennames in most cases are upper and lower case, causing cpp to fail. Example include stdafx.h, however the file is named StdAfx.h... Am I missing...

    2005-04-12 23:39:18 UTC in FreeScan

About Me

  • 2004-05-10 (6 years ago)
  • 1038820
  • cyberdotone (My Site)
  • Dan

Send me a message