I'm afraid to jinx myself, but my 436 has been going for several hours with no issues either...the 536 lasted about an hour or so.
- Status
I'm afraid to jinx myself, but my 436 has been going for several hours with no issues either...the 536 lasted about an hour or so.
I can remember going to RS hoping they had Xtals for my VHF 4 channel Pro handheld scanner in stock. No free firmware upgrades no instant answers for questions on the internet....I guess were spoiled...Thanks UPman this stuff is amazing
Gee... Another rush to put out the product before fully vetting ?? Odd.. Where have we seen that before ?.
I have all upgrades. DMR/ProVoice/NXDN. The only problem I saw was the squelch issue. I didn't get a chance to further explore anything else at the moment.
I've since reverted back to the older version. Looking forward though to a final update.
I've since reverted back to the older version. Looking forward though to a final update.
Did you just try this? The version now serving is 1.14.00 (but because of the way I had to do this, it is going to always download and install an update if you pull another f/w update, but it will still be 1.14.00...this will change when I get a fixed production version).
cellphone
Silent key.
I’m also trying to narrow down variables that might cause the open squelch issue. My radio that is exhibiting the open squelch issue is a 436 with ProVoice, DMR, and NXDN installed.
They really do have good donuts. I used to live in Farwell and work in Mt. Pleasant.
I swore I read a fairly recent post from UPMan that he had pulled the update and sent it back to engineering so they could take a look.
I decided to try an update check on a 536 and a 436, both downloaded version 1.15.01.
Is this just a higher version that is really the same as 1.14.00 or is it a fixed version of 1.15.00?
I've not seen anyone mention a 1.15.01 version but that is what all mine just installed.
Have not done any testing yet.
I decided to try an update check on a 536 and a 436, both downloaded version 1.15.01.
Is this just a higher version that is really the same as 1.14.00 or is it a fixed version of 1.15.00?
I've not seen anyone mention a 1.15.01 version but that is what all mine just installed.
Have not done any testing yet.
In order to re-serve 1.14.00 so that it would replace 1.15.00, I had to change the file name. The version itself is really 1.14.00.
Thanks Paul, I was just going to post that 1.15.01 does pass a file compare against version 1.14.00.
I kind of figured you had to put up a higher version.
Thanks Again
Yeah, but did you buy any “We’ve Got Your 6” shirts?! [emoji601][emoji61]*[emoji1516]*[emoji600]
Sent from my iPhone using Tapatalk
krazybob
Member
I am just curious why people seem so interested in NXDN when it is a business standard in the digital world. There's nothing wrong with it or the users. I'm just surprised so many users like to listen to other than public safety or aviation. I caught something on cable TV about some Backwoods Sheriff Department and they were running for repeater site DMR system so I guess it could happen. I'm just curious. Don't mind me.
Sent from my SM-N920V using Tapatalk
Which explains why my 436 still works. I thought I got it before you pulled 1.15.00, but I see it's 1.15.01.
Just something else in addition to Public Safety to listen to. Many of us (including myself) have more than one scanner running. I have police and fire as my primary and a scanner for Miscellaneous listening (File name ironically is 536 Misc). I don't miss much this way and can also listen to the businesses that work with the police department (Tow truck companies, airlines, private ambulance companies) in some capacity. Plus it keeps you fresh on how to program new types of systems so you're ready for the next adventure.
In the DFW Metro area, there are two NXDN systems used for public safety. One system for Lancaster, TX, and another, SWRCC, that includes three suburbs (Cedar Hill, Desoto, and Duncanville).
While there are a number of business systems and users, some of the school districts are also shifting to NXDN. And, eventually, railroads will transition to the NXDN format. That is likely several years off, but will eventually happen according to current plans.
DMR is more common, and it's use among public agencies, including public safety, is spreading in some areas.
Reverted 2 of my 3 scanners back to 1.14.00. I'm living on the edge...keeping 1 of my 536's on the 1.15.00. So far no squelch issues, MotoTRBO and One Channel DMR functioning as 1.14.00. P25...no changes either. NXDN aliases and all other NXDN 4800 trunking functioning as before. Still seeing occasional false NXDN talk groups as version 1.14.00. Still seeing issue with P25 Phase 2 radio ID's which wasn't addressed per the release notes.
The 436 issues were as described by others...
So you can manually change firmware just by taking the .bin file and manually placing it on the scanner's SD card? Because Sentinel doesn't ask you for a path to the appropriate .bin file when you update the firmware. Is there a source for past firmware .bin files?
Both of my 536s have been running since I did the update this morning without issues. It must be related to some kind of transmission that I haven't received yet (my scan list is pretty narrow). 436 behaved over the lunch hour in the truck, and I left it turned on when I parked; will go out later and see if it is still OK.
Speaking of "Aliases" is it possible to have that feature on the other types of systems as well? DMR etc..
Or is this simply just an NXDN feature?
Or is this simply just an NXDN feature?
NXDN is the only one (out of the systems scanners can decode) that pushes aliases over the air as far as I know.
- Status
