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.
I'm frustrated for you! Dang man it's like right there.
Replacement adapter should be here today. I notice if I try to connect to AT ECU network directly while mobile device will connect to OBD dongle (Wifi or BT) it just times out. Curious if the PNs on AT ECUs are different between the RWD and AWD models.
• Would not pair with IOS.... I haven't had one that wouldn't pair in years. Said it was unsupported
• Paired up with my Android devices but took longer than usual / that being said it seemed to be quicker to connect than of the adapters I have
• Still no dice on access to AT ECU.
Hopefully we can find someone with a '07-'08 X model who can validate that issue is some kind of incompatibility with AT EVU or just some one off issue with my G. I have no known issues with my G. It is a 1/07 build.
Bluetooth ? If so, that's a limitation (??) with iOS and ODB-style adapters. WiFi is the only way to go for this.
Originally Posted by treacherous
Hopefully we can find someone with a '07-'08 X model who can validate that issue is some kind of incompatibility with AT EVU or just some one off issue with my G. I have no known issues with my G. It is a 1/07 build.
I have an '08 G35X. I apologize, but what's the consensus at this point ? There's been different apps mentioned and I'm not sure what direction to go (if I were to try). Summarize it ?
Actually BT and the OBD Fusion/Link with my iPhone 7 works great on my Mazda CX-5 and Lexus GX 460. I can connect fine to the Infiniti... it just can't scan for any AT PIDs. It finds most of the other ECUs IMO: There is something here beyond the mobile device and connection method.
So far the only reported success is with OBD Fusion, 2007 G35 Journey and this adapter---->
The following is the official OBD Fusion/Link adapter. It also can't find any PIDs for AT ECU. Whereas with Fusion you have to buy every model year (assuming using 3rd party adapter)... if you use Link they give you all of them for the included price of the following Link adapter.
Got my new Ultra Gauge ordered, but they didn't have it available with preprogramming for Infiniti, so I got it preprogrammed for Honda CANBUS and will tweak it as needed. The only thing they tell you to do is to get one with the same protocol as your car (CANBUS in our case). Also ordered the firmware update for my ScanGauge and will be sending it in tomorrow. Once I get it back I should be able to read the PIDs from the original post. I got Fusion downloaded and a BAF-X Adapter is en route. Once I get the adapter I'll see what I can find and if anything transfers from/to the Ultra Gauge or ScanGauge. I'll update as I find information.
Got the UG today and plugged it in. It's going to take a bit to decipher the codes and how exactly to input them. The direct input of the translated scangauge codes didn't work, but there are some variable values I can tweak to make it (hopefully) see the data points.
Update: Haven't been able to decipher the codes for the UG yet. I get the ScanGauge back today, so I'll try it out tonight to see if the info from the original post works. I got the BAFX and Foseal OBD adapters and tried them out with OBD Fusion. The BAFX adapter works great, has no issue feeding the transmission data to my tablet. the Foseal adapter connects with the tablet, but it won't link within the app itself and therefore sends no information. I'm going to see if I can hack OBD Fusion on my computer to find the PIDs that it uses to get its info, if I can do that it may make it easier to input the info into the UG and SG.
Hopefully we can find someone with a '07-'08 X model who can validate that issue is some kind of incompatibility with AT EVU or just some one off issue with my G. I have no known issues with my G. It is a 1/07 build.
It works for me using OBD Fusion and a BAFX OBD Adapter. the Foseal adapter hasn't done anything for me, connected to the tablet, but not the app.
ETA: The amazon page for this adapter states that it can't read TPMS. I played with it a little bit, while it can't read the pressures it will acknowledge the tire pressure light and allow you to clear it.
Last edited by Joenavy85; Sep 16, 2019 at 10:52 AM.
Unfortunately my proprietary '07 G35x seems to want a full blown Nissan Consult 3 to read AT temps. BAFX like others doesn't find any PIDs for the AT ECU.
It will scan through the 0-100 with Fusion but nothing is ever found.
Perhaps it is models with Tech package & Radar Cruise like mine that have issues? If someone has a '07-'08 G35x with tech package I'd like to hear if you can pull AT temps from options listed in this thread.
Last edited by treacherous; Sep 18, 2019 at 06:37 PM.
149° is dumb: What is the build month of your '07? Mine is 1/2007.
I also had all of the '07 ECU updates performed. I liked the stock flash with very sensitive pedal but got bit by some of the weird heat soak idle issues of the RTM stock flash.
It is weird that you successfully find 100 PIDs and mine shows a scan of 100 but never finds any.
Originally Posted by treacherous
I will bring this up to support. I do see a scan of 100 but it never finds any PIDs.
OBD Fusion/Link support might need to see a debug log of successful PID scan and compare it to my failed scan. At this point it could be my car is an anomaly or an issue with the X models.
Unfortunately my proprietary '07 G35x seems to want a full blown Nissan Consult 3 to read AT temps. BAFX like others doesn't find any PIDs for the AT ECU.
It will scan through the 0-100 with Fusion but nothing is ever found.
Perhaps it is models with Tech package & Radar Cruise like mine that have issues? If someone has a '07-'08 G35x with tech package I'd like to hear if you can pull AT temps from options listed in this thread.
Tomorrow during my lunch I'll go step by step (taking pictures) through getting to the Trans temps on my X. Just to make sure we're all on the same page. It took some playing around with it for me to figure it out.
Thanks! In 20 years of pulling OBD data from cars this has been the most frustrating one for me. I will take a video this weekend as well if I get time. There has to be some build/firmware revision anomaly with my vehicle preventing the AT ECU from cooperating.
