Has anyone experienced a problem with the volume control on the 396? When I push it in, the display goes back & forth between where I had it at and 3. Any solutions or suggestions? Thank you.
Mike
Mike
396 Volume control
- Thread starter radiowaves1
- Start date
- Status
Fixed...reverted firmware!!
Something IS "buggy" with the new firmware. I just reverted back to the old one and the volume issue is gone, then I loaded the new firmware and the volume probelm is back. I'll give it a day or six before I make my mind up totally that the new firmware is the problem but right now its looking like it.
Something IS "buggy" with the new firmware. I just reverted back to the old one and the volume issue is gone, then I loaded the new firmware and the volume probelm is back. I'll give it a day or six before I make my mind up totally that the new firmware is the problem but right now its looking like it.
cws
Member
Instead of just reinstalling the new version, you might try re-downloading first. Sometimes you can get bit errors on a download. I haven't noticed any problems with my new version.
actually, zip files have checksums, so if the download failed, the checksum would fail.
I believe the flash update protocol also includes a checksum, but don't know that for sure. In any event, if you think you have a bad firmware load...the easiest way to fix that is to check the communications parameters for the serial port and the radio are the same.
I'm not sure I understand your problem description: "the display goes back & forth between where I had it and 3." What about the display is going back and forth? What is "3" (Display mode 3?)
Good advice from all....
Thanks for all of the advice however, there is still an issue with this.
I did re-download the original zip file, unzipped of course and re-installed it. Problem is still there. Then I cleared the scanner and re-installed old version and the volume control issue is not there. So, I went back to the new version and downloaded it then re-installed it using my IBM laptop and re-installed it to the 396 thinking there possibly could be an issue "somewhere" by using my desktop (heck, you never know) and the problem is still present.
*The problem: I had the volume on "5". When using the volume control and trying to either turn the volume up or down, the volume display setting will only go between "5" and "3" or "7" or, in other words only two settings up or down from five and this is shown on the 396's display.
I have been here all day...literally...looking at data from the 3.01.00 download trying to figure this issue out including serial port settings and baud rates. There are no protocol issues with flashing the memory of the 396 as the perimeters are the same (as far as the info I'm looking at) for both the new & old firmware. BUT something is off here and I had 4 PM's from other users who stated they also experienced the same problem. I asked them to post publically but haven't seen any of them as of yet.
Still looking at this. So far, when I re-install the old firmware the problem is no longer there. So.........
Thanks for all of the advice however, there is still an issue with this.
I did re-download the original zip file, unzipped of course and re-installed it. Problem is still there. Then I cleared the scanner and re-installed old version and the volume control issue is not there. So, I went back to the new version and downloaded it then re-installed it using my IBM laptop and re-installed it to the 396 thinking there possibly could be an issue "somewhere" by using my desktop (heck, you never know) and the problem is still present.
*The problem: I had the volume on "5". When using the volume control and trying to either turn the volume up or down, the volume display setting will only go between "5" and "3" or "7" or, in other words only two settings up or down from five and this is shown on the 396's display.
I have been here all day...literally...looking at data from the 3.01.00 download trying to figure this issue out including serial port settings and baud rates. There are no protocol issues with flashing the memory of the 396 as the perimeters are the same (as far as the info I'm looking at) for both the new & old firmware. BUT something is off here and I had 4 PM's from other users who stated they also experienced the same problem. I asked them to post publically but haven't seen any of them as of yet.
Still looking at this. So far, when I re-install the old firmware the problem is no longer there. So.........
ATCTech
Active Member
- Joined
- Aug 13, 2002
- Messages
- 1,857
- Reaction score
- 770
Is this happening with the radio completely disconnected from the PC interface? Just curious if you have software perhaps simultaneously trying to control the radio as you change it directly. I'm using V3.0.1 and ARC396 release 6 and don't see that problem at all, even with it all running at once.
I tried it both ways, disconnected as well as connected just in case there were any conflicts and it was still present. I may just need to send this 396 to Uniden as I'm pretty much out of possible solutions to fix this other than just running the older firmware which still allows me to hear what I listen to here. I of course, like other radio-minded types would prefer to have the latest updates/upgrades on my gear.
Mike
cws
Member
Four PMs reported the same issue? Did any of those four say that they resolved it? If not, what were they planning to do about it?
Did you notice anything you had in common with them - like all of you having d/l and installed in the past few days? Or, all of you had the volume set at 5?
I hadn't moved my volume more than a couple of steps, since I installed the new version, so I just now checked my 396, and it goes from 0 to 15. No problem. It's a real long-shot, but have you tried installing with volume set to 9, for example. And, if so, does it only move from 7 to 11, then?
Did you notice anything you had in common with them - like all of you having d/l and installed in the past few days? Or, all of you had the volume set at 5?
I hadn't moved my volume more than a couple of steps, since I installed the new version, so I just now checked my 396, and it goes from 0 to 15. No problem. It's a real long-shot, but have you tried installing with volume set to 9, for example. And, if so, does it only move from 7 to 11, then?
All the same issue and only one stated he had installed the firmware uppdate within the last week (7 days) I just mailed by 396 on my way home from work this morning to Uniden as this has to be resolved by them, either from a mechanical or software point they have to fix it. If it turns out to be an actual part then I'll gladly pay for it. Otherwise if its firmware then Uniden can fix it. Rather than me spending hours looking at data bits they will have the equipment to "read" whats there and find anything that isn't suppposed to be. Either, I will update here when I get it back.
THANK YOU to all of you who took the time to offer help. RR has the best forum members anywhere and I'm honored to be here.
Mike
Ah, I was going to suggest that you post your programming so I could test on a sample unit before you took any other steps.
If the firmware goes in without error, there is no (0) possibility that the update is corrupt (checksums prevent such a thing). There might be some odd (or at least rare) combination of settings that is causing what you are seeing.
Since this is the first public post of this, it certainly hasn't been examined in any way shape or form. If 5 people are having the same symptoms (that disappear when you go to a different firmware load) then the chances of it being a hardware fault are pretty slim (but not impossible).
If the firmware goes in without error, there is no (0) possibility that the update is corrupt (checksums prevent such a thing). There might be some odd (or at least rare) combination of settings that is causing what you are seeing.
Since this is the first public post of this, it certainly hasn't been examined in any way shape or form. If 5 people are having the same symptoms (that disappear when you go to a different firmware load) then the chances of it being a hardware fault are pretty slim (but not impossible).
- Status
