Unhappy saber owner
Moderator: Queue Moderator
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
Unhappy saber owner
Hi All
After so long I am still battling with my saber2 / mx2000 radio and the error02 message.
Several comments of try this and that but no-one can offer any remedy.Please if anyone has reflashed this radio back from this error code please could you be kind enough to assist me.Imported the radio and now sit with a brick.
Need prog software used , aswell as the type of computer setup and spec.
Thanks in advance.
Brad node 8300
After so long I am still battling with my saber2 / mx2000 radio and the error02 message.
Several comments of try this and that but no-one can offer any remedy.Please if anyone has reflashed this radio back from this error code please could you be kind enough to assist me.Imported the radio and now sit with a brick.
Need prog software used , aswell as the type of computer setup and spec.
Thanks in advance.
Brad node 8300
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
Sabers are picky. It's kinda hard to completely kill one though so, all is not lost. Get your programming platform in order and you'll get rid of the error code.
If all else fails and you can't find a stable programming platform, you can always send the radio to me or someone else who has a good stable programming platform and we can un-brick the radio for you. Might be kinda expensive from S.A. though.
John
If all else fails and you can't find a stable programming platform, you can always send the radio to me or someone else who has a good stable programming platform and we can un-brick the radio for you. Might be kinda expensive from S.A. though.
John
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
- jnglmassiv
- Batboard $upporter
- Posts: 512
- Joined: Sun Feb 24, 2002 4:00 pm
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
Hi
Using the msd command in dos I have the following setup:
Amaerican Megatrend 80386
Memeory 640k , 3072 ext
1984k XMS
MS-DOS ver 5.00
Bios Ver V3.128
Processor 80386
Bus type ISA/AT/Classic Bus
DMA Controller :YES
Cascaded IRQ2 :YES
Not sure what else is needed to confirm my setup should be able to program the saber / mx2000.
Any comments?
Brad
Using the msd command in dos I have the following setup:
Amaerican Megatrend 80386
Memeory 640k , 3072 ext
1984k XMS
MS-DOS ver 5.00
Bios Ver V3.128
Processor 80386
Bus type ISA/AT/Classic Bus
DMA Controller :YES
Cascaded IRQ2 :YES
Not sure what else is needed to confirm my setup should be able to program the saber / mx2000.
Any comments?
Brad
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
Hi All
Thanks for the continued support-I have finally after 18 months come right-found that I had used the Astro saber programming pins which take pin 3 from radio to pin 6 of rib instead of pin 8 of the rib.Have programmed and read radio several times.
Still need to hex edit software to allow 430-440 operation.
Thanks again to all.
Brad
Kind regards
Thanks for the continued support-I have finally after 18 months come right-found that I had used the Astro saber programming pins which take pin 3 from radio to pin 6 of rib instead of pin 8 of the rib.Have programmed and read radio several times.
Still need to hex edit software to allow 430-440 operation.
Thanks again to all.
Brad
Kind regards
- jnglmassiv
- Batboard $upporter
- Posts: 512
- Joined: Sun Feb 24, 2002 4:00 pm
- bradlington
- 1 Warning for RSS/CPS Wanted/For Sale/Links
- Posts: 155
- Joined: Sun Jan 05, 2003 10:34 am
Hi All
I agree that a simple mistake has cost me 18 months of frustration.
I imported the radio and these are not used in this country so I was alone on this one and not even Motorola local could advise or help.
I still need to get the correct pins of the battery layout to make a charger for it .
My next project are the 3 jedi series radios that are to be returned from "brick"status.
Thanks again to all for the mental assurence.
Bradley Glen
I agree that a simple mistake has cost me 18 months of frustration.
I imported the radio and these are not used in this country so I was alone on this one and not even Motorola local could advise or help.
I still need to get the correct pins of the battery layout to make a charger for it .
My next project are the 3 jedi series radios that are to be returned from "brick"status.
Thanks again to all for the mental assurence.
Bradley Glen
- oh2glg
- Posts: 106
- Joined: Tue Aug 09, 2005 7:32 am
- What radios do you own?: DP4801 DM4601 SL7550 MTP850S
Saber 2 ERR 0 81 (was: Re: Unhappy saber owner)
Hello all on the board,
Writing for the first time here I must say that the amount of information on this board is REALLY overwhelming!
I've been reading this and few other threads with similar topics, since I have quite the same case on my hand.. Well, only thing different this time is that I got this saber just few weeks ago and tried to program new freqs to it today.
In my case, I have UHF Saber II-R, 120ch 403-433MHz.
The codeplug was read by Saber RSS R07.01.00 nicely with no problems. I saved it on the disk just in case.
After I modified the original codeplug (changed frequencies etc) and tried to send it back to Saber, it went sour.
Now it says "ERR 0 81" on the display, battery indicator is blinking and that's about all it does.
Now when I try to re-read codeplug from the radio, RSS warns few times during transfer that there's parity errors on CORE- and COPE-processors memory.
I also tried to create new RPF from scratch, but it didn't manage to correct it. Nothing changed.
Only thing I didn't check yet, if the cable is for Saber instead of Astro Saber, since it's loaned it from a friend. And after reading the two last posts on this thread I'm quite convinced that the cable is worth checking for correct connection.
Oh, by the way: Since this unit is for bandsplit 403-433, it is not unexpected that the RSS will complain if any of the frequencies are above 434.000 MHz. Is there any other way to work around it than modifying the channel data file directly with an editor?
Jussi OH2GLG
Writing for the first time here I must say that the amount of information on this board is REALLY overwhelming!
I've been reading this and few other threads with similar topics, since I have quite the same case on my hand.. Well, only thing different this time is that I got this saber just few weeks ago and tried to program new freqs to it today.
In my case, I have UHF Saber II-R, 120ch 403-433MHz.
The codeplug was read by Saber RSS R07.01.00 nicely with no problems. I saved it on the disk just in case.
After I modified the original codeplug (changed frequencies etc) and tried to send it back to Saber, it went sour.
Now it says "ERR 0 81" on the display, battery indicator is blinking and that's about all it does.
Now when I try to re-read codeplug from the radio, RSS warns few times during transfer that there's parity errors on CORE- and COPE-processors memory.
I also tried to create new RPF from scratch, but it didn't manage to correct it. Nothing changed.
Only thing I didn't check yet, if the cable is for Saber instead of Astro Saber, since it's loaned it from a friend. And after reading the two last posts on this thread I'm quite convinced that the cable is worth checking for correct connection.
Oh, by the way: Since this unit is for bandsplit 403-433, it is not unexpected that the RSS will complain if any of the frequencies are above 434.000 MHz. Is there any other way to work around it than modifying the channel data file directly with an editor?
Jussi OH2GLG
Last edited by oh2glg on Sat Aug 27, 2005 7:33 am, edited 1 time in total.
Well, you did the first step correctly...you saved a copy of the codeplug! What are the specs for your computer? I've come to find the Sabers are one radio which can read fine on most set-ups, but can corrupt when written to on the same set-up. It's very possible you'll have to 'step down' to an older system in order to successfully program the known good codeplug back into the radio.
Todd
Todd
No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.
Welcome to the /\/\achine.
Welcome to the /\/\achine.
- oh2glg
- Posts: 106
- Joined: Tue Aug 09, 2005 7:32 am
- What radios do you own?: DP4801 DM4601 SL7550 MTP850S
Re: Saber 2 ERR 0 81
Well, it is an older model Compaq laptop, but I really can not recall its model on processor speed right now, since it's at my workplace.wavetar wrote:What are the specs for your computer? I've come to find the Sabers are one radio which can read fine on most set-ups, but can corrupt when written to on the same set-up. It's very possible you'll have to 'step down' to an older system in order to successfully program the known good codeplug back into the radio.
Todd
However, it is a 486-based slow thing, using MS-DOS 6.22 as an operating system. It has been used as a programming computer for other models as well (Yaesu, Icom, Kenwood, TP-Radio and other Motorolas like GP300)
I'm afraid that it's still too fast for Saber flashing anyway.
Well, I'll look into it on Monday. Unless I'm not able to get this computer slower, it might be useless for this. Only problem is, that it's really the slowest PC I have in my hands an the moment