For example no user interface yet… Having said that, I think thet the proof is there and this concept is worth developing further.Īt last the snow has melted in Finland. Still quite a bit of development to be done before I can go live with this software. The QSO status is maintained inside a new QSO object structure, and QSO objects are in a dynamic list in frequency order. The implementation is fully scalable with dynamic data structures, audio mixer, etc. The IMD is caused by receiving rig saturating due to very close proximity to my home QTH. This is very valuable since, directives can be given and Tx message can be changed from the user interface, while running QSOs on split frequency. You can see that OH3T keeps on calling CQ on the same time at 2456 throughout the QSO. I was remoting OH3NE and replied by clicking the CQ and then immediately moving the Tx freqeuncy to 2161 from the waterfall window.
![hrd 6 uploads to lotw not showing on server hrd 6 uploads to lotw not showing on server](http://3.bp.blogspot.com/-pJYKmA1MQ2M/UOheeLb85lI/AAAAAAAADUM/8GBhvw8ACnQ/s1600/Ham+Radio+Deluxe+Utilities+(1)_page7_image2.jpg)
In this picture OH3T was calling CQ at 2456 (Hz). Sponsors can be give a special high affinity and they can be worked down even if the “work down” is not checked from the first page.įinally, after several days of work I was able to run the first on-air tests. A nice way to remember them is to give a special treatment at least at some point of the pedition. Note the affinity 50 and affi limit 40 set for “Work Down”.įinally, if you are going to a DX pedition and you have sponsors. On the other hand a special treatment will be granted to OH3T, OH3BK and OH1LXF. In this case all OH9 stations are blocked and also our local clubstation OH3NE. Just set Affi limit to 1 and define Call affinity 0 to certain missbehaving stations. The next tab is an effective and simple way to create for example Blacklists. What if the operator wants even more fine grained control of what stations to work or what stations NOT to work. JAs and VKZL will be also worked Up with higher priority, but they get very exclusive treatment with this setup. Affi limit 0 (Work Up) enables the rest of the world being worked above. If affi limit is set to for example 11 “Work Down” and Japan + VKZL affi limit is set to 12 then ONLY JAs and VKZL stations will be worked DOWN from my CQ frequency. Note that the Affi limit comes to play here.
![hrd 6 uploads to lotw not showing on server hrd 6 uploads to lotw not showing on server](https://s3.manualzz.com/store/data/025738109_1-4a6addba2534a1784e252b014eda5df0-360x466.png)
Higher the affinity level, the more processing priority the call gets.
![hrd 6 uploads to lotw not showing on server hrd 6 uploads to lotw not showing on server](https://slideplayer.com/slide/17296989/100/images/51/Daily+Use+Logging+–+Winlog32.jpg)
The computer picks the right calls from the pileup for processing based on affinity. Affinity to certain calls / geographical areas. I have introduced a new concept that I have dreamed of for many years.
Hrd 6 uploads to lotw not showing on server code#
The user interface code (signals) link back to stub functions to the main code. Hectic user Interface development work is ongoing.