[Peter VK3ZPF]

Hi Andrew

Thank for your reply

Could you please confirm <MODE:12>DIGITALVOICE <SUBMODE:5>DSTAR been implemented?

This ADIF change is part of ADIF Version 3.1.3

Cheers
Peter VK3ZPF

[Peter VK3ZPF]

Hi Manfred

The correct date is 31 January 2024.

[Peter VK3ZPF]

Hi Andrew

I am about to release an updated version of VK port-a-log and I’d like to ensure the data included in the WWFF export file will be accepted in to Logsearch without error, where possible.

Is there a list of ADIF modes, in particular related to the various digital voice modes, that Logsearch accepts or does it strictly follow ADIF V3.1.5 as updated 28 Novemeber 2024?

Cheers
Peter

[Peter VK3ZPF]

Hi Robert.

I do double activations on FT8 for SOTA and WWFF and I usually post a spot on the relevant spotting pages and then work the stations as they arrive.

If contacts slow down a little, I’ll run CQ SOTA VK3ZPF QF21 for 3 or 4 cycles then CQ WWFF VK3ZPF QF21 for 3 or 4 cycles then go back to CQ VK3ZPF QF21.

I also find FT4 is effective and takes less time per QSO than FT8, but I often forget to do FT4.

I hope this helps.

[Peter VK3ZPF]

Hi Andrew

Is there an update regarding <MODE:12>DIGITALVOICE <SUBMODE:5>DSTAR implementation?

Cheers
Peter VK3ZPF

[Peter VK3ZPF]

Hi Andrew

Today I tried loading a log of 58 QSOs that had 6 QSOs with <MODE:12>DIGITALVOICE <SUBMODE:5>DSTAR but these QSOs were not created.

I subsequently changed the QSOs to <MODE:5>DSTAR and uploaded the 6 QSOs in a different file and they were accepted OK.

Has <MODE:12>DIGITALVOICE <SUBMODE:5>DSTAR been impelmented?

Cheers
Peter VK3ZPF

[Peter VK3ZPF]

Hi Andrew

Thank you for your assistance – all good now.

Cheers
Peter VK3ZPF

[Peter VK3ZPF]

Hi Graham

The MRPA is an award for those who activate or hunt parks along the Murray River in Victoria, New South Wales and South Australia.
There are six stages to this award.
Details can be found at https://www.wwffaustralia.com/murray-river-parks-award.html

[Peter VK3ZPF]

I too have seen strange behavior regarding log file names.

Yesterday Logsearch said it was rejecting a log file due to a name issue, despite the name meeting the name convention {callsign} @ {reference} {date}.{extension} but the file was still accepted for upload on the QSOs were added to Logsearch.

VK port-a-log names the file as {callsign}@{reference}_{yyyymmdd}.adi
e.g. VK3ZPF@VKFF-2224_20200111.adi which, up until recently, have passed the Logsearch upload process without warning.

Please advise if the {callsign}@{reference}_{yyyymmdd}.adi is no longer acceptable.

73
Peter VK3ZPF
VK port-a-log author

[Peter VK3ZPF]

Hi Adrian

We are currently reviewing the MPRA and this includes lifting the maximum number of parks available.

We should have this issue resolved in the next week or two.

Peter VK3ZPF

[Peter VK3ZPF]

I checked the ADIF standard at http://adif.org.uk/ and found that JS8 needs to be entered in the log as MFSK.

Once logged as MFSK the log loads into Logsearch without issues.

[Peter VK3ZPF]

Hi Adrian

Is it activator or hunter that is different?

For activator VKFF needs 10 QSOs for qualification and WWFF needs 44 QSOs.

For hunter WWFF shows all refs chased, while VKFF only shows VKFF refs.

Or – maybe it’s somethings else.

[Peter VK3ZPF]

Thanks Bob.

The WWFF NATIONAL PROGRAMS link goes to https://wwff.co/wwff-country-divisions/ and this returns file not found when I try from here.

[Peter VK3ZPF]

For P2P contacts do the call signs need to match exactly or are additions such as /P or /M ignored?

[Peter VK3ZPF]

I have a similar issue numbers along side are 63/87 but “No results for Award P2P-A-44 (WWFF P2P References) is returned”

Peter
VK3ZPF

[Author]

Posts