When the program does not have a live call to monitor, it "parks" the voice radio. If you are parking on a fixed frequency ... park mode specifies the modulation. Suppose you wanted to park on 121.5 Mhz - which is AM - but your radio is using NFM for trunked voice. This is only used if the park use is set to "Frequency" (in which case you'd fill out 121.5 as the park frequency).wolter said:I only have the options of [NFM] and [AUTO]. BTW, what does "Park Mode" mean?
Each group and radio id has a Listen yes/no flag associated. It's the exact opposite of the Lockout yes/no flag. You can limit calls monitored to ...OK, but what does "Scan for Listen" mean? What is its purpose?
Park use tells the program how to park the radio:Along that line what is the purpose of "use", "Frequency (Mhz)", and "Memory"?
The green channel indicates the program is attempting to tune the radio. I'll have to do some digging to find out why this isn't working.wolter said:So, UniTrunker does have control of it. It just isn't doing anything with it.
Yes. Earlier you mentioned some channels were green. The program shouldn't select a channel with a zero'd frequency. I need to check that.wolter said:I simply thought it would determine the frequencies, too. I suppose this is due to a lack of data in the control channel? And, this makes it a PIA to map out new EDACS systems.
Here's the trick. Some (mostly networked) systems tell you in what band they operate. Other's don't. For those that don't, the only way to infer 900 mhz operation is for you to type at least one frequency - preferably the active control channel. That's enough of a hint for the program to fill in the other channels.And along this line, I noticed that this issue happens with Motorola 900 MHz, too, but not 800 MHz. UniTrunker displays all frequencies used in 800 MHz Motorola Type II systems, but not 900 MHz. Is this expected?
The original design called for a generic mechanism to partition IDs. This would allow it to accomodate any fleetmap. I've backed off from that. For Motorola - the program uses the fleet codes (code A, D, or K for example). I need to add an extra display mode to display both Motorola and EDACS in AFS format. Don't worry about editing the fleetmap unless you're monitoring a Type I system.What is "fleet map support?" I don't see an explanation in the About. I'm trying to determine the IDs for this EDACS system, and its a PIA to convert from decimal every time.
Actually, I said that the frequency is green, which is true when one displays in the channel column of the main activity viewer (is that the correct term?). But, if a frequency is zero'd, only the LCN displays. In which case, the number (LCN) is not green but white when the system channel is active.rfmobile said:Yes. Earlier you mentioned some channels were green. The program shouldn't select a channel with a zero'd frequency. I need to check that.
Oh, OK. Its filling in the 900 MHz frequencies, now. Thanks!rfmobile said:Here's the trick. Some (mostly networked) systems tell you in what band they operate. Other's don't. For those that don't, the only way to infer 900 mhz operation is for you to type at least one frequency - preferably the active control channel. That's enough of a hint for the program to fill in the other channels.
I see. Thanks.rfmobile said:The original design called for a generic mechanism to partition IDs. This would allow it to accomodate any fleetmap. I've backed off from that. For Motorola - the program uses the fleet codes (code A, D, or K for example). I need to add an extra display mode to display both Motorola and EDACS in AFS format. Don't worry about editing the fleetmap unless you're monitoring a Type I system.