Jump to content

Driving from NC to Alaska!


Recommended Posts

Posted

I think if you want bear spray it will have to be bought in Canada. I did a 12,200 mile round trip from Ohio in 07. We turned around at the Arctic Circle on the Dalton Hwy. I changed the oil before leaving with 5w30 extended life Mobil One, then changed it after getting back home. We had a camper on the truck.

 

The only mechanical problem was going into Skagway. It started making noise lile a wheel bearing going out. I pulled the rr tire and found a pieceof gravel stuck between the caliper and rotor hat. The only other thing was the bad roads killed my oem aux. battery. Never had a flat but had to have a windshield afterward.

 

A warning about the roads. Once you get north of Grande Prairie watch the fog line on the side. When it dips, the road dips. The frost heaves can be killers. BC and the Yukon Hwy depts will mark bad dips, holes and broken pavement with cones and orange flags on the edge of the road. Be on the lookout.

 

The worst road stretch was between Destruction Bay Yukon and Tok Alaska. The Scenery will blow you away though.

 

Mark

  • Replies 40
  • Created
  • Last Reply
Posted

Yes, you can take certain weapons through Canada provided you declare them...I had them shipped down as it just made it alot easier to get through customs.

  • 2 weeks later...
Posted

One other fluid you might want to change out and that is the power steering fluid. You can change it out to synthetic and it will help with the colder temps up there as well as the extreme heat you might be getting into driving there from here in NC. What base in NC are you stationed at?

 

 

Never really thought about power steering fluid..gives me a good reason to put another amsoil order in though! I am in the Coast Guard at Air Station Elizabeth City. (Please no jokes about the coast guard haha)

 

Safe travels Coastie, I thought maybe you were doing a DIDY move..thats a hard one all the way to Alaska. My son is stationed now in Cape May. He went from Marquette MI to Petaluma and now Cape May. Stay safe and make sure you document all your belonging he has had some issue with stuff getting damaged and they questioned the condition of his furnitue and attempted to low ball him on replacement

Posted

Having lived in Alaska for many years I would recomend that you not opt for a block heater, but install an oil pan heater instead.. If you are running synthetic oil in your motor and gear boxes you will have less problems in the cold weather. Kodiak is not as cold as where I have lived but the freezing and heating of all the components is hard on all vehicles. A lot of people install a battery charger under the hood to keep the battery warm, but I doubt that would be necessary in Kodiak. Get as much done as you can before you get there, Kodiak is EXPENSIVE !!!

Posted

Having lived in Alaska for many years I would recomend that you not opt for a block heater, but install an oil pan heater instead.. If you are running synthetic oil in your motor and gear boxes you will have less problems in the cold weather. Kodiak is not as cold as where I have lived but the freezing and heating of all the components is hard on all vehicles. A lot of people install a battery charger under the hood to keep the battery warm, but I doubt that would be necessary in Kodiak. Get as much done as you can before you get there, Kodiak is EXPENSIVE !!!

 

 

great advice,,,awesome

  • 4 weeks later...
Posted

I can't believe nobody commented about the trailer...??

Going that far, go thru that whole trailer front to back. Look at all the weld joints / look for cracked welds. Re- do the bearings, no matter how new it may be . Check all the lights and wiring, get spare bulbs or sealed light assembly. Consider new tires for the trailer, trailer tires never seem to last as long as car/ truck tires, check your hitch , ball , safety chains , coupler .... Etc ...give everything a good going over .

Good luck preparing :)

Posted

I can't believe nobody commented about the trailer...??

Going that far, go thru that whole trailer front to back. Look at all the weld joints / look for cracked welds. Re- do the bearings, no matter how new it may be . Check all the lights and wiring, get spare bulbs or sealed light assembly. Consider new tires for the trailer, trailer tires never seem to last as long as car/ truck tires, check your hitch , ball , safety chains , coupler .... Etc ...give everything a good going over .

Good luck preparing :)

 

I'll second that...haven't driven the Alaska Highway twice now.

February/March 2004 from Delaware to Alaska

May/June 2008 From Alaska to Georgia

 

Both time went across the US and then straight up from California throuh Seattle. Both times ended up being about 6k miles with stops for famiy/friends/vacation. Can't wait to do it again, probably after I retire from the Air Force. British Columbia/Yukon have some of the most awesome scenery I've ever seen.

  • 3 weeks later...
Posted

Welcome to Alaska. I'm in Anchorage currently. My wife and I did the drive back in 2008. We went through Minneapolis straight north and then straight west 2000 miles to Edmonton.....I will never do that 2000 miles again. I am from the midwest and that 2000 miles is the most BORING drive ever. Completely straight flat boring farm land. I would recommend shipping any guns and ammo you have up instead of going through Canada. You can take bear spray through the border, you have to declare it. Make sure it SAYS bear spray on it. If it does not, they will confiscate it.....ask me how I know. Mine only said pepper spray on it. Even though its the same stuff. I wouldnt worry to much about carrying extra gas cans unless you are wanting to drive all night. I think the longest distance between gas stations is around 120 miles. One thing to consider is get up early and drive until you run out of gas. Most of the gas stations have bankers hours, and they are old school pumps. I didnt see a single pay at the pump option except in Edmonton. They will come out after hours and turn the pumps on for a convenience fee. If you have not picked up the book the Milepost, you may want to. It was only about $15 a few years ago. A ton of cool info in there as well as places to stop. Definitely stop at the hotsprings. Lastly, enjoy the drive. If you have the time to slow down and take your time, do it. The drive past Edmonton is absolutely gorgeous. You will be blown away by the scenerary. Take a ton of pictures and bring extra batteries and memory cards for your camera.

  • 1 month later...
Posted

Sounds like you saved yourself a lot of maintenance, but I would still give the truck a good "look over". Good luck and enjoy the drive!

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