Here’s my review of the Autoenginuity scan tool along with the enhanced Nissan expansion. Background: I’m not a professional auto tech, I’m an engineer. I have two Nissans and a Honda. Most of the work I do is on my 1997 Nissan Maxima. Along with the generic OBD2 features, I wanted AE so I could: 1) pull DTCs and display live data from enhanced powertrain, SRS, transmission, and airbag systems, 2) graph live data, 3) display decoded mode 6 data, 4) record and playback live data.
I ordered the software directly from the AE site back on January 30. They neglected to send me the USB key that enables the Nissan expansion, but a phone call corrected that. Along with the USB key they sent me activation codes that didn't work, requiring another phone call. These were glitches I wasn't expecting, but they weren't too troublesome.
In generic OBD2 mode, AE connected fine to my cars, and other than being slow to connect, also worked as expected. It retrieved and decoded mode 6 data, but very slowly - it seemed to take about two minutes to enumerate all the TIDs/CIDs and then it runs down the list, taking about 5-10 seconds to retrieve the value of each TID/CID, one after the other.
The trouble started when I tried to use the enhanced Nissan expansion. First, you have to read the manual closely to discover that you have to change the Initialization Type in the Vehicle Communication Configuration to "Non-OBDII-only" when any system other than generic powertrain is selected. If you don't do that, it won't connect. If you then leave that setting at "Non-OBDII-only" and try to connect to the generic powertrain system, AE gives you an error saying that you can't use non-OBD2 initialization for generic OBD2. Makes sense, but if the software already knows the difference between initializing generic OBD2 and anything else, why can’t it simply change that initialization setting for you? Annoying, but at least it was documented. I also couldn't get AE to auto-detect the Vehicle Interface Type on any of my vehicles. I had to set it manually.
When I connected to my 1997 Maxima, it tried to pull DTCs for four non-generic systems. I had no DTCs, so I attempted to look at the live data for the enhanced powertrain system. AE said there were 32 sensors, but no list of sensors appeared. There were no errors or any indication of what went wrong. Irksome. Then I switched the system to automatic transmission,
and this time I was happy to get a list of sensors. But when I clicked on a few of them to get live data values in the Live Data Grid, all I got was "No data." Again, no error messages. I emailed AE customer support, using their web form. I got an automated response telling me to reply with all the information I already sent them, and also include the AE log file, even though the web form doesn't tell you to do that. OK, so I have to go back out to the car and go through the whole process over again, generate the log file this time, and email it back to them. A day later, here's the response I get: "We don't have ECM TCM tables for the Maxima. Reading DTCs is the only thing that will work for that engine." But their web site says full enhanced powertrain coverage for 1996-2011 with the enhanced Nissan expansion. Disappointing that this isn't really true.
A couple of months go by, and the MIL illuminates on my Maxima. I use AE to pull the DTCs - P0130 bank 1 O2 sensor 1. I expect to be able to see the freeze frame data associated with the DTC, but for the life of me I can't figure out how. Either it's not there, or it's not obvious how to display it. No problem, I'll look at the O2 sensor display while the car’s idling. The upstream O2 sensors on both banks seem to be switching normally during idle. I decide I'll turn on data logging and take it for a test drive, and see if anything shows up during playback. I do a 2-minute test drive, take the laptop back inside, play back my data log, and get - nothing. Nada. The .csv file is empty, except for a header line. I figure I must’ve done something wrong, so I go for another test drive. I drive about 3 minutes, but this time I get only about 17 data points. Thinking I didn't go on a long enough test drive, I go back out for a 10 minute test drive. That should be long enough, I think. But this time I get only about 10 data points. Looking closely at the .csv file, I see that the points aren't uniformly spaced in time. It looks like AE is recording for a few seconds, then not recording, then recording another second, etc., then just stopping for no apparent reason. The data logging feature is totally useless.
I can't remember things accurately enough to list all the little ways the software is annoying, but here are a few general observations: it takes much longer to connect than my Actron scanner, it takes much longer to retrieve DTCs, much longer to clear the MIL, much longer to get the list of mode 6 TIDs/CIDs. It occasionally fails to connect. It’s crashed a couple of times. The design of the interface is like something from the Windows 95 era. Particularly irritating is the method for changing the scale of a graph on the Live Data Graph page. To graph a sensor value, you select the sensor from a dropdown box. If you want to change the scale on the graph, what do you expect to do? Click the axis, double-click the axis, right-click on the axis, right-click on the graph - none of that works. Instead, you have to click the arrow on the sensor selection dropdown box, then select "Configure sensor." This is completely unintuitive. The selection of the sensor should be done in one combobox, and the axis scaling done by interacting with the axis or the graph, not the sensor. I'm not configuring a sensor, I'm configuring the scale on a graph. If you insist on calling it sensor configuration, why not just put a button at the top? Since I've already selected a sensor, it's clear which one I want to configure, and why would it occur to me to go back to the sensor selection box to configure the sensor I already selected? This is the kind of bad design that gets a piece of software described as crapulent.
The graphs commit a mortal sin - the x-axis isn’t captioned and there’s no unit of measure. Is it time in seconds? There’s a tab labeled Live Data Graphs (2X) that shows two distinct graphs, one above the other, each of which can display two sensors. There’s another tab labeled Live Data Graphs (4X). Since the 2X tab shows two graphs, would you think the 4X tab shows four graphs? No, it shows one graph, which can display four sensors. I’m baffled by this. What developer would be proud of this? Why not a more flexible design that allows create as many graph windows as you want, with as many sensors as you want, and tile them?
Clicking on the Help menu selection just displays a copy of the PDF manual. Again, laziness on the part of the developers.
In summary, even if this software worked flawlessly it still has a pretty amateurish design that I expect from old shareware from the 90s, not something I paid $400 in 2012 for. And for the vehicle I needed it most for, the enhanced features it was supposed to have don’t even work, so it’s no better than a $200 Actron I already owned. The support was pretty weak - I think it’s one guy running the business out of his house with an assistant or two, and they weren’t very helpful. I'm about as disappointed in this software as I can be. Hopefully they'll agree to my request to return the product for a refund.
I ordered the software directly from the AE site back on January 30. They neglected to send me the USB key that enables the Nissan expansion, but a phone call corrected that. Along with the USB key they sent me activation codes that didn't work, requiring another phone call. These were glitches I wasn't expecting, but they weren't too troublesome.
In generic OBD2 mode, AE connected fine to my cars, and other than being slow to connect, also worked as expected. It retrieved and decoded mode 6 data, but very slowly - it seemed to take about two minutes to enumerate all the TIDs/CIDs and then it runs down the list, taking about 5-10 seconds to retrieve the value of each TID/CID, one after the other.
The trouble started when I tried to use the enhanced Nissan expansion. First, you have to read the manual closely to discover that you have to change the Initialization Type in the Vehicle Communication Configuration to "Non-OBDII-only" when any system other than generic powertrain is selected. If you don't do that, it won't connect. If you then leave that setting at "Non-OBDII-only" and try to connect to the generic powertrain system, AE gives you an error saying that you can't use non-OBD2 initialization for generic OBD2. Makes sense, but if the software already knows the difference between initializing generic OBD2 and anything else, why can’t it simply change that initialization setting for you? Annoying, but at least it was documented. I also couldn't get AE to auto-detect the Vehicle Interface Type on any of my vehicles. I had to set it manually.
When I connected to my 1997 Maxima, it tried to pull DTCs for four non-generic systems. I had no DTCs, so I attempted to look at the live data for the enhanced powertrain system. AE said there were 32 sensors, but no list of sensors appeared. There were no errors or any indication of what went wrong. Irksome. Then I switched the system to automatic transmission,
and this time I was happy to get a list of sensors. But when I clicked on a few of them to get live data values in the Live Data Grid, all I got was "No data." Again, no error messages. I emailed AE customer support, using their web form. I got an automated response telling me to reply with all the information I already sent them, and also include the AE log file, even though the web form doesn't tell you to do that. OK, so I have to go back out to the car and go through the whole process over again, generate the log file this time, and email it back to them. A day later, here's the response I get: "We don't have ECM TCM tables for the Maxima. Reading DTCs is the only thing that will work for that engine." But their web site says full enhanced powertrain coverage for 1996-2011 with the enhanced Nissan expansion. Disappointing that this isn't really true.
A couple of months go by, and the MIL illuminates on my Maxima. I use AE to pull the DTCs - P0130 bank 1 O2 sensor 1. I expect to be able to see the freeze frame data associated with the DTC, but for the life of me I can't figure out how. Either it's not there, or it's not obvious how to display it. No problem, I'll look at the O2 sensor display while the car’s idling. The upstream O2 sensors on both banks seem to be switching normally during idle. I decide I'll turn on data logging and take it for a test drive, and see if anything shows up during playback. I do a 2-minute test drive, take the laptop back inside, play back my data log, and get - nothing. Nada. The .csv file is empty, except for a header line. I figure I must’ve done something wrong, so I go for another test drive. I drive about 3 minutes, but this time I get only about 17 data points. Thinking I didn't go on a long enough test drive, I go back out for a 10 minute test drive. That should be long enough, I think. But this time I get only about 10 data points. Looking closely at the .csv file, I see that the points aren't uniformly spaced in time. It looks like AE is recording for a few seconds, then not recording, then recording another second, etc., then just stopping for no apparent reason. The data logging feature is totally useless.
I can't remember things accurately enough to list all the little ways the software is annoying, but here are a few general observations: it takes much longer to connect than my Actron scanner, it takes much longer to retrieve DTCs, much longer to clear the MIL, much longer to get the list of mode 6 TIDs/CIDs. It occasionally fails to connect. It’s crashed a couple of times. The design of the interface is like something from the Windows 95 era. Particularly irritating is the method for changing the scale of a graph on the Live Data Graph page. To graph a sensor value, you select the sensor from a dropdown box. If you want to change the scale on the graph, what do you expect to do? Click the axis, double-click the axis, right-click on the axis, right-click on the graph - none of that works. Instead, you have to click the arrow on the sensor selection dropdown box, then select "Configure sensor." This is completely unintuitive. The selection of the sensor should be done in one combobox, and the axis scaling done by interacting with the axis or the graph, not the sensor. I'm not configuring a sensor, I'm configuring the scale on a graph. If you insist on calling it sensor configuration, why not just put a button at the top? Since I've already selected a sensor, it's clear which one I want to configure, and why would it occur to me to go back to the sensor selection box to configure the sensor I already selected? This is the kind of bad design that gets a piece of software described as crapulent.
The graphs commit a mortal sin - the x-axis isn’t captioned and there’s no unit of measure. Is it time in seconds? There’s a tab labeled Live Data Graphs (2X) that shows two distinct graphs, one above the other, each of which can display two sensors. There’s another tab labeled Live Data Graphs (4X). Since the 2X tab shows two graphs, would you think the 4X tab shows four graphs? No, it shows one graph, which can display four sensors. I’m baffled by this. What developer would be proud of this? Why not a more flexible design that allows create as many graph windows as you want, with as many sensors as you want, and tile them?
Clicking on the Help menu selection just displays a copy of the PDF manual. Again, laziness on the part of the developers.
In summary, even if this software worked flawlessly it still has a pretty amateurish design that I expect from old shareware from the 90s, not something I paid $400 in 2012 for. And for the vehicle I needed it most for, the enhanced features it was supposed to have don’t even work, so it’s no better than a $200 Actron I already owned. The support was pretty weak - I think it’s one guy running the business out of his house with an assistant or two, and they weren’t very helpful. I'm about as disappointed in this software as I can be. Hopefully they'll agree to my request to return the product for a refund.
