A few questions concerning WIN96

[OmensEdge]

Alright, I just downloaded this program the other day to help me program a friends scanner. It's pretty easy-going so far, but I have a few quick questions.

If I have both conventional and trunked frequencies in a bank, do I designate the bank as 'Conv' or 'MOT'?

Need I enter an alpha tag to a channel that holds a digital trunked frequency? It never showed up on my Pro-96, but I saw on the WIN96 site where there were alphatags listed for 800 MHz frequencies. It's on the pic towards the top of the page. I was just wondering if the program unlocked that option to be able to name the control channel frequencies.

And last, if I designate a certain channel to a particular band and it's the wrong type, will the scanner automatically correct this upon receiving a transmission on that channel? I noticed it always did this on my Pro-96. Say for instance if I would enter an aviation frequency as FM, when I would receive something on that frequency, it would change it to AM. Keep in mind that my friend is using a Pro-2096.

That's it for now. I might have more questions in the near future since I hope to finish this by Friday. Thanks!

 

[SAR923]

You would designate the bank for MOT but you can still put conventional frequencies in the same bank. This isn't true with EDACS, however.

You don't have to enter an alpha tag for a trunk channel but it helps if you are monitoring different sites. On my 96, it shows the site name on the third and the talkgroup tag on the fourth line.

I haven't seen the behavior you describe about the 96 changing modes depending on frequency. I've entered a few AM air band frequencies wrongly as FM and that's how they got received.

 

[OmensEdge]

Alright. Thanks for the answers.

Another question - regarding the MOT 3600 CC and the MOT 9600 CC table options in each bank, can I leave those at the default settings (both selected as normal) when I'm just entering digital trunked or regular trunked frequencies? Maybe a better question to ask would be when do I have to switch either to Splinter, Custom table, etc. in the 3600 area or Custom/Multi table in the 9600 area?

 

[fmon]

You would designate the bank for MOT but you can still put conventional frequencies in the same bank. This isn't true with EDACS, however.

EDACS banks like Motorola may have Conventional freqs.

Maybe a better question to ask would be when do I have to switch either to Splinter, Custom table, etc. in the 3600 area or Custom/Multi table in the 9600 area?

Custom tables and the Base, Offset and Step size settings apply to all Motorola VHF or UHF and a few 800 MHz systems. Leave as default otherwise.

 

[OmensEdge]

Got it. Thanks fmon!

 

[SAR923]

You would designate the bank for MOT but you can still put conventional frequencies in the same bank. This isn't true with EDACS, however.

EDACS banks like Motorola may have Conventional freqs.

Correct, my bad. I meant to say that you can't have both EDACS and MOTO systems in the same bank.

 

[OmensEdge]

I got to the part where I need to enter the talkgroup IDs in my banks and I was wondering if I could enter them in HEX format. It seems much easier.

I was trying to enter the IDs in decimal format and I wouldn't let me. It would keep popping up an error saying it was out of range. Say I entered '3471', it would only let me enter it by putting a zero before the ID. After I did that, it took off the last digit of the ID. Basically all of the IDs are following in the number when I enter them (3471, 3472, 3473, etc. all show up as 0347).

Also, if I do enter the IDs in HEX mode, will the regular IDs show up when receiving a transmission or the HEX letters?

 

[fmon]

I was trying to enter the IDs in decimal format and I wouldn't let me. It would keep popping up an error saying it was out of range. Say I entered '3471', it would only let me enter it by putting a zero before the ID. After I did that, it took off the last digit of the ID. Basically all of the IDs are following in the number when I enter them (3471, 3472, 3473, etc. all show up as 0347).

Recheck the bank setting, it appears you may be set for Conv or EDACS. And you don't need to enter the leading 0, Win96 will do that for you.

Also, if I do enter the IDs in HEX mode, will the regular IDs show up when receiving a transmission or the HEX letters?

I've never used nor ever found a reason to use HEX, so can't help on this, though Win96 will take HEX entries.

 

[OmensEdge]

Recheck the bank setting, it appears you may be set for Conv or EDACS.

Yeah. That was the problem. I had it set as conventional.

 

[loumaag]

Also, if I do enter the IDs in HEX mode, will the regular IDs show up when receiving a transmission or the HEX letters?

I've never used nor ever found a reason to use HEX, so can't help on this, though Win96 will take HEX entries.

No, the TG's will display in DEC format only. As an aside, the HEX numbers for the Motorola systems listed here in the DB (note I said Motorola, not APCO-25) are not equal to the decimal number of the TG. That is normally a point of confusion with users of the DB and I wish we would do away with the HEX display entirely for Moto systems.

 

[Al42]

As an aside, the HEX numbers for the Motorola systems listed here in the DB (note I said Motorola, not APCO-25) are not equal to the decimal number of the TG.

They seem to be the decimal numbers shifted right - IOW the same number without the flag, which is normally 0, so adding a 0 on the right end of a hex TG number should work.

 

[loumaag]

As an aside, the HEX numbers for the Motorola systems listed here in the DB (note I said Motorola, not APCO-25) are not equal to the decimal number of the TG.

They seem to be the decimal numbers shifted right - IOW the same number without the flag, which is normally 0, so adding a 0 on the right end of a hex TG number should work.

That is essentionally correct. What they are, are the numbers used to program an actual Motorola radio. TG ignoring the status bits. In any case, they only serve confusion here on the site.