[TenTec] Original Orion 565 Firmware issues and suggestions

[Ralph Jerald 'Jerry'Volpe]

  John Henry,

Here is my list of known issues and firmware functionality improvements 
or additions. I believe items 5 and 6 would make the Orion a much more 
user 'responsive' transceiver.

I am using the latest version 2 beta and have since it became available. 
I agree that future development needs to continue only with the version 
2.x tree.

1. Naturally, improve the Noise Reduction function. As is not very 
useful. What exactly caused the deterioration of this important feature? 
There seems to be users preferences to older firmware versions that 
appeared to have far more useful Noise Reduction.

2. Add additional AGC Slope choices to provide greater apparent 
listening dynamic range between week and very strong stations. Some hams 
like a very compressed AGC while I personally don't. So I would like 
another choice if possible. I believe a bit more dynamic AGC would drop 
down the apparent noise level somewhat. The Orion's AGC is highly 
compressed even at the current maximum slope of 2:10 dB

3. Need to add back the SWEEP frequency scale.

Would it be possible to open up the displayed content should the user 
choose to not display the sweep? Things are a bit crowded at present and 
the filter graphic is not nearly as nice and easy to see as it was 
before the sweep height was increased.

4. Please confirm that all of the Remote serial port programming 
commands are working properly and correctly documented. One that I know 
that isn't working correctly on the latest beta is the TUNE command. 
N4PY is no longer able to control the auto tuner (check with Carl, 
N4PY). Also, would it be possible to add CW SPOT as a remote command?

5. Dynamic frequency tuning rates determined by how quickly the user 
rotates the tuning knobs..... Slow rotation would provide the highest 
tuning resolution (perhaps 1 or 10 Hz).... Fast knob rotation would 
automatically change by a factor of 100 (?). This was done as a third 
party modification for the Omni-V ROM and worked great. Really miss it.

6. Add a second function to the STEP menu. A long press of the STEP 
button (two seconds or more) results in the normal STEP tuning rates 
choices. A quick press of the STEP button (less than 1 second) provides 
seven preset receive DSP bandwidth choices. For example: 100Hz, 300Hz, 
600Hz, 900Hz, 1800Hz, 2100Hz, and 2400Hz. If firmware memory allowed it 
would be great if the user could choose which values in each slot by  
MENU --> FILTER. There is easily enough room for seven user choices. The 
Orion as is is very clumsy when it comes to quick filter selection. This 
added functionality uses the existing GUI and provides the user with up 
to seven 'quick' bandwidth choices. It would not be necessary to add CAT 
commands to support this. It would probably be a bit over the top but 
wouldn't it be nice if the user could optionally attach roofing filter 
choices to these seven bandwidth choices.

7. The AUX input/output levels need to be reviewed carefully for 
practicality. These settings have varied greatly from version to version 
and many users have picked a particular firm ware simply by the levels 
provided. I believe they need to be compatible with typical computer 
sound cards. (Personally, my Sound Cards are professional grade so they 
are even less sensitive on their inputs.... I added miniature Radio 
Design Labs adjustable amplifier modules to correct for this. They are 
tiny, inexpensive, and very versatile. A mono amp for the AUX input and 
a Stereo amp module for the Left/Right channels of the AUX output.)

8. DSP Filter Length tap settings do not work correctly for many TAP 
choices. For example, You may choose a tap setting of 134 and then 
discover that rotating the PBT control through its range results in 
bazaar filter configurations (translation: audio jumps all over the 
place... hissss..... filters break, etc).  It really must be possible to 
determine which actual TAP settings function properly and then to 
provide ONLY those as viable Taps choices.

9. Sidetone recovery issues when changing from FSK back to CW (and 
perhaps other modes as well). The sidetone usually does NOT reset 
properly. The problem happens most often when only the main receiver 
goes to FSK and back to CW.

10 Sidetone levels must remain adjustable to compensate for different 
types of headphones etc. (probably a moot point but I've read some 
suggestions to fix its level).

11. Audio Derived AGC feature does not work correctly.

12 DSP Noise Reduction, DSP generated Noise Blanking should work in AM. 
Currently they don't.