Archive for December, 2014

Allstar Nano Node Construction

Thursday, December 18th, 2014

I have a preliminary schematic of the Allstar Nano Node.  This is still under construction and I will be adding additional construction pictures as I progress through this project.

Nano Node - USB FOB/Transmitter Module Schematic

Nano Node – USB FOB/Transmitter Module
Schematic (updated 12/20/2014)

These modules do need additional filtering. I will be posting a link or provide additional information regarding the output filter.

Nano Node using Modified USB Audio FOB and an 818 UHF Module.

Nano Node using Modified USB Audio FOB and an 818 UHF Module.

The audio FOB shown above was modified based on the following article by Doug, WA3DSP:

I mounted it above the board using cut resistor leads to raise the board above the proto-board.  This was similarly done with the transceiver module.  There are small copper pads that I made with my punch from a single sided circuit board to insulate the PTT and COS lines and make a convenient junction point.

The three pin edge connector is for programming the module.

Here is the final result:



Doug, WA3DSP, has a 818 transceiver module page. His module  mounted in an Altoid  style tin and uses a 9 pin connector to interface with the URI – USB Radio interface.  He also has information on filtering. The following is a link to his page:

URI USB Radio Interface Link:

Audio FOB Modification Links:

KP4TR – great idea for a simple enclosure:

Final Notes

I have been using the 818 transceiver modules for a while.  One thing I noticed is that the receiver in the modules  “crackles” with multi-path signals as if the receiver AGC is clipping.  It sounds like a bad mic or connection.  This occurs on all the modules that I have tested and does not matter what radio is transmitting to the module. I can’t explain this issue and I have also seen the same issue on my Baofeng UV-82 transceivers during receiving.  The “crackling” is very noticeable and bothersome and does not matter how the module is programmed or if filters are enabled or disabled.

DRA818/SA818 Module Programming Software

Thursday, December 4th, 2014

I have written a simple program to configure the DRA818/SA818 RF modules. It supports the 3.3V level FTDI USB to serial devices.  I believe that the SA818 modules can be programmed at the 5V TTL levels, but I have not tried this.

Below is a diagram of the minimum configuration to program or set the module for use. Note, +VCC is 3.3V for the DRA818 Modules.


This program is written in python2 and is configured to use a FTDI USB to Serial Adapter. It works but it has very little checking on the value/range syntax. I have tested these programs  on Linux systems running both Lubuntu and Mint as well as  on BeagleBone Black computer.

The program requires phython2 and pyserial module.  The module information on pyserial can be found at:

Arch Linux

 The packages are python2, and python2-pyserial.  To install, use the following command:

  • pacman -Sy python2 python2-pyserial


A package is available under the name “python-serial”.  Note that some distributions may package an older version of pySerial. Note that some distributions may package an older version of pySerial.

  • sudo apt-get install python2.7 python-serial

For the BeagleBone Black, I’ve included a simple install script that will
install any package dependencies.

There are no syntax checking for the value format  at this time. When prompted for values,
pay close attention to the format of the data.


To install the software, download either the zip or the tar zip’ed file  from the end of this article.  If you are using the BeagleBone Black, there will be an script. This will install the python package dependencies and copy the two programs, 818cli-prog and 818-prog, to /usr/local/sbin.

For others distributions, you will need to manually install the python package dependencies (as shown above), and copy the programs from the “src” directory to the desired location. I would recommend /usr/local/bin. You may run into permissions issues with the usb/serial device if you are running these programs  with standard user permissions. (more on this later).

Program Syntax

Value Syntax

Frequencies should be entered in MHz as XXX.YYYY using a  four digits suffix. For example, 446.05 should be entered as “446.0500

Likewise, CTCSS/DCS values should be entered with four digits, 0022 or 0754N. See
below for more details.


The CTCSS tones should be entered using all for digits, for example CTCSS
tone 181.8, should be entered as 0020.

DCS Codes

The format needs to be full three digits plus an “N”. For example, DCS code 7

should be entered as : 007N

Inverted DCS Codes

The format for inverted codes is the same as DCS codes except instead of an “N”
you change it to “I”. For example, DCS code 7 inverted, would be entered as:

Here is the program.  The script is meant to be used for the Beagle Bone Black.  It requires python2 and py-serial.  I have added a non-interactive version to allow command line programming without interaction.  This is included in version 12 below:

Latest changes include channel spacing and updated 818cli-prog help.