When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Please post your entire debug log from the time you connect with the device until the read cancels it self. We need to see what took place before what you posted to see whats going on.
Ah, using a J2534 tool. Yes we've learned there is an issue that arose when the code was compiled into an executable file and are working on a resolution to this issue. This is one of the top priority's at the moment so just sit tight and we'll get that sorted out for you.
And I just wanted to say thank you for submitting the log, when people submit a log back for errors it's the most constructive way to help us find bugs AND is the only way we can help people sort out they run into. I've had a number of users inform me the J tool wasn't working and only one of them had a debug log for us to look at.
I like seeing these posted publicly, it's a way for other people that may run into the same error to see what was done to resolve the issue
Ah, using a J2534 tool. Yes we've learned there is an issue that arose when the code was compiled into an executable file and are working on a resolution to this issue. This is one of the top priority's at the moment so just sit tight and we'll get that sorted out for you.
And I just wanted to say thank you for submitting the log, when people submit a log back for errors it's the most constructive way to help us find bugs AND is the only way we can help people sort out they run into. I've had a number of users inform me the J tool wasn't working and only one of them had a debug log for us to look at.
I like seeing these posted publicly, it's a way for other people that may run into the same error to see what was done to resolve the issue
Same thing happened to me. I am using a vxc nano. HOWEVER, it worked to change the vin which is what I needed it to do. That little thing right there might make all the difference for me and some people on here in regards to a project i am working on. Ill make a thread about that though. You guys are awesome. Where do I donate to?
To start with there's no place to donate and no need it. This has been a group effort by a number of people from several diffrent forums and represents years worth of work.
Now......It's not ready for release but the issue with the J tool has been found and is being corrected. I was working with Envious Customs pretty late last night and they were able to get it working again, the issues wasn't as hard to fix as it seemed. There are a couple of other things that need to be altered a bit but I'd expect an updated release version with the j tool working early next week.
Nice awesome work, this is going to be the cherry on top of my sonoma project.
Thanks so much for all your hard work and i hope that the debug log helped in identifying the problem.
This project is phenomenal, thank you so much for all your hard work. The only question I have is, what is the current recommendation on cable for a windows pc?
i think the allpro usb is the go-to cable right now.
Yep. It has a lot going for it...
It's inexpensive
It's fast (supports "4x" mode and large messages)
It's reliable
It's got open-source firmware (so it should be future-proof)
It's an original product, sold by the guy who created it.
And the guy who makes them has incorporated some changes from Antus (one of the developers on this project) which suggests that if any issues come up in the future we can work together to get those fixed too.
The AVT is nice, but expensive. (But if you have one, it should work just fine.)
The Scantool is nice, but doesn't support 4X. (But if you're patient, it works too.)
ELM devices don't support 4X or large messages, and the market is flooded with poor imitations. (All bets are off.)
Legitimate J2534 devices are expensive. (But if you have one, it should work too, very soon.)
Inexpensive J2534 devices... I'm admittedly not 100% sure of this, but rumor has it that they're using pirated software. (Should also work soon though.)
The vcx nano has worked for me so far. It has done everything a tech2 can and I have used ac delcos service programming service to reprogram my fbodys pcm with it. I used it with pcm hammer to change the vin but was not able to read (but they mentioned the solution to that above). All in all the the nano was worth the 118 I paid for it.
I started a thread about flex fuel on the Fbody. You guys saved the day on my project and in return I posted up my solution to getting it to work. Thanks guys!
Got my AllPro cable today. I'm having trouble reading the PCM for some reason. I got this message. Any idea where I should start troubleshooting this? I'm on Windows 10 if that makes any difference.
Thank you!
Can you click the "Debug Log" tab and copy-paste everything in it?
Did you retry? If so, did it help?
How long had the PCM been turned on? I've found that it can be unreliable for the first 10 seconds or so.
The PCM was on for several minutes and I've been making multiple tries. I was able to get a partial read tonight. I'm not so sure it isn't something on my end though. I've attached the data in the text. Thank you for looking at this.
In that log, the message from the PCM was shorter than expected. I suspect there's something interfering with communication between your PC and your PCM. Maybe electrical noise, or a bad connection, or something like that.
The log doesn't show any modules present besides the PCM, so I'm guessing you're testing with the PCM on a workbench and you've made your own harness to connect to it... I have the same kind of setup at home, and I've had some similar issues. It has always been reliable in the car though. Which is weird - I would have expected more noise in the car and less noise on my workbench.
The ObdLink Scantool SX has been perfectly reliable with my bench setup, but it's also a lot slower (20+ minutes for a full read).
Whatever the cause, the app didn't know how to handle the problem. It should have printed an error message, instead of just halting with no explanation, and I'll fix that. It is tempting to add code to retry in such cases, but I think it's actually better to fail (with an error message) rather than using retries to hide the connection-quality problem. There are measures to detect data corruption, but they're not perfect, so an unreliable connection could lead to bad data getting saved to disk and/or written to the PCM.
Do you know if your dealing with a factory OS are is this possibly a custom OS from maybe Hp Tuners or EFI Live? Like NSFW said the log seems a bit odd.Would have liked to see the debug log for the screen shot you posted where the response length was wrong on the unlock.
What year pcm or service number are you working with?
Thank you for your responses. This was done in the car. I put an LS4 into my MGB so I'm using a stand alone harness. I'm using a 0411 which I believe I got out of an 01 Chevy Blazer 4.3 V6. It isn't factory, I had it flashed by a well known tuner in my area and it was based on a manual transmission 12202088 OS. It runs really well but I've had some weirdness with my OBDII port that I will need to troubleshoot. I'm going to a bench setup in the next few weeks, i think I have almost everything I need including a spare 0411. Just missing an OBDII port for it.
Thank you for your responses. This was done in the car. I put an LS4 into my MGB so I'm using a stand alone harness. I'm using a 0411 which I believe I got out of an 01 Chevy Blazer 4.3 V6. It isn't factory, I had it flashed by a well known tuner in my area and it was based on a manual transmission 12202088 OS. It runs really well but I've had some weirdness with my OBDII port that I will need to troubleshoot. I'm going to a bench setup in the next few weeks, i think I have almost everything I need including a spare 0411. Just missing an OBDII port for it.
Thanks again for your help.
One question so I don't hijack the thread: Which tranny did you use behind the LS4? Never seen one used in a north-south (rear drive) configuration.
