I have torque pro. On my Hyundai Accent the Current Drive Cycle Status and Emissions Readiness displays only show Components as complete. Everything else is listed as not available. Is this because of the Chinese ELM-327 I am using or is that all that can be reported by this car?

That was very useful information. Thanks for pointing it out to me. The not available part is kind of weird seeing that the status of each system is a bit flag.

After some fooling around I was able to get it to report more. I had to connect torque then shut the car off. Wait a short time then turn it back on. Some times the dsplay would update. It only works with Torque Lite. With Torque Pro it will flash green Completes then go back to not available.

here is what see in pro.

here is what I can get in lite after tuning off then back on again.

I am going to try a different ODB2 adapter but part of the problem appears to be Torque.

I’ve used the telnet server in Torque scan. I have to figure out how to decode the replies.

>0140
7E9064140C0800000
7EF064140FC000000

>0141
7E906414100040000
7EF0641410007E165

>0140
7E9064140C0800000
7EF064140FC000000

>0141
7E906414100040000
7EF0641410007E5E5

Any suggestions as to how to query it without using torque? Perhaps there is an android/bt version of putty?

I created a little spread sheet that I can enter the codes into and it will reproduce the Torque display.

7E906414100040000 matches what I see in Pro.

7EF0641410007E165 is close to what I can get lite to show except it indicates the EGR system is complete.

7EF0641410007E5E5 is close to what I can get lite to show except it indicates the evap system is incomplete.

I’ll try probing 7EF. The 7E9 response can’t be correct though. The component system can’t be the only test available, right?

The reason I am looking at this is my daughter also has a 07 accent. Her drive cycle isn’t completing and is preventing her from getting the car inspected. I’ve read that the Hyundais can have finicky drive cycle requirements so I reset my ECU to see what it would take to complete. I suspect she has problem with her evap system, but that is another matter.

Getting the telnet to work was simple. Connect Torque to the ECU, open the telnet server. It will indicate what your phone’s IP address is and what port to connect to. You need a telnet client on the laptop like Putty (I just used the stock windows client). Assuming the phone and laptop are on the same wifi network and no ports are blocked it should connect.

Changing the initialization string as you suggested now gives me results that match the second response for both mode 01 PID 01 and 41.

Interestingly lite now shows the same thing even though yesterday the emissions readiness showed all supported tests as being complete.

There are more PID available now. For instance I didn’t have intake manifold pressure before but I do now.

I saw a new PID that may have solve the problem, Distance travelled since codes cleared, PID 31. I haven’t clear the codes or disconnected the battery in about 1300 miles. This morning torque indicated some drive cycle tests as incomplete when yesterday all showed completed. PID 31 was reporting 5km. I drove around a bit and it was incrementing. I now have more tests completed. So some how the ECU is getting cleared. I normally leave my BT adapter plugged in. I am going to disconnect it a while and see if that solves the problem.

thanks for all of you help!

I know this is an old thread but I have the same issue. I have a 2008 Dodge Attitude (Hyundai MC Accent) and it shows that the dtc readings are not available. I have had a play around and managed to get it to show that some tests are incomplete but the información always disappears. I have not taken it for a drive cycle yet as I live in México City and it is hard to find a road to do it on. I have been reading up about PIDs but this is new to me so I am still learning about them. What I wanted to ask is if you managed to sort your issue out? We have new verificación rules using obd2 here in México City and it is a huge mess!

Thanks!