Looks like I’ll be making another pass through the WSJT-X documentation I’m hosting and should have some clarifications and *maybe* another helpful guide sometime in the first quarter of next year.
Also, I have some more to write about regarding the trip to Wallops and my experience as a NASA Social Media Commentator for you, soon. I’ll give you the real skinny on how AMSAT, and especially the ARRL, blew any credibility they had for news reporting when the Antares disaster happened; you’ll also get a bit of insight as to why AMSAT is losing members, too. I think it’s a neat story, and probably one most amateurs wouldn’t otherwise be aware of.
Recently, I got the chance to participate as a NASA Social Media Commentator for the Antares launch from Wallops Flight Facility, VA. As you have no doubt heard, the flight did not go as expected and some, as yet to be determined, anomaly caused the vehicle to crash. It will be some time before any real reasons reveal the cause of the launch vehicle failure. So, in the meantime, please enjoy my collection of photos I’m posting of the different toolboxes and workbenches I saw around the facility on my tour.
If I learned a lesson, it’s that I need a new camera. Please enjoy the blur!
I have been invited to the Orbital Sciences Corporation’s Antares launch (presently 10/27, but subject to change) at NASA’s Wallops Flight Facility in Virginia as a social media commentator! I’ll be located within the press pool, get to view a night launch, and take a tour of NASA’s Wallops Flight Facility! For someone who went to Space Camp as a kid (that’s right, I’ve got the nerd cred), this is simply a dream come true. I’ll be delivering the social media goods, cats and kittens, so please keep your dials locked to the left, but right on me!
(N.B. The User Guide is going through changes as the RC is tested and feedback returned to the developers. That said, my own work won’t finalize until the developers push out a stable volume; please consider all of this a work in progress until then.)
The WSJT-X v1.4 Beta is due out October 1st, and it is coming packed with new features, hopefully more stability and an updated User Guide.
Unfortunately, the present User Guide leaves a lot to be desired: it doesn’t appear to have been checked for grammar or spelling, contains references to unfinished (or unattempted) sections, introduces terms and then never explains them, it includes the rife use of jargon which is also never explained and lastly, the User Guide is inconsistent in terms of formatting, voice and consistency- which were K1JT’s own criteria for this document. If he can’t get his own standards right, I don’t know who can!
Sensing an opportunity, I took some of the sections I had previously worked on that were subsequently discarded from the main draft and have collected them here for those who may have more questions than the present Guide answers. Feel free to browse around and see if they are helpful to you. In time, I hope to put together a PDF file of what I am going to call the “Official Unofficial User Guide for WSJT-X v1.4.” Until then, I hope the following is helpful to those with questions about certain features and helps to illuminate the design of the program so that you can maximize your fun, station performance and contacts.
You can click on the link in the menu above to find the first two installments: one about the different menu settings within the program configuration and the other about the installation and location of program files for Windows, OS X and Ubuntu. Enjoy!
While it is completely anecdotal that people with musical inclinations tend to have an easier time learning Morse code (to my knowledge, there have been no double-blind studies to examine this supposed relationship) I suspect there may be some truth to this assertion if only because, try as I might, I’m seemingly unable to learn and use the code- and, of course, I’m not musically inclined at all. Somehow, this makes my deficiency more soothing. I’ve tried to learn Morse code using all sorts of techniques and mediums: I’ve used tapes, CDs, on-air listening, sending characters (on the premise that if I can make the noise, I can learn to hear it), mobile apps, and I’m sure other methods which escape my present memory. When I hear Morse code, it’s a jumble of sounds such that, for the most part, I can’t tell a dit from a dah.
This doesn’t prevent me from trying to continue to learn the language. I can cipher some characters and prosigns and phrases, so I must be picking something up. I’ve not developed the bad habit of trying to memorize a character chart and instead listen to the code only. It could be that I’ve simply not really given it my all. Whatever the reason, I’m just not adept at it, whether it’s because I don’t have a musical bone in my body, have no facility with foreign languages, or haven’t tried hard enough.
During my trip to Dayton Hamvention 2013, I ran across K8RA and bought a key from him- if I spent over one hundred dollars on something, my thought was, I’d definitely learn how to use it. I also saw Doug Hauff, W6AME, displaying his keys at his table for his sideline business, American Morse Equipment (you’ll note this write-up is about the KK2-A, which can be ordered by selecting the KK2. The -A update indicates that this kit uses springs instead of set screws for arm adjustment). I didn’t buy one then, mainly because I had spent all I was going to, but I did like the idea of a more substantial kit and knew that I’d later get one, which I did. What convinced me to purchase one, other than I like the idea of supporting locally owned small businesses, was the rugged quality- everything but the paddle handles is metal- and it is finished in the raw, so you can customize the finish if you’d like. I admit it’s a bit crazy to purchase another item that you can’t use just to put it together. But kit building isn’t really about the destination, it’s the journey that’s important. And for $71, you aren’t going to go broke playing with it. In what follows, I’ll show you how I finished my key and maybe it will give you an idea on what you’d like to do for a project you are working on or that is coming up soon. Or, maybe it will inspire you to purchase a key from Doug and finish it out yourself- I bet he wouldn’t mind!
From July 22nd to July 31st, The Southeastern Underground Radio Fellowship would like to extend a warm welcome to all and intends to spread good cheer and celebration over the last time General Sherman came to town, looking for a light. It isn’t every day that you get to celebrate something that happened 150 years ago; or at least, anything of much consequence.
The Battle of Atlanta was, in fact, the culmination of four different battles: The Battle of Peachtree Creek, The Battle of Bald Hill, The Battle of Ezra Church and The Battle of Jonesboro. These were the major battles of the Atlanta Campaign, which got its start in May of 1864 and finished in September of that same year. The actual fighting in and around what is present day Atlanta started on July 20th at Peachtree Creek, followed by the most pivotal battle, and the one associated with Atlanta the most, Bald Hill, on July 22nd. Atlanta finally fell September 2nd, 1864. President Lincoln was re-elected, due in large part to this Union victory, Sherman went to the sea and Lee surrendered to Grant at Appomattox in April of 1865.
A large part of rebuilding remained to be done after the close of the Civil War, and out of those ashes rose Atlanta, now the de facto capital of The New South. The city logo has two dates: its chartering in 1847 and its rebirth in 1865. Fittingly, the mythical Phoenix is the city symbol.
We’ll be on the bands mostly during the 26th and 27th of July, but we are going to endeavor to be active on all other days as is possible. Our call will be W4A and we look forward to working you! We’ll be sending out a complimentary QSL card, because in the grand tradition of Southern gentility, we ought to make certain that we do our duty and send out a “final courtesy” to all we work. Please look for us on the bands!
Field Day is the holy high holiday in amateur radio. It’s like Easter and Christmas got together and had a baby, and the baby became Field Day. It is an occasion to socialize with your friends, take radio outdoors, and stay up all night making QSO’s. Many people really get into the event- I’m not one of them. This year, however, Field Day happened to coincide with Jim’s, N4BFR, birthday and so I put in to take time off from work in order to celebrate both his birthday and get a little operating time in as well. He was good natured enough to humor me and helping me to work the event using my call. I suppose I should at least get Worked All States at some point in my amateur career, right?
We decided to operate as a completely digital station for the event. We ran all sorts of modes: PSK31, RTTY and WSJT-X. I’m glad we didn’t really care about how many Q’s we would make, because the bands were in horrible condition for the entire event. 20 Meters seemed to be the band everyone had some degree of luck with, though the lower bands supposedly opened up later in the evening and early morning. We didn’t run the event as a contest or even for the entire 24 hours- we instead wished to enjoy a leisurely pace. We nevertheless had a great time making what Q’s we could and did attempt some satellite contacts and a direct contact with the ISS. We weren’t successful in that regard, but we had a great time trying and may have located some excellent spots for future satellite attempts.
Something that I did learn this year while waiting for decodes was that social media can be used as a powerful propagation map. In this case, I don’t mean G+ or Facebook, but rather using Twitter. It’s near real time conversation approach is ideally suited for checking out what other people are experiencing right then- so if someone reports 10 Meters is open to WA, for instance, it might be an opening you want to investigate. It’s just another tool that some may find helpful. In my case, it was a way to commiserate with others about the poor band conditions!