BCDx36HP Firmware 1.15.00 Available

[KevinC]

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.

Are you 1.15.00 or 1.15.01?

 

[iMONITOR]

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

As log as they have a 'Fast Food Drive Through' mode! :roll:

 

[IdleMonitor]

Ok, good to know. Thanks.

NXDN is the only one (out of the systems scanners can decode) that pushes aliases over the air as far as I know.

 

[garys]

It's a NXDN feature, actually it's an option. An Alias doesn't have to be programmed into the radios, but if it is, that is transmitted over the air. It's very handy when trying to track down a system using DSD+. It will be convenient with the scanners as well, I think.

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?

Some systems want digital, but can't afford P25. Or can't get grants to buy P25. NXDN and DMR are less expensive ways to do that. With DMR, a system can opt to use one time slot for voice and one for data. I've seen some non public safety systems that are running conventional DMR with Slot 1 used for AVL and messaging, while Slot 2 is used for voice.

Additionally, some private ambulance services and private security companies like DMR or NXDN because they can have some degree of voice privacy (if they want it).

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

 

[Jay911]

Are you 1.15.00 or 1.15.01?

I'm on 1.15.00.

 

[KevinC]

I didn't know there was an .01. I'll put it on one radio now.

1.15.01 is actually 1.14.00. Confused now?

The original non-working 1.15.00 is pulled, 1.14.00 was renamed 1.15.01 and that is what Sentinel gives you now.

I thought maybe you got 1.15.01 and that's why you're still working.

 

[03msc]

People don't read...or don't pay attention to what they read. KevinC is right but he shouldn't have had to clarify since it's been said more than once already...

 

[Jay911]

1.15.01 is actually 1.14.00. Confused now?

The original non-working 1.15.00 is pulled, 1.14.00 was renamed 1.15.01 and that is what Sentinel gives you now.

I thought maybe you got 1.15.01 and that's why you're still working.

Missed that in the thread until you mentioned it. I am on 1.15.00 as delivered this morning by Paul in the thread (as opposed to the automatic update).

 

[KevinC]

I'm on 1.15.00.

Ok, it hosed my 536 as far as squelch goes.

 

[JamesO]

Future note/reminder, no Firmware Friday's!

Release firmware earlier in the week, then maybe things can get sorted for the final Firmware Friday update.

 

[cellphone]

The open squelch issue has also occurred for me on a UHF freq that was set for NFM, Audio Type Analog, CTCSS/DCS Search. My squelch is set to 2. Again, going in and out of replay mode returned it to normal.

 

[CQ]

Was Begining to Wonder

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.

I noticed the file name difference as well but the upgrade showed 1.14.00.

Passing the hash for those on 420.

Both 436/536 suffered from squelch issues as well and have DMR/NXDN.

 

[CQ]

In Soviet Russia...

...In fact, that goes for automobiles and even firearms as well. Sig has had to pull to recently released hand guns from production to fix issues that became apparent only after they put the guns into production.

:lol:

Yea, the last time I tried to upgrade my SKS with firmware, things went horribly wrong.

 

[chill30240]

What's going on with the firmware update? I did the update and instead of showing 1.15.01 which I know is really 1.14.00 my 436 still shows 1.14.00. I did it several times and instead of Sentinel telling me that I have the latest version it keeps downloading to the scanner as if it were updating. I disconnect the scanner from the computer just like I always do and it says its updating the firmware. Is it supposed to show 1.15.01 or 1.14.00? I'm confused.

 

[jonwienke]

Its a temporary glitch due to the firmware number not matching the filename. If you have 1.14.00 don't try to update until the real 1.15.xx is released.

 

[chill30240]

Oh ok thanks.

 

[SCPD]

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

There are tons using dmr, nxdn due to costs or those who don't go for the grants for obvious reasons in government municipalities. Many having better systems then some analog and p25 I have heard. It is all in how the system is designed and studied prior to a deployment.

 

[iMONITOR]

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.

You're not alone. There's not much to listen to on DMR, NXDN, and especially Provoice where I live.

 

[Jay911]

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

You're not alone. There's not much to listen to on DMR, NXDN, and especially Provoice where I live.

And believe it or not,

(a) In other places in the world, there are agencies using NXDN like the 3 fire departments near me;

(2) Not everybody shares your likes and dislikes. It should not be a surprise by now that somebody else might be interested in something you're not.

 

[garys]

Obviously this conversation is above your level of understanding. Look at what happened to the Remington R51. Or look at some of the issues Tesla has had with their battery management software.

:lol:

Yea, the last time I tried to upgrade my SKS with firmware, things went horribly wrong.