Trying to read live data from a 6299

**Markmx6** · 05-30-2015

Since I am new to this and all of my own vehicles are obd2. I was trying to minimize the investment. I would be willing to try other options, but if I can do it cheaper and just as well, then it is worth a shot...

I have considered using the 7747 and just might if it comes to that

I just got home from work so I tried to get this running and Tunerpro says the cable is working, but it isn't showing data. I also can't find the .adx file in the above link.

Obviously I need to do some more homework on how to use the software, but these are what I have come up with so far.

Also I don't know if it means anything but the usb serial converter I am using does work flawlessly with Nissan consult devices.

I also could build the max232 cable and probably will next (mainly because I like to say I made stuff myself, that and I am cheap...)

Thanks again for your help and any advice you can offer

-Mark

Also, what do the prom codes mean? is there a chart or something that decodes them or do you just have to match the one in your ecm?

OK, also found out I need to use Tunerpro rt V4. I got the .xdf and .ads imported and it says my cable is working , but I am not sure what I need to do to get actual information from the truck. It does saay I am connected though, so that seems like a good sign.

My wife will kill me if I start the truck again as it is almost midnight here and she is worried about pissing off the neighbors, but I will be out of town until Thursday and won't have a chance to test anything until then. That will give me plenty of time to read the tutorials until I get back

**Six_Shooter** · 05-30-2015

No, working with any other devices means squat when it comes to working with communications with a GM ECM, like I said before, GM used non standard baud rates, and this causes problems on it's own, with perfectly working cables, let alone combinations of adapters that add their own latencies.

You don't need TP RT V4, V5 works and is what I use on everything I tune anymore. Just import the ADS and save as an ADX, there's an option for it under the acquisition menu.

I too like to build my own stuff, as I said I built a MAX232 based cable, I did that years ago, along with trying both a single and two transistor cable. The MAX232 was the least flakey, but still flakey in the end, especially when coupled with a USB to serial adapter. I bought the Moates cable and never looked back. Well, that's not totally true, I do use my MAX232 cable on my test bench sometimes, since my PC has a bonafied serial port.

A lot of the 160 BAUD ECMs (ADXs) will show connected, even if they are not, due to the nature of the 160 baud datastream. The 160 baud stream is always being transmitted, even when no cable is attached. There is no real handshaking, per say, just start bits that tell the listening device when the stream is starting at the fist bit.

The 8192 ECMs, will only transmit data after the ECM and the listening device has hand shook, and in sync.

**Markmx6** · 05-30-2015

Thank you for the heads up about TP RTV5. I was able to go through and get the files imported and loaded up.

You keep mentioning the 160 baud. I'm not following as I thought pin E was for 160 and pin M was for 8192 in the ALDL connector. I don't have anything in pin E and I didn't see any loose wires around the connector. Which is why I thought it was a 8192 ECM.

I'll probably just order the moates usb cable, I can always manage to justify buying more tools.

**fastacton** · 05-30-2015

I use pin E with my '299 that I do a lot of my testing with and it works the same as if I had a '7747 hooked up when I'm using Tunerpro. I've pulled a good number of harnesses out of vehicles with the '299 in them and I don't recall seeing any that didn't have a wire in pin E.