Jump to content

Recommended Posts

Posted

As title asks, is anyone running a Pulsar LT with the 6.6 gasser?  I've been considering getting it for my truck to try out, but wondering if anyone else has it already and can give some feedback.  I guess really the only things I'd use it for is to change the tpms thresholds and adjust for the 35's I'm now running.  It also says it can be used to clear engine codes, which I currently already have a cheap handheld scanner that can do that. 

Posted

I have it. I put 37s on and used it to adjust for that, throttle sensitivity, and lower tpms warning. No complaints. 

  • 1 month later...
Posted

Has been working great here. Bought mainly for tire size and TPMS modding. I keep the throttle at 30% over stock and it makes the truck feel like it should from the factory. Kills the sluggish hesitation and makes the truck feel like the 464tq is there. Also reduces the 2>1 shift clunk on deceleration.

Posted

Good info thanks.  I bought one, just haven’t had a chance to install it yet.  I added 35’s so my main reason for getting the Pulsar was to change the tire size and tpms lower threshold.

  • 4 months later...
Posted

finally got around to installing this.  Went to plug in the harness and it doesn't fit the oem plugs of my truck.  The 2 guide rails on the connectors of the Pulsar plugs are further apart than the ones on my oem plugs.  I reached out to Pulsar and they are telling me it should fit; well it doesn't.  Ugh, hoping they will take it back, but no further response from them yet.  the raised part of the grey connector, as seen in picture; top one is lined up in groove, but bottom one doesn't line up as it's spaced further out.  oem plugs spacing is 2-5/8" between the 2 guides and the Pulsar plugs are 2-7/8" apart.  Guess they use slightly different Delphi plugs.

IMG_2756.jpg

Posted

There is another connector that is very similar looking in the same area..try it. I ran into the same issue. Instructions are horrible at showing the correct one to plug into. If you havnt figured it out by tomorrow, i'll get a pic of where mine is plugged in.

Posted (edited)

I gave up for the night.  I didn’t see another connector like that in that area anywhere.  If you don’t mind sending a picture my way that would be great.  The one I tried is right below the coolant tank and brake fluid reservoir.  It has a big plastic bracket coming off the frame rail up, and the comnector has a christmas tree clip holding it to the bracket.  Wire harness runs from firewall, along inner fender up to the ecm.

Edited by Sonders
Added more details
  • 4 weeks later...
Posted

I finally got mine installed recently after talking to TS423.  I was overlooking the correct plug like a big dumbie.  I’ve only driven the truck once since installing it and the throttle response is noticeably better in setting 3.  When going through all the different programmable options I noticed the rear gear ratio defaulted to 3:23 so I changed it to 3:73, along with my tire size from 34 to 35’s.  

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...