Jump to content

Recommended Posts

Posted

Did you get the transmission tuned as well or just the PCM?

  • 1 month later...
Posted
On 7/18/2020 at 6:41 PM, SuperCharged-5.3L-2020 said:

$8.5k 

PCM was sent to HP Tuners, they unlock it and send it back, then ProCharger sends the tune files and you load them through your pc. 
I shipped it on a Monday, arived to HP tuners on a Wednesday and they shipped it back on a Friday aternoon. 

 


Absolutely everything works. But the car will not start at the first press of the start engine (starts at the second press). You need to take if yo someone (dealer, mechanic, yourself) with an MDI2 tool and SPS suscription. I did it myself and I am not a mechanic. My local dealer sucks and was lost on what needed to be done. 

What exactly did you have to do with the mdI2? I just ordered a procharger myself. Was hoping the hp tune would be all I needed for the truck to work fine. I have no experience in using a mdI2 but very willing to learn. 
Also If day you added a cat back or cai to your truck can you change parameters with the hp tuner they sent with the kit? Thanks man.

Truck looks unreal btw 

Posted

any dyno numbers? send some videos of idle and acceleration please. I had a Procharger P1SC on my 2001 Silverado 5.3 back in 2001 and I'm considering one for my 2020 Trailboss 6.2.....

Posted

Did you have your hood scoop painted or were you able to order already color matched?

 

Congrats on going boosted. It's a lot of fun. Ran 682hp at the wheels on my last mustang.

What tunes did you go with? 93 octane, E-85? You can usually pick up considerable more HP running E-85 provided the tuner has the ability.

Posted
On 9/2/2020 at 11:56 AM, ap9 said:

What exactly did you have to do with the mdI2? I just ordered a procharger myself. Was hoping the hp tune would be all I needed for the truck to work fine. I have no experience in using a mdI2 but very willing to learn. 
Also If day you added a cat back or cai to your truck can you change parameters with the hp tuner they sent with the kit? Thanks man.

Truck looks unreal btw 

I had the K&N Cai and just reverted back to the system that comes with the procharger. It took 7 tune attempts to get my truck correctly working but the guys from Procharger are good. I guess they now have the correct parameters for future trucks. I do not have any CEL on. 

 

The MDI2 I bought from amazon (a bit expensive). There is a Chinese version but I decided to go with the original one. You actually do not need one if your dealer has a clue about things... (not my case). It is only for the truck to start the engine on the 1st push of the button instead of doing it 2 times each time. If you need more details I will be happy to help. 

 

Posted
On 9/2/2020 at 10:13 PM, 6.2TRAILBOSS said:

any dyno numbers? send some videos of idle and acceleration please. I had a Procharger P1SC on my 2001 Silverado 5.3 back in 2001 and I'm considering one for my 2020 Trailboss 6.2.....

no dyno numbers, but I will upload a couple of videos later

Posted
6 hours ago, repins1911 said:

Did you have your hood scoop painted or were you able to order already color matched?

 

Congrats on going boosted. It's a lot of fun. Ran 682hp at the wheels on my last mustang.

What tunes did you go with? 93 octane, E-85? You can usually pick up considerable more HP running E-85 provided the tuner has the ability.

I had it painted locally, just by giving the color code.

I live abroad, so locally I get 95 octane.

Posted

upload those videos!!!!

 

I wanna put a blower on my 6.2 so badly but I've has it for less than 2 months and don't wanna lose my warranty just yet  

Posted
On 7/19/2020 at 2:29 PM, SuperCharged-5.3L-2020 said:

The scoop is just because I like the way it looks. It may be removed anytime. It installs with a strong double sided tape
 

the light bar is a must for these trucks. The original hi-low beam is very bad. 
I did install the switch on the right side, which I feel is much easier to reach while driving:

 

DA15FDC6-62DA-4D6F-9A89-6AE8CC81328D.jpeg

73AC20ED-DD69-4579-8AB9-21AA894B4ECA.jpeg

Can you share more info about the LED Bar?  Where did you get it? Wiring? Thanks

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,633 Guests (See full list)


  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...