Jump to content

Recommended Posts

Posted

Nice job,Mike. Thanx!

No problem man! Looks good! Do you have any pics of how they are mounted?

Posted

No, I didn't see in process. They are mounted to the diagonal bars, but don't know exactly how.

Posted

Local Truck Gear shop did the work - had a terrible time getting the grill off. I couldn't be happier.

Posted

Samsung Galaxy Note 3. Anyone know how to downsize or load through Tapatalk?

I post from my note 3 to the site. On the thread push the three dots in the top right corner and select reply. There left middle press the camera, select gallery. Select gallery or photo next, I use photo. select the picture and add text. Send is in top right corner like a play arrow.

Posted

But I've done exactly that and I get a message that the file is to large (and it doesn't post).

I may need to reset the camera settings. As I've mentioned, I would ordinarily download to my confuser, downsize, send anywhere, but my confuser's harddrive died last week.

Posted

I've always used Photobucket to host my pics and their Snapbucket app.

Posted (edited)

But I've done exactly that and I get a message that the file is to large (and it doesn't post).

I may need to reset the camera settings. As I've mentioned, I would ordinarily download to my confuser, downsize, send anywhere, but my confuser's harddrive died last week.

I know this isn't ideal, but in a pinch you can send yourself a text, and attach the pics. It will then reduce/compress it. Once you receive it, then save it in your gallery. Then when you post you can attach it to your post by retrieving it from your gallery, or you can load it into your gallery here at GM Trucks and it will be hosted here. Edited by Ventilator
  • Like 1
Posted

From my Note 3 taken last night at full resolution, so not sure what is up. Try reinstalling tapatalk.

 

76e50a10fe9f8ad2e717824a881a213c.jpg

Posted

Ventilator - Great suggestion! Thanks.

Posted (edited)

Thanks to Spurshot and others who have provided guidance here. I just completed the #10 to #22 diode mod so my fog lights will be on any time my headlights come on and they stay on with high beams. This took about 5 minutes to do and about half of that time was taken to be extra careful not to bend/break the diode. The only thing I noticed is the indicator light in the DIC does not light up, even though my fogs are lit. If I push the button, the indicator light comes on, but the fogs are already on and don't change. Push it again, the indicator light goes out, but fogs remain lit. As such, the indicator light must be tied to the switch and not to the fog lights themselves. I can certainly live with that, as I found it quite annoying that the fogs could not be set in a manner to default to ON when the lights are on. I also manually tested the parking light position on the switch and the fogs lit on with those alone (not requiring headlights), too.

 

If anyone is looking to do this mod, PM me, as I have an extra diode from Radio Shack from the 2-pack.

Edited by Magoomba
Posted

I'm looking to do this mod, I'd love to have a diode if this would work on my '15 Sierra.

Posted

I'm looking to do this mod, I'd love to have a diode if this would work on my '15 Sierra.

Mine's a 2015 and it worked. PM your contact info to me and I'll send the diode in the mail this week.

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