Thread: PW 70A Random Reboot While car cranked

veetid... I have been having the same exact problem... the difference with my setup is I am using a 3.5" HD. Last I read on the board the talk was that the power to a 3.5" HD was likely the problem... I am in the process of converting to a 2.5" to see if this solves the problem.

Now the other things I have suspected is a USB conflict with the GPS... mine seems to reboot more often when the GPS in running... Perhaps there is a driver issue between my touchscreen usb driver and gps usb driver? (I use a Xenarc Screen)... What sort of screen are you using?

Anyone who can weight in... please do... I am in need of a solution too. Thanks.

I am using a serial GPS device powered by my battery, totally seperate from the pw70a, so that can't be the problem for me. Also I use a 2.5 HD and I still have the reboot problem, so thats no solution for me. I am using a lilliput, which has the same usb touchscreen as the xenarc, I think. I have no idea what could be causing this for me. Everything I have is well within what people say works fine with the pw70a. I got the pw70a because of its size.. It fits in my center console with my computer, which the opus would not have. I hope I can find a solution to this.. Anyone that has it working have any suggestions.

Where are you measuring the 13.5V? Right at the PW70, or at the batt?

Are you using a digital or analog meter. Most digital ones are too slow to see the real drop for the few milliseconds that it takes to cause the reboot. An analog meter may be a little better, but a scope is the right tool to use.

I am using an analog meter... The weird thing is, everytime it has rebooted it is in the same time frame... Basically it only reboots a couple of minutes after you crank the car and start going, unless this is coincidence.. I have had the PW70a in my car for two days and it has rebooted once each day. Both times it was a couple of minutes after I cranked and started moving that it rebooted. The most power intensive part is the spin up / boot up process of the computer and it always does that fine and starts running and playing music, then it reboots after a couple of minutes and after the reboot it always works fine... I drove both times for about an 1 hour with no reboots other than the initial one. My battery in my car always says 14V according to my gage and I have never seen it drop below that, unless I cut on everything in the car such as windshield, defrost, lights, and so on is when I have seen it go lower, but non of that was on the two times it rebooted and my battery was outputing 14V...

When you say cranked, you mean "on" right? I initially was thinking that you were talking about during "cranking" or starting the engine.

Are you running Motherboard Monitor or anything else to watch the voltages? Does your mobo support that?

When I was saying cranked I meant while the car was running.. I know I can't survive crank, but it should run fine while cranked.. I have the M10000 and I think it has MB Voltgage monitoring.... I think I found the problem, but I am not sure... The battery in my car has about 45,000 miles on it... I have been doing a lot of testing and playing with my car over the past month... cranking it 15 - 20 times a night playing with stuff and running the computer in ACC... Basically this morning my car wouldn't crank anymore.... I jumped it off and now my battery stays aroun 13V... I think my battery finally died....

It is pretty stressfull on a battery to crank it many times in a night and let it sit idle while pulling a full load on it right? I have been doing this for a month on a battery with 45,000... I know the ITPS will stop working if the battery ever falls below 13.1 because of the 1.1V the ITPS eats up, it actually needs 13.1 to get a clean 12V.. I am going to get a new battery and see if it stops...

I got a new battery and all is well...

Its your ignition wire going into the ITPS. You probably cut power while cranking.. so it goes through the ITPS shutdown, and cuts power 45 seconds later..


Doesn't that sound more like the problem?