Logging Queries

Tuesday Jan 22
Logbook Issues
Petrus has been on Bouvet for just over a month now. Within that time, he’s made some people very happy with a new one. We completely appreciate he’s not been as active as perhaps we thought he would, but as has been stated by Petrus himself, sometimes his working day can be as long as 16hrs. Of course, ham radio is secondary to this.
When Petrus is on air, he’s doing very well as a newcomer to the hobby. Not only in handling pileups and working split, but logging too. There’s an art to being a rare/much wanted DXpedition operator, and he’s not doing too badly. I’m sure you’ll agree.
This updated page is to do with logbook queries which are occuring daily. Either on site or via email to team members. First of all, we’d like to apologise for a small glitch in the logbook program software which showed two or three callsigns differently to how they were orginally. This has been resolved and i’m certain the problem will not arise again. We do know a couple of you were anxious to see this fixed!
Secondly, and perhaps most importantly, the issue of part or wrong calls in the logbook. It should be explained that Petrus sends his logbook generally every two or three days (sometimes sooner) to be updated. Stan, SQ8X then does his wizardry and enables the logbook to be displayed instantly. It’s when the logbook is “live” that some of the issues appear. Some from being a missing letter in the prefix, omitted letters in suffix or prefix, or even missing callsigns altogether. For this reason alone, we’ve decided to disable the partial call check, for reasons explained below.
Petrus promised Rhy, ZS6DXB before he left for Bouvet that he would thoroughly check his logbook on arrival home to RSA - this is where we have to draw a line under anymore queries. Petrus has the last decision to correct his log. It would be easy to just change a small error to the correct call in the log. Indeed, some have looked obviously incorrect, and that operator has been in touch to confirm our suspicions, but some have been in contact with the team also saying they are not even in the log, but were sure they’d worked Petrus. We honestly know as much as you with regards that.
This is where you can help yourself and Petrus/3Y0E team. Record your QSO with Petrus or similarly do what Volker ZS1Y did, record a whole episode of 3Y0E working the world. There is no better proof than hearing yourself working Petrus - without proof the team are unable to fix the issue, and unfortunetly you will have to wait another 3 weeks or so before Petrus returns home to confirm or not your call is in his logbook.
We will keep this page open for queries, whereby future logging issues will be available for Petrus to look at when he returns home, and subsequently deal with them.
73s
Col, MM0NDX
Webmaster: 3Y0E.COM
(on behalf of team)

Hi, I think you may have me logged incorrectly as WD2CQB. If it could be corrected to WD8CQB I will feel O-SO Much better! Thanks again, Tom
Hi,
Thanks for QSO 2008-01-20.
could not get a correction from SP7BZV TO SM7BZV.
Appears on the audiofile, great!
Hope to see You on more bands later.
73 Jerry/sm7bzv
Jerry, I’ve heard you/Petrus loud and clear last night working each other, so this could be a double check then.
73 de Stan SQ8X (ex SQ8AQD)
Hi
My compliments for Petrus, he’s doing VERY well indeed operating from one of the most wanted DXCC. His operating skills meets our expectations for a DX op by far.
Congrats and God Bless,
David HB9TMW
The QSO from 20.01.2008 at 18.02 UTC is not in the Log?
73 from DL9UBF, Bernd
Hi Bernd
Within the past week or so, a few others are also wondering where their call is in the logbook.
Like you, we honestly do not know.
We’ve made a list of all callsigns who have queried.
This list will be kept until Petrus returns home, then sent to him, whereby he can again check his log, with the help of Pilot Station ZS6DXB.
It’s very unfortunate some will have to wait until 3Y0E QRT’s from Bouvet, but at this moment there really isn’t a lot we can do.
Hope you understand and appreciate the difficulties at times.
73s
Col MM0NDX
Webmaster: 3Y0E.com
Will contacts be confirmed in LOTW?
Hi Robert.
LOTW uploads have been mentioned previously
I think at the moment this is unlikely to happen.
When Petrus is home and meets up with Rhy ZS6DXB, i’m sure more info will be forthcoming regarding this..
73s
Col MM0NDX
Webmaster: 3Y0E.com
Hello Petrus,
yesterday on 29.01.08 you called me up three times at 20:41 UTC.
My report was 4 by 4.
The QSO is not in your log.
Please be so kind and check your log.
Good DX and vy 73 de Peter, DH1PS
Hello
All log queries will be revised after Petrus arrival to RSA around Feb. 20th.
thought I heard you and put you in the log at 1951 gmt
today. You were light hope it was not a pirate…
note VP8LP was 59+ at 23:10 gmt..
73 and tnx for being there
Ed NX7TT
Idaho Falls, Id
Hello,
just looking online log and there is not my call there 4O/YT1HA
qso was 2.2.2008 19:20 gmt rst 55 rcvd 55
73 Zik YT1HA
Hi,
On 31st Jan I worked Petrus at 14:57 with 55 rst both ways but my call does not appear in the on-line log.
73’s Alan GM0HTT
Hello Alan
I’m sorry to say that but Petrus didn’t operate on Jan 31st at all. You’ve been cheated by a station pirating his call then….
Hi,
0n 01st feb i worked Petrus at 20:38 utc 56 rst.
but my call not appear in the log.
Is possible recheck.
Best 73′ de Tony IK8VRH
Dear Petrus,
I believe I worked you on Sunday, Feb 3 at 18:36 Z. The signals were 57. I do not find myself when the auto search is carried out so will you kindly check the log for this time. Thank you regardless for all you have done for us all.
73 Doug EI2CN
Dear Petrus,
I have checked your on line log once again and find that EI1CN is listed. As this operator no longer resides in Ireland, I wonder if you do not have my call recorded in error? Glynn now lives in the States and a one can look like a two if originally recorded on paper. Thank you for your consideration - I am a bit anxious as tomorrow you are closing down. Again thank you for all you have done for our hobby.
73 Doug EI2CN