Originally Posted by Mahwy1441
(Post 11938498)
Yea battery was good i got a charger attached. I use the latest ecuflash i just downloaded since i just got the tactrix last week. Haven't tried evoscan or mitsulogger yet since i was just about to disable egr first.
Based on your photos should be set correctly.. possibly your re flash connector is a bad connection? The error is basically saying no response from car ECU is my understanding |
Originally Posted by OzAirtrek
(Post 11938500)
Ok I would try just logging while the car is running next.. use evoscan or mitsulogger. If that works then you know there is no problem with the openport 2.0 ..
Based on your photos should be set correctly.. possibly your re flash connector is a bad connection? The error is basically saying no response from car ECU is my understanding |
Originally Posted by Mahwy1441
(Post 11938705)
Tried logging with mitsulogger and the status window says no device detected. Cant get through evoscan, are they still in business?
Are you using a genuine device? Complete reinstall? |
Originally Posted by OzAirtrek
(Post 11938707)
It sounds like your problem is the tactrix device (drivers?
Are you using a genuine device? |
Originally Posted by Mahwy1441
(Post 11938708)
Yeap bought directly from tactrix, i emailed them about the problem but no reply yet. Will try reinstall later, someone suggest to conect the tactrix and let the driver install before installing the openport?
|
Originally Posted by Mahwy1441
(Post 11938705)
Tried logging with mitsulogger and the status window says no device detected. Cant get through evoscan, are they still in business?
Usually solved by: 1. Cleaning out and making sure there are no cold joints on the OBD connector as well as the Flash Connector 2. The Openport pins are not making proper contact, I resolved this by using a cheap OBD port extender on Ebay. Cars that gave trouble to connect or maintain a stable logging connection never gave issues after doing this |
Originally Posted by scientist
(Post 11938804)
This has happened to me quite a few times with Airtreks.
Usually solved by: 1. Cleaning out and making sure there are no cold joints on the OBD connector as well as the Flash Connector 2. The Openport pins are not making proper contact, I resolved this by using a cheap OBD port extender on Ebay. Cars that gave trouble to connect or maintain a stable logging connection never gave issues after doing this |
Originally Posted by scientist
(Post 11938804)
This has happened to me quite a few times with Airtreks.
Usually solved by: 1. Cleaning out and making sure there are no cold joints on the OBD connector as well as the Flash Connector 2. The Openport pins are not making proper contact, I resolved this by using a cheap OBD port extender on Ebay. Cars that gave trouble to connect or maintain a stable logging connection never gave issues after doing this |
EGR disable
Anyone here have disabled the egr on airtrek? Tried to disable from ecuflash but i still get cel and p0403 code. What else do i need to change?
P.s i removed all the egr solenoids since they're dead. |
Originally Posted by Mahwy1441
(Post 11939237)
Anyone here have disabled the egr on airtrek? Tried to disable from ecuflash but i still get cel and p0403 code. What else do i need to change?
P.s i removed all the egr solenoids since they're dead. |
Originally Posted by nikush
(Post 11939270)
your trek is 2002 or 2004?
|
Originally Posted by Mahwy1441
(Post 11939273)
It's an '03 so i guess it's the same as '02?
|
1 Attachment(s)
Originally Posted by nikush
(Post 11939274)
can you post your rom?
|
1 Attachment(s)
try this rom
|
Originally Posted by nikush
(Post 11939313)
try this rom
|
All times are GMT -7. The time now is 06:52 PM. |
© 2024 MH Sub I, LLC dba Internet Brands