Author Topic: ECU editor won't connect to engine data (Read 24993 times) Tweet

FlatlandBusa · « **on:** March 03, 2010, 09:55:27 PM »

I just installed the boost by smith flashing interface and I can't get the engine data to connect.
When I go to the engine data screen it asks you to set the com port, when I select a com port from the drop down box then click connect whatever number I have selected (I have tried #'s 1 to 8 ) the com port selection box goes blank and the error message that says select com port comes back up.

What I have tried;
running ecu editor as an administrator and normal
uninstalled ecu editor and re-download it
changing the com port number from every number from 1 to 8.
different usb ports, the computer has 3
flashing does work, it goes through and says flashing successful
I made a map with a very rich spot in it to make sure and when you reach that throttle position and rpm the bike starts loading up and making black smoke out the pipe.

The lap top is a Toshiba 32bit windows 7 with a 2gig dual core AMD processor.
I did a full virus scan with norton and it came up clean
What am I missing?
John

FlatlandBusa · « **Reply #1 on:** March 03, 2010, 10:48:43 PM »

FYI also tried running ecu editor in compatibility mode set on windows XP service pack 2 and 3.
After selecting the com port number, when I click connect, the com port box goes blank and the select com port error message comes up.
I gotta be missing something simple.

smithabusa · « **Reply #2 on:** March 03, 2010, 10:52:03 PM »

hmm weird, i can make it happen here, but had a customer with XP call and say same thing yesterday. He could flash fine, but com port would dis-appear like that. to me still seems like an administration rights problem or something bizarre..

you installed the com port driver in ecu editor under setup right?

FlatlandBusa · « **Reply #3 on:** March 03, 2010, 10:55:35 PM »

Yes I installed the com port driver in set up, first thing I did.
Also tried compatibility set as vista service pack 1 and 2.

smithabusa · « **Reply #4 on:** March 03, 2010, 10:58:53 PM »

did you download 2.0 or 2.1 from www.ecueditor.com

i am using 2.1 here, cant make it happen on my computer, just tried. I sent petrik an email asking if he has any ideas.

Dumb question, have another laptop there you could give a whirl to see if something is just goofy on that laptop?

I am running 32 bit windows 7 on the laptop i just tried as well using ecu editor 2.1

FlatlandBusa · « **Reply #5 on:** March 03, 2010, 11:05:46 PM »

I down loaded ecu 2.0. I'll try 2.1.
I tried it on an old XP desk top I have and it lets me set up the com port and it keeps the number in the box when I click connect, and has the interface not connected error code but that is expected.
I have a friend that does computer networking and repair, I might give him a call in the morning, I'm thing its a windows 7 thing, just gotta find a way around.

smithabusa · « **Reply #6 on:** March 03, 2010, 11:09:19 PM »

well weird thing is that an xp computer did it the other day, now the guy it happened to is not a computer guy by any stretch LOL

Only way i can get that to happen here is if i select the wrong com port, meaning my actual com port for the cable is COM 5, which can be verified in device manager, unplug and plug device in and should see the com port show up or go away. Anyhow in my drop down menu i also have a com 3 that is always there, though its not my flasher, if i select it, it will disappear once i hit connect and tell me to set my com port. Any chance you are doing something like that?

Give 2.1 a whirl, then let me know if you have more than 1 option in your drop down menu for com port selection etc.

Sorry for the hassle, we will get it though, this is a brand new one surprisingly there are a lot of these things out there reading gauge data LOL.

Greg

FlatlandBusa · « **Reply #7 on:** March 03, 2010, 11:16:01 PM »

Don't be sorry about it, its just a windows 7 thing I think..
The only way I can get any number to show up in the com port selection box is to have the flash interface plugged in, then I can go to device manager and change the number of that port to any one that I want, I have tried number 1 to 8.

smithabusa · « **Reply #8 on:** March 03, 2010, 11:17:51 PM »

ok.....hmmmm...the plot thickens LOL

FlatlandBusa · « **Reply #9 on:** March 03, 2010, 11:34:45 PM »

Just uninstalled EE2.0 and installed 2.1, setup com port drivers, restarted computer, same thing, com port box goes blank when I click connect engine data.
Also double checked to make sure I put the additional wires in the correct locations on the bike.

It's got to be an issue with this computer, I'll see if my computer guy has any ideas in the morning. I have to be to work in 4.5 hours so I'm gunna worry more about it tomorrow night.
I am just happy that I have a way to tune without extra modules on the bike.
I have a LM2 for the data any way.
I'll figure it out and post what I find if I get it sorted out.

PetriK · « **Reply #10 on:** March 04, 2010, 03:50:12 PM »

The only way I have seen this happening is if there are 2 ftdi devices, eg. usb com port and flashing interface connected. Deleting everything from control panel / applications will rebuild the application space and fix issues in that.

This is an interesting one, difficult fish to catch until we figure out how to repeat the same in many computers.

FlatlandBusa · « **Reply #11 on:** March 04, 2010, 07:53:46 PM »

Just out of curiosity I loaded EE2 in the wifes windows 7 HP laptop, it acted the same. Dam windows 7, not my first time having compatibility issues with it, not as bad as the vista that I down graded from just after it came out.

I also tried opening a gen 1 base map and the com port number stays, and it appears that it would display the engine data if I had a gen 1 bike, my issue appears to only be with the gen2 data screen.

FlatlandBusa · « **Reply #12 on:** March 13, 2010, 07:46:57 PM »

Got EE2 to run the Gen2 data finally.

Never got it to work on my windows 7 toshiba laptop though. I tried every thing from dual booting with XP, also tried running virtual box with XP, never had any luck. I'm not a computer guy, maybe its the way toshiba sets up their hardware? Maybe its just my machine? I have no idea.

I got a cheap used windows XP laptop and every thing works great.

Thank you PetriK for the ecu editor software, it's awesome! YOU THE MAN.

Thank you smithabusa for the super easy interface install, just plug and play.

smithabusa · « **Reply #13 on:** March 13, 2010, 07:48:53 PM »

well glad to hear interface is totally fine, but still concerned on the toshiba not functioning, i wish i lived closer could help ya out.

FlatlandBusa · « **Reply #14 on:** March 13, 2010, 08:10:01 PM »

One of the guys that helped me a little with the computer side of things said that the toshiba's seem to be having more issues with compatibility that the other brands, he said something about the drivers being set up differently. I don't know.

I still think that it could be made to work, it just reached a point were it was less time and money to get a machine that I knew would work.

I am still very happy with the results with EE2, even with a few minor snags.

smithabusa · « **Reply #15 on:** March 21, 2010, 05:47:41 PM »

Flatland, was your other laptop also AMD processor, another guy on hack forum is having same issue as you, and he has AMD processor, hmm maybe on to something?

FlatlandBusa · « **Reply #16 on:** March 21, 2010, 07:28:51 PM »

Yup, the HP and the Toshiba are both dual core AMD processors.

The HP got traded for 2 older XP OS machines so I don't have it any more, one is a Pentium 4 The other is a Centrino Dual core and EE2 works great on both of them. Like I said in the earlier post one of the guys who helped me said that he has seen Toshiba windows 7 machines have more compatibility issues than other brands and he said it was the way the drivers were set up. Windows 7 seems to try and reconfigure settings even after manually setting up drivers.

I think you might be on to something with the AMD processor, cause I thought it was strange that it wouldn't work ever running virtual box with XP or dual booting with XP.

On a side note I was out ridding, logging and tuning today I'm on my third map and already the A/F trace is getting much smoother, same with the power delivery, not that an '08 is bad out of the box. I'm having to remove about 6-10% fuel in the IAP map and add 4-8% in the higher portions of the TPS map.

Big thumbs up to PetriK

and you

EE2 is awesome..

John

smithabusa · « **Reply #17 on:** March 26, 2010, 05:04:37 PM »

John,

Been digging around some and i think this might be worth trying, any chance you could give this a whirl? I think it should maybe lead us in right direction on Vista and Win 7.

Okay did some more searching, here is a link that shows you how to unlock a true hidden administrator account.

http://www.vistax64.com/tutorials/67567-administrator-account.html

basically you need to go to programs, accessories, right click on command prompt, run as administrator.

when it loads type the following
net user administrator /active:yes

then in the start menu log off.

Then when you go to log back in there should be a new ADMIN account.

Give that a whirl.

FlatlandBusa · « **Reply #18 on:** March 26, 2010, 07:16:19 PM »

I'll try it when I get home later tonight.

FlatlandBusa · « **Reply #19 on:** March 26, 2010, 10:00:14 PM »

I just got done trying running ecu editor as the true administrator of windows 7.
Here is what I did.
Logged in as administrator and down loaded and installed ecu editor, and installed the com port drivers, restarted the computer.

Plugged the flash interface in and opened ecu editor, set up com port, opened gen2 base map, opened the engine data screen, selected the com port,
and when I click connect, the com port box goes blank and the "select com port" error comes up. I also tried resetting the com port number from 1-8 with the same result.

It acts like the XP machines do when the incorrect com port is selected, when connect for engine data is clicked the box goes blank and the "select com port" error comes up.

When the gen1 data screen is opened the com port # stays and it appears that it would connect if I had A gen1 bike.
I was really hoping that would work.

It is very possible that it is just this machine, as ecu editor wouldn't work even when I ran virtual box with XP and dual booted with XP.
I wish I would have tried running the virtual box on the HP windows 7 machine before I got rid of it.

John

PetriK · « **Reply #20 on:** March 27, 2010, 06:14:15 AM »

Quote from: FlatlandBusa on March 26, 2010, 10:00:14 PM

Plugged the flash interface in and opened ecu editor, set up com port, opened gen2 base map, opened the engine data screen, selected the com port,
and when I click connect, the com port box goes blank and the "select com port" error comes up. I also tried resetting the com port number from 1-8 with the same result.
It acts like the XP machines do when the incorrect com port is selected, when connect for engine data is clicked the box goes blank and the "select com port" error comes up.
When the gen1 data screen is opened the com port # stays and it appears that it would connect if I had A gen1 bike.
I was really hoping that would work.

This is very interesting issue and something have not heard of before. The gen1 and gen2 com port handlers are different. The gen1 is detected by looking any ports connected to a FTDI device where as the gen2 detects all com ports and lets the user choose any of those regardless if there is FTDI or not. This was done to avoid being in a need to use administrator rights. Now if there are any com ports in the laptop should list all those when gen2 is selected. With gen1 there was an issue if more then 1 ftdi devices were found - with gen2 this is something new. Lets hope there is a bug in ecueditor that we can find instead this being windows 7 issue (my son runs windows 7 and wants to go back to vista just to be able to play the normal games without computer hanging up.)

smithabusa · « **Reply #21 on:** March 27, 2010, 07:30:31 AM »

Another guy had the same issue Petrik, gen 1 flashing works fine, gen 2 does exactly like mentioned below.

PetriK · « **Reply #22 on:** March 27, 2010, 08:43:40 AM »

I looked at the ecueditor 2.1... programming code and there is no doubt that this is an issue on with the setup on this particular laptop. There is nothing in the ecueditor code it does differently for Windows 7 compared to Vista or XP. Gen1 and Gen2 differences are listed below and explained in programming code. There is no sense going back to gen1 detection method with gen2 as it creates more hassle with the need to set admin rights. If management objects finds the port in gen1 detection mode but gen2 using standard visual basic call does not then there are some alternatives as the source of the fault either in hardware, driver or even microsoft vb runtime compatibility with windows 7. Anyhow if there are two laptops with this kind of fault then we need to narrow down what are the various driver versions, bios settings, user right settings to nail this down.

Can you guys do that and dig into very details for figuring out whats going on and help tracing this down. Its beyond ecueditor programming code, somewhere on the system level so someone competent with operating system and goole to seek out the problem sources ?

... or shall we just leave this as it is ? Its your call, there is nothing I can do for Windows 7 and FTDI drivers as such, but I am very interested in finding out the source for this just to be able to communicate it publicly for anyone reading this thread.

---

Gen1 requires admin settings and is based on seeking the ports using management objects.
Gen1:

For Each queryObj As ManagementObject In searcher.Get()
ps = queryObj("PortName")
If ps = s Then
pvs = queryObj("InstanceName")
j = i 'Val(Mid(ps, 4, 1))
End If
ComboBox_Serialport.Items.Add(ps)
i = i + 1
Next

Gen2 is based on standard windows call.
Gen2:
For Each port In ports
ComboBox_Serialport.Items.Add(port)
If port = s Then
j = i
End If
i = i + 1
Next port

xDegeneratex · « **Reply #23 on:** March 27, 2010, 01:02:24 PM »

I had the same problem, You need to do this and run ecu editor from the secret admin account
http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-windows-vista/

FlatlandBusa · « **Reply #24 on:** March 27, 2010, 01:22:21 PM »

Quote from: xDegeneratex on March 27, 2010, 01:02:24 PM

I had the same problem, You need to do this and run ecu editor from the secret admin account
http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-windows-vista/

Read above posts... I already tried that, also you are flashing gen1. I can get gen1 to work; just not the gen2 data screen.

PetriK · « **Reply #25 on:** March 27, 2010, 03:01:53 PM »

OK, Show me if this tells that you have comports connected ... disconnecting the ftdi interface will show / not show the comport on this list.

http://macmadigan.no-ip.com/comportlist/publish.htm

FlatlandBusa · « **Reply #26 on:** March 27, 2010, 03:23:58 PM »

Quote from: PetriK on March 27, 2010, 03:01:53 PM

OK, Show me if this tells that you have comports connected ... disconnecting the ftdi interface will show / not show the comport on this list.

http://macmadigan.no-ip.com/comportlist/publish.htm

When I plug the flash interface in the com port list shows "com port 1" when I unplug the interface it is blank.

xDegeneratex · « **Reply #27 on:** March 27, 2010, 03:37:42 PM »

Sorry about that I have a Toshiba also with windows 7 64bit. What i did was Uninstall every thing including the drivers for the cable Then logged on to admin account and re-downloaded and installed everything from there. I did try to run it from my main account and come up with the error so I have to use the admin account for flashing. Also check the security settings and allow full control to the programs I noticed that the program did bot have full control so I went in and edited the permissions to make everyone have full control for some reason it installed with limited control.

FlatlandBusa · « **Reply #28 on:** March 27, 2010, 08:07:55 PM »

Quote from: xDegeneratex on March 27, 2010, 03:37:42 PM

Sorry about that I have a Toshiba also with windows 7 64bit. What i did was Uninstall every thing including the drivers for the cable Then logged on to admin account and re-downloaded and installed everything from there. I did try to run it from my main account and come up with the error so I have to use the admin account for flashing. Also check the security settings and allow full control to the programs I noticed that the program did bot have full control so I went in and edited the permissions to make everyone have full control for some reason it installed with limited control.

I have also tried uninstalling all of the ports and drivers as well and reinstalling while logged in as system administrator, I don't think that I had mentioned that yet. The security settings are set for full control for the program and com port drivers . I am completely open to any suggestions that would help sort this issue out. What I have learned in the last couple of weeks, is that windows 7 seems to basically be a smoothed over and re-marketed version of the old vista, that so many people including me disliked.

PetriK · « **Reply #29 on:** March 27, 2010, 08:35:56 PM »

you can try downloading to see how it works.

http://www.ecueditor.com

Name: Hayabusa ECUeditor for K2-K7, K8- and BKing models
Version: 2.2.0.9
- com port detection method for first port changed.

smithabusa · « **Reply #30 on:** March 27, 2010, 08:58:11 PM »

Petri,

in case there was any doubt, I just downloaded latest version, and I didn't have issues before, but just wanted to let you know I can still successfuly read gauge data and flash with the latest software with ftdi detection changed.

Greg

FlatlandBusa · « **Reply #31 on:** March 27, 2010, 09:00:12 PM »

WooooHoooooo

I can confirm the data screen works, the flashing works all without EE2.2 being set as administrator on this windows 7 machine!!!

I have said this before but it needs to be said again

PetriK you are the man.

smithabusa · « **Reply #32 on:** March 27, 2010, 09:02:24 PM »

Oh my god I am so happy

Flatland thanks so much, if you need anything for helping out just let me know, can send some paypal your way

The other thing people probably don't realize, right now I think its 4 or 5 am in Finland

Petrik you rock!

FlatlandBusa · « **Reply #33 on:** March 27, 2010, 09:13:38 PM »

No paypal needed, just glad that I could help out in some way with this project.

Yup I looked up the time in Finland when PetriK made the last post, about 4 a. m. !

PetriK deserves a vast amount of respect for all the time and effort that he has invested.

smithabusa · « **Reply #34 on:** March 27, 2010, 09:21:20 PM »

yes, he most certainly does. Thanks again Petri!!!

FlatlandBusa · « **Reply #35 on:** March 27, 2010, 11:54:50 PM »

Another thing I ran into when switching versions of ecu editor, and thought I would mention.

Be sure to go to the control panel and uninstall the previous version of ecu editor first, before downloading the newer version, otherwise an "application can not be started" error comes up when the newer version tries to start.

FASBUS · « **Reply #36 on:** March 28, 2010, 01:15:10 AM »

PetriK deserves a vast amount of respect for all the time and effort that he has invested.

[/quote]

NO DOUBT !!!! Mad props to everybody thats helped with all phases off ecu tuning !!!!

Amode · « **Reply #37 on:** May 02, 2010, 11:09:10 PM »

I am having the same problem with windows 7. Will not connect to engine data. I just gave up.

FlatlandBusa · « **Reply #38 on:** May 02, 2010, 11:44:00 PM »

Follow through this thread from reply #17 on,

Make sure that you have ECU editor set to run as administrator, and FDT set to run as administrator as well if your flashing GEN1.

Also be sure to use the latest version of ECU editor, ALFA 2.2 available here, www.ecueditor.com.

smithabusa · « **Reply #39 on:** May 03, 2010, 06:00:16 AM »

Yep 2.2 software

News:

Author Topic: ECU editor won't connect to engine data (Read 24993 times) Tweet