Seite 1 von 1

ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 01:07
von oz1bii
Hi
I use the ClubLog UpLoad but are missing some ADI tags.
The <OPERATOR:xx> tag

Do you have a list of which tags UCXLog sends to ClubLog?

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 08:14
von DL7UCX
Hello Henning,

UcxLog uploads these fields to Clublog:
call
band
freq
mode
qso_date
time_on
rst_sent

What do you want to upload with the "OPERATOR" field :?:

This is defined as the "logging operator's callsign".
UcxLog uses the callsign of the actual logging operator already as "own callsign" for Clublog login/upload :!:

73 Ben

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 09:17
von oz1bii
Hi Ben
I want to log the Operator. The one set by the program.
Reason.
We are more ops using the same call and want to see who on the download from clublog.

By the way it would be nice if it also are oncluded in Adi export. Especilly in Multioperator.

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 09:58
von oz1bii
Hi again.

ADIF 3.0.4. Specification:
"OPERATOR - the logging operator's callsign
if STATION_CALLSIGN is absent, OPERATOR shall be treated as both the logging station's callsign and the logging operator's callsign"

So it would be correct to implement both.

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 10:34
von DL7UCX
Your used call sign during logging is sent to Clublog OUTSIDE of ADIF data, it is an extra required PHP upload parameter.

What will you say with (the same!) OPERATOR callsign :?:

73 Ben

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 11:08
von oz1bii
What will you say with (the same!) OPERATOR callsign :?: ???

It is NOT the same.
OPERATOR is the actual operator.
The used STATION callsign is the used call sign.
See document

http://oz1bii.dk/documents/UCXLog%20Operator.pdf

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 15:49
von DL7UCX
Sri, it is difficult because the "Operator" is used for different situations in UcxLog.

We have 3 valuess:
- Main_Callsign :- This is from field "callsign" in "Settings-Station-General" while "Chief-Op" is selected
- Operator_Name: Selected field in Settings-Operator
- Operator_Callsign : This is from field "callsign" in "Settings-Station-General" while Operator_Name is selected

In the moment UcxLog uses for Clublog upload only the Operator_Callsign.

If you work at a club station, you have for example
- Main_Callsign: OZ90EDR
- Operator_Name: OZ1BII
- Operator_Callsign: OZ90EDR
For Clublog must be used:
- Log parameter Callsign: OZ90EDR
- ADIF STATION_CALLSIGN: OZ90EDR
- ADIF OPERATOR: OZ1BII

But if you use the operator for a portable operation, you have for example
- Main_callsign: OZ1BII
- Operator_Name: FYN
- Operator_callsign: OZ1BII/p
For Clublog must be used:
- Only Log parameter Callsign: OZ1BII/p.

Some users defined a senseless operator with Operator_Name = Main_Callsign = Operator_Callsign.

I will add a new field in the Clublog window for "Operator" and
initialize it with the operator name, if it is a valid callsign and different from Operator_Callsign.


73 Ben

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 16:35
von DL7UCX
New field in the Clublog window for "Operator" added in Version 7.71 Beta 7.

If "Operator" is used, these ADIF QSO fields will be added
STATION_CALLSIGN
OPERATOR

Please check entry for "Operator" in the Clublog windows before upload.

73 Ben

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 16:41
von DL7UCX
Henning, for what is the "Operator" entry in Clublog needed ?

73 Ben

Re: ClubLog ADI tags

Verfasst: Mittwoch 4. Januar 2017, 17:53
von oz1bii
Hi Ben
YES it is working perfect.

The reason is that we do have this special call OZ90EDR througout 2017.
Read more at http://www.oz90edr.dk
All the operators uploads there logs to the same Clublog acount and then we download the whole log from Clublog.
To see who have uploaded the QSOs we only have the OPERATOR field.

So thank you Ben, for your always quick response and great help.
Happy New Year!