Batboard

Talk about feeling stupid... I did up a radio for channel only operation-can't figure out how to direct enter channel #'s to jump to a freq. When I try to enter a # after hitting the mode button, I get an "unprog_t" error. I can't see repeated hitting the mode key to get to 100 channels down the line.

Can someone tell me what I did wrong, either programming or operator-wise? I'm missing something here.

Thanks a lot!

Rich

If your talking about operating the radio, use the channel select switch on top. If your talking about programming, select the "enter channel" function key.

DJP126 wrote:If your talking about operating the radio, use the channel select switch on top. If your talking about programming, select the "enter channel" function key.

I have the radio set up for channel only-which means the ch select switch is disabled, there are no zones and you are supposed to be able to select your freq directly with the keypad, and it doesn't let me do that. I checked everything in programming several times.

Rich

that radio is not front panel programable, you can change the zones from the front panel if you put 1 channel in each zone and direct access it that way but you can't physically change the frequency or pl's.

Is it possible that your radio is in fact a Sys Saber 2 rather
than a 3, but with a 3 case installed? That might account
for the problem.

Sabers with channel only should respond immediately to
numerical keypresses to change the channel.

HLA wrote:that radio is not front panel programable, you can change the zones from the front panel if you put 1 channel in each zone and direct access it that way but you can't physically change the frequency or pl's.

No, I'm talking about changing the channel #... ch. 1, ch.2, etc. not the frequency.

I believe he is saying he wants it to act like a TV remote control. You press Key #5 and then the Enter key, and it changes the channel to Channel 5.

HLA wrote:that radio is not front panel programable, you can change the zones from the front panel if you put 1 channel in each zone and direct access it that way but you can't physically change the frequency or pl's.

No... he's referring to Channel Only operation. Just like taking a Jedi or Astro and putting all the channels in one zone. You then have to use the CHAN menu item and the keypad to change channels.

The fact that the radio does produce a response, even if it is an error, when using the numeric keypad, suggests that there is not a model # mismatch.

If you want, you can shoot me your codeplug and I can take a look at it.

akardam-sent you a PM.

Rich

Well, nothing looks wrong in the codeplug as far as I can tell.

The only way I was able to reproduce the UNPROG_T error was to hit MODE XXX where XXX equaled an unassigned mode (and since my SysSaber was originally setup for Zone/Chan, I have "blanks" every once in a while).

I take it from your experiences to date, that you can indeed hit MODE a bunch of times, and scroll all the way through all the channels?

What happens when you hit MODE, and then enter 001, and hit HOME? Does it send you back to the first mode?

akardam wrote:Well, nothing looks wrong in the codeplug as far as I can tell.

The only way I was able to reproduce the UNPROG_T error was to hit MODE XXX where XXX equaled an unassigned mode (and since my SysSaber was originally setup for Zone/Chan, I have "blanks" every once in a while).

I take it from your experiences to date, that you can indeed hit MODE a bunch of times, and scroll all the way through all the channels?

What happens when you hit MODE, and then enter 001, and hit HOME? Does it send you back to the first mode?

That's the problem-when I hit mode to start the display flashing, and then any combination, say 001, only the zeroes take. Any other keypress brings up the error.

Maybe the systems just don't take direct entry...

Rich

The Systems Sabers do do Channel Only, direct Mode operation. I know because I configured mine for that mode of operation for testing and it worked fine.

So I think what you're saying is, when entering in the Mode # to go to, pressing the 0 key produced a 0 on the display, but none of the other number keys work?

I see you have scan on/off programmed for the number 2 key. Does scan on/off work from that key?

(Inserted my comments)

The Systems Sabers do do Channel Only, direct Mode operation. I know because I configured mine for that mode of operation for testing and it worked fine.

So I think what you're saying is, when entering in the Mode # to go to, pressing the 0 key produced a 0 on the display, but none of the other number keys work?

**Correct. I get an UNPROG_T with any other number key, which would mean the channel would be unprogrammed. Doesn't make sense...

I see you have scan on/off programmed for the number 2 key. Does scan on/off work from that key?

**Scan, all else work fine.

Rich

akardam wrote:So I think what you're saying is, when entering in the Mode # to go to, pressing the 0 key produced a 0 on the display, but none of the other number keys work?

I've only dealt with conventional Sabers, so I'm not familiar with the error, but....

What happens if you just do "1 [enter]" or "2 [enter]," rather than 001 / 002? I only fiddled with Channel Only operation briefly, but I don't recall having to pad the numbers with leading 0's, which makes me wonder if it's somehow barfing on them. (Although it shouldn't be?)

I tested mine with both leading zeros and no leading zeros. Worked the same way regardless.

akardam wrote:I tested mine with both leading zeros and no leading zeros. Worked the same way regardless.

So you are saying that yours works fine on channel-only, and your codeplug is set up the same as mine, configurationwise?

Rich

Also: If anyone has any more thoughts, let me know. Otherwise, thank you to all those who responded and tried to help, especially akardam!

Guess this'll go down as one of the bizarre ones...

Rich

Dorpmuller wrote:So you are saying that yours works fine on channel-only, and your codeplug is set up the same as mine, configurationwise? Rich

Yes, that is correct.

Dorpmuller wrote: Guess this'll go down as one of the bizarre ones...

Is your radio a CON 5? At the depot we would automatically replace CON 5 with the latest version due to high failure rates and "bizarre" behavior. CON5 radios would work fine and then for no apparent reason they wouldn't.

DJP126 wrote:

Dorpmuller wrote: Guess this'll go down as one of the bizarre ones...

Is your radio a CON 5? At the depot we would automatically replace CON 5 with the latest version due to high failure rates and "bizarre" behavior. CON5 radios would work fine and then for no apparent reason they wouldn't.

Yes it is. I guess that would mean changing the main board? If that's the case, I'll just program it back to channel/zone.

Rich