Ideas for my ALP stuck in parking mode...

[AirMoore]

I would like to get some ideas from you guys...


As I posted in my recent "introduction" post... my civic blew it's head gasket so I haven't been able to really use the car, and didn't use the countermeasures for ~5-6months.

Last I knew, the ALP worked, but had a head possibly going bad (error 2)

I have tried firing it up since getting my car back going and have had these issues:

1) The ALP will not go out of parking mode no matter what I do. After all else failed I even tried completely resetting the entire unit and updating everything to the newest updates (and the app too). Still stays green (it never turns blue, regardless of the settings I load onto it via USB). I have no clue why it would lose it's old settings, the power was off to it for weeks at a time, but it's my understanding this shouldn't have done anything. I should have been able to fire the thing up like I never left it.

2) The "Error 2" message I talked about now comes up every time I fire up the ALP, one of the heads I thought was on it's way out ~6-8 months ago (when ALP implemented the deeper self-check) is now gone for sure. How do I find out the exact head that is causing this? Do I reset the unit and only use one head at a time?

Does the ALP now stay in parking mode if it notices an error with one of the heads?


PS: When I try to get the "system info" my tablet searches for awhile... and then the tablet tells me the "ALP is disconnected" and I can't pull any info from the ALP. If I turn off the ALP via kill-switch it will again say "ALP Disconnected."


Also, using the regular control module that comes with the unit, the same stuff happens (regarding staying in parking mode), so it doesn't seem to be the BT interface causing the issue.


I'm in no rush, I won't have much time to really apply many fixes right now, but it would be great to get as many ideas as possible so I could run through them when I eventually get some time. That is to say instead of trying one fix, coming back and reporting it does(n't) work, having 4 or 5 options right off the bat would be nice.

[BestRadarDetectors]

Start by pulling a Statistics file and see if any head is showing offline. If it is unplug it from the CPU and see if everything goes back to normal.

Sent from my SM-G928T using Tapatalk

[radargeek]

Do you have privacy mode enabled? If you do, you need the key file on a USB to get it to work in defense mode.

[AirMoore]

Thank you both for the input I've made some "progress" as I did some 350 miles the past 2 days:

The unit which was stuck in parking mode became "unstuck" by running into a radar source. Seriously. What follows is a quick blurb:

I started the unit up... it gave it's usual "Error 2" and was stuck in parking mode for quite a few minutes (~10)... so I reset it yet again and reapplied the settings.

(I) Same "Error 2" but I said screw it an drove with it
(II) 2 minutes later I drove into a "k-band false" it not only alerted, but pushed the ALP into Defense mode
(III) 2 Minutes after that, I got a false Poliscan alert
(IV) 1 Minutes later, K-band
(V) 1 Minute after that, I got another false Poliscan alert


So now here is where I am at with it:
-It DOES go into "defense mode" in one of two conditions:
1) The unit encounters a radar source (this will 'push' it into defense mode in some cases almost on the spot)
2) It will on occasion switch over (Parking>Defense) by itself sometime between 1min 30seconds - 5 or 6 minutes

Now, however, the unit very rarely gives "Error 2" or "Warning: Sensor Check Failed" (when before it would almost always give errors).

It generally gives numerous false poliscan alerts IF it goes into defense mode. Though, as I stated before it almost always goes into defense mode


Is there any way to find what head is causing the "Error 2" and "Warning: Sensor check failed" notifications?

Here is my stats file:


495549564957

[AirMoore]

Here is the history:

