Jump to content

Pics of the new truck


Recommended Posts

Posted

Hey all-

 

got time to snap some pics of the new rig today, still has lots of work to be done on her. Still have to add the CB, PA/Siren/Airhorn, Switch Panel, LED strobes in the grille and rear window, Work lights in the rear window, striping/lettering, and the spotlight for thr driverside A pillar. Allready added the K&N Airfilter, carphone, front worklights, and wiering for everything...ill post more when i get-er-done

 

gmc_frnt_angl_1.jpg

 

gmc_side.jpg

 

gmc_rear_angl.jpg

 

gmc_int_1.jpg

Posted

good lookin rig

so what r u gonna be towin?? dont see a repo stinger so whats the plans 4 this beaut

 

 

 

where r ya gonna mount the speaker? i cant seem to keep my frame mount form getting worn by the vibration

Posted

Im not exactly sure where to put the speaker yet, still tryin to figure it all out, probably right behind the grille or front bumper depending on whats eaiser to reach. Currently shes going to be the new service truck more or less, I may put a repo wheel lift on it eventualy, just no plans to be doin repo work any time soon.

Posted

well hope she works out 4 ya an let me know what works for you mounting wise ive already gone through 2 mounts and i just seem to beat the hell outta them

 

 

well good luck with the truck shes a nice one

Posted

Nice look'in truck. Hope you have good arms. When I had my Supra, which was black, getting the swirls out after a wax job was so tough. However, that being said I think waxes have come along way since then.

 

Keep it Clean!

  • 4 weeks later...
Posted
good lookin rig

so what r u gonna be towin?? dont see a repo stinger so whats the plans 4 this beaut

 

 

 

where r ya gonna mount the speaker? i cant seem to keep my frame mount form getting worn by the vibration

 

 

 

 

I assume its a metal speaker as opposed to plastic if your using it for a siren as well? I mounted mine just below the top of the front bumper. There should be two holes. I just took a piece of flat stock, to go between the first and second hole, then drilled 2 more holes towards the center to mount the speaker on. Just make sure to use locking nuts or lockwashers. Things tend to rattle loose otherwise. I will try and get some pictures today since it finally stopped storming. Truck needs a bath! :cheers:

Archived

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

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   3 Members, 0 Anonymous, 2,122 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • 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.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...