Haltech Haltech F9 Turbo MAP anyone ? ? ?
#1
Haltech F9 Turbo MAP anyone ? ? ?
I can't find jack **** in terms of a F9 Haltech base map. It would help me to get my friends car started, or at least something to start with and then build up. Does anyone know where I could get one? Hitmans site for MAPS has been down for weeks.
Its a Turbo 88 motor with a T04, 550cc primaries and 1650cc secondaries.
Its a Turbo 88 motor with a T04, 550cc primaries and 1650cc secondaries.
#5
'RECONNECT HALTECH'
Rxrotary2_7 suggested that and I downloaded Maps from ricemobile.net. I changed the filenames extension toi match the f9 filenames extension. It seems to have worked but... It's doing me no good b/c I can't get the damn laptop to communicate with the Haltech unit properly.
I get connected and 'ONLINE' when I turn the car on. The map which is stored in the HALTECH gets downloaded to the PC (you would think they are communicating right?) . But then when I go to calibrate the TPS it keeps telling me to 're-connect Haltech'. It says this when I view the MAPs too. I can't figure this thing out. The ECU is getting power and ground(I checked at the harness). The communications cable isn't bad (I tried 2 different ones). I even pulled back the wire shield to check the integrity of the wires and they look good.
Could the software I am using be incompatible with the ECU? Its F9 software,ver 5.06. Could the COM port on the laptop be bad or configured wrong. I am using windows 98.
I would like to try another laptop but I dont have one with with anything less than WIN2K on it.
I get connected and 'ONLINE' when I turn the car on. The map which is stored in the HALTECH gets downloaded to the PC (you would think they are communicating right?) . But then when I go to calibrate the TPS it keeps telling me to 're-connect Haltech'. It says this when I view the MAPs too. I can't figure this thing out. The ECU is getting power and ground(I checked at the harness). The communications cable isn't bad (I tried 2 different ones). I even pulled back the wire shield to check the integrity of the wires and they look good.
Could the software I am using be incompatible with the ECU? Its F9 software,ver 5.06. Could the COM port on the laptop be bad or configured wrong. I am using windows 98.
I would like to try another laptop but I dont have one with with anything less than WIN2K on it.
#6
did you try to use 2 different computers. one to view the e6k maps running in the e6k program, and then the one using the f9 software to basicly "copy" what the values are in all the e6k maps (obviously minus the ignition) and save that way, then try to load the f9 based map into the ecu? instead of just changing the extentions like we were discussing before. it may take a while, but try to upload *something* different and then see if when you view the maps online they haev changed.
as far as the tps goes... did you use a GM sensor? are you sure it is hooked up right? this would cause it to say something similar to what you said. i forget exactly what mine said before....
as far as the tps goes... did you use a GM sensor? are you sure it is hooked up right? this would cause it to say something similar to what you said. i forget exactly what mine said before....
Trending Topics
#8
I dont think it's the way I was switching the extensions of the file names. I didnt even try to use the E6k map. I dwas trying to use the map that came loaded in the HALTECH CPU.
The TPS is a GM TPS from an anniversary Turbo Trans AM ( 3 BAR) . I don't think that this is my problem. I am getting communications errors across the board. I get them in the maps, I get them in the TPS calibration. I get them whan I just want to look at the engine data. I get them pretty much everywhere.
The TPS is a GM TPS from an anniversary Turbo Trans AM ( 3 BAR) . I don't think that this is my problem. I am getting communications errors across the board. I get them in the maps, I get them in the TPS calibration. I get them whan I just want to look at the engine data. I get them pretty much everywhere.
#12
confused. . . exactly.
I get the reconnect Haltech when I go to calibrate TPS & about 6 secs after I go to any particular fuel map. I also get it flashing on top(very quickly/barely legible) when I go to ENGINE DATA.
I get the reconnect Haltech when I go to calibrate TPS & about 6 secs after I go to any particular fuel map. I also get it flashing on top(very quickly/barely legible) when I go to ENGINE DATA.
#14
had this problem with a mates F9, are you booting up your laptop in dos or windows and running the software through it??
if i tryed through windows i would get that,
but dos worked fine,
Dale
if i tryed through windows i would get that,
but dos worked fine,
Dale
#18
sheeshh.. i dont know anything else to tell you pal. maybe try calling haltech aust. ?? or ask on the yahoo haltech support groups which has recently turned into the "bash haltech and praise microtech" support group...
#19
my sony vaio used to the same thing. the simple solution for me was to make a bootable floppy and run the haltech program off the floppy. worked perfect. that laptop died so i am using a 10 year old toshiba satellite now and it works in win98
#20
Vosko,
I can give that a try.
Forgive me because I dont understand this bootable disk stuff.
A bootable disk? I think the HALTECH manual states how to do this. I tried it their way but when I restarted the LAPTOP the disk didnt start , instead it just went to WINDOWS.
I will look into this . Thank you mr VOSKO & company
I can give that a try.
Forgive me because I dont understand this bootable disk stuff.
A bootable disk? I think the HALTECH manual states how to do this. I tried it their way but when I restarted the LAPTOP the disk didnt start , instead it just went to WINDOWS.
I will look into this . Thank you mr VOSKO & company
Last edited by dcee; 03-04-03 at 03:15 PM.
#21
danny here is how to make it. put a floppy in your floppy drive. type sys a:
then copy the F9 program and any maps onto the floppy disk
reboot machine. make sure floppy is set to first boot priority in the bios.
after it boots type F9A (or whatever) that's it. it's super easy! it actually took me a while to figure that out because i had a brain fart
then copy the F9 program and any maps onto the floppy disk
reboot machine. make sure floppy is set to first boot priority in the bios.
after it boots type F9A (or whatever) that's it. it's super easy! it actually took me a while to figure that out because i had a brain fart
#22
i am curious to see if this fixes your problem. if it does, i am curious to hear an explination from vosko or someone else about *why* running it off the floppy will allow it to work, but runing in DOS does not. i am not a 'computer guy' by any streach of the imagination, and just curious...
#23
I went to play with the computer again last night. Long story short... no good.
I made a boot disk like Vosko and the Haltech book had suggested. Reboted the computer and set the bias to boot from a: then c:. The laptop rebooted and said 'starting windows 98', then proceeded to an MS-DOS prompt. The Haltech didn't start on its own contrary to what the Haltech manual said. I had to type 'F9' for the program to begin. I am not sure if this is a sign that it wasn't *really* running off a boot disk. I encountered the same problems when running the Haltech.
I also tried again to reboot the laptop and restart in MS-DOS. That basically gave me the same thing as when dong the boot disk thing.
I did encounter a new error. It only happened once out of the 20 times I tried to run the Haltech. I got and error which read:
'Incorrect programmer version use a later version of F9 programmer'
Don't know why this happened. I am wondering if anyone else has an F9 program I can try. maybe there is some sort of incompatibility between program & laptop/WIN98.
I am using version F9 program version 5.06.
I made a boot disk like Vosko and the Haltech book had suggested. Reboted the computer and set the bias to boot from a: then c:. The laptop rebooted and said 'starting windows 98', then proceeded to an MS-DOS prompt. The Haltech didn't start on its own contrary to what the Haltech manual said. I had to type 'F9' for the program to begin. I am not sure if this is a sign that it wasn't *really* running off a boot disk. I encountered the same problems when running the Haltech.
I also tried again to reboot the laptop and restart in MS-DOS. That basically gave me the same thing as when dong the boot disk thing.
I did encounter a new error. It only happened once out of the 20 times I tried to run the Haltech. I got and error which read:
'Incorrect programmer version use a later version of F9 programmer'
Don't know why this happened. I am wondering if anyone else has an F9 program I can try. maybe there is some sort of incompatibility between program & laptop/WIN98.
I am using version F9 program version 5.06.
#24
you have to type F9 or E6k or whatever when it boots to dos. you make an autoexec.bat and put in E6K or F9 and it will autorun the haltech program. dcee did the program work ? or did the same thing as before and then once it said that gave new error. i'm sorta confused.
keith the haltech program is VERY basic. you need nothing but dos to run it by using a boot disk you are giving only that
keith the haltech program is VERY basic. you need nothing but dos to run it by using a boot disk you are giving only that