Jump to content

Recommended Posts

Posted
6 hours ago, Another JR said:

Did they need a WDH?

image.jpeg

I'll go out on a limb and say YES they did on that rig.  Probably shouldn't tow faster than 55 with it either.  :)  

Posted
15 hours ago, the wanderer said:

You should read what I wrote, not what you want me to have written. I said: "generally recommended".

So far only YOU are recommending this, and based on YOUR recommendation ANYONE towing faster than 65 is a "clueless drunken cowboy". So, when you call someone out, you better have something to back it up.

 

15 hours ago, the wanderer said:

 

Towing a trailer at that speed means you're just clueless. It's a 10 second google search for any number of experts to enlighten you, but somehow I suspect googling is a little above your paygrade amirite?

What specifically are we clueless about? "Experts", I'll need to see some credentials first.

 

15 hours ago, the wanderer said:

And it's why I refuse to provide sources 

There are none.

 

Despite all this... I RECOMMEND driving according to conditions, abilities, equipment condition and ratings. 

Posted
1 hour ago, XY74 said:

I'll go out on a limb and say YES they did on that rig.  Probably shouldn't tow faster than 55 with it either.  :)  

No, no, no... they had the little tag trailer between the car and main trailer. 55 is all it could go. :D

 

Posted

Are you all still doing this?  I think you all need to meet up and just bash the crap out of each other and get it out your systems....then go to the closest bar and get drunk together.  Next morning you all are best buds helping each other out saying, I love you man, the other saying, I love you too man....lol....You all could be best buds....think about it.  It's not far off the whole life scale is it?

  • Haha 1
Posted
On 3/10/2023 at 12:04 AM, Jettech1 said:

We never put hushkits on our 737's.  We did on the MD's along with an upper wing heater blanket because the fuel use to get too cold.  Thank goodness we retired all of those during the covid period.  Those extended DC-9s had a 50,000 cycle limit.  Insane.....what I don't like is we are still running the 717's....they are nothing but an old ass DC9 with upgraded engines and avionics.  Thank goodness they are retiring those as we speak.  It's not that they are unsafe at all.  It's just that technology has pretty proven them worthless these days...

I was a passenger many times in the MD87 back and forth from KLGA to KPBI.  I liked it, old school and more room.

 

How about 707s and DC8s?  I remember being served real food for dinner on those birds and they were very comfortable.

Posted (edited)
On 3/11/2023 at 1:52 AM, swathdiver said:

I was a passenger many times in the MD87 back and forth from KLGA to KPBI.  I liked it, old school and more room.

 

How about 707s and DC8s?  I remember being served real food for dinner on those birds and they were very comfortable.

At Delta we never bought any of the MD87's.  We only bought the MD88s, later on in the years we bought the MD-90's, a rare bird to say the least....lol...but a great A/C.  The V2500 engines on the MD90's were amazing.....They were old school for sure.  Basically an extended DC-9 with larger engines and upgraded avionics.  Here's the thing about the MD-88's, the JT8D-219 was so efficient (back then of course) that we had to do heater blanket mods on all of them to help heat the wings up to keep the fuel warm.  The fuel wasn't being used fast enough and was getting cold soaked in the tanks.  That was a huge mod we did to all of them.  

 

I've never laid hands on a 707, a tad before my time.  The 707 fuselage is the same as the 727 and 737.  Believe it or not.  All basically the same exact fuselage...weird but true.

 

When I first hired in I actually did work on DC8's.  At that time we were converting them to freighters for UPS.  We would strip them down inside, fix anything corroded, then it would fly to Italy to have the giant cargo doors installed in them.  Great memories...we are talking over 35 years ago for those memories of mine of the DC8's and the MD88's LOL.  Great memories for sure.

Edited by Jettech1
  • Like 1
Posted
On 3/10/2023 at 8:52 AM, asilverblazer said:

