Jump to content

MBNA Cal Ripken Jr. 400 ??


Elwood

Recommended Posts

Posted

From Jayski.com :

NEWS/RUMORS

--------------------------------------------------------------------------------

Ripken Scheme? UPDATE 4: hearing #18-Bobby Labonte's car will have a special Cal Ripken Jr farewell paint job at Dover in September. Ripken Jr plays for the Baltimore Orioles and is retiring at the end of the 2001 baseball season(8-17-2001)

UPDATE: hearing that since Cal Ripken's last home game will be the evening of the race, at Camden Yards vs. the Yankees. To honor his achievements, MBNA will be renaming the race from the MBNA 400 to the Cal Ripken 400 (or something similar) and that Ripken will be present at the race as the Grand Marshal(8-20-2001)

UPDATE 2: also hearing that #18-Mike McLaughlin will drive the Cal Ripken car in the MNBA 200 BGN race and that a formal announcment will come in the next 7-10 days(8-23-2001)

UPDATE 3: NASCAR and Major League Baseball are expected to finalize an unprecedented agreement within the next 10 days that would celebrate Cal Ripken Jr.’s retirement in a most unique way. For starters, the MBNA 400 Winston Cup race scheduled for Sept. 23 at Dover Downs International Speedway in Dover, Del., will be renamed the MBNA Cal Ripken Jr. 400. In addition, the Orioles third baseman will act as the grand marshal for the 1 p.m. race before flying back to Baltimore to play in the final home game of his career at Camden Yards that night. “We have been waiting for a couple of days for a sewn-up package,” said Carmine Tiso, a media relations specialist handling business matters for Major League Baseball. “Hopefully in the next week or 10 days it will be (finalized). There are a lot of parties involved including us, the Orioles, MBNA.” Tiso described the deal as “all but done.” Another source close to the deal said a joint announcement about the specifics could come as early as Thursday at Camden Yards. NASCAR has some other tributes planned for Ripken, as well. The Interstate Batteries/MBNA #18 car driven by defending Winston Cup champion Bobby Labonte will be repainted for the Dover race to include a Cal Ripken logo. The Ripken logo will also be on Mike McLaughlin’s car during the MBNA 200 Busch Series race that Saturday at Dover Downs, Tiso confirmed. The tentative plan, according to the source close to the deal, is for Ripken to arrive in Dover — about 100 miles from Camden Yards — on Sunday around 9 a.m., sit in on the morning drivers’ meeting and conduct a short news conference with the motorsports media. Ripken will be part of the drivers’ introductions and will be driven in a convertible around the track before the race begins. Ripken will then wave the green flag to start the race before getting in a helicopter and flying back to Baltimore. The winner of the Winston Cup race will be invited to fly to Baltimore as Ripken’s guest for that night’s game.(York Daily Record) and another story at the Washington Post: Ripken Farewell Faces a Switch(8-24-2001)

UPDATE 4 - maybe? One major obstacle lies in the path of Dover Downs’ quest to rename the Sept. 23 MBNA 400 after one of major league baseball’s all-time greatest players. According to track publicist John Dunlap, if the New York Yankees agree to allow the Baltimore Orioles to push back the start of their game at Camden Yards from its currently scheduled 1:35 p.m. start to “somewhere between 5 and 7,” Cal Ripken Jr. will serve as grand marshal of the MBNA Cal Ripken Jr. 400 at Dover Downs International Speedway. Dunlap also said a press conference is “supposedly” scheduled for Thursday at Camden Yards regarding this announcement, but didn’t name a time.(NASCAR.com)(8-30-2001)

 

Personally I'm not a huge baseball fan, but I like it ok.  And I know enough about it to have alot of respect for what Ripken has done for the game.  I think it's pretty cool that they want to honor him, but I hope they don't get too carried away with this and start doing this stuff all the time.

What do you guys think about this????

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   4 Members, 0 Anonymous, 1,993 Guests (See full list)

  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...