Jump to content

Mississippi?


jakeweeman08

Recommended Posts

  • Replies 31
  • Created
  • Last Reply
Posted
Are there any other members from ms on here?

 

 

Jakeweeman08, I'm a MS boy down McComb way.

Posted

Yep,

 

I'm in Brandon (burb east of Jackson). Trey (C&A's Dad) and I get together for lunch from time to time. Y'all are welcome join us.

 

Let us know.

  • 1 month later...
  • 3 weeks later...
Posted
Bill here from the southside of the state

 

On the coast in Gulfport

 

Hey Bill. I'm down that way often my wife is from Biloxi. How are you doing with rebuiding from katrina?

  • 1 year later...
Posted

NORTH MS here Clarksdale, Work offshore on an oil and gas production platform out of Venice LA, So i travel most of the state twice a month. Glad i found the site to keep me entertained

Posted

Senatobia MS here... Just south of Memphis. Hey Carp what Heafner motors did you get your truck from?

Posted

Sab i got it in batesville, ms wasnt a great deal but wanted to be close if i had issues. My mom got a black one 3 weeks later in southaven. I have the SLE she has the SLE2 and paid 600 more than i did. But i have been fairly happy with my purchase. Now time to Mod it up...

Posted

Yeah, she went right by Senatobia to get to Southaven. I looked at Heafner and they wanted way more than Sunrise did in Memphis. (About 4-5k more) so I got it from up there no doubt. You're right up in my neck of the woods ha

  • 4 months later...
  • 2 months later...
Posted

Im in FL, about 2.5 hours from Biloxi. I am originally from Biloxi though.... Does that count?

Posted

Born and raised in Bexely (7 miles southwest of Lucedale in George County). Own ten acres there still and every member of my family still lives in George County except me. I'm the only one that ever moved away. Moved to Des Allemands Louisiana (southwest of New Orleans in St. Charles Parish) just after high school in 1982 to work for the 'summer' during the construction of the nuclear power plant in Taft Louisiana to make some money I would need for a few things because I was moving to Jackson Mississippi with a full scholarship to Mississippi State University I received by playing the saxaphone.......

 

Everything was going to plan until I met a Coon-ass named Susan......

 

The rest, as they say, is history.

 

:thumbs:

Archived

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

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