OP25 -- ZeroDvisionError

[mtindor]

Are you running the max branch now? If so it'll be in a file named p25_demodulator.py.

Don't edit those tsv files in LibreOffice, use the gedit text editor. Each field needs a tab separator.. and no empty lines.

It probably is a space vs tab / extraneous character / LF / CR type of issue. He's using nano to edit it, so there aren't any nonprintable characters injected in . He'll just have to make sure that between every set of double quotes there is a tab, and that immediately after the end of hte line hi hits enter and then uses ctrl-K to delete the newly created line below.

His NAC has an alpha character in it, we tried both 'b' and 'B'. It would be interesting know if the NAC is case sensitive though.

I love all of the suggestions you are giving him. I'm going to add these tidbits to my own site so that I can easily find them, and of course I'll attribute the assistance to you. I won't tell you what the name of my cheesy site is, but someday if I collect enough good info / tips on there for this stuff it'll show up in a google search rofl. Otherwise, I'll be the 1 unique visitor per month.

m

 

[jcardani]

Hi Scott,

Working great now! That tightened the filter up nice. Adjacent channels now have almost no effect. Can it be tightened any more or would it start degrading the decode?

 

[mtindor]

Hi Scott,

Working great now! That tightened the filter up nice. Adjacent channels now have almost no effect. Can it be tightened any more or would it start degrading the decode?

Joe,

Why don't you just try it yourself and see? It's easy enough to do that.

Then you can share your experience so that the rest of us reading know whether to try anything tighter or not if we run into the issue.

mike

 

[jcardani]

Hi Mike,

I did. Reduced it more and audio started breaking up. So went back to 12500/2
And slightly wider at 15000/2 works even better - I kept it there

I commented out the old values and marked the changes with my initials.

I'll work on the trunk.tv file details over the weekend. Getting tired.

Again thanks and happy new year !!!!

Joe

 

[PiccoIntegra]

His NAC has an alpha character in it, we tried both 'b' and 'B'. It would be interesting know if the NAC is case sensitive though.

The NAC format can be either 0x3b1, 0x3B1 or 945. It cannot be 3b1 or 3B1. Just make sure it's the valid NAC for each site. This is important to know prior to setting up any TSV files, and should be verified against what's in the RRDB. Many sites don't have the NAC value, or modulation, etc...

 

[PiccoIntegra]

I did. Reduced it more and audio started breaking up. So went back to 12500/2
And slightly wider at 15000/2 works even better - I kept it there

You'd typically want to use a value that is half of the channel bandwidth of 12.5k, 6.25k in this case. These settings are better observed in real time to see their effect. I've got a GRC script that demonstrates this somewhere. If I can find it, I'll post it here..

I commented out the old values and marked the changes with my initials.

That's ok.. just be aware that Python is very picky about how lines are indented. Mixing spaces and tabs can throw errors all over the place.

 

[mtindor]

The NAC format can be either 0x3b1, 0x3B1 or 945. It cannot be 3b1 or 3B1. Just make sure it's the valid NAC for each site. This is important to know prior to setting up any TSV files, and should be verified against what's in the RRDB. Many sites don't have the NAC value, or modulation, etc...

Sorry, I meant it is prefixed with 0x in the file. As a general rule, being an rr admin, i think of NAC in terms of 3 digits and say them that way, right or wrong, better or worse rofl.

-- Mike