NXDN LCN order - BCD436

[kg4pbd]

I manually entered the frequencies for one of the sites for the Fleettalk NXDN system, and after running LCN finder the radio monitors the system pretty well. Now that ARC536 supports NXDN I tried loading the system via RR and it doesn't work. I tried running LCN finder and it just spun its wheels. This is the Stuart Andrews Site in Charlotte.

If I go back into ARC and look at the site for the system I created manually, the LCN is as follows:
0464.325000 747
0463.862500 710
0463.300000 665
0462.737500 620
0462.537500 604
0461.812500 546
0451.012500 82

Here is the same system as it reads when imported from RR:
0451.012500 1
0461.812500 2
0462.537500 3
0462.737500 4
0463.300000 5
0463.862500 6
0464.325000 7

Does anyone understand why it works when I manually enter the system and use LCN finder, but not when I import?

 

[troymail]

I thought I recalled at some point that the LCN finder for DMR expected/required the programmed LCNs to be 0 for the LCN finder to work - I could be wrong. Maybe the same holds true for NXDN?

 

[u2brent]

The DB is based on user submissions

Most likely because the LCN's listed in the DB are wrong. You should submit your updated frequencies & CH #'s/RAN's if your sure your info is correct!!

Then the next person won't stumble in the same spot in the path :lol:

 

[mtindor]

The LCNs in the DB are correct. I think ARC if fouling things up. That still doesn't explain why importing from the DB with LCNs 1-7 and then running LCN Finder causes the wheels to spin. That is odd behavior.

From DB:

CH ID Frequency
82 451.0125
546 461.8125
604 462.5375
620 462.7375c
665 463.300
710 463.8625
747 464.325

Mike

 

[MtnBiker2005]

https://www.radioreference.com/apps/db/?siteId=24496
https://www.radioreference.com/apps/db/?sid=8150

 

[u2brent]

I thought I recalled at some point that the LCN finder for DMR expected/required the programmed LCNs to be 0 for the LCN finder to work - I could be wrong. Maybe the same holds true for NXDN?

I don't believe that to be true.
Running LCN finder will re-write an existing # if it is re-analyzed.
a 0 value is just a placeholder, it will change any value if it differs during the run.
If you do not enter a value it defaults to 0.

maybe the analyzer handles NXDN different, but I doubt it..

 

[mtindor]

I do see that the admin Phillipsc84 is so graciously going through the SC Fleetnet and adding the LCNs (since they now know it's using a standard UHF bandplan).

It doesn't look like he has had to do that on the NC Fleetnet system for as many sites though -- no changes like that recently on the Stuart site -- which suggests to me that the Stuart site was already correct in the DB for some time.

That leads me to ask (a) why is ARC importing it with LCNs 1-7 and if it's importing that wrong, what else is it importing incorrectly?

Mike

 

[u2brent]

Yep, looks like an importation error of some sort, have you checked for a newer version. ARC536 is going through NXDN growing pains.

At least you know the LCN finder is working like a charm!!

 

[mtindor]

At least you know the LCN finder is working like a charm!!

No kidding. The LCN Finder is an awesome tool!

Mike

 

[u2brent]

I just checked, with the newest version arc536pro 2.01 build 4 imports all NXDN systems ch's as 1,2,3,4,5,6,7,8 and so on, despite the info in the DB being correct.

 

[WX4JCW]

it is an ARC import issue, i thought Gommert fixed it

 

[u2brent]

thought is the key

 

[WX4JCW]

FYI Proscan is working fine, its just ARC messing up

 

[WX4JCW]

thought is the key

my wife gets on me for that all the time
if i say "Honey I was thinking" i get all kinds of sarcastic remarks

 

[u2brent]

I'll have to look into this PROSCAN thing :lol:

Build 5 anyone!

 

[jonwienke]

I'll have to look into this PROSCAN thing :lol:!

You won't regret it.

 

[kg4pbd]

I just imported the same system using Proscan, and it imported perfectly. So it must be an ARC issue.

 

[troymail]

FWIW - I manually set 6 LCNs in a configuration yesterday and then ran the LCN finder -- the LCN finder only found 1 LCN (seems only 1 of 6 site frequencies were active). The radio cleared/set the other 5 LCNs to 0 upon saving results.

 

[captainmax1]

I have had the same problems importing LCN's and RAN's correctly with ARC & ProScan. There seems to be various reasons for this which isn't always the fault of the software and is related to the info in RRDB. Some of the site gps locations are not correct with RAN number and sometimes the LCN's appear to be same as talkgroup or other info in RRDB. I believe ProScan has the best handle on this so far. I always try to double check all the info before I write to my scanner.