Mitsulogger v2.0 Beta 1a Released
May 30, 2009, 08:26 PM
#17
is it b/c I extract the files wrong?
here is what I did, I double click the mistulogger app icon and a window pops out ask me to extract it. I extract it to the folder I created under program files x86 and then I double click the mitsulogger icon and the interface pops up
here is what I did, I double click the mistulogger app icon and a window pops out ask me to extract it. I extract it to the folder I created under program files x86 and then I double click the mitsulogger icon and the interface pops up
May 30, 2009, 09:00 PM
#20
Honestly, your description of the error is just too vague to know for certain. The only thing I can think of is a driver issue (or lack of installed driver) or your missing a component that both Evoscan and Mitsulogger requires that is normally available.
another thought did occur to me. I have only tested Mitsulogger and Vista x64 Ultimate, I didn't try other versions of Vista such as Home, or other lower editions. My laptop did actually come with Vista x64 Home, but I upgraded it to Ultimate, and its currently running Windows 7 Ultimate. There could be a component different between the editions.
another thought did occur to me. I have only tested Mitsulogger and Vista x64 Ultimate, I didn't try other versions of Vista such as Home, or other lower editions. My laptop did actually come with Vista x64 Home, but I upgraded it to Ultimate, and its currently running Windows 7 Ultimate. There could be a component different between the editions.
May 30, 2009, 10:52 PM
#25
I don't think the edition is the actual problem, or at least not something that couldn't fairly easily be resolved. However until I get some sort of confirmation from other users and the versions they use, then it may just be isolated to your system. If everyone with Home edition has an issue (not just 64 bit home edition) then It is more likely the case.
May 31, 2009, 01:11 AM
#26
Obviously your computer is not infront of me so I have to play the guessing game based on the information available.
May 31, 2009, 04:46 AM
#27
you may using the same OS but there're different hardware and software configuration situations between different machines. your not work but many other work implies there's must be some "unknow" issue is on your machine. If you have more useful information then we may help. Is Ecuflash working on your notebook? What is the error message or condition you're getting with EvoScan?
Obviously your computer is not infront of me so I have to play the guessing game based on the information available.
Obviously your computer is not infront of me so I have to play the guessing game based on the information available.
For mitsulogger, I get error msg saying "unhandled exception has occur ... " I click on the details and it says microsoft visual basic.
as far as evoscan goes, I can log, but I either not getting enuf rpm foot prints in excel or getting too much rpm foot prints. i spoke to the evoscan guy, he said evoscan might be logging to fast than my ecu? i think my laptop can handle program like evoscan even w/ battery saving mode.
next time I'll try to see if I can save the error msg
Last edited by fugiwara; May 31, 2009 at 04:54 AM.
May 31, 2009, 05:27 AM
#28
Are you trying to log with a wideband enabled? If you are, did you set the proper com port in the wideband module?
I have gotten no feedback from anyone else whether or not it works at all so I cannot be sure what the issue is yet.
You also did say it was working in Demo mode. In the device dropdown, did you select the proper device (If you have more than one USB device plugged in that does serial communications its possible that the wrong one is selected if there are more than one FTDI based device)
I have gotten no feedback from anyone else whether or not it works at all so I cannot be sure what the issue is yet.
You also did say it was working in Demo mode. In the device dropdown, did you select the proper device (If you have more than one USB device plugged in that does serial communications its possible that the wrong one is selected if there are more than one FTDI based device)
Last edited by MalibuJack; May 31, 2009 at 05:33 AM.
...Thanks