I keep getting a "data collisions" error on a VHF Systems Saber III when trying to read the unit. None of the other nearly identical Sabers are throwing this at us. Since there are only a handful of Sabers in our system, I'm not up to snuff on whassup.
Saber is a C model, radio serial indicates a '94 build, software is SYSSABER 4.00.02, RIB is a new 4008E model, cable is in the correct switch position ( pin 8 ).
I've tried 3 computers, all dedicated to RSS:
1) 600 mHz WinME with DOS bootup - no problems with the other Sabers,
2) 800 mHz WinME with DOS bootup - no problems with the other Sabers,
3) 486/DX2/66 mHz DOS 6.02/W3.11 - even old faithful here won't do the trick.
I might add that all of these computers have been doing RSS duties for several years and NEVER has there been a problem until now. I don't think it's a radio problem since the LED on the radio indicates something going through, I think it's something computer related. Too fast maybe? Seems a bit wierd if the other Sabers aren't having a problem.
Systems Saber programming probs
Moderator: Queue Moderator
Systems Saber programming probs
curmudgeon.....and I like it.
Just a thought but have you tried cleaning the contacts on the back of the radio? You could also swap cases on one known good radio with this one, and if it works, it's probably the contacts. I had that problem once, ended up swapping the cases temporarily to get it programmed up, and then put it back for normal use.
Model H99QX+099H
ID H43TUK5170CN
And yes, we're aware that there are Systems Sabers and there are Sabers. We've got both, and the corresponding software for all. ALL of these radios in question are Systems Sabers, and this particular one is the only one with the problem. Did try the original computer that was used to program it (386SX33) and it does just fine. Go figure. Because of that, I don't believe it's a contact problem, but I'll try the contacts option 'cuz I got nuttin' to lose there. Sometimes it's a just a matter of snake oil, smoke, and mirrors anyway.
Of the 3500+ radios in the system, there are only about two dozen Sabers, and since they NEVER seem to give a problem, we don't see 'em except at cert time, and that's only for an FPM check. None of these have ever had the case off, if that tells ya something. The only other radios we can say that about are the Syntor 9000s and the 9000Es.
ID H43TUK5170CN
And yes, we're aware that there are Systems Sabers and there are Sabers. We've got both, and the corresponding software for all. ALL of these radios in question are Systems Sabers, and this particular one is the only one with the problem. Did try the original computer that was used to program it (386SX33) and it does just fine. Go figure. Because of that, I don't believe it's a contact problem, but I'll try the contacts option 'cuz I got nuttin' to lose there. Sometimes it's a just a matter of snake oil, smoke, and mirrors anyway.
Of the 3500+ radios in the system, there are only about two dozen Sabers, and since they NEVER seem to give a problem, we don't see 'em except at cert time, and that's only for an FPM check. None of these have ever had the case off, if that tells ya something. The only other radios we can say that about are the Syntor 9000s and the 9000Es.
curmudgeon.....and I like it.
Systems Sabers...programming troubles.
You hit the nail square on the head with your last post...use the 386 PC, it's slow enough for the job you are doing.
Systems Sabers are FINICKY to say the least, but like the regular Sabers, they can take the abuse.
Although the computer appears to be 'the' culprit, it doesn't hurt to remove the radio from the case and check the frame contacts and the case as well, oxidation can and gas been seen in this area.
If the gasket looks okay, check to see if it's still elastic enough to reuse, otherwise replace it.
Dirt and maoisture still get into the cases no matter how well you assume it is sealed, and a little PM can only help.
Check all screws for proper torque(6 In. Lbs.) and make certain the controller retaining screws are also tight.
The one item that gets overlooked is INSIDE the case, it's the reference oscillator; it is rarely held securely to the controller board except by the rubber boot and the front cover. Check to make certain this 'module' is firmly seated, and you may want to place a small piece of nonconductive foam over it to help keep it firmly seated.
Just trying to help.......
Systems Sabers are FINICKY to say the least, but like the regular Sabers, they can take the abuse.
Although the computer appears to be 'the' culprit, it doesn't hurt to remove the radio from the case and check the frame contacts and the case as well, oxidation can and gas been seen in this area.
If the gasket looks okay, check to see if it's still elastic enough to reuse, otherwise replace it.
Dirt and maoisture still get into the cases no matter how well you assume it is sealed, and a little PM can only help.
Check all screws for proper torque(6 In. Lbs.) and make certain the controller retaining screws are also tight.
The one item that gets overlooked is INSIDE the case, it's the reference oscillator; it is rarely held securely to the controller board except by the rubber boot and the front cover. Check to make certain this 'module' is firmly seated, and you may want to place a small piece of nonconductive foam over it to help keep it firmly seated.
Just trying to help.......
Thanx to all fer all the help. It mostly confirmed what I already knew, I just didn't realize how finicky some of the Sabers can be. For the time being we'll just use the 386, even if it's in an inconvenient location 90 miles away. All this for one radio.........
I have an old 70 mHz Think Pad with 6.02 that I dug out this AM, and even with a dim display, I feel it's gonna be a Saber programmer.
I have an old 70 mHz Think Pad with 6.02 that I dug out this AM, and even with a dim display, I feel it's gonna be a Saber programmer.
curmudgeon.....and I like it.
