I experienced problems with radio bleedover (particularly with peak radios, but reading responses from the OA's indicates that the problem may also reside in Denro. ############################################################################ ############################################### -----Original Message----- From: Ken Jackson [mailto:ken@score.com] Sent: Friday, August 27, 2004 16:54 To: Dave Huckabee (E-mail); Fleming (E-mail); Jmadd (E-mail); tphillips@score.com; ken@score.com Subject: Peak Radios Last night (26 Aug 04...2100-2400), two primary fixed frequencies for the MITT op were tuned up to peak radios....263.9MHZ, and 265.05MHZ. Everytime the 263.9MHZ radio was keyed, it overrode the 265.05MHZ radio. The 263.9MHZ radio (Peak 1 and Peak 8) was assigned as the MAC freq, and primarily used by NZ. The 265.05MHZ radio (Peak 6) was the primary acft reporting frequency for the north op area, and much radio traffic was lost (sonobuoy deployments, attack calls, etc), which denigrated the overall data collection and display effort. A solution could be to ensure that close frequencies be split between peak and thirst radios, if the radio frequencies are not remotely tuneable. Recommendations: 1. Score operations program engineer needs to have the final say on radio configuration prior to event commencing. 2. Radios need to be shielded? 3. ?? %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%% I EXPERIENCED MUCH OF THE SAME PROBLEMS ON THE SAME DAY IN THE AM. I HAD THE SHIP AND ZULU TEAMS SHIFT THE PEAK RADIOS USED FOR XMIT, TO SEE IF IT WOULD HELP. NO JOY. THE OPTION TO HAVE SOMEONE GO TO THURST TO MAKE CHANGES, WAS A "TOO HARD" IDEA. THE BALANCE KNOB ON OA5 IS NOT VERY HELPFUL. I TOO MISSED A LOT OF DATA AND ATTACKS BECAUSE OF THIS ONGOING PROBLEM. DOES ANYONE CARE AND WILL THE MONEY BE PUT UP TO RESOLVE THE PROBLEM? THIS IS NOT A NEW PROB. IT IS MY UNDERSTANDING THAT THE NAVY OWNS THE RADIOS AND HAVE THE PMS RESPONSIBILITIES. THIS IS GOING TO TAKE SOME HIGH VIS TYPES TO ADDRESS THIS ISSUE. Dave &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& &&&&&&&&&&&&&& From: Joe Maddalena [mailto:joem@score.com] Sent: Wednesday, April 14, 2004 09:38 To: 'Steve Conrad'; 'david f huckabee' Cc: 'Maddalena, Joe' Subject: RE: communication problems at the score range Steve, I concur with Dave Huckabee about the unit tracking and radio bleedover. It was worst yesterday than any time I can remember. In order to complete my exercise, I had to run a GENTRACK and guess where the shooter was. We were switching between NCTS and LATS and IFF throughout. We had mean bleedover between peak and peak radios and thirst and peak radios. **************************************************************************** *************** Other problems include: unbalanced volume on the various radios... Sometimes this is not SCORE's fault, and we cannot correct it. But we need to make sure that we have done all we can do make the volume we hear (and which our users hear)is as balanced and readable as we can make it. Also, some radios pick up interference from LATS or whatever source causes that constant "clicking" noise. Again, we need to ensure that SCORE has done all it can to eliminate or minimize that major distraction. The main impact is the direct degradation of exercises, but it also causes bad advertisement for SCORE... exercise after exercise. TF