|
Post by imircea on Aug 13, 2012 21:30:54 GMT -8
Hi Issac, I'm Mircea There are many OBD2 applications on the market but your application caught my attention about Nissan extended functions (Consult II). I have a Nissan Primera P12 2.2 dCi manufactured in 2004 and i'm happy to test some functions of the application (can be one of the yours beta testers). I think I'll buy the application after I will be sure that will supports properly diesel engines from Nissan (YD22). I not have the ELM bluetooth adapter yet but I will buy in next month and will send the first test results. If anyone has tested some engines please post here your results to have a compatibility database with ELM and Consult II functions implemended in Car Gauge Pro. PS: Sorry for my english 
|
|
|
Post by Issac on Aug 14, 2012 7:09:51 GMT -8
Hello Mircea,
I heard some of the early phase of Nissan Consult 2 uses the 14 Pin Connector just as the Consult 1 Did. Here in USA they use the K Line from the OBD II 16 Pin Connector and started around 2001. I will be interested to find out if it works on your vehicle. Google will allow you to refund within 15 minutes. The app supports 2 types of Nissan ECM Module. I believe address 0x12 from the ECM is the Diesel type system.
|
|
|
Post by rob on Aug 14, 2012 15:19:30 GMT -8
Issac,
I've got a similar issue. Basically, I've got a Nissan and I've installed the lite version. It connects with the ISO 9141-2 protocol, but gives no information. I've also tried with the Torque Pro and gives slightly more information telling me that no PIDs are available (due to Nissan locking the OBD2 protocol). Is your consult II support likely to give access to PIDs. Does it use the ISO 9141-2 or CAN (ISO 15765-4). My wiring diagram shows: CAN coms line (pins 14, 6) for CPU, Intelligent Key, body control module. DDL2 coms line (pins 7) for ECM, air bag, ABS DDL coms line (pins 13, 12) for Transmission control module.
Cheers
|
|
|
Post by Issac on Aug 14, 2012 23:34:40 GMT -8
Hello Rob,
It is unfortunate it did not work with OBD II Generic but the Pro Version works with the enhance PIDS. Can you send me the Debug Log to my email. I am curious as to why it did not work. The OBD II Generic is required in 1996 Vehicles (USA) and 2001 (Europe).
Consult II is on the K line (pin 7) and uses KWP2000 protocol. CAN BUS is not supported by the app.
I have a Sentra 2001 ECM that uses ISO-9141 for the OBD II Generic and KWP2000 for the Enhance PIDS Consult II.
|
|
|
Post by Rob on Aug 15, 2012 2:33:09 GMT -8
Isaac,
I'm in Australia. This may make a minor difference, but my understanding is that Nissan disables the OBD2 outputs.
However, I had a quick play with the pro version. I can confirm that the Constult II (I believe port 10 or channel 10) works. This is extremely good news and a testament to the quality of your app. However, I was trying to evaluate the available PIDs in the 15min time limit. It didn't seem to have rpm, which would not be so great. Is it possible to get a list of supported PIDs through that the extended functions reads?
I'll run the debugging in the morning on the lite version.
For Mireca, I'm using a generic ELM327 V1.5 bluetooth adapter. I believe it must be a clone as it reports as V1.5.
|
|
|
Post by Issac on Aug 15, 2012 9:52:09 GMT -8
That is nice to hear it works! Engine Rpm is available, but the ECM has to supported it. The name is "Engine Speed". Some of the sensors name are different from others. OBD II Generic is "Rpm". I will correct this later on. The ECM has to be connected to see the supported list. Thanks for testing and wonderful news. Isaac, I'm in Australia. This may make a minor difference, but my understanding is that Nissan disables the OBD2 outputs. However, I had a quick play with the pro version. I can confirm that the Constult II (I believe port 10 or channel 10) works. This is extremely good news and a testament to the quality of your app. However, I was trying to evaluate the available PIDs in the 15min time limit. It didn't seem to have rpm, which would not be so great. Is it possible to get a list of supported PIDs through that the extended functions reads? I'll run the debugging in the morning on the lite version. For Mireca, I'm using a generic ELM327 V1.5 bluetooth adapter. I believe it must be a clone as it reports as V1.5.
|
|
|
Post by imircea on Sept 7, 2012 9:42:18 GMT -8
Hello Mircea, I heard some of the early phase of Nissan Consult 2 uses the 14 Pin Connector just as the Consult 1 Did. Here in USA they use the K Line from the OBD II 16 Pin Connector and started around 2001. I will be interested to find out if it works on your vehicle. Google will allow you to refund within 15 minutes. The app supports 2 types of Nissan ECM Module. I believe address 0x12 from the ECM is the Diesel type system. Hi Issac, Ok, after some holidays and a busy work i bought ELM327 Vgate and Car Gauge Pro from Google Play. I try to connect but i have problems with ECM-12 C2. It say "Negative or No Response from ECU" with red exclamation sign and message "Try Different Protocol". The settings for protocol is "auto". I tried 9141-2 and 14230-4 (both) but with same results. With Lite version is connect OK and show some PIDS. With paid version i can connect with "OBD II Generic (all)" same as the Lite version but cannot connect with "Nissan" option to see enhaced PIDS. The car is marked as EOBD. There is any settings wich i missed? I attachhed the debug logs. Is encripted (is unreadable)? I have some screenshoot too, maybe is helpfull...My email is imirceabucharest at yahoo dot com. Mircea Attachments:
|
|
|
Post by imircea on Sept 7, 2012 9:44:06 GMT -8
And screenshoots. Proboards accept to upload only one file on one message. Mircea Attachments:
|
|
|
Post by Issac on Sept 7, 2012 14:51:45 GMT -8
Mircea,
Thank you for the log. I think I may have fix this problem. Try Version 3.60.07 and please report back. Send Log if necessary.
Thank you
|
|
|
Post by imircea on Sept 9, 2012 8:36:10 GMT -8
Hi Issac,
Is working now! Thank you for prompt support.
Mircea
LE: The working version is 3.60.09.
|
|
|
Post by Mikey on Oct 13, 2012 12:05:58 GMT -8
Hi there.
Firstly, thanks for your awesome app, it's the only thing which reads my 350z ecu.
I'm swapping the engine into an old car and using your app I can see that most sensors are working. However the engine won't start and the DTC menu doesn't show up on my phone so I can't check DTCs.
Is there any thing I can do to get the DTCs out?
Thanks!
|
|
|
Post by Issac on Oct 13, 2012 14:11:47 GMT -8
Hi there. Firstly, thanks for your awesome app, it's the only thing which reads my 350z ecu. I'm swapping the engine into an old car and using your app I can see that most sensors are working. However the engine won't start and the DTC menu doesn't show up on my phone so I can't check DTCs. Is there any thing I can do to get the DTCs out? Thanks! Hello, Check it with OBD II Generic. There is no DTC checking in the enhance mode. -Issac
|
|
|
Post by Mikey on Oct 13, 2012 15:53:19 GMT -8
Hi isaac, I've tried the and I get "negative or no response from ecu"
Any other ideas?
|
|
|
Post by Issac on Oct 13, 2012 19:00:19 GMT -8
Hi isaac, I've tried the and I get "negative or no response from ecu" Any other ideas? Did you try setting adaptor protocol to 9141-2 or both of the 14230-4. Sometimes auto does not work well for those protocols. If no success, enable debug log and connect few times for each protocol then send the log to my email. -Issac
|
|
|
Post by Mikey on Oct 14, 2012 0:26:00 GMT -8
Hi isacc, I gave this a go and sent you the logs.
Cheers, Mikey.
|
|