Programming Saber III questions

N9NU · Post by **N9NU** » Sat Aug 26, 2006 8:59 am

I am having trouble writing a new codeplug I made for my Saber III. I read the codeplug ok and it has a CORE of 5D it says and comes up with a model number of H44SAK7139AN...which is fine, but I need a C model to enable scanning. Now I have never heard of a Saber III that does not scan. I saved the original codeplug to disk and created a new codeplug or RPF with the following parameters:

HIGH
FULL KEYPAD
SCAN CAPABLE
DISPLAY

CLEAR
433-470 MHz

Model #: H44SAK7139CN - all i changed is the A to a C

I then was able to select Slaved scan in the options menu and when I tried to write the RPF, it failed saying the CORE didnt match.

I don't know what version RSS was used to program it initially, but I tried using v4 through v7 and none worked.

Is there a way to "reset" the radio somehow or does anyone have any ideas ??

Tim
N9NU

GlennD · Post by **GlennD** » Sat Aug 26, 2006 11:53 am

In the F4,F4 screen does it show the 2K memory high lighted? Someone may have previously forced a 2K code plug into it.

Our FD aquired several hundred WHCA VHF sabers. Of the ones that I have put into service, about 20% were programmed this way.

Follow the Batlabs instructions to recover. The radio then needs to be totally realigned.

N9NU · Post by **N9NU** » Sat Aug 26, 2006 4:11 pm

From the main RSS menu I hit F4 then F4 again to get to the options menu and I saw nothing in that list that mentioned anything about memory...2K or 8K even. I assume that F4 F4 is where you wanted me to look right?

If thats the case, maybe I can just recoever it with the instructions you said and re-align it. I have access to equipment here at work. Just point me to the instructions and I will have at it.

Tim

GlennD · Post by **GlennD** » Sat Aug 26, 2006 4:27 pm

The proceedure is on the main Batlabs site but basically you write to the radio and very very quickly turn off the radio at the second dot. This corrupts the code plug letting you start fresh. It also corrupts all of the tuning values.

mike m · Post by **mike m** » Sat Aug 26, 2006 5:39 pm

The very first versions of the sabers did not have scan in them and they are all of the AN revision sabers.

I don't know if there was even a BN version either as I've never seen one but only some of the CN's revisions are capable of scan and only if they are the correct model, saber II or III.

For instance I have a H43YXN7139CN, submersible saber I VHF that will not scan in it's present state no matter how much I want it to, that is unless I hack it into a model II or III and then loose the submersability but if it were an AN rev radio then it would never scan no matter what i do to it.

By this I mean that you cannot change an AN revision to a CN revision. The revision letter is hardcoded in the radios firmware or CORE, 'Control Of Radio Electronics' or the main operating feature set/code that was programmed at the factory, so your radio cannot and will not scan, period since it's an original AN rev.

Turn it back in to the correct AN version and try programming the correct rev codeplug back in to it. That should fix it.

Mike

AEC · Post by **AEC** » Sat Aug 26, 2006 11:00 pm

I have taken several 'AN' revision Saber IIIs and had scan enabled, but older RSS usually will not allow this.

In fact, I still have my original model from 1993 and even though it was actually an 'AN' version, I was able to 'convert' the CP so that scan capability was possible and it's in daily use here.

The simplest method is to corrupt the CP data by programming it and when the 'dots' appear on the screen, shut off the radio, this is all that's needed to temporarily 'brick' the memory.

Then you can rebuild the codeplug data with H44QXK7139CN/H99QX065H data within the 'Create/Modify' section (F3).

This is the starting point, then choose the proper band split, usually 440-470 and proceed with building the codeplug options(F4).

The options below are only 'ideas' you can use...
H901: Non-standard timeout...110 sec.
H371: ZONE & CHANNEL OPERATION
H346: ZONE DISPLAY NAMES
H380: CHANNEL DISPLAY NAMES
H345: RADIO LOCK (password= )
H384: MUTING VIA KEYPAD
H359: CHANNEL BUSY LED
H649: SELECTABLE PL (ENCODE/DECODE)
H967: UNIT ID W/ AUDIBLE EMERGENCY-MDC 1200 (UNIT ID = XXXX)
H779: MDC NON-STANDARD PRETIME DELAY (150 MILLISECONDS)
H297: MANUAL TELEPHONE INTERCONNECT (MANUAL LENGTH)
H273: OPERATOR SELECTABLE SCAN
H344: MODE SLAVED SCAN
NUISANCE MODE DELETE
SCROLL SCAN LIST

DO NOT SELECT THE BELOW OPTIONS WITH ANY 5D OR EARLIER CORE!

H852- 6D MASTER OPTION...DO NOT SELECT WITH LESS THAN 6D CORE!
H549- 8D MASTER OPTION (ADVANCED STATALERT) DO NOT SELECT
WITH LESS THAN 8D CORE!

Now you can build your channel information...

These options will work on almost ALL standard Saber III models.

If you need help, Email me at: [email protected] and I'll be happy to walk you through the process......I do this every day here for several others, and I am certain I can help you with yours.

mike m · Post by **mike m** » Mon Aug 28, 2006 7:13 am

I've tried the corrupt CP method numerous times on AN rev radios using CPS 5, 6 and 7 and never could I make a AN radio scan.

AEC · Post by **AEC** » Wed Aug 30, 2006 10:47 pm

That must be a fairly old radio or one with very limited options available.

I've never had a Saber III that could not be made to scan, even the model IIs are scan capable with the proper option selected.

Even the main user's manuals and factory release books indicate every Saber III has the capability to scan.

I wonder what version of RSS is being used that causes this conflict?

I know R07.00.01 allows this option, as does vers. 4 and 5.....??

Saber II had the II.2 scan with 36 channels active, and the loss of 12 channels for scan, but a model III that did not scan?

Rare beast indeed!

Ver. D04+/-10M Release date: 01/10/89
Ver. R05.00.00 Release date: 12/25/89
Ver. R07+99-99...RVN4002J Release date: 09/01/92

Programming Saber III questions

Programming Saber III questions

2K option