Re: VZ E55/E40 ECU LINKER
Posted: Wed Dec 14, 2022 6:51 pm
Been a hecktic day didn't get a chance to have a look at it again. I tried a few things last night - I think it may be the gscan2 we have being the issue. I am waiting for a usb elm327 device to come. Hopefully next week it will be here.
The ecu can be read no problem with the scan tool. Basically car starts about 75% of the time we have a new reconditioned unit from injectronics. We were going to send their unit down to them however the customer needs his car. So he was happy to have his car start 3/4 of the time but still to have access to it.
I tried the kia/hyundai option it was the same error of 8 with the demo tool. I downloaded the brute force version by The1 modified the error output of his code to see what error came back when just trying to connect. Using the "gscan2 Other" option I would get error code 9 - timeout. Using the "kia/hyundai" option it would wait longer then a few dll exception errors and a bit of random gabled text.
I found some other aftermarket diag/performance software that would use the J2534 protocol all of them failed with the same code 9 timeout response. I tried few different vehicles just to see if anything would connect. It did not so I am leaning on towards something wrong with the gscan2. So I will twait till the other device comes and see how it goes with that.
Thanks for your help.
The ecu can be read no problem with the scan tool. Basically car starts about 75% of the time we have a new reconditioned unit from injectronics. We were going to send their unit down to them however the customer needs his car. So he was happy to have his car start 3/4 of the time but still to have access to it.
I tried the kia/hyundai option it was the same error of 8 with the demo tool. I downloaded the brute force version by The1 modified the error output of his code to see what error came back when just trying to connect. Using the "gscan2 Other" option I would get error code 9 - timeout. Using the "kia/hyundai" option it would wait longer then a few dll exception errors and a bit of random gabled text.
I found some other aftermarket diag/performance software that would use the J2534 protocol all of them failed with the same code 9 timeout response. I tried few different vehicles just to see if anything would connect. It did not so I am leaning on towards something wrong with the gscan2. So I will twait till the other device comes and see how it goes with that.
Thanks for your help.