900mhz
Member
- Joined
- May 13, 2005
- Messages
- 432
ouch is right. Meaningless comment. I allowed my wife to read this. She came out with an old Yiddish comment. I reserve comment.Ouch!
ouch is right. Meaningless comment. I allowed my wife to read this. She came out with an old Yiddish comment. I reserve comment.Ouch!
perhaps, but responses are inconsistent from the manufacturer. Users can provide better guidance. Manufacturer responses benefit all users.
Sigh... I did try to word my question in such a way that this thread would not become contentious. It is unreasonable to think that Uniden does not have a representative monitoring the Uniden tech support thread. Tell me that's not true.Ouch!
@trentbob Never to worry. Exactly my wife's sentiment. She is not a radio person, but she was curious about the thread.. Old Yiddish responses came out. My understanding is that repeating her responses would not be family friendly. That is why I married her. Old school. Honest commentary. Long live Walter Cronkite..Sigh... I did try to word my question in such a way that this thread would not become contentious. It is unreasonable to think that Uniden does not have a representative monitoring the Uniden tech support thread. Tell me that's not true. Why bother to have the thread.
This is a reasonable question, I'm sure there are many members that are also curious, why don't we give Uniden a chance to respond in case they don't monitor it daily.
Sigh... I did try to word my question in such a way that this thread would not become contentious. It is unreasonable to think that Uniden does not have a representative monitoring the Uniden tech support thread. Tell me that's not true.
This is a reasonable question, I'm sure there are many members that are also curious, why don't we give Uniden a chance to respond in case they don't monitor it daily.
Yeppers, you know I am very knowledgeable of the overall situation for many years, including the present situation.You know my view of this.... "Air Spy/Voyager" Joe will pop on when the conditions are favorable. Good question though, deserves a response.
Yep, it's always been understood you only update the 436, 536, 100, 200 from the latest version of Sentinel. This is off topic for my question in this thread but you are correct.This warning looks like a typical CYA (no insult intended) warning seen for any update process.
ONLY use Sentinel to upgrade firmware. Some users have rendered their scanners non-functional using other update methods.
It is basically saying that the update process that Sentinel uses has been tested with the update and has no known errors. Other methods if they exist may not have the same read/write/handshake that Sentinel uses. If they differ this could result in bad data being written/overwritten or deleted causing the scanner to brick.
I think it means that Sentinel retrieves the firmware from the 'official' Uniden server that's password protected and anything else will use another source where there's no guarantee. But on the other hand, the firmware is encrypted and therefore can't be hacked so I think other sites will have the real deal too.This warning looks like a typical CYA (no insult intended) warning seen for any update process.
ONLY use Sentinel to upgrade firmware. Some users have rendered their scanners non-functional using other update methods.
It is basically saying that the update process that Sentinel uses has been tested with the update and has no known errors. Other methods if they exist may not have the same read/write/handshake that Sentinel uses. If they differ this could result in bad data being written/overwritten or deleted causing the scanner to brick.
The Sentinel FTP process is known to timeout with a certain satellite internet provider.Sentinel uses has been tested with the update and has no known errors.
Yep, the FTP server password is easily obtainable (more than one way).I always thought it was amazing they used FTP. No security there at all.
Not only that, there's no verification the site you're connecting to is actually Uniden's. Someone could poison DNS and have you go elsewhere and you'd never know it. At least with TLS, you get site verification and someone has to do a lot more work to trick you there.Yep, the FTP server password is easily obtainable (more than one way).
Uhhh I'm pretty sure they're not hosting a highly coveted "Uniden Depot" on there lol...Yep, the FTP server password is easily obtainable (more than one way).
This warning looks like a typical CYA (no insult intended) warning seen for any update process.
ONLY use Sentinel to upgrade firmware. Some users have rendered their scanners non-functional using other update methods.
It is basically saying that the update process that Sentinel uses has been tested with the update and has no known errors. Other methods if they exist may not have the same read/write/handshake that Sentinel uses. If they differ this could result in bad data being written/overwritten or deleted causing the scanner to brick.
Try and get the serial numbers where it starts to use new hardware and details of what the hardware (circuit name) was changed to. If anything in the receiver chain have been altered it would be interesting to test that scanner and see if it changed the performance in any way.Some hardware changes: New receiver chips, new LCD drivers, and new displays.
Anything else I can answer about that version?
Try and get the serial numbers where it starts to use new hardware and details of what the hardware (circuit name) was changed to. If anything in the receiver chain have been altered it would be interesting to test that scanner and see if it changed the performance in any way.
The old release note for the 436 says:
" Note that LCN finder on DMR system using RAS will not be 100% reliable, since there is no error detection on RAS systems. You might need to run several times, noting the results each time, then selecting the LCN based on all results."
As Unidens scanners immediately skips conversations that are encrypted and never test for it several times, it might backfire in RAS systems that are not encrypted. Giving a user the selection of forcing a system or TG to ignore the encryption flag and be forced to monitor the conversation would probably help in a lot of situations, even to those who prefere to monitor and study encrypted calls.
/Ubbe
As I read Unidens statement it says that any data received in systems that are detected (falsely or true) as RAS will have errors in the data received (error correction are turned off) that will make the LCN finder unpredictable. But that's just one of the functions that will be compromised. The encryption detection are so much more sensitiv and will have a bigger impact on reception if it's not 100% reliable.With respect to RAS systems, I'm not sure I understand the "might backfire in RAS systems that are not encrypted" part.
The best solution as I see it would be to have RAS and encryption user selectable in a similar way as NAC, to set them to Search (as it works now) or forced to On or Ignore/Off.