Installer error fix

Good afternoon Handiham Members and Volunteers. We would like to report another fix that has been posted after the initial release of the remote base client version 6.1. Please visit the Handiham web site for the latest download of the remote base client. In this release, we identified and corrected a bug in which the installer was not completing before the new Remote base client was being launched. Hence, the client would launch and the installer would remain running until the remote Base client was closed. Now, we have posted a new Full installer for version 6.1 that fixes the confusing condition. 73: KK4JZX

New Client & Update Client Released!

w0zsw_2013

I am pleased to announce the release of the Handiham Remote Base software release version 6.1! Since the beginning of my work with the Handiham Remote Base software, it truly has been an honor to work on technology that facilitates the use of the W4MQ software for ham operators that are handiham members.

This version of the Remote Base client is a springboard release. We believe that this release will enable many enhancements to the remote base right now and in the future. With this release, we are prepared to continue the life-cycle of the W4MQ client through the recently announced Microsoft support of Visual Basic 6 applications. Microsoft, as of November 2012, announces that Visual Basic applications will be supported through the lifetime of Windows 8. This means Windows 7 and 8 are now shipping with common components that enable continuing support for the Handiham Remote Base client. Typically, Microsoft will support a released operating system for five years with an additional five years of extended support. That means we are prepared to have the Remote Base client supported for at least five years if not ten.

With this release of Web Transceiver, version 6.1, we have included the following major fixes.

1. Phone Home Bug Fix – Essentially, the Phone Home bug was uncovered and fixed. We now have an interim update that enables one station to be phoned home, the W0ZSW station. Without enabling one remote station to be polled, the remote base client times out on a constant basis and non-sighted users will have no functionality with the client; hence having to shut it down from Windows Task Manager. The Phone home bug fix / workaround is not required with this release of the W4MQ client. For those that have implemented the Phone Home Bug fix, you may remove the HOSTS file entry as soon as the update is applied.

2. Increased Performance – The Web Transceiver software is now faster than ever. The interface is crisper and feels much more robust.

3. .Net support enhancement – With this version, we get closer to the day when the Web transceiver can be converted to the .Net framework.

4. Menu enhancements – The Web Transceiver menu is much more robust and all options now work. There are options that have been removed and new options added as well.

5. Addition of an Exit Option – you may now press ALT+X to exit the Web Transceiver application..

6. Removal of Legacy / Obsolete Code – Much of the obsolete code has been removed from this version of the remote Base client, hence making it much more robust.

7. URL Updates – Many of the broken links within the application have been fixed. The links now work and bring up the correct web sites.

8. Internal Code Improvements – To make the code much more readable and user friendly, this version of the Web Transceiver has been updated to be more readable internally.

9. User Friendly Messages – Application messages are now much more descriptive and provide details on actions that the software will take.

10. Debugging Facility Included – This facility will improve with time and has been added to improve software debugging.

As we continue working on enhancements to the remote base client, we hope that our beta team will continue to participate in this great tool for Handiham members and the like. Team, without your help, this release would not be possible. For those of you who will continue on to the next release, thank you for your continuing support.

I thank Pat, WA0TDA, and Lyle, K0LR, for leading this effort and for getting me started in this development. Pat, I never imagined that I would be working on this code but when you mentioned you needed help with the remote base, I truly was excited about the prospect of working through the code. For me, it had been a good ten years since I had worked on VB6 but it came back so quickly; it was like knowing how to ride a bicycle, I just remembered.

Now I am hooked! Time to work on the documentation and audio files!

73,
Jose Tamayo – KK4JZX

Client Update News

As we head into the weekend, we are happy to report that we have been making some really good progress on the updates for the W4MQ client software. We now plan to have an update release that will bring current installations up to date as well as a new client for first-time installations. Several bugs were worked out this week. Thanks to everyone on the team and to KK4JZX for doing the heavy lifting with the coding.

Remote Base Client Release Progress

Dear Handiham members and volunteers,

We are pleased to announce that we are days away from releasing the new W4MQ remote base client version 6.1. With this release, we are including fixes for all known critical issues uncovered in beta versions 6.0.2.0001 through 6.0.2.0007. If you are interested in learning more about “What’s under the hood” with this version 6.1 release, please stay tuned for a detailed update. We have been working very diligently to get this product out the door for the benefit of all Handiham members. Among the critical fixes is the “Phone Home” bug fix which has plagued the W4MQ client for several months now. If you have been running the beta versions, don’t worry, we will be releasing a tool that will remove all existing betas from your computer.

In addition to the many updates in version 6.1, we are working on additional upgrades that will enhance the Web Transceiver client to include accessibility support, power level support, and updated Skype support.

Audio Balance Adjusted on W0ZSW

I have adjusted the balance between the output of the speech frequency announcements and the receiver audio. This makes the received signal louder relative to the speech frequency announcements. Please let me know how this is working for you.

73 – Pat
wa0tda@arrl.net

W0ZSW mini-tour

Ever wonder what the remote base station looks like? The answer is that it’s surprisingly like a typical ham radio station anywhere, sporting a radio, power supply, and that all-important station accessory: the shack computer. w0zsw_2013

