I am still struggling with this rotator issue, any help please?
Вид для печати
I am still struggling with this rotator issue, any help please?
Alex hi
Maybe it would be interesting for users of your programme to improve the reception of telnet DXCluster spots for interested group of users of POTA and SOTA programme. On the S50CLX DXCluster I have implemented the integration of spots that are not part of the classical telnet DXCluster network. More in my note below. The user of your programme would thus have the possibility to select in the programme the reception of specific spots via a button, with predefined commands to be sent to the S50CLX DXCluster after a successful connection. Sorting, searching by reference ... etc is a matter of implementing of LogHX. The idea for the button is:
1. POTA ONLY spots -> command executed: ACC/SPOTS INFO -POTA-
2. SOTA ONLY spots -> command executed: ACC/SPOTS INFO -SOTA-
3. BOTH POTA&SOTA spots -> command executed: ACC/SPOTS INFO -POTA- OR INFO -SOTA-
4. S50CLX CLUSTER DEFAULT (all spots) -> command executed: CLEAR/SPOTS ALL
A connection via telnet protocol to S50CLX s50clx.infrax.si:41112 which is a completely free service is required to receive POTA/SOTA spots.
Good luck, Dan S50U
************
POTA and SOTA enthusiasts!
POTA (Parks On The Air) and SOTA (Summits On The Air) are internationally renowned programmes. They encourage licensed radio amateurs to operate outdoors in nature parks or on mountain peaks. Operators making contacts in parks or on summits are called activators, and the other operators who contact them are hunters.
On the S50CLX telnet DXCluster I implemented the collection of spots from POTA and SOTA that are not part of the classical telnet DXCluster network (potaapp and sotawatch). Such spots are tagged with [-POTA-] and [-SOTA-] respectively. In the comment field a spot tagged as such carries:
POTA:
- International POTA reference number, example: SI-0831
- Mode of operation, example: CW
- POTA reference name, example: Preval Vrh Ravni
SOTA:
- International SOTA peak reference number; example: S5/CP-002
- Mode of operation; example: SSB
- SOTA summit name, altitude, points; example: Porezen, 1630m, 8 points
With the right settings, the exact DX spots you want can be received and this is achieved using the filters below. To change an existing filter, simply overwrite it with a new command. Each command (BOLD formatted text) must be entered on a new line, confirm the entry by pressing ENTER.
- for receiving only POTA spots, command: ACC/SPOTS INFO -POTA-
- for receive only SOTA spots, command: ACC/SPOTS INFO -SOTA-
- for receiving POTA and SOTA spots, command: ACC/SPOTS INFO -POTA- OR INFO -SOTA-
The CLEAR/SPOTS ALL command removes all set filters and the S50CLX passes us all SOTA, POTA, DXCluster and optionally RBN (SET/SKIMMER <mode>) spots.
In cases where you do not want to receive POTA and SOTA spots e.g. in a contests, use the command as the first filter before all others REJ/SPOTS 1 INFO -POTA- OR INFO -SOTA-
Spot forwarding is based on the DXSpider DXCluster software validation and normalisation algorithm, rejecting duplicates spots and ensuring quality spots in the face of increasingly frequent malicious attacks on global amateur radio DXCluster network.
The S50CLX DXCluster can be reached via telnet at: s50clx.infrax.si port 41112
My small contribution to the promotion of outdoor activities in POTA and SOTA hamradio programmes. :-)
Spread the news, thanks
73 Danilo S50U sys S50CLX DXCluster
p.s. The information is also published on the Radioklub Cerkno S50E website https://s50e.si/pota-sota-dxcluster/
Is there a way I can send each QSO automatically to an SQL database?
SQL database or eQSL service?Цитата:
Сообщение от M0CGF
• Отправлено через приложение Tapatalk на Android | 73 de RC3C/m.
I want to create my own local SQL database and run some stats for my club contest. Also I want to learn more about SQL, this would be a good way. I'd only want to send date,time on, mode,band,P150C,locator
As I know all #QSO data is stored in MS Access files like .mdb ones. I am thinking that you can parse files (by some scripts or so) to get needed data for your SQL database.Цитата:
Сообщение от M0CGF
• Отправлено через приложение Tapatalk на Android | 73 de RC3C/m.
I guess. I used to run the English Castle Awards (WCA) database for all the UK hunters so I had manual log uploads working. That scheme closed but it got me interested to see if I could generate my club monthly contest stats automatically. As now I export to excel then manually(with a few macros) sort the data.
Hello,
I am sorry, but version 777 does not work for me - CAT is faulty, does not read radio, does not control radio (Omnirig and FT991A or IC-7100). Installed back 776 and all is OK.
73 Josef OK2WO
Fixed in build 778!
I can confirm - build 778 works well! Thanks and 73 Josef OK2WO
- - - Updated - - -
A little problem: Autocq does not repeated. The same from macro [AUTOCQ] as from Alt+R. Button CQ is red, delay is 5 sec. What is wrong? Josef OK2WO
Here -Цитата:
Сообщение от Josef
Вложение 370121
change RX/TX? AutoCQ is not work if log not receive RX/TX signals for TRX.
Since v777:
- Network error : messageclient exeption UDP server 127.0.0.1: 2237
- Drop.Win32.ScoreSelfDel.915434 inside the exe (F-secure), not before V777
73, Thierry.
Thank you for the help. Now worked with FT991A. I have to set RTS handshake ON in Omnirig and radio. 73 GL Josef OK2WO
Hi Alexei.
An error message is displayed when LogHX (builds 777 or 778) is used with JTDX v2.2.160-rc3 in ‘JT/FT-modes active calls’. The message ‘Network error: MessageClient exception: Invalid message format UDP server 244.0.01:2237’.
JT/FT-modes active calls' also does not work correctly with MSHV 276_rc2 (UDP Multicast 224.0.0.1 port 2237), but no error message is displayed.
I've reverted to the previous version 776.
I hope this information can help you debug the new build.
Thank you for your tireless work with the LogHX.
73 of py5ej,
Pavanatti.
Pse QRX! I'm trying to find a mistake because I don't have one.Цитата:
Сообщение от F5MXH