Jump to content

Picture of my old truck


Recommended Posts

Posted

This was my old truck. I bought it used in 91 and had it until 96. When I bought it, it was bone stock. As you see it here:

 

87 K5

300hp 5.7L

4.88 gears

Dana 44 front

12 bolt rear

8" Full spring lift

35" Swamper Boggers

 

I got about 8 miles per gallon and got 150k miles out of it. The second pic is what the old tilt test in New Jersey looked like.

 

fc275fa9.jpg

fc275ec9.jpg

Posted

In NJ, once you lift a truck over 4" including tires, your supposed to go to a specialized inspection. First you have to go through a safety inspection where they check the condition of the suspension and frame(Steering angles, everything tight, frame cracks, steering play etc...) If you pass the safety inspection, they weigh the truck. Then they tilt the truck 15 degrees(Drive up on the ramp) with the down side tires on the scale. If you have more then 2/3 body weight on the down side tire you fail.

 

Back when I went through, when you passed, they gave you paperwork so then you could then go through regular inspection. The paperwork had all the dimensions of your truck and if you made any changes, you had to go through again.

 

I think it's different now. I think they do both inspections all in one place now and there is no paperwork but there is a window sticker stating you passed.

 

If you fail the test, it's just like failing inspection. When I went, the inspector said he never had one flip over but if it did, the owner was responsible for getting it out of there.

 

Kenny

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...