MStep
Member
An "anomaly" is generally defined as:
a) something that deviates from what is standard, normal, or expected
b) an oddity, peculiarity, abnormality, irregularity, inconsistency, quirk
I want to focus this thread on anomalies which I and others have discovered on the Icom R8600 receiver. Indeed, the is a very complex and sophisticated monitoring tool. But as I have discovered, there are certain peculiarities associated with the operation of the receiver which come into play, and once discovered, can add to the flexibility of the unit during certain operating conditions.
I would hope that others who discover unusual or unexpected behavior with the R8600 will also help by contributing their observations to this thread.
With that in mind, let me present:
Mike's Icom R8600 Anomaly # 1
Interesting tuning step variations come into play when using the "Programmable Tuning Step" function, as described in section 3-3 of the R8600 Instruction Manual.
The best way to demonstrate/describe this anomaly is to give a brief description of the occurrence and then instructions on how to observe this on your own R8600.
Here in New York City, the Police Department operates in the "T" band, on what were once considered "spilt" frequencies. (These days, the "splits" of frequencies have become even more narrow, but that is not particularly germane to this demonstration.)
The NYPD's main dispatch frequencies operate 25 KHz apart, but on "Odd" frequencies. They start at 476.31250 and range up to 477.13750.
In order to demonstrate this "anomaly":
1) use the F-INP (Frequency Input screen) to manually program in 476.31250 in FM mode
2) On the Tuning Step screen, select the "standard" (not custom) 25 KHz step.
3) When you start to manually tune, you will see the radio jumps to 476.32500, then 476.35000, etc, thus "rounding off" and missing the "splits". Bummer.
4) Now, got back to the Tuning Step screen, and select the Programmable Tuning Step function to set up a 25 KHz step. (The custom step is turned on when you see the background area of that function turn blue in color.)
5) You must, once again, manually enter 476.31250 on the Frequency Input screen.
6) Manually start tuning again and wow, neato--- with the Programmable Tuning Step engaged, you are now hitting all the correct "splits"--- 476.31250, 476.33750, etc. The radio is not "rounding off", as it does with the standard 25 KHz split.
It appears that you must always manually enter the starting frequency via the Frequency Input screen for this little trick to work.
This can be a useful function during manual tuning, or "searching" to hit only certain frequencies within a range. It demonstrates one of what are likely dozens (or perhaps even hundreds) of operational variations in the R8600, which make it such a flexible and powerful monitoring tool.
I have not experimented with the operation of other "standard" vs "programmable" tuning steps-- I will leave that to others to explore or discover.
I hope those here on the forums who discover unusual operational behaviors in the R8600 will contribute to this thread. One interesting sidenote is that these "undocumented" features could inadvertently be eliminated with future firmware upgrades. That's why I feel that it is so important to document as many of these anomalies as we find.
a) something that deviates from what is standard, normal, or expected
b) an oddity, peculiarity, abnormality, irregularity, inconsistency, quirk
I want to focus this thread on anomalies which I and others have discovered on the Icom R8600 receiver. Indeed, the is a very complex and sophisticated monitoring tool. But as I have discovered, there are certain peculiarities associated with the operation of the receiver which come into play, and once discovered, can add to the flexibility of the unit during certain operating conditions.
I would hope that others who discover unusual or unexpected behavior with the R8600 will also help by contributing their observations to this thread.
With that in mind, let me present:
Mike's Icom R8600 Anomaly # 1
Interesting tuning step variations come into play when using the "Programmable Tuning Step" function, as described in section 3-3 of the R8600 Instruction Manual.
The best way to demonstrate/describe this anomaly is to give a brief description of the occurrence and then instructions on how to observe this on your own R8600.
Here in New York City, the Police Department operates in the "T" band, on what were once considered "spilt" frequencies. (These days, the "splits" of frequencies have become even more narrow, but that is not particularly germane to this demonstration.)
The NYPD's main dispatch frequencies operate 25 KHz apart, but on "Odd" frequencies. They start at 476.31250 and range up to 477.13750.
In order to demonstrate this "anomaly":
1) use the F-INP (Frequency Input screen) to manually program in 476.31250 in FM mode
2) On the Tuning Step screen, select the "standard" (not custom) 25 KHz step.
3) When you start to manually tune, you will see the radio jumps to 476.32500, then 476.35000, etc, thus "rounding off" and missing the "splits". Bummer.
4) Now, got back to the Tuning Step screen, and select the Programmable Tuning Step function to set up a 25 KHz step. (The custom step is turned on when you see the background area of that function turn blue in color.)
5) You must, once again, manually enter 476.31250 on the Frequency Input screen.
6) Manually start tuning again and wow, neato--- with the Programmable Tuning Step engaged, you are now hitting all the correct "splits"--- 476.31250, 476.33750, etc. The radio is not "rounding off", as it does with the standard 25 KHz split.
It appears that you must always manually enter the starting frequency via the Frequency Input screen for this little trick to work.
This can be a useful function during manual tuning, or "searching" to hit only certain frequencies within a range. It demonstrates one of what are likely dozens (or perhaps even hundreds) of operational variations in the R8600, which make it such a flexible and powerful monitoring tool.
I have not experimented with the operation of other "standard" vs "programmable" tuning steps-- I will leave that to others to explore or discover.
I hope those here on the forums who discover unusual operational behaviors in the R8600 will contribute to this thread. One interesting sidenote is that these "undocumented" features could inadvertently be eliminated with future firmware upgrades. That's why I feel that it is so important to document as many of these anomalies as we find.
Last edited: