NXDN Upgrade for BCD436HP and BCD536HP Now Available!

[sfb88]

Let's see if I remember algebra.

Freq = Base + ((Channel - 1) * Step Size)
Freq - Base = (Channel - 1) * Step Size
(Freq - Base) / Step Size = Channel - 1
((Freq - Base) / Step Size ) + 1 = Channel

Sorry, don't know enough about either Excel or radio to help further.

 

[u2brent]

Except a Custom Channel Plan can never be calculated.

https://forums.radioreference.com/v...derstanding-nexedge-trunking.html#post2249645

 

[kh6sz]

Let's see if I remember algebra.

Freq = Base + ((Channel - 1) * Step Size)
Freq - Base = (Channel - 1) * Step Size
(Freq - Base) / Step Size = Channel - 1
((Freq - Base) / Step Size ) + 1 = Channel

Sorry, don't know enough about either Excel or radio to help further.

Wow! That was fast. It looks like it just might work! I will try and add it to my program tomorrow and check the results. That should be easy to code in excel, except that the base and step size will also be a formula, but it should work. Thanks so much and I'll add it and then upload it here to see if anyone has any comments or suggestions on it.

 

[WX4JCW]

I'm in the process of writing another NXDN calculator in Excel that will hopefully be customizable depending on the date that you enter into it. I took WX4JCW's info on his sheet,as well as the other information I've found here. The problems that I kept coming up with is that nothing seems to follow the standard settings. So in my program, you enter 2 known channel numbers and their frequencies, and it will give you the Step Size as well as the Base Frequency, and then entering a NXDN channel number will display the frequency for that channel, even displays 10 lower and 10 higher than the entered channel.

I would also like to have where you can enter a frequency, and given the base, step size, and frequency, I would like it to find the Channel number.

I know the formula to find the Frequency is this:

Freq = Base + ((Channel - 1) * Step Size)

I'm hoping someone that is good in algabra can come up with a formula from the above that will let you have the Freq, Base, and Step Size and display Channel. Any takers!?!?!?!

Edit: Also if you do come up with the formula, maybe you know enough about excel to send me the formula that will work in excel!

This is outstanding thank you


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
Unication G4, BCD536HP

 

[RichardKramer]

BCD 436 encryption issues

Upman; any progress on the elimination of recording encrypted comms on the current firmware update; as the last version only recorded the clear comms on the Fed freqs?

 

[kh6sz]

NXDN System Calculator V1

Here is my program in progress in ZIP form. Any comments or suggestions (both good and bad) are welcome. Please note that it might or might not work correctly on your data and use it only as a guide to verify your data. It works fairly well on several systems here locally, but on others it doesn't. The coding for the program might not be perfect, but seems to do the job, I'm far from an expert in Excel.

 

[troymail]

Here is my program in progress in ZIP form. Any comments or suggestions (both good and bad) are welcome. Please note that it might or might not work correctly on your data and use it only as a guide to verify your data. It works fairly well on several systems here locally, but on others it doesn't. The coding for the program might not be perfect, but seems to do the job, I'm far from an expert in Excel.

It seems to work in the 450Mhz or 460Mhz range but if the system has a combination of 450Mhz and 460Mhz frequencies, it must be done in multiple calculations with a known pair from the respective ranges.

 

[Ubbe]

It works equally well for DMR dt3 channels. I had done a similar excel sheet but not as nice looking.

/Ubbe

 

[WX4JCW]

Thanks for doing that


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
Unication G4, BCD536HP

 

[dkljunk]

I am soooooo lost with all this. Just thought all I needed was to upgrade and update sentinel when it's available....

 

[mtindor]

The talk about formulas to determine LCNs really should be in another thread. It's going to get lost here.

More importantly [and not discounting anyone using the formulas -- I do], please don't just start using the calculations willy-nilly making assumptions that a particular standard bandplan is in use -- and then submit it to the DB. Admins aren't going to really be able to verify your data in many cases and you must may totally pollute the database with incorrect information by using the wrong formulas / calculations.

There are particular times when those formulas work and when they don't, and it always requires that you know something about some existing LCN<-->frequency pairings on the system beforehand so that you can make sure the formulas you are using apply to those particular systems / sites.

I can really anticipate a lot of bad data getting submitted to the DB by unwitting people who just know a single LCN or single frequency, run it through the calculations, and then submit it to the DB -- or worse apply those calculations to a bunch of sites on a trunked system with multiple sites making assumptions that those formulas work on all systems. And then suddenly nothing works for anyone. An admin can't be expected to weed that all out. We have to have some trust factor that submitters are doing their due diligence to confirm that there data is correct.

So please be thorough, and absolutely positive that if you are using formulas to calculate LCNs and frequencies that you have gotten it right before you submit.

I'd encourage people to use a combination of (a) DSDPlus and (b) LCN Finder and (c) formulas along with comparing existing data that you already know about LCN<-->frequency pairings.

If there is any doubt, just post what you are thinking about a particular system / site in an appropriate thread and let others review so that you can get a consensus.

Mike

 

[kh6sz]

It seems to work in the 450Mhz or 460Mhz range but if the system has a combination of 450Mhz and 460Mhz frequencies, it must be done in multiple calculations with a known pair from the respective ranges.

That's what I've found. If the pairs are from a different group, like 1 in 1-400 and the other in the 401-800 group, then it probably will not work. The 2 known frequencies should be in the same group for this to work.

 

[troymail]

The talk about formulas to determine LCNs really should be in another thread. It's going to get lost here.

More importantly [and not discounting anyone using the formulas -- I do], please don't just start using the calculations willy-nilly making assumptions that a particular standard bandplan is in use -- and then submit it to the DB. Admins aren't going to really be able to verify your data in many cases and you must may totally pollute the database with incorrect information by using the wrong formulas / calculations.

There are particular times when those formulas work and when they don't, and it always requires that you know something about some existing LCN<-->frequency pairings on the system beforehand so that you can make sure the formulas you are using apply to those particular systems / sites.

I can really anticipate a lot of bad data getting submitted to the DB by unwitting people who just know a single LCN or single frequency, run it through the calculations, and then submit it to the DB -- or worse apply those calculations to a bunch of sites on a trunked system with multiple sites making assumptions that those formulas work on all systems. And then suddenly nothing works for anyone. An admin can't be expected to weed that all out. We have to have some trust factor that submitters are doing their due diligence to confirm that there data is correct.

So please be thorough, and absolutely positive that if you are using formulas to calculate LCNs and frequencies that you have gotten it right before you submit.

I'd encourage people to use a combination of (a) DSDPlus and (b) LCN Finder and (c) formulas along with comparing existing data that you already know about LCN<-->frequency pairings.

If there is any doubt, just post what you are thinking about a particular system / site in an appropriate thread and let others review so that you can get a consensus.

Mike

I concur with Mike's post -

I recently ran LCN finder (and DSD+) for 3 of 6 sites on a nearby system and was able to guess what the LCNs for the other sites might be. However, I only submitted the confirmed information for the 3 sites I monitored - and not the speculative information about the others 3 sites...

There are no guarantees unless you monitor it.

 

[kh6sz]

It works equally well for DMR dt3 channels. I had done a similar excel sheet but not as nice looking.

/Ubbe

Thanks Ubbe, I'm glad that someone will be able to use it. I know with all the NXDN systems popping up around here, it will be a good start.

 

[kh6sz]

I'm sorry if I high-jacked this thread with the calculator. I apologize if I did, and if the moderator wants to transfer it to another thread, that's ok. One last thing to say, always trust but verify! Like several other people have stated, this is a tool, and not fact. ALWAYS verify your data by actually listening to it before submitting it into the RR database. This tool can just give you a general area to start looking!

 

[mtindor]

I'm sorry if I high-jacked this thread with the calculator. I apologize if I did, and if the moderator wants to transfer it to another thread, that's ok. One last thing to say, always trust but verify! Like several other people have stated, this is a tool, and not fact. ALWAYS verify your data by actually listening to it before submitting it into the RR database. This tool can just give you a general area to start looking!

Absolutely. I am not discounting that at all. For systems where that Excel forumula is appropriate, you can theoretically nail down a much of a wide area trunked system verifying frequencies for which ones knows the LCN, or for which ones knows the frequencies and not LCN. Great tool.

Mike

 

[WX4JCW]

Absolutely. I am not discounting that at all. For systems where that Excel forumula is appropriate, you can theoretically nail down a much of a wide area trunked system verifying frequencies for which ones knows the LCN, or for which ones knows the frequencies and not LCN. Great tool.



Mike

It’s my fault for hijacking


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
Unication G4, BCD536HP

 

[kb7gjy]

UPMan,

Just had this happen. Had a Close Call hit. Garbled audio. Display showed NX9 then ENC back an forth. It showed the RAN of 2. Gives two U numbers 102 and 108 as they talk. Freq is 168.750, This could be something in Canada because how close I am to Canada. In the US this is a wild land fire fighting freq. In Canada it also is assigned to a trucking company, and it wouldn't be the first time a Canadian trucking company used their company radios here in the states, (Read, others that chat back and forth on our County main law enforcement dispatch channel, with a different tone squelch setting).

Main thing I wanted to let you know is that it isn't muting on ENC.

I will try to get a log file next time if it happens when I am here.

 

[UPMan]

No need for log, but thanks. It will be on our list of things to adjust.

 

[u2brent]

Uniden's global muting of encryption

It would be nice if muting encryption was an option that a user could set on a per system basis. Some folks (I for one) would like to be able to at least log TG's & RID's when researching a system for the purpose of determining & submitting to RR. If everything is encrypted then there is no research that can be performed. Effectively turning a $500 tool into a paper weight is BS Uniden.

No, I don't want to listen to un-intelligible audio but I'd like it to be an option. (If Whistler can do it! nuff said..)