Page 1 of 1

Saber III conversion

Posted: Mon Aug 25, 2008 6:31 pm
by ledzep
Well, I got the saber II converted to a III ...still cant get it to scan... any ideas?
I created a new file personality and entered the channels, the options, etc..when you prog the radio it says an invalid menu has been detected, and after that, all the scan options disappear...wonder if this is the difference between cope 4 and 5...if it is, does that mean i have to get another 8k memory front that will hopefully be cope 5 compliant? and then the next question would be the part number for such...

Re: Saber III conversion

Posted: Mon Aug 25, 2008 9:28 pm
by FireCpt809
Is it an 8K front or a 2K?

Re: Saber III conversion

Posted: Tue Aug 26, 2008 1:32 am
by ledzep
the one i have is an 8k

Re: Saber III conversion

Posted: Tue Aug 26, 2008 7:29 am
by FireCpt809
I would think its a Cope4 issue. TominDC would know better. I only had one 4 that was a Saber II 2k that would act that way

Re: Saber III conversion

Posted: Tue Aug 26, 2008 6:54 pm
by ledzep
well the part source says its an 8k unit...it even comes up as a 160 channel capable radio...wouldn't this indicate that it is definitely 8k?

Re: Saber III conversion

Posted: Tue Aug 26, 2008 11:54 pm
by Tom in D.C.
160 channels? That does not add up. No such thing as a 160 channel Saber 3.
Tell us exactly what you are doing to get that 160-channel indication. A Saber 1
is 12 channels, a Saber 2 is 48 or 120 channels, a Saber 3 is 120 channels, and a
System Saber is 255 channels.

Scanwise, have you set up everything in the RSS to make the radio scan? There
are several options in the radio options for scanning and these must be set right
to make the radio scan.

Re: Saber III conversion

Posted: Wed Aug 27, 2008 1:36 am
by ledzep
My mistake...i meant 120 ch...but i did try mode slaved scan and set up a scan list...that didnt work..it detected an "invalid menu" and changed it back to a "an" model...also tried operator selectable scan, and once again..."invalid menu" message...

Re: Saber III conversion

Posted: Wed Aug 27, 2008 7:11 am
by Tom in D.C.
In order to scan the Saber must be a CN.
An AN will not scan, ever, no how.
What model number shows at the upper
left of the RSS screen?

If your radio is an AN that's the reason
it won't scan and is giving you that message.

Re: Saber III conversion

Posted: Wed Aug 27, 2008 6:16 pm
by ledzep
I built my own archive to convert the radio from a II to a III. The number on the back of the case is a c model. It could be the wrong one, though. In the rss , when I prog the c archive to the radio, it comes up as " an invalid menu has been detected, and the current build will be terminated F2 continue" and reverts it to an a model number. A question that comes to mind is what exactly is the difference between the a model and the c model? Is it firmware or hardware? Ive got a whole box of saber parts, extra mainboards, and stuff....if its in the main board, is there a physical difference between the a and the c (extra chips, etc) or are they identical?

Re: Saber III conversion

Posted: Thu Aug 28, 2008 7:01 am
by Tom in D.C.
What model number shows at the upper
left of the RSS screen?

Answer the question I posed and we'll all know more
about the possible reason for the radio's not scanning.

It doesn't depend on what you started with, or what
you did. It depends on what the program THINKS the
radio is right now, and it looks as if it thinks it's an AN
non-scanning Saber.

Re: Saber III conversion

Posted: Sat Sep 06, 2008 9:15 am
by DJP126
Also to be considered is IF the radio is VHF, what is the part number of the VCO?