Wizkers:Radio review on www.machamradio.com

Machamradio.com, a blog on - you guessed it - ham radio software for Apple computers, just published a review of Wizkers:Radio. 

The choice of Ham radio software on MacOS X has historically been a lot poorer than on Windows. Some might say that the software that is available on the Mac makes up for it by its general very high quality. Nevertheless, we are glad to be adding to the choices of Apple-friendly Hams by supporting Wizkers:Radio on the Mac as well as most other operating systems.

Wizkers:Radio is out!

We are very happy to announce the release of Wizkers:Radio on the Android Store and the Chrome store. Wizkers:Radio is a version of Wizkers that is dedicated to HAM Radio operators, and supports a lot of Elecraft equipment: KX3, KXPA100, PX3 and XG3. It also provides experimental support for the Sark110, only as a Chrome app.

In our very unbiased opinion, Wizkers:Radio is one of the most advanced, and certainly the best looking HAM radio controller available on Android today. Its role is to be a natural extension of your rig whenever you have access to a phone and tablet, make the use of your KX3 even simpler and leverage your equipment to the maximum of its abilities.

Remote control and monitoring

The KX3 display is entirely reproduced on Wizkers:Radio, all the way to the buttons that are all functional.

Wizkers:Radio connects to your rig/instruments using either a USB OTG cable, or a Pignology Piglet. You then get a complete remote display of your KX3 or your KXPA100 in case it is not located right next to you.

Of course, all the buttons are active, and for the KXPA100, all the setting entries as well.

KXPA100 monitor and configurator

Moreover, Wizkers:Radio is compatible with hamlib: if you use logging or digital mode software that supports hamlib, your tablet will be turned into a full-fledged rig controller.

Stay tuned for a tutorial and demo video of these capabilities.


The KX3 is a very advanced radio. It supports no less than configuration 73 menu entries, many of which contain up to 6 sub-entries, or are band-dependent. In other words, this translates in to hundreds of parameters!

Audio settings - including TX and RX equalizers!

Wizkers:Radio tames all these by organizing configuration settings by functional group - Audio, Band settings, etc - and lets you adjust each of chose with just a couple of touches/clicks.

Band related configuration

Band related configuration

In the next few releases, we will introduce even more menu options, as well as an inline help system to explain how those menu options work - similar to the 3-second press on "DISP" on the KX3 while a menu is displayed.

Text mode

The KX3 has built-in support for PSK31 and RTTY. Wizkers supports those modes, and includes a simple macro system to make it faster to chat.

Text more QSOs

Text more QSOs

XG3 Support

The Elecraft XG3 is a very cool RF generator that supports tons of features, including a CW and RTTY beacon mode. Wizkers supports all the same capabilities as the official Elecraft XG3 utility (sweep settings will be implemented in the next release), and adds complete remote control with a copy of the XG3 front-end, and beacon mode configuration.

When coupled with a Piglet, you can install the XG3 in one location and control it remotely, which can be very useful in many situations.

Complete remote control of the XG3 - click on the LEDs to change band.

Next steps

This Android release of Wizkers:Radio is the first official specialized Android build of Wizkers. We have used it in many situations so far, on phones all the way to tablets, laptops and Chromebook.

Wizkers:Radio is a truly innovative piece and software, supporting a wider range of platforms and devices than anything else on the market today. We are planning to continue improving it at a rapid pace, and are counting on you to give us feedback: what works, what doesn't, what you would like to see included.

So please, try Wizkers:Radio, get in touch, give us your comments, this software exists for our users, help us turn into into your favorite rig controller!

73 de Ed, W6ELA

Power monitoring: one project in one day

So we get asked the question, “how easy is it to use Wizkers for my own sensor project” ? The answer is “very easy”. This post describes a new Wizkers project from start to finish, which took one Sunday to put together.

The goal of this project was to great a simple power monitoring dashboard for our house, and get a real time graph of whole house power usage.

Power Monitor

The power monitor we picked for this project is the Blue Line Innovations Power Cost Monitor. This is a device which has been around for a long time, and is very reliable. More importantly, the US power grid being somewhat of an antiquity in most of the country, it is compatible with the old school ‘disc’ home power meters which disappeared about 20 years ago in the rest of the western world. No fear though, it also works with standard electronic meters with flashing/infrared LED lights. And it requires no fiddling with the meter at all either.



Yep, works with those old school meters too!


This power monitor sends its data as a pulse modulated signal over RF at 433MHz. The FCC filing from BlueLine innovationscontains all the information that is necessary to put together a simple receiver using off-the-shelf modules.

As a nice surprise, our job was made even easier by the fact a couple of people had already worked on the transmission protocol: Github contains a couple of attempts which we used as a base for our own receiver.

Arduino-based receiver

Using “Powermon433” as the base, we modified the Arduino sketch to output data over the serial link using the JSON format, and we added a couple of nifty features:

  • Automatic discovery of transmitter ID (couldn’t resist the fun of doing a small CRC bruteforcing algorithm…)
    • The receiver is able to narrow down the TX ID to sometimes two and most of the time one (correct) candidate.
  • Saving of Transmitter ID in the Arduino’s eeprom, so that it is preserved between resets.
  • Power factor calculations on the Arduino to output the correct power figure  (saving the PF in eeprom as well).
  • And a couple of simple serial commands to manage the features above.

This took a couple of hours to put together and get a serial stream to show up. As you can see below, this is pretty much as simple as I could make it, but it works surprisingly well!


Adding a new Wizkers device

As described in the documentation, adding a new Wizkers device is fairly straightforward:

  • Create the front-end visualization.
  • Create the front-end driver.
  • Create a back-end driver for Chrome and/or server mode.
  • Connect the new instrument to the front-end and server instrument managers.

The task is made easier by the fact you can use the “sample_instrument” template for most of the files. There are already a couple of devices on Wizkers which speak JSON, so getting the drivers to work literally just took a couple of minutes.

Front-end visualization

For most time visualizations, Wizkers provides a “flotplot” library, based on “Flot Charts”, which makes it super easy to add graphs in your screens: flotplot takes care of all  formatting, data buffer and storage, etc. The only real task is to tell Wizkers the name of the json keys which you want to plot.

Back-end drivers

Likewise, our Ardiuno sketch outputs json data, so we can use nearly the same driver as some of the other instruments (USB geiger, Onyx, etc). A future revision of Wizkers might actually include a fully generic driver for any device that outputs JSON-formatted data, in order to make this even simpler.


Receiving the power monitor, installing it, researching online, adapting/programming a new Arduino sketch and soldering a simple radio receiver took about 3 hours.

Writing the basic visualization for a new “Power Monitor” instrument on Wizkers took about 2 hours from start to the first graph.

All in all, a good busy Sunday!


You can find all the code on the Wizkers Github repository. The implementation contains both a Chrome mode driver, and a server mode driver which is probably the most interesting, since it will let you log all the power data continuously.

Next steps

Of course, this power graph is very basic: it will be more interesting to capture hour/day/month/year-level figures, make use of the “energy” field which is present in the sensor output, create better visualizations, etc. We will add those over time…

The point is, now that all the basics are in place, we can simply focus on creating those visualizations, knowing that all the data is flowing and getting logged. So stay tuned for new revisions to this home power monitor!