As most of you know, I'm in the early stages of rewriting N3FJP software in C#.NET to make certain it will be compatible with operating systems beyond Windows 8.??I've started with one of the hardest parts - rig interface, because it is really hard to do without the actual rigs connected to test.
I put the e-mail below out a few days ago on the Users group ().? While I've had a lot of great response and I think we have all?Kenwood and Icom rigs working fine, there are still a number of Yaesu and Ten Tec rigs that I haven't received reports for.? If you have one of these models and would take a few minutes to give it a test run, I would really appreciate it.
Speaking of beta testing,?I know some of you are very interested in beta testing and software development, so I've created a separate group for those interested in software development and would like to help with beta testing:
All are welcome and invited to join the new group and your help will be very much appreciated!
Hi All,
After weeks of work, I finally have a C# version of the rig interface code ready for beta testing. Every line of code is new, even things most folks take for granted like sizing for user's resolution.
This form was the single most difficult and time consuming part of developing our logging software in VB6 the first time around, so I've decided to try and knock out one of the hardest parts of the C# rewrite first.
I have only been able to test it on Kenwood and Icom radios here, which is just two of the 17 rig options I've rewritten code for. Quite frankly, I'll be amazed if any of the other options will work at all. Things came to light in how C# handles characters differently than VB6 only when the rigs were actually connected and I could see the data. Since I suspect you would much rather have me ship my code to you for beta testing than for you to ship your rigs to me, I will really appreciate your help in working out the bugs that are bound to currently exist! ;)
Please install the program by clicking on this link:
The program should detect and list your available Com ports.? Please select the port you are using for rig interface.
If your rig is on the list, please select it and give it a try (Icom and Kenwood users, please send me your reports too. Confirmation of my tests will be comforting with those two rigs).
- Please test your ability to poll the current frequency and mode (PH or CW will be returned.? Other modes will be added later).
- Please enter a frequency in the CW portion of an Amateur band and click Send. Your rig should read CW. Then enter a frequency in the phone portion of any band. Your rig should switch to the appropriate sideband when it tunes to the frequency you enter.
- Please try clicking on the mode buttons to change modes (without changing frequency).
- After your tests, success or fail, while you are polling your rig, please click the Copy Data to Clipboard button and e-mail me the results. As long as there is buffer data, it should be helpful in working out the bugs.? Also let me know if the change frequency and mode functions worked properly.
If your rig is NOT on the list, but you would like me to add it.
- Select Other from the rig list
- Check your radio's manual for the command to poll the frequency from your rig
- Enter the command in the Command field (For two character hex commands, include spaces between each two character set (click on Icom for an example)).
- If your rig requires two character conversion to hex, make sure the conversion check box is selected. Otherwise, deselect it.
- Click Test. Once you have your settings properly selected, data will at least be returned to the buffer (I've verified that works here). Once data is being returned to the buffer, click the Copy Data to Clipboard button and paste it into an e-mail, along with the specs from your manual that I'll need to decode the data. I can't promise, but I'll do my best. Again, having your actual buffer data to work with will be a great help.
All, thanks so much for taking the time to test this section of code. With all the various rigs and protocols out there, there is no way I can do it here without you. As the inevitable problems emerge with specific rigs, I'll attempt fixes and send the updates along for your additional testing.
