Jump to content

I was out in western Illinois Saturday


CMNTMXR81

Recommended Posts

Posted

I was out helping my sister and brother in law move from Polo, IL to Shannon, IL.

 

Even my Mother (who was driving with me) noticed one thing....EVERY FARM/BUSNINESS whatever all had CHEVY'S!!!  Particularly 2500HD's!!!  Not a ford Super Duty in sight!  :D

 

On a side note, my Brother in law had borrowed his company's pickup, a 2000 Ram 2500 4x4, regular cab, 8ft bed.  After moving more of the big stuff (like entertainment centers, etc) It wouldn't start!!  LOL!   :)

 

It was like 11pm and we had just gotten done and were going to eat, and it'd just crank!  :D  They were flustered but I noticed that the gauges didn't go through their self checks and were not registering anything, so I told them to forget about trying to start it, A PCM feed was probably shorting out.

 

BTW, my truck did ALL the heavy work, thank you very much!!  :)

Posted

Na, Western IL is down near Macomb, Monmouth, etc.  You were in NWIL, course I guess for you Chicago guy it was still all "downstate."     :)  

 

As for the claim of all Chevys found out in the country, I'd say about half of them are, with the other half split between Ford and Dodge.  At one time I thought it was all GM country, but then I actually started counting them, more other makes out there than you first realize.  

 

So how'd you like your venture out of the city?  We aren't all that bad are we?

Posted
Na, Western IL is down near Macomb, Monmouth,

Keep coming about another 1 and a half to 2 hours and you'll be in "God's Country" :)

 

The bigger Crop sevices down here use Fords. Ask them why and they'll tell you. "Cause they're what we could get the cheapest." Then I reply "You said it, cheapest" It's funny they all drive Chevy's to work then have to work out of a ford all day. Some of the smaller companies that are locally owned use GM.

Posted

Like I say though, I didn't see a ford SD anywhere.  My Mother was the one that even picked this up.  :)

 

It was a shock to my system JP.  The air was too clean for my lungs!  My allergies went ballistic because across the street from their place in Polo, the had a combine cutting down the cattle corn (I think that's what it is called).

 

Funny thing, we take 88 out that way and once you get past DeKalb, it's amazing how desolate the highway is.  There was like one car every 5 minutes coming the other way (and I was the only one heading west in my little zone) and this was high noon.  :)

 

Oh yea, I keep forgetting that to us city slickers, everything is a suburb of Chicago!  It's a shock to see that There is another part of Illinois out there.  :D

 

Hog, I thought Wisconsin was God's country "Ya Hey der!"

Posted
I don't recall seeing any of them either.  Funny thing, my Mother goes "So where are all the fords?"  Just as she said it, we passed by one that was for sale (it was an older F-150).  LOL!  Her response..."Never mind!"  :)
Posted

If you want to see Ford SuperDuties, just come out here to Kansas.  I'll show you plenty of them, probably even go the full day without seeing a HD Silverado or Sierra.  As much as I hate to say it, ever since GM came out with the C/K pickups the Fords have dominated the 3/4 ton and up market around here.  Most of the farms around here run diesel pickups which practically eliminates GM right there.  Can't say I blame them for using so many SuperDuties though, they are simply the better pickup for farm use.  Maybe GM will eventually make a dent in the HD market around here, but it will several more years.

 

But you sure see a lot of GM HD's in town though...

Archived

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

  • Latest Articles

  • Posts

    • 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.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...