Jump to content

Recommended Posts

Posted
12 hours ago, Mike437 said:

Hey @th3magpi3 I sent you a PM inquiring about your services for my truck. Phone number is in the PM if it’s easier for you to call. Looking forward to chatting. Thanks!

Sent you a message, Mike! 

  • 3 weeks later...
  • 2 weeks later...
  • 1 year later...
Posted

On the 2015 cluster, it shows instant and average MPG on the same page - looks like they're separated on the upgrade?

 

Also, for my Model Year, only red is available - I have blue interior lights.  Does anyone have pictures of what a red cluster upgrade would look like with the rest of the lights being blue?  I'm sure it would look just fine, since the gauges are an isolated area, but kind of want to see one first hand.

  • 1 month later...
Posted (edited)

BEWARE!!

I shipped a Denali cluster to Coastal Flash for my 2018 Silverado 2500HD diesel.   Living in Canada, it just seemed like the easiest solution.  It was an absolute nightmare.  After shipping it to them twice and it still not being right I asked for a refund.  This was a 6-month process.  I heard every excuse in the book.  I then got in contact with WAMS. It sure sounds like I’m not the first person to go through this.  WAMS was very professional and told me to ship them my cluster so they could have a look.  Once they received the cluster they fixed it and had it shipped back to me within a few days.

Save yourself a huge headache and go straight to WAMS.

Rick

Edited by RickR15
grammar
  • Like 3
Posted
BEWARE!!
I shipped a Denali cluster to Coastal Flash for my 2018 Silverado 2500HD diesel.   Living in Canada, it just seemed like the easiest solution.  It was an absolute nightmare.  After shipping it to them twice and it still not being right I asked for a refund.  This was a 6-month process.  I heard every excuse in the book.  I then got in contact with WAMS. It sure sounds like I’m not the first person to go through this.  WAMS was very professional and told me to ship them my cluster so they could have a look.  Once they received the cluster they fixed it and had it shipped back to me within a few days.
Save yourself a huge headache and go straight to WAMS.
Rick

Glad to hear you finally got it resolved. WAMS should be the only place anyone considers for their programming needs. Hopefully more members on here can see that Coastal was banned on this forum for a reason.


Sent from my iPhone using Tapatalk
  • 9 months later...
  • 10 months later...
  • 2 weeks later...
Posted

Bought mine from WAMS no issues also specified that it came with navigation. Def worth the 650 also shipped out fast. 

55E396EC-C828-43F1-BA11-4A14D8BA9798.jpeg

Posted
16 minutes ago, gJesus1911 said:

Bought mine from WAMS no issues also specified that it came with navigation. Def worth the 650 also shipped out fast. 

55E396EC-C828-43F1-BA11-4A14D8BA9798.jpeg

it does look awesome

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...