OmniRig Tester's Guide INSTALLATION 1. Make sure that you have only one copy of OmniRig on your system. Close all programs that use OmniRig, such as BandMaster, HamPort, MixW and Client.exe, then uninstall or just delete all copies of OmniRig. 2. Download and install http://www.dxatlas.com/OmniRig/OmniRigSetup.exe . This will place OmniRig in the "Program Files\Afreet\OmniRig\" folder. 3. Place the new INI file that you are going to test in the "OmniRig\Rigs" subfolder. CONFIGURATION 1. If you are testing OmniRig with an ICOM transceiver, disable the CI-V Transceive mode in your rig. 2. Start Client.exe. 3. Click on the Open Dialog button. 4. Select rig type and set the COM port parameters. Do not change Poll Int. and Timeout. TESTING 1. Turn off the rig, start Client.exe. 2. Check the Rig Type and Status labels on the upper panel. The correct rig type should be displayed, and the status should be 'Rig is not responding'. 3. Check the Parameters panel. A color box to the left of each parameter should be black if the rig has a command for reading this parameter, and gray otherwise. The Set button to the right of the parameter name should be grayed if the rig does not have a command for setting this parameter. Compare the state of boxes and buttons to the list of commands in the transceiver's manual. 4. Turn your rig on. The Status label should change to 'On-line'. If another application is using the selected com port, the status should be, 'Port is not available'. When you close that application, the status should change to 'On-line' immediately. Compare the state of the color boxes to the actual state of the rig. 5. Using the controls of the transceiver's front panel, change each of the supported parameters and see if the changes are reflected in the program. 6. Change each parameter wit the Set button and see if the state of the transceiver changes accordingly. 7. Start two or three copies of Client.exe and see if they have simultaneous access to the rig. REPORTING ERRORS It is more than likely that something (or everything ;) will not be working. I developed and debugged the code using my TS-570. For all other models, all I had was the documentation that I found on the Internet - incomplete, ambiguious, and full of errors. It will help me a lot if you generate an error log and send it to me along with the error description. To enable error logging, stop all programs that use OmniRig and add the following lines to the OmniRig.ini file: [Debug] Log=1 The log file (OmniRig.log) is created in the OmniRig directory upon the exit from all programs that use OmniRig, and is cleared on the next start of the program. If Client.exe crashes before it has a chance to create the log, enable the incremental logging mode: [Debug] Log=2 In this mode, the log file is closed and re-opened after each write operation. MORE INFORMATION All currently available information on the Omni-Rig project, including the latest versions of the code and rig description files, is available at http://www.dxatlas.com/omnirig . Please send your beta testing reports and comments to ve3nea@dxatlas.com . ACKNOWLEDGEMENTS MNI TNX to Alex RZ4AG for coordinating the efforts of beta testers. MNI TNX to all beta testers! 73 Alex Shovkoplyas, VE3NEA