You can see the sequence of events I described above (I-V) - Bottom of the first screenshot (Also, I just noticed... it never recorded the error for the November date, just October, which is odd considering there should be a huge list of "errors" between that October date, and the K band. So thats something else that's amiss).

As well as the most recent errors and Poliscan alerts - Top of the second screenshot


49594958

[radargeek]

That is odd that it's staying in park mode until a radar alert. Maybe some odd bug that crops up due to your faulty head? Try disconnecting one head at a time and see if the problem goes away. If it does when you unplug one head, the problem is probably that head.

Something else odd I noticed: in your statistics, your unit shows some of the overseas guns like Reigl, Laveg etc. as enabled. I don't see those when I go into ALP setup (North America), and my statistics show those as disabled.

Maybe you're running with an old setup file from a prior firmware version? Try generating a new one at http://www.alpriorityupdate.com/Setup and loading it.

[BestRadarDetectors]

You have a bad head or a bad sensor cable causing false alerts and interference. Disconnect one head at a time to see which one clears it and then try swapping the sensor to the wire from the opposite sensor to determine if its the sensor or the cable.

[AirMoore]

I thought that was odd too... as I don't remember anything besides stalker/poliscan being set for options.

As you can see in the first screenshot from my computer (top 2 lines):


The firmware is updated to 5.1.4 (my understanding is this is the newest)
And it is the "North American" database for region




I have completely reset the unit, updated it the latest and greatest firmware, uninstalled the old app, and reinstalled the newest app.

Really weird stuff going on with this unit.

Guess I'll try the old unplugging one head at a time and seeing if it fixes anything.

Do I need to force it to memorize the heads and reload the settings file every time? Or can I just unplug one at a time, have it yell at me, and then it should work anyways?



EDIT: Thank you both again.

Ok, I will try doing this when I get time, however, I do have to ask:

Can I just unplug say "Port 1" and leave "Port 2" in... let it yell at me that there isn't a sensor in 1, and run the unit with "Port 2" only?

Or do I have to take out head two, reset the unit the memorize a head in only port 1, reinstall the settings, then reboot and repeat for the second head?


PS: This is WAY UP on my wishlist for what we will see with the ALP in the feature...

Have it not only run self-diagnostics, but actually report back what they are... (e.g. - "Warning sensor check failed - port 2"). It would make life so much easier, and also a diagnostic on the radar antenna too (if that is possible) as my Sti-R+ went bad... a "service required" for the radar antenna would have been nice there.

Speaking of which... I wouldn't be surprised if it is a cable somewhere after having to check the wires countless times due to my Sti-R+ failing, I bet a sensor cable got chaffed in the process of running wires countless times. The issues only started happening after I kept having Sti-R+ issues IIRC, that would make perfect sense.

[BestRadarDetectors]

I thought that was odd too... as I don't remember anything besides stalker/poliscan being set for options.

As you can see in the first screenshot from my computer (top 2 lines):


The firmware is updated to 5.1.4 (my understanding is this is the newest)
And it is the "North American" database for region




I have completely reset the unit, updated it the latest and greatest firmware, uninstalled the old app, and reinstalled the newest app.

Really weird stuff going on with this unit.

Guess I'll try the old unplugging one head at a time and seeing if it fixes anything.

Do I need to force it to memorize the heads and reload the settings file every time? Or can I just unplug one at a time, have it yell at me, and then it should work anyways?

You might get a sensor error but that wont matter.. Set your LID settings to Unlimited when doing the test so that it will switch almost immediately into defense as soon as you correct the issue. If you do not have unlimited it will only go back into defense mode 60 seconds after the correction.

[AirMoore]

You might get a sensor error but that wont matter.. Set your LID settings to Unlimited when doing the test so that it will switch almost immediately into defense as soon as you correct the issue. If you do not have unlimited it will only go back into defense mode 60 seconds after the correction.

Sounds good, I'll upload new settings (unlimited jamming)... and unplug one head at a time and run each to report back what I find.

(Edit: I won't skip the first warm-up, I forgot that is when it runs the checks I needed)

Thanks again. I really think I'm going to end up narrowing it down to a cable; I must have gone through my wiring close to 5 times trying to troubleshoot the radar antenna issues, which (likely not coincidentally) is when all this started.

[AirMoore]

Well that narrowed it down pretty easily.

Unplugged "Head B" from "F2" and drove ~15 minutes.
No issues.
ALP fired up, instantly said "Warning: Sensor check failed" then went into "Defense Mode" 1:05 into it's bootup (including the 60 second boot time)
Worked flawlessly the entire ~15 minute ride

Turned everything off. Unplugged "Head A" from "F1" and plugged in "Head B" into "F2"
"Error 2" "Warning Sensor check failed"
Then it took ~1:40 to boot into "Defense Mode" and the second it did: "Error 2" - "Error 2" "K-Band" - "Error 2"
I got ~6 errors in 5 minutes of Driving


Stopped, and turned everything off

Unplugged "Head B" from "F2" and plugged "Head A" into "F2". (This was to make sure the "F2" port wasn't the issue)
Normal Start up sequence, and drove ~10minutes without a single issue.


Got back to my place, turned everything off and put "Head B" back into "F2"
Took 1:28(ish) to go into "Defense Mode" and 2 minutes later "Poliscan" alert.


So I now know it's either that head or that wire. Now I just need to find time to swap over the cable from "Head A" to "Head B" and try things. That might take some time


Thank you both for your input. Looks like I'll have to run with the 1-head for awhile until I have time to troubleshoot the exact cause.

[radargeek]

Nice troubleshooting. I had a feeling it was the faulty head causing it.

BTW, the self test runs regardless of whether you have the first warm-up disabled or not. The first warm-up just puts it in parking mode for 60 seconds so you can show a cop "hey it's parking sensors" by turning it on and letting them shoot/try it.

If you have the parking sensors/beeps enabled this is also a good way to test out heads,by seeing if they respond to obstacles as they should

But you're right, it would be nice if the ALP told you which head (on which port) was causing the error.

[BestRadarDetectors]

Nice troubleshooting. I had a feeling it was the faulty head causing it.

BTW, the self test runs regardless of whether you have the first warm-up disabled or not. The first warm-up just puts it in parking mode for 60 seconds so you can show a cop "hey it's parking sensors" by turning it on and letting them shoot/try it.

If you have the parking sensors/beeps enabled this is also a good way to test out heads,by seeing if they respond to obstacles as they should

But you're right, it would be nice if the ALP told you which head (on which port) was causing the error.

It does depending on the failure, Normally it will tell you which port has the error when the self check determines the problem. The issue here is the head is not ignoring the self check commands so it knows the head is attached and connected but its hanging up and causing the self check to stall causing it to stay in parking mode. The ALP unlike other systems will not start up and let you run it if there is an issue so if the self-check hangs or can not determine the error it will not put you into defense mode and give you a false sense of security. When the error is determined and we can get the bad head or cable back engineering will try to duplicate it and then add an additional routine to identity the failure if someone else in the future has the same problem.

[AirMoore]

It does depending on the failure, Normally it will tell you which port has the error when the self check determines the problem. The issue here is the head is not ignoring the self check commands so it knows the head is attached and connected but its hanging up and causing the self check to stall causing it to stay in parking mode. The ALP unlike other systems will not start up and let you run it if there is an issue so if the self-check hangs or can not determine the error it will not put you into defense mode and give you a false sense of security. When the error is determined and we can get the bad head or cable back engineering will try to duplicate it and then add an additional routine to identity the failure if someone else in the future has the same problem.

Sounds good, I can't really take my install apart right now, as I am not home (and likely won't be until the Holidays)... but I'll spot shoot the wiring v. head the moment I can.

Thanks for you help, and TBH, as I said before I am really leaning towards a wire causing the issue.

[RedRocket]

Thanks for you help, and TBH, as I said before I am really leaning towards a wire causing the issue.If you had Mechanics in the engine compartment doing work I'd be suspect of a cable or a connector being crushed/damaged, too.

[AirMoore]

If you had Mechanics in the engine compartment doing work I'd be suspect of a cable or a connector being crushed/damaged, too.

I guess I should clarify a bit more so people don't think the motor work is the cause of it.

The problem almost assuredly stems from me checking the wires when my Sti-R was dying on the ALP (and subsequent installation of the 9500ci on the ALP). I knew something was messed up (with the radar unit), so I checked and reran my wiring countless times to make sure nothing was wrong. This including moving and rerouting of the wiring for the heads as well on some occasions.

Around this time, I started getting numerous poliscan alerts and then the random "error 2" alerts... it was only then that my head gasket went.


Furthermore, due to the small size of my car (Honda Civic) I had enough wire run the heads inside the quarter panels, and down into the front bumper, so it would have been virtually impossible to incidentally mess up the wiring for the ALP no matter what one did in the engine compartment.

So I am almost assured now that by pulling the wires through or messing with the re-wiring of the heads, I may have chafed or pinched something during the process of trying to fix my Sti-R+ issues.


At any rate, I'm just happy I was able to narrow the issue down with the help of BRD&rg. I don't mind running one head for awhile, as long as I can get the 9500CI use out of it, and I'll just run as if I have no laser protection (even though one head should provide some). Point is, the unit works flawlessly at least as a 9500CI right now, except better than a 9500ci because the ALP gives the option of K-band segmenting (which I love... though it's not for everyone).