In this first photo we see the Kenwood TS-480HX transceiver paired with matching SEC switching power supplies. The Systemax rig control computer is in the background, interfaced to the radio with a RIGblaster nomic from West Mountain Radio. The RIGblaster is on top of the antenna tuner, an LDG AT-200PRO. On the wall above the radio there is a board with a two-position coaxial antenna switch that allows us to switch the output of the radio to a dummy load for testing. Our vintage sign, “Amateur Radio Station W0ZSW” sits atop the computer, just beneath the LCD monitor screen. This sign has been in the Handiham radio room for as long as anyone can remember, so it seemed appropriate to keep it in place at the remote base station.  Partly obscured by the control head of the radio is a W0ZSW QSL card.

The two power supplies are needed to accommodate the TS-480HX’s requirements, since it is capable of running at 200 watts.  The same is true of the LDG AT-200PRO antenna tuner.  At our sister station, W0EQO at Courage North, the radio is a Kenwood TS-480SAT, which is capable of a maximum 100 watts and thus needs only a single power supply and an LDG AT-100PRO antenna tuner.

w0zsw_ant_switch

This dual-position switch is mounted upside down, which seemed to be the best way to accommodate the heavy RG-8 cables. George, N0SBU, gave me the switch, and I mounted it on a scrap of pine board for stability before affixing it to an outer wall near the point where the antenna cabling goes through the wall.  This switch allows for a dummy load antenna to be placed into the circuit so that testing can be done off-air.

RIGblaster_nomic

Here is a close-up of the RIGblaster nomic interface by West Mountain Radio. In our installation only the microphone audio is interfaced through this device.

balun_cover

Next, we head outdoors, to the other side of the wall above the antenna switch.  We see the coax exiting the wall and dropping down from the entry point so as to prevent water from following the cable into the wall when it rains. The coax is coiled into a five turn choke coil to prevent RF from following the outside of the coax back down into the shack. Under the plastic radome (really just a poly food container) is a rehabilitated MFJ 4 to 1 current balun.  450 ohm ladderline exits the top and goes out to the center insulator of a 200 foot double extended zepp antenna commonly known as a “W0OXB Special®”.  This photo was taken late last summer, so don’t go on the assumption that the greenery on the nearby bush is common in Minnesota in January!

w0zsw_remote_screen_mic

Finally, here is the view from the point of a remote user:  The W4MQ screen shows up on a computer monitor and a USB desktop microphone does the honors for voice communications.  Remember that there is no microphone at the station itself, since the rig’s microphone port is connected via the RIGblaster to the rig control computer’s sound card.  The W4MQ software will also run CW and PSK-31 with its built-in interfaces for those modes.

 

Development Update: 03 October 2012

The W4MQ client has been undergoing many changes. We are working on solving several issues which will make the next client version work much more smoothly.

1. The new W4MQ proof of concept Enter Login Information is under development. With this new interface, both sighted and non-sighted users will have a way to manage their remote stations in a much more intuitive and efficient manner. We are adding visual as well as non-visual features to this interface which we want to release to testing very soon.

2. Skype Runtime error 6 : overflow – This is an issue that we are working to solve in a current beta version of the client. We are gathering information in order to figure out what is causing the runtime error. Current, beta 7 of the W4MQ is under testing and we are obtaining technical information which will allow Jose Tamayo – KK4JZX to figure out how to solve the runtime error.

3. Various fundamental code changes are still being made to W4MQ in order to minimize the number of conversion errors in the application when moving to.NET.

4. A station has to be chosen from the list first before the status message shows for the particular station even when the station shows as the first in the list.

5. Various comments are being added to the client code in order to document certain functionality.

6. Client deployment process. We are working on preparing an installer that will allow Handiham members to install new versions of the W4MQ client without having to perform manual steps to copy files.

7. Performance Improvements. Look for many improvements in performance with the new client versions. This is a target for all versions of W4MQ client releases that we are going to make available to the general public.

8. Minor Interface improvements. Other improvements are going to be made to W4MQ and other items that are broken are being fixed. For example, the DX Summit option under Info will be fixed in the next version of the Web Transceiver client. A future version of the client will make the DX summit URL a customizable option. We are also making the client keyboard keys easier to understand.

Regards,

Jose – KK4JZX

Late September Update – Client fixes

KK4JZX:
Working on resolving a few things with the client.

1. Minimizing the number of .net conversion issues from over 400 to under 100.
2. accessing where accessibility will need to be addressed at this time.
3. Working on performance enhancements.

History:
September 11, 2012: working on researching Array conversions from the current VB version for pre-VB.NET conversion. Will have to ensure that all arrays are properly dimensioned and that they are relative to 0 and not relative to 1. For arrays that are referenced incorrectly, I will address each individually.

September 11, 2012: release version build 0003 to the group. We want to test several changes that were made to the client. Specifically, we want to test how changing all Variant data types to typed variables will affect the application. While I completed extensive searches through the code to ensure no other areas were affected, nothing beats working on the code directly. Clients will have the final word.