So far only YOU are recommending this, and based on YOUR recommendation ANYONE towing faster than 65 is a "clueless drunken cowboy". So, when you call someone out, you better have something to back it up.

 

What specifically are we clueless about? "Experts", I'll need to see some credentials first.

 

There are none.

 

Despite all this... I RECOMMEND driving according to conditions, abilities, equipment condition and ratings. 

 

You didn't google it did you? If you did, you'd quickly understand how completely stupid you sound right about now.

Posted
On 3/10/2023 at 8:52 AM, asilverblazer said:

So far only YOU are recommending this, and based on YOUR recommendation ANYONE towing faster than 65 is a "clueless drunken cowboy". So, when you call someone out, you better have something to back it up.

 

Lovely strawman, did you prop it up all by yourself?

 

I didn't say "anyone towing faster than 65 is a 'clueless drunken cowboy'". That's reserved for complete morons who tow at 80.

 

I said the generally recommended towing range is 55 to 65.

Posted

Dear God, does this forum not have any moderators? Time to hand out some time outs and save the rest of us from the horror. 

Posted
10 hours ago, Jettech1 said:

At Delta we never bought any of the MD87's.  We only bought the MD88s, later on in the years we bought the MD-90's, a rare bird to say the least....lol...but a great A/C.  The V2500 engines on the MD90's were amazing.....They were old school for sure.  Basically an extended DC-9 with larger engines and upgraded avionics.  Here's the thing about the MD-88's, the JT8D-219 was so efficient (back then of course) that we had to do heater blanket mods on all of them to help heat the wings up to keep the fuel warm.  The fuel wasn't being used fast enough and was getting cold soaked in the tanks.  That was a huge mod we did to all of them.  

 

I've never laid hands on a 707, a tad before my time.  The 707 fuselage is the same as the 727, 737 and 757.  Believe it or not.  All basically the same exact fuselage...weird but true.

 

When I first hired in I actually did work on DC8's.  At that time we were converting them to freighters for UPS.  We would strip them down inside, fix anything corroded, then it would fly to Italy to have the giant cargo doors installed in them.  Great memories...we are talking over 35 years ago for those memories of mine of the DC8's and the MD88's LOL.  Great memories for sure.

 

Must've been MD88s as those trips were with Delta by the same two pilots most of the time, they were ex-US Navy Tomcat pilots as I remember it.

  • Like 1
Posted
16 hours ago, swathdiver said:

 

Must've been MD88s as those trips were with Delta by the same two pilots most of the time, they were ex-US Navy Tomcat pilots as I remember it.

I bet the landings were fun with them being ex-carrier pilots....lol...

  • Haha 1
Posted
7 hours ago, Jettech1 said:

I bet the landings were fun with them being ex-carrier pilots....lol...

Yes, especially right after 9-11!  Loved it but some folks got upset but that was normal for a while back then.

 

Sometime in 2002 we had another crew take us to LaGuardia.  This pilot dropped us down to below 10,000  while still over New Jersey and we flew along the coast for a long time.  Then, I don't remember how we got there but we were over City Island getting lower and lower as we lined up for runway 22.  Well, we flew just to one side of that boardwalk of markers until the last moment, the gear barely above of the water until the last moment when the pilot finally applied enough power to get us over the ramp and then set down.  Weirdest flight of my life.

  • Like 1
Posted
20 hours ago, swathdiver said:

Yes, especially right after 9-11!  Loved it but some folks got upset but that was normal for a while back then.

 

Sometime in 2002 we had another crew take us to LaGuardia.  This pilot dropped us down to below 10,000  while still over New Jersey and we flew along the coast for a long time.  Then, I don't remember how we got there but we were over City Island getting lower and lower as we lined up for runway 22.  Well, we flew just to one side of that boardwalk of markers until the last moment, the gear barely above of the water until the last moment when the pilot finally applied enough power to get us over the ramp and then set down.  Weirdest flight of my life.

Love it!!

  • Like 1
  • 3 years later...

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

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