UTC
| SSN: | 122 |
| SFI: | 131 |
| A: | 9 |
| K: | 4 |
JOIN OUR DX CHAT! »news categories
DX DIARY
Recent comments
- R8TX on 7O6T and Israel – Amateur Radio Newsline: Good shot, Nick!
- Henry on A5A – Bhutan: Thanks for activating A5, my only QSO with A5 was with my old friend Jim Smith on SSB...
- Laurie on Images – KL7RRC/P: Yuri & Tim, Great to work you as always. I gotta say it, with a smile on my...
- Nick VK2DX on 7O6T and Israel – Amateur Radio Newsline: Ham Radio enthusiast says: VK2DX – you are right – this...
- Nick VK2DX on Images – KL7RRC/P: Fantastic effort, you’ve made many IOTA chasers happy – well done....
- iain - N6ML on A5A – Bhutan: Hmmm.. the survey forces selection of at least one mode … I have all three...
- Cezar VE3LYC on Images – KL7RRC/P: Exceptional effort, under very difficult conditions.
Propagation
Helpful links
Blogroll
TX7M, TX5A & TX3T – Marquesas Island & TahitiThursday Oct 20, 2011
TX7M – Marquesas Isl OC-027 hit the bands starting at 0435z on 14197.7
Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.
Team consists of Oleg R3FA, Alex UT5UY, Serge UR5MID, Michel FO5QB, Oleg US7UX, Mike RU3UR, Alex US0KW, Andy UU4JMG, Alex UX0LL, Andy RK7A and Leo UA7A will be active on all bands, all modes as:
- TX7M - October 19 to November 1, 2011 from Hatiheu, Nuku Hiva, Marquesas Isl.
- TX5A - October 28 to October 30, 2011 from Hatiheu, Nuku Hiva, Marquesas Isl. (for CQ WW SSB)
- TX3T - October 16 to October 19 and November 1 till November 4, 2011 from Papeete, Tahiti.
Marquesas Islands FO/M is ranked #26 in EU and #36 in the World’s Most Wanted List (by www.clublog.org statistics). The team will make a special attempt for LOW Band activity. The team invite organisations and individuals to make a donation towards the cost of this operation. TNX to everyone, who has supported already.
Updates in real time (and online log) will be published on the official website.
33 Responses to “TX7M, TX5A & TX3T – Marquesas Island & Tahiti”
Leave a Reply
all rights reserved © 2012
Any unauthorised use of our text, photos and information without written permission prohibited!
TX7M 15.10.2011 – photo from airport Borispol http://hfdx.at.ua/photo/tx7m/58
Online log for TX3T is up – http://tx7m.com/log.php
I am very sorry to report that the TX7M operator on 15m CW has been making QSOs for more than 25 minutes WITHOUT once sending his call (only TU UP). IMHO, this is arrogant, LID operating – apparently to try and create a larger pileup and/or boost rate for some ego purposes. Bad, bad, bad operating – really bad ;-(
And now later the 20m CW operator made 22 QSOs WITHOUT signing the callsign (only TU UP). This is not typical FB Russian operating and only creates confusion to those without packet cluster access. I hope someone from the homeland can straighten these guys out.
Let’s count “Happy Calls” in the online log, not minutes and QSOs. They are ANTIPODES for all in EU. Propo window is extreamely short. Let EUs write their comments! Anyway, tnx Rick for your minutes to count minutes & QSOs
working on 17M 18.167.7 is out of the band in any country on USB
300 cycles below the top of the band with a radio with a minimum bandwidth of 2.4 khz is “OUT OF BAND”
Be much easier to spin the dial if they don’t adhere to your strict operating standards.
I understand the Antipodes QTH premise theory, Andy, but must respectfully disagree with the rationale for several reasons.
The DX-Pediton operator’s responsibility is to eliminate or at least minimize confusion. No skilled DX’er or IOTA Chaser I know would ever rely on a packet cluster post to validate having worked a new DXCC/Band Country or IOTA in their log.
Not everyone has access to, or uses, cluster system. So the only option some choose is to blindly call a non-ID’ing station in a pileup. In one listen today on 24Mhz, I noticed TX7M ID’ing every 20 QSOs, but also responding with ‘QSO BEFORE’ to a number of callers. Not a good sign. Especially, since mostly W/VE QSOs were being made during this period. So much for the Antipodes case.
The DX CODE OF CONDUCT Item #3 states: I will not trust the cluster and be sure of the DX station’s callsign before calling.
The DX-PEDITIONER’S CODE OF CONDUCT states: Announce your callsign frequently like (almost) every QSO.
I think most reasonable operators recognize that ID’ing every 3 to 5 QSOs is pretty much the standard depending upon the pileup. But when the op is sending 32WPM with a short 4 letter call, only giving the ID every 20 QSOs for whatever excuse is out-to-lunch. The first 25 minute period I referred to in a previous post actually ended up being over one-half hour before I turned the radio off.
This has certainly been the week for out-of-sync operating by DX-Peditioners. One of the 3XY1D ops was similarly making 20 QSOs with signing his callsign, but worse yet, while working split, was only ending each QSO with TU (omitting the UP). The consequences were on-frequency callers, and a bunch of QLF ‘Cops’ who could not even send UP without making a mistake.
The lack of R-E-A-S-O-N-A-B-L-E interval DX station callsign ID forces those who believe in ‘copy what you hear’ to sit and wait and wait and wait for a callsign ID *BEFORE* calling wilst the pileup continues to grow due to the mushrooming packet cluster point-and-click crowd. This is blatant poor operating by the DX Station ;-(
Obviously, W7WQ doesn’t ‘get it’… read the DX-PEDITIONER’s CODE OF CONDUCT, OM.
http://dx-code.org/DXpednew.htm#announce
73/DSW…
Rick, K6VVA
I’m sorry but I think the lack of frequent ID by the DX is such a tiny problem to complain about and I can’t believe someone is actually monitoring this in such detail.
Be thankful these ops are there in the Marquesas doing this. They are really doing very well. Better than many I’d say.
I’d agree that frequent id is just good operating practice, and rather than taking away from the throughput actually enhances the actual experience of all involved. With todays computerized operating, it’s so easily programmed in. I remember one of the DXpeditions last spring id’d at the end of each contact – “TU TX7M UP” and I remember how impressed I was with the way they worked.
Granted, in the overall scheme, it’s great to have this one on the air, but that slight tweak would make it even better.
Rick and the others, TNX for your time!
1) Issues related ID’s, 18167.7, CW speed were transferred to Dxped, so, expect the case will be solved.
2) The team did not accepted the DX Code, due to the fact that most of the last Dxpeds, used the DX Code as a “weapon” vs “DX hunters”.
Most of them have OQRS with the commercialization QSLing rule “from the five ($, etc..) to the sky”… With LoTW period from 6 months to 1 year and … DX Code has only obligations to the hunters, but none to DX peds in such subjects as QSLing, Propagation knowledge, Proper antennas layout, etc.
So, let DX code becomes “true and equal” for everyone! Hope, it happens one day! Good luck to everyone with TX7M!
to Larry Skylton
You are not ritht:
working on 17M 18.167.7 is out of the band in any country on USB
300 cycles below the top of the band with a radio with a minimum bandwidth of 2.4 khz is “OUT OF BAND”
There are upper FRQ 18168.0 and USB mode legal in my licence.
I will able to transmite on 18168.0 USB,It’s 100% valid,IMHO.
Buy
Wow.
I agree with Rick. A good DX operation gets calls in the log quickly and efficiently. That means good pileup control and frequent IDing. If I hear a DX station going on and on with out an ID I will jump in and work the guy only to ask “What’s your call?” I’ve now wasted his time and mine, and if it’s rare then someone won’t get in the log who wanted to be there. That’s just poor operating practice.
Thanks for passing on the request to ID more often!
73, Alan AD6E ex K7C, TI9M, P29NI, /DU3, /KH9
More frequent ID is certainly appropriate. I haven’t heard any of the issues listed above, and I have worked them on every band slot. Let’s not forget…this isn’t life and death…it’s supposed to be enjoyment – let’s get out there and have some fun!
Good luck and good DX my friends!
Andy, RZ3EM: see ‘DX Code of Conduct’ section for DXpeditioners: http://www.dx-code.org/DXpednew.html
I believe that poor pile-up technique sometimes causes the chaos. Infrequent identifying causes irritation and frustration, leading to increased chaos.
73 de Roger/G3SXW.
Hi Roger!
Was great fun to meet You on MK convention!
Sure, your preparation to give me EL on 160 and 80 goes well! ;)
As everyone can note there are no open issues now, related TX7M activity mentioned above. ID’s, QRQ, band freqs – are Ok. But, as I wrote above, DX code mentioned NONE words about “user friendly” = no cost for everyone = LoTW, eQSL, etc = QSLing policy. Requiring no time, no expenses for paper QSLs preparation, MNGR work, etc. Let’s check the site of DX Code, DX peds supported part, I read too often last days the complains from the people, who used OQRS, but NEVER received the QSLs from the list of DXpeds! Accepted DX code. That’s true of the life! So, MNI TNX to your team and to the others, who has been going to keep the true HAM spirit. Operate for own fun, and for people quick DXCC satisfaction (rapid CFM via LoTW, etc)
DX Code of Conduct is useless without section about QSLing. We should STOP selling of QSLs for 5-10 USD ! Every expedition and manager must provide all types of QSLing: buro (free, on request), direct (with return postage only, not extra cost for vacation, accomodation, e.t.c.) and LOTW (who want, some HAMs do not like new style qsling). Donations are not reason to QSL or not to QSL.
Guys, cut these folks some slack……. I have contacted them on several bands and modes….. and they ID pretty regularly. I listened for the call due to the fact that there were other “T” calls out there at the same time and wanted to ensure I had the right guys. I did and I knew it because they were IDing. So I am not sure what you folks are talking about. My biggest complaint are all the stations that do NOT listen to the DXped operators. Like the ones who call on top of the station when anyone, who is actually listening before transmitting, would know they are operating SPLIT! LISTEN!
Nice contact. Was just tuning and found the FB signal on 14.025. Keep up the good work and 73′s
TX7M is QRT at 16 UTC on 01 Nov 2011 with result 79,647 QSOs (+5725 QSOs as TX5A). TNX to Everyone, who helped us with Pile Ups, donations and kind words!
Wish to thank everyone who made this expedition possible.
I made 7 QSO’s in SSB and some of them I thank the cluster that has been a great help, hence the propagation windows are very short and fly away very fast.
Thank you guys for the chance you gave me!
Great job. Sometimes towards the end, it sounded like you were very lonely, since you’d worked so many stations on so many bands, there wasn’t as many trying to find you. I never found you on 20 ssb, and couldn’t hear you on 80 ssb, but got all the other cw and ssb slots, and one rtty.
Thanks, and I hope you had the trip of a lifetime
Great job , thanks for the qso and this new one on 80 m cw
ALL the TX7M QSOs are finally in LoTW now! It was a 1,5 days delay due to LoTW overload. The team hopes – the best end of good Dxped is prompt, true and equal QSOs confirmation, specially in spite of DXCC year end score update. Meantime, the team is still in Paris, and only today some members will arrive home in Kiev.
Thanks for great DX-pedition guys! Great sigs on higher bands. 3 new bands for me: 10,12 & 15 meters. Thanks also for very fast LotW confirmation. Other expeditions can learn from you. CU on the bands.
73 de Zlatko, 9A2EU
All the TX7M & TX3T QSOs are in eQSL now! Scans of licenses were sent to eQSL to get asap the AG status.
Andy,
Many thanks for the TX7M QSO’s and posting to LOTW.
Will the TX5A QSO’s be posted to LOTW?
Hello Jim,
TX5A will be posted to LoTW after CQ WW 2011 SSB logs dead line. TX3T QSOs were uploaded more than 24H ago, but not yet appeared.
TNX for the Warm words to the team.
Regards, Andy RZ3EM
Andy,
Very good. Thanks for the information.
73,
Jim N6VH
It’s finally happened! TX3T QSOs are in LoTW now! After 6 days delay due to LoTW servers overload. Enjoy!
I did not find my eQSL (TX7M) …
Did anyone report same problem, or shell I wait a few days more ?
Thank You!
73, Vlatko, 9A2TD
No eQSL or LoTW from TX3T ….
(TX7M – LoTW only few weeks ago) ….