Disciple Off Road
Hooked
Been crazy busy working on a new project and we hope to get up soon for all of you to see
View attachment 432920
WAYALIFE on the GO : Miscellaneous Photos from Cindy & Eddie!
- Thread starter wayoflife
- Start date
LOL - it's coming. It'll be today for sure
OverlanderJK
Resident Smartass
LOL - it's coming. It'll be today for sure
Just posted
www.wayalife.com
VIDEO : 20 YEARS of SEMA Highlights
At the risk of showing our age, 2025 will be the 20th year that Cindy and I will be in Las Vegas, Nevada and to cover SEMA or at least, in regards to Jeeps and the off-road industry. But, before we do, we thought it might be fun to look back and highlight some of the cool rigs we’ve seen over...
www.wayalife.com
As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
DirtHeadDavis
Hooked
Holy hell now that's an ordeal! Glad you guys made it there in the end and that you had 2 Jeeps to drive down there, one Jeep to pull the other Jeep, a Jeep to drive back to get a truck and a trailer, and were able to drive that truck and trailer back down to the other Jeep... LolAs some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Bummer about Moby but he's in good hands and I know we'll see him again soon.
Last edited:
Trail Bud
Hooked
That sucks, but it came out pretty good, all things considered. Glad you had 2 jeeps, to make it work. The weekend can only get better.As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Mike Pierson
Hooked
Wow guys, sorry that happened, but happy it worked out. Hope they can get him fixed up quickly.As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
Andy5160
Hooked
Damn! What a story. Get some rest. Oh and how wide is your trailer?As some of you may have noticed, WAYALIFE was down yesterday and apparently, it was because there was some kind of data center outage in Chicago. Needless to say, we were just one of many website affected by it but of course, at the time we didn't know it. And, to make matters worse, we had literally just started our long drive down to Boulder City in both Moby (going down to Motech for some updates) and our 392.
To add insult to injury, about 3 hours into our drive, Moby got a check engine light soon after we did a big pass around 4 semi trucks. Being that I just installed a clean K&N filter, I figured it was just oil getting into the MAF sensor as this is something we've seen before. So, I pulled over, checked things out, cleared codes and hopped back on the highway.
Unfortunately, as soon as we got going, I realized that I was still in a transmission limp mode and couldn't get past 3rd and so, I pulled over again. This is a known issue that happens every now and then can can be cleared simply by disconnecting the battery for a few minutes. I should note, this is actually why we were taking Moby down to Motech as they now have a fix for it.
After reconnecting the battery and clearing any codes that might be in the system, I fired up the engine, all was good and we were off again. But, after we were on the highway for about 5 minutes, Moby went back into limp mode and so I quickly pulled over again and shut off the engine especially being that this time, the oil pressure idiot light was on. After giving things a closer look, checked for any signs of trouble and verified there was oil in the engine, I went through the same things I did the first time to get us running again and then tried firing up the engine again.
Well, the good news is that there were no new codes and the oil pressure light was off but engine didn't sound good at all - kind of like a pully went bad but not exactly. Needless to say, I immediately cut the engine and started to plan what we were going to do next and just as rain started to fall
Fortunately, we were traveling with 2 Jeeps and so, we decided to have Cindy tow me in the 392, on a pole line paralleling the highway, to the nearest town (if you can call it that) and with Moby's engine off. As in, he had no power steering and no power boosted brakes.
Once we got to a place were we felt that we could somewhat safely leave Moby, we unloaded him, hopped in the 392 and headed back to Carson City. 3 hours later, around 11 pm, we transferred all our stuff into our new RAM, drove down to Pizen, hooked up our trailer and then went back to rescue Moby.
At 1 am, we finally got back to Moby, loaded him up, hopped back on the highway and continued our drive down to Vegas.
Around 4am, I needed to sleep a bit and so we pulled over and took a couple hour nap before continuing our drive south.
At around 8:30 am, we finally made it to Motech.
With all that said, I just heard from Kalan and apparently, he found that the noise appeared to be coming from the flywheel. After pulling the inspection cover off, he noticed there were a few bolts that were missing on it but the real questions is, where did they go? Needless to say, Moby may be spending a bit more time down here than we had planned but really, I feel lucky that things worked out the way they did and this as opposed to being out in the middle of nowhere and solo - something we would never do
Anyway, I think I'll take a nap now but I'll keep you posted once we find out anything new.
OverlanderJK
Resident Smartass
did the trucks pass you back?