Jump to content

Recommended Posts

Posted

i just bought a 2001 chevrolet 2500 hd with 9200 gvw that has a 4 button switch suggesting it has autotrac with the round auto button on top. i checked the rpo code for transfer case and its np1 that is a two speed transfer case not awd or autotrac. just wondering how this switch got put on this truck. i know all about the 1500hd and 2500 light duties with autotrac but my truck has the wrong switch  the the dash was made for it with no blank spot at the top of a normal 3 button switch. i bought it from the second owner and said truck was only two years old when he bought it and said when he went for a test drive he pushed auto and nothing happened. i will be changing stereo soon and i will see if its wired ? and maybe change the switch then. just wondering if anyone has seen of this before thanks

Posted

Most likely a p.o. bought and installed the wrong switch.  2500hd's didn't come with awd.  The right switch setup just has "4x4" stensiled on the plastic instead of an awd button.  I just looked through rockauto's website for the switch, and it would be easy for someone to buy the wrong switch.

  • Like 1
Posted

thanks davester i have seen alot of 1500hd and 7200 light duty 2500 with that switch but not a 9200 gvw 2500hd i included pic of her shes just got 139k on her just bought it yesterday, this is my favorite body style chevy!

00O0O_fsYEicUKt7Qz_0CI0t2_1200x900.jpeg

Posted

ive allready changed it out because i dont like things that are not correct to the truck i paid 35 on amazon for a dorman brand part. i was just wondering if it was an assembly line goof up and the worker didnt see it said hd on the door . i think all 2500 non hd had autotrac .giving the old one to a friend with 2002 1500 with autotrac.

Posted (edited)

No, I believe autotrak was an option, you could get either a regular 2 speed TC or autotrak.  It's much more likely someone replaced it with the wrong switch after it left the factory.

 

Edit: meant to indicate autotrak was an option for 1500's and possibly 2500ld's. 2500hd and 3500 didn't have it as an option.

Edited by davester

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...