northzone: What he said. Please capture a log for us...we will be able to study the control channel information to see what might be going on in your situation. Hold on the system (no need to stop on a channel).
HP-1: HomePatrol-1 2.06.xx Open Beta
- Thread starter UPMan
- Start date
- Status
Well, just got a new version just for northzone. Please try:
http://info.uniden.com/twiki/pub/Partnerweb/HomePatrolBeta/HomePatrol-1_V2_06_06.zip
http://info.uniden.com/twiki/pub/Partnerweb/HomePatrolBeta/HomePatrol-1_V2_06_06.zip
Nothing to log if the radio stops receiving completely (no signal as shown by signal strength meter)
Great, I will give it a try later this afternoon. Thanks
JamesO
Member
I am totally confused by what NorthZone is running into. Scanner quits receiving after 15 minutes?
Is NorthZone ONLY monitoring a single System?
I have version 2.06.04 running since late yesterday, had the scanner sitting next to me running most of the morning and I have not had any issues with the scanner not receiving traffic.
I am currently in the core of the house just the 800 MHz Radio Shack antenna and it is doing quite well with any system it can reliably receive.
If I find a sweet spot in the house I can pick up the DCFD Project 16 fine as well.
More details for this 15 minute radio going stupid seem to be needed as I am not seeing anything like this.
Is NorthZone ONLY monitoring a single System?
I have version 2.06.04 running since late yesterday, had the scanner sitting next to me running most of the morning and I have not had any issues with the scanner not receiving traffic.
I am currently in the core of the house just the 800 MHz Radio Shack antenna and it is doing quite well with any system it can reliably receive.
If I find a sweet spot in the house I can pick up the DCFD Project 16 fine as well.
More details for this 15 minute radio going stupid seem to be needed as I am not seeing anything like this.
Whoa. NoFear2005, you can't just post that picture without telling us what's up. Did you put 2.06.06 in and that was the result? Or did it just happen on its own?
jasonhouk
Member
Thats a first...
I had the same issue last night right after updating to 2.06.04.
Took out batteries then unseated and reseated the SD card and unit powered on normally.
Attachments
I decided to give it a go and did the update to 2.06.06, got the same error. Like you said, pulling the batteries, reseating the card, and trying again seemed to work.
Now to get this thing logging data...
Now to get this thing logging data...
Go back and read the thread, all the details are there.
UPMan,
Downloaded and installed version 2.06.06 . Same issue. I will try to get a log file and post.
Northzone
JamesO
Member
A bit hard to follow everything split up over multiple posts, but correctly me if I am wrong here, you are monitoring only 1 site on 1 system and this happens to be a 700 MHz portion of the system based on the 1 site? Correct?
I am monitoring about 10 different sites and have had no issue with the receiver going dead with any of the Beta release versions, however, I missed the fact that version 2.06.03 was released so I did not get a chance to try that version.
I believe that of the current sites I am monitoring, none are 700 MHz systems.
So for now I will assume that the 700 MHz may be the issue with something getting confused with the control channel?
It just strikes me as very strange you seem to be one of the few that is having this issue that after 10-15 minutes the radio seems to loose the control channel.
Does powering the scanner off and back on resolve the loss of Control Channel? Or changing sites back and forth?
Again, really strange that your unit seems to go "stupid".
Maybe you are working behind the scenes providing Uniden more info, but you have not post much detail on what is going on in your specific situation.
jasonhouk
Member
May be a function turned off for the beta FW, just like the squelch has no bearing on my analog channels.
J
J
JamesO
Member
Running Beta 2.06.06. Overall sound quality and decoding is about as good as I think I have heard so far.
The random squelch breaking/non decoding issue that I had in version 2.06.03 appears to have gone away.
However, in this current Beta Version I seem to be getting random System hangs where the scanner is behaving like you have chosen to hold on a system. The first time it happened when I was driving so I could not really focus on what was happening.
The next time I waited and watched for traffic to drop and expected the unit to continue to scan but it did not resume scanning as expected.
I finally hit the lower TG to Lock it, then immediately hit the TG again to Unlock it and the scanner immediately resumed scanning off the System the scanner was hung on.
I will hopefully have some more time this week to try and again verify what is going on and see if this issue is with specific systems or is randomly happening.
Not sure if anyone else has run into this same behavior yet?
The random squelch breaking/non decoding issue that I had in version 2.06.03 appears to have gone away.
However, in this current Beta Version I seem to be getting random System hangs where the scanner is behaving like you have chosen to hold on a system. The first time it happened when I was driving so I could not really focus on what was happening.
The next time I waited and watched for traffic to drop and expected the unit to continue to scan but it did not resume scanning as expected.
I finally hit the lower TG to Lock it, then immediately hit the TG again to Unlock it and the scanner immediately resumed scanning off the System the scanner was hung on.
I will hopefully have some more time this week to try and again verify what is going on and see if this issue is with specific systems or is randomly happening.
Not sure if anyone else has run into this same behavior yet?
JamesO
Member
Update Beta 2.06.06
So today a different issue popped up.
I was unable to see the scanner hang on a System, however, I did have a situation where 2 times the scanner lost audio. Note this was not a speaker/amp/headphone jack issue as the touch screen tone worked when I moved around menus, TG would show up with no audio.
The only way I was able to get the audio back was to shut down the scanner and restart it.
Cannot say for sure if there was a timed component to when the audio dropped out, could have been in the 10-15 minute range? I was able to see TG info come up on the display without any audio so I knew something was up.
I was able to capture 2 logs with no audio. Linked 3 logs and I am not 100% sure which of the 2 were without audio, however, I believe they were the later 2 log files.
https://www.dropbox.com/s/an6youv54rlmelh/log0032659.txt
https://www.dropbox.com/s/qwskfwelnb8fxr3/log0423285.txt
https://www.dropbox.com/s/20avrf82930zjmr/log3243355.txt
So today a different issue popped up.
I was unable to see the scanner hang on a System, however, I did have a situation where 2 times the scanner lost audio. Note this was not a speaker/amp/headphone jack issue as the touch screen tone worked when I moved around menus, TG would show up with no audio.
The only way I was able to get the audio back was to shut down the scanner and restart it.
Cannot say for sure if there was a timed component to when the audio dropped out, could have been in the 10-15 minute range? I was able to see TG info come up on the display without any audio so I knew something was up.
I was able to capture 2 logs with no audio. Linked 3 logs and I am not 100% sure which of the 2 were without audio, however, I believe they were the later 2 log files.
https://www.dropbox.com/s/an6youv54rlmelh/log0032659.txt
https://www.dropbox.com/s/qwskfwelnb8fxr3/log0423285.txt
https://www.dropbox.com/s/20avrf82930zjmr/log3243355.txt
JamesO
Member
One more possible clue to at least the no audio issue that I ran into yesterday may be the audio Mute control.
Uniden will know for sure, but I am pretty sure these scanners have both a Squelch control and an Audio Mute.
I also was experimenting with a small portable amplified speaker today and it is very sensitive to the Audio Mute control in the scanner and you can hear a faint switching or snapping when the Audio Mute is triggered on and off.
What I saw yesterday was the scanner would stop on TG's and there was plenty of signal, just no audio from the speaker, then I would see the TG drop and the scanner would resume scanning. So I fully expect the Squelch may have opened, but the Audio Mute did not?
So while listening today, I was able to hear the Audio Mute triggering on and off and often times very rapidly if the signals were borderline or I was driving and in motion.
So there may be a timing/hysteresis issue with the Audio Mute circuitry and/or somehow the Audio Mute was stuck in an invalid Logic State.
I was unable to get the scanner to loose Audio today and as I mentioned previously this was not an issue due to a headphone jack issue as the touch screen beeps were all working and as loud as they would usually be while I was holding on a TG and/or going to play with the Squelch and also enabling the Logging function. It was not until the scanner was power cycled did the audio come back, so this clearly tells me there was an invalid Logic State for the Mute control at some point and it was only cleared once the scanner was power cycled.
Uniden will know for sure, but I am pretty sure these scanners have both a Squelch control and an Audio Mute.
I also was experimenting with a small portable amplified speaker today and it is very sensitive to the Audio Mute control in the scanner and you can hear a faint switching or snapping when the Audio Mute is triggered on and off.
What I saw yesterday was the scanner would stop on TG's and there was plenty of signal, just no audio from the speaker, then I would see the TG drop and the scanner would resume scanning. So I fully expect the Squelch may have opened, but the Audio Mute did not?
So while listening today, I was able to hear the Audio Mute triggering on and off and often times very rapidly if the signals were borderline or I was driving and in motion.
So there may be a timing/hysteresis issue with the Audio Mute circuitry and/or somehow the Audio Mute was stuck in an invalid Logic State.
I was unable to get the scanner to loose Audio today and as I mentioned previously this was not an issue due to a headphone jack issue as the touch screen beeps were all working and as loud as they would usually be while I was holding on a TG and/or going to play with the Squelch and also enabling the Logging function. It was not until the scanner was power cycled did the audio come back, so this clearly tells me there was an invalid Logic State for the Mute control at some point and it was only cleared once the scanner was power cycled.
JamesO
Member
Today's Update.
I decided to roll back to Version 2.06.03 for a while due to the loss of audio on the HP1 with Version 2.06.06.
The I realized how crappy a decoding job the 2.06.03 was doing a few systems I "thought" were just problem systems based on how my x96XT's decoded these system. I kind of gave up trying to listen to these systems in the past, but the new Beta firmware for the HP1 clearly shows that Uniden may be onto something.
Well what I found is overall the 2.06.06 is probably the best sounding decoding so far on my HP1 that I can tell. There may be some other funny things going on, but comparing to some of my other radios on other systems, the biggest issue is the audio dropping out that I have found.
So since I again moved back to Version 2.06.06 and late this evening I have had the audio drop out 2 more times until I restarted the scanner.
This is clearly an Audio Mute issue from what I can tell as the scanner is stopping and waiting on TG's that I am monitoring on another scanner. So it is not a traffic or trunking problem, it is a basic Audio Mute problem what I can see. Should be a rather easy fix?
Would be interesting to hear from others if they are running into the loss of audio on this or other versions of the Beta software.
I certainly hope that Uniden can learn from this exercise and that the decoding firmware is somewhat portable to the x96T/x96XT and the x36HP platforms. It would be great to see some of these decoding improvements passed around to the cousins while they are in dealing with other issues.
I decided to roll back to Version 2.06.03 for a while due to the loss of audio on the HP1 with Version 2.06.06.
The I realized how crappy a decoding job the 2.06.03 was doing a few systems I "thought" were just problem systems based on how my x96XT's decoded these system. I kind of gave up trying to listen to these systems in the past, but the new Beta firmware for the HP1 clearly shows that Uniden may be onto something.
Well what I found is overall the 2.06.06 is probably the best sounding decoding so far on my HP1 that I can tell. There may be some other funny things going on, but comparing to some of my other radios on other systems, the biggest issue is the audio dropping out that I have found.
So since I again moved back to Version 2.06.06 and late this evening I have had the audio drop out 2 more times until I restarted the scanner.
This is clearly an Audio Mute issue from what I can tell as the scanner is stopping and waiting on TG's that I am monitoring on another scanner. So it is not a traffic or trunking problem, it is a basic Audio Mute problem what I can see. Should be a rather easy fix?
Would be interesting to hear from others if they are running into the loss of audio on this or other versions of the Beta software.
I certainly hope that Uniden can learn from this exercise and that the decoding firmware is somewhat portable to the x96T/x96XT and the x36HP platforms. It would be great to see some of these decoding improvements passed around to the cousins while they are in dealing with other issues.
We have a new version specifically to address the issue JamesO is pointing out. But, I'm in Taos with no good connectivity so cannot upload the files. That said, our engineer in Irving will be putting the file to a publically accessible area and I've asked one of the moderators to let you know when it is ready. Great, beautiful, old (opened as hotel in 1934) hotel in Taos, so not giving them too much of a hard time on the Wi-Fi front.
- Status
