- AUTOENGINUITY SCAN TOOL FULL
- AUTOENGINUITY SCAN TOOL SOFTWARE
Can't Write to Modules to write VIN# or Mileage. AutoEnginuity and the others can't do everything the Dealers scan tools can, but enough they will pay for themselves in avoiding dealership visits. There are other similar tools out there for a competitive price, running of PC's. Send Bus Commands to turn things on and off.īefore I too blatantly advertise for AutoEnginuity. Change configuration options on various modules. Reprogram Wheel Diameter for different size tires. Basic maintenance operations features, like activating the ABS Pump to bleed the ABS module and brakes. Read all the manufacturers proprietary codes. The extended Manufacturer Features give you the ability to: If you purchase the codes to activate the extended features for "Chrysler" you get all vehicles, Jeep, Dodge, RAM for that Manufacturer. There are various cost for several or all Manufacturers. ~$220-$250 for the codes to "Activate" the built in Extended Manufacturer Capability for 1 Manufacturer. Still, like most generic OBDII tools you can't read the manufacturer proprietary codes for things like ABS, Body Codes, radio, etc. ~$225 for the basic tool that is really a generic OBDII tool, more capable than my $100 Innova 3100, Specifically you can read out and plot a lot more sensor data. Although AutoEnginuity is rather expensive, its cheapest tool with its abilities, and is less than the cost of 3-5 visits to the dealership to just read codes for you. This is the 10th time the AutoEnginuity tool has saved me time and money, either in troubleshooting, wasting money on guesses or wasting money on having dealerships scan and provide me the fault codes. Of course there are other troubleshooting steps to confirm its actually a bad wheel sensor and not something interrupting the signal, but I risked the cost of a quality wheel speed sensor ($40) and just jumped to replacing the wheel speed sensor. It read out various codes for different systems, all saying a bad front right wheel speed sensor. I use my AutoEnginuity Scan Tool, which is software that runs on any PC with an OBDII connector (with a translating chip inside it) connected via USB. I used an Innova 3100 OBDII Scan Tool (a good, but still Generic OBDII Scan Tool), no codes read out.
The vehicle had spurious ABS and Traction Control Reactions, sometimes couldn't get up past 40mph.
I got the ABS, Traction Control and BAS/ESP Warning Lights on. I think the problem may be with the device class but I'm out of my depth and could use some input.This is not a question, I've solved my problem, more a public service announcement.Ģ010 Jeep Commander 4WD, 3.7L, W5A580, QTI USB 2.0 Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubThen lsusb -d -v 1aa0:0008 returnsĬode: ******-MBP:~$ lsusb -v -d 1aa0:0008īDeviceClass 0 (Defined at Interface level)Ĭannot read device status, Operation not permitted (1)So what I'm looking to do is get the device recognised by ubuntu so that the program can see it in wine. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)īus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. Internal Keyboard/Trackpad (ANSI)īus 001 Device 003: ID 0a5c:4500 Broadcom Corp. IR Receiver īus 002 Device 003: ID 05ac:8507 Apple, Inc.īus 002 Device 002: ID 0424:2514 Standard Microsystems Corp.
Usb 1-1.4: new full speed USB device using ehci_hcd and address 20
0 kommentar(er)
