openport 2.0 troubles
Dec 24, 2011, 12:40 PM
#1
openport 2.0 troubles
Currently my 2.0 cable is not working. Ecu flash and evoscan both do not recognize the existence of my cable. The only thing i have done is leave it plugged into my obd port for a couple weeks. I did re install ecuflash 1.42 after uninstalling the 1.43 beta that keeps crashing aswell.. any thoughts? Is my 2.0 done?
` 1.43 crashes when i use the scroll bar to go to further down the line maps.
do i have to fill in the licensing information for the 2.0 in ecu flash? i dont recall doing this before, it has been too long.
` 1.43 crashes when i use the scroll bar to go to further down the line maps.
do i have to fill in the licensing information for the 2.0 in ecu flash? i dont recall doing this before, it has been too long.
Last edited by 211Ratsbud; Dec 24, 2011 at 01:25 PM.
Dec 24, 2011, 02:54 PM
#3
Evolved Member
1.43 is crashing because there is a problem with the xml you are using. 1.43 is much more discriminating about the xml structure. Look in the xml for a map table that either has no scaling at the right hand end, or a scaling that does not exist in the xml or the inherited xml.
Dec 24, 2011, 06:39 PM
#5
ive had customers that had that issue also.. they ask me why i locked their rom and i was like huh? cause i sure don't lock roms.
i like 1.42 build 2595
sounds like 1.43 sucks if it allows the rom to be loaded and randomly crashes without any error code.. you would think it would scan the xml for error pre loading like the older ones do and not just randomly crash and burn.
i think this is an actual bug in 1.43 honestly. the program will just segfault when you scroll down for no apparent reason.
i like 1.42 build 2595
sounds like 1.43 sucks if it allows the rom to be loaded and randomly crashes without any error code.. you would think it would scan the xml for error pre loading like the older ones do and not just randomly crash and burn.
i think this is an actual bug in 1.43 honestly. the program will just segfault when you scroll down for no apparent reason.
Dec 24, 2011, 08:21 PM
#6
Sigh ive even checked my 2.0 usb cable and that wasnt it. Its like there's a driver missing from. My 1.42 download. But the driver package says to not download if you're using ecu flash because its included .. I set this up a year ago without a hitch now im doomed. Lol
Dec 25, 2011, 01:36 AM
#7
the drivers are in 1.42. U need to make sure when u uninstall the ecuflash program, in the control panel, that you also uninstall all of the drivers that have been installed, when installing another version of ecuflash, each time... check em, you probobly have a few in there by now.
Trending Topics
Dec 25, 2011, 08:54 AM
#9
1.43 is crashing because there is a problem with the xml you are using. 1.43 is much more discriminating about the xml structure. Look in the xml for a map table that either has no scaling at the right hand end, or a scaling that does not exist in the xml or the inherited xml.
To the OP what OS are you running? If its windows 7 if you look under Control Panel->Programs->Uninstall a program and see if you see the drivers listed there.
Dec 25, 2011, 10:48 AM
#12
dont stress my new laptop gave me issues too, w/ the 2.0 cable...
as stated theyre located in the control panel>uninstall programs, and is at the bottom of the list... Says "windows driver package - Tactrix CDM Driver Package" Delete these (3), uninstall program, and reinstall the program.
It might also help to install ecuflash in a different location than the default... When I finally got mine to work I installed EcuFlash in my Computer name>Downloads directory... Doesnt really matter where, just not in the default...
GL
as stated theyre located in the control panel>uninstall programs, and is at the bottom of the list... Says "windows driver package - Tactrix CDM Driver Package" Delete these (3), uninstall program, and reinstall the program.
It might also help to install ecuflash in a different location than the default... When I finally got mine to work I installed EcuFlash in my Computer name>Downloads directory... Doesnt really matter where, just not in the default...
GL
