There are other developers working to bundle hardware and software to use Mr. Retzler’s OpenWebRX engine. An example of this is found @ http://www.jks.com/KiwiSDR/ . So consumer grade products are on the horizon for this application. But being a Ham, I’m more interested in “rolling my own” to the extent practical.
The advantage in use is lower throughput required to monitor a section of spectrum, but it comes at the expense of higher resolution that I’ve come to expect with the USB connected RTL-SDR, and the Network connected RTL-TCP server. So listening to the radio on a web browser is a good tool, it does not replace the higher resolution and spectrum views provided by SDR# or HDSDR. I imagine I could monitor my transmissions at various locations around the world by opening an OpenWebRX station at that geographic location and monitoring my transmitted frequency. DX all by myself, well nearly. LOL
In rpt.conf there are stanzas that start with the node number, such as:
 ; Change this to your assigned node numberrxchannel=Radio/usb;rxchannel=Simpleusb/usbduplex=0~archivedir=/media/USB
If it contains the “archivedir=<some recording location>” as shown above, then the audio passing through the radio will be recorded. In my case the recording location is a USB stick formatted as an ext4 file system identified by the system as /dev/sda1. So edit the file /etc/fstab and add a line as shown in bold below:
The AllStarLink system will add the node number to the directory structure, so when you navigate to the saved audio files, you will do something like this:
[root@AllStar-KA7U /]# cd /media/USB/28174[root@AllStar-KA7U 28174]# ls -ltotal 1188-rw------- 1 root root 6154 Mar 15 21:22 20160315.txt-rw------- 1 root root 12800 Mar 15 20:51 20160315205145.WAV-rw------- 1 root root 5455 Mar 15 20:51 20160315205153.WAV-rw------- 1 root root 5130 Mar 15 20:52 20160315205159.WAV.... snip...
As you can see above the system has been busy recording audio files in the mounted USB stick. To use these files, we need to copy them to a computer capable of playing them. In this case the Raspberry PI is connected to another Linux computer by SSH, so we will copy the desired files to the connected computer with the SCP command issued from the connecting computer in the directory we wish the files to be copied to. Note: there is a space between *.WAV and ./ , don’t forget the space. 🙂
From here we can play the files one by one in a player of choice, such as Audacity, or we can concatenate them into one or more files using SOX. Without our intervention, SOX will concatenate the files in the correct date and time order with the simplest command.
ron@linux-zdyj:~/wave> sox *.WAV test.wavron@linux-zdyj:~/wave> ls -l test.wav-rw-r--r-- 1 ron users 1034926 Mar 15 21:42 test.wavron@linux-zdyj:~/wave>
Notice in the above that a new file “test.wav” now exists. Also note that the AllStarlink system uses a naming convention on the audio files using capital letters WAV. Audacity has the ability to further edit the file and change from wav to other codecs such as mpg. This screenshot shows the presentation of this audio file in Audacity.
The file is linked above, if you would like to listen to it or work with it. This recording is quite useful in as much as one of the radios has an intermittent connection problem and one of the radios is over modulated. The picture in Audacity is worth a thousand words, and being able to listen to the audio more than once, makes it much easier to determine how things sound.
If the radio is breaking squelch to often, the recordings of that will be plentiful. So if we plan to record, the squelch should be sufficient to silence the radio until a signal appears.
This is a copy of the relevant post. If you have relevant information, please leave a comment about it.
The R-1200AX is the basic 1200 with the option of a high stability timebase (the "X.")
The modules have been added later.
There is no internal load in this model. It is designed to monitor off-the-air signals or
to be used with a pick-off enroute to an external dummy load or antenna.
I don't have the manual anymore, but this is how it works to measure deviation and frequency:
1) Dial up the known carrier frequency
2) Press the RECEIVE button
3) Press 1.5, 5 or 15 KHz to select range (FREQ ERROR)
4) Connect whip antenna or cable from pick-off to broadband mixer
5) Place wide/narrow switch in "wide" unless there's interference, in which case use "narrow."
6) Read frequency error on ERROR KHZ meter
7) Set deviation meter range as desired
8 ) Read deviation on meter when transmitter is being modulated
Unfortunately these are 30+ year old instruments which have usually seen a hard life.
They are worth little on today's market, as they have no value to commercial shops, thus
intensive labor to get one running has to be considered a lost cause at some point.
I have had some where the electrolytics in the deviation meter module were totally dried out
and open circuit. Other electrolytics in the unit, same story. Tantalum dip capacitors can
be shorted, they are becoming notorious for this.
The manual, as I recall, is rather huge and would be a life's work for someone to scan
and put on the internet. Operating the thing should be a pretty intuitive process.
For generating a signal, use the CW position generally as that is locked to the TCXO.
The red "Leveled" lamp should be lit normally. If it is out, it means the output has
either become unstable or the overload protect circuit has tripped (hence the reset button.)
The FM Cal knob sets the frequency when the generator is in the modulated FM mode.
It should be zeroed with the zero center meter. The stability while in the FM modulated mode
is rather poor, it's just for testing receivers and not frequency setting. Leave it in
posted by: Geoff Fors
OK, so after reading the above I setup to test the Service Monitor on the bench. I decided to use it in FM modulated mode to see how unstable that might be too. This video pretty much tells the story of how that worked out. https://www.youtube.com/watch?v=a5lSJb3t4nc
DECT telephones offer advantages for wireless because they use different frequencies than WiFi. I have 3 telephones registered with the base unit and the base unit is registered with an Asterisk ver.13 PBX as SIP extension 7005 using voicemail box 8005. (This means that when the extension is called, all 3 telephones ring. The phones can be configured to ring individually on different extensions. That is up to the user.) This DECT set is working with the Asterisk ver.13 configurations found in my previous post, title: Configuration Files for Asterisk v.13 and AllStar Link . The network it is configured for is a HSMM-Mesh Network, so if it were to be configured for a normal LAN the host names would change to IP addresses.
Quick Start: A newly purchased KX-TGP500 base unit that is “open” (that is not pre-configured by a provider) and a KX-TPA50 handset need to be powered on. The handset needs to be registered with the base. To register the phone with the base you need to do the following:
Open the menu of the handset by pressing down on the joystick on the telephone
Then press #130 on the telephone dial pad
There is a button located on the DECT base unit. Press it down for 4 seconds
Then press OK on the Telephone, which will be the button to the right of the word menu just under the screen.
Then dial 0000 on the telephone. Once it returns to the normal screen the handset should be registered and show you a number beside the battery symbol in the screen.
This needs to be done for each phone being registered.
To open the HTML configuration for the base unit, you need to press the joystick on the telephone down and then select the “tool box”, “Network Settings”, “Embedded Web”, and then “On”. The phone will sound a long tone. Then from a web browser sharing the same LAN, type in the IP address of the DECT base unit. You can find this IP address on the telephone by pressing down on the joystick and selecting the tool box icon, then Network Settings, then IP settings. Log into the DECT Base unit HTML configuration with the default username Admin and default password adminpass. Select the VoIP tab on the top menu, and then “line 1” under “SIP Menu” from the left sidebar menu. You should now be on a page that looks like this image:
You may want to change the addresses from ka7u-2 to your host name or IP address and the extension number is the authentication ID in my Asterisk PBX. The authentication password is the “secret” for the extension as listed in sip.conf.
This should be enough configuration for the DECT phone system to work with Asterisk ver. 13 PBX. There are many other configurations according to your needs.
Configuring the SPA941/942 Telephones for use with ASTERISK.
SPA941_Manual. The link above should load the manual for these phones.
For a quick Start: plug your telephone into the network jack and connect 5vdc power to the telephone. After the telephone starts up, press the setup button located on the front of the telephone. Use the arrow keys to scroll through the options until you find #14 “Factory Reset”. Use the select button and accept to reset the telephone to the factory defaults. The telephone should reboot and when it does use the setup button and scroll to item #9 “Network”. Select Network and you should find the IP address of the telephone. Enter this IP address into a Web Browser address bar (running on a computer served by the same network), and the telephone HTML setup screen should be displayed in the Web Browser. In the upper right menu area, select Admin and then Advanced. You should see a setup menu like the example found at this link: SPA941/942 Web Setup Menu
The configuration example found at the above site is for the radio/telephone system described in the posts about AllStar and Asterisk ver.13 in use at KA7U at the time of this writing. While you can use it and replicate what I have going on here, it is intended to be an example of how to do the configurations. By considering it and the manual, you might be able to configure the telephones to fit into other telephone networks as you wish for them to operate in that environment.
The Raspberry Pi2 can be configured to become a Node on the HSMM-Mesh. The Raspberry Pi2 is capable of providing server functions while being a HSMM-Mesh node. For example the Raspberry Pi2 could run an Asterisk PBX which is directly addressable across the Mesh network, or it could run a NAS, or both.
The HSMM-Pi nodes lack the more robust router features of the WRT54Gx series of routers or the Ubiquity routers, but they do provide a great way to consolidate servers on the network and are quite useful for mobile connections to HSMM-MESH networks.
Depending on the type of service you intend for your Raspberry Pi node, will indicate what type of antenna you will want to use. The new Pi3 that just came out has a built in WiFi but the Pi2 does not and you will need a USB to WiFi adapter. The Raspberry Pi2 has a limited current capability through the USB ports and therefore you might need a powered USB Hub to power the WiFi and/or other USB devices connected to it. A list of supported WiFi adapters and discussion on the problems and attributes of each one is located here: http://elinux.org/RPi_USB_Wi-Fi_Adapters .
I have been using the ALFA AWUS036H v5 802.11 b/g Long Range USB Adapter with my PI node. It does a good job, but it did require some setup in the operating system to make it work reliably in this service. I added a file containing the following to the folder “/etc/init.d”.
#!/bin/bash#/etc/init.d#iwconfig wlan0 rate auto iwconfig wlan0 frag 512iwconfig wlan0 rts 512iwconfig wlan0 retry short 11iwconfig wlan0 retry long 11iwconfig wlan0 power off
The permissions for this file would be set by “chmod 755” and the owner and group are root:root. The file is added to the system with this command:
sudo update-rc.d <yourfilename> defaults
After a reboot IWCONFIG wlan0 gives this report:
pi@KA7U-2 / $ sudo iwconfig wlan0wlan0 IEEE 802.11bg ESSID:"BroadbandHamnet-20-v3" Mode:Ad-Hoc Frequency:2.412 GHz Cell: 86:E9:B7:56:2F:EF Tx-Power=20 dBm Retry short long limit:11 RTS thr=512 B Fragment thr=512 B Encryption key:off Power Management:onpi@KA7U-2 / $
A different WiFi adapter may or may not need this instruction to stay on and operate correctly with the RPI, but I have included the information in case you have a challenge and need to know where to look.
A “How To” For Linux User to Add N4PY Radio Control Software to the Operating Position.
Getting started, we need to choose a distribution. For purposes of this discussion I will describe the
setup in OpenSUSE 13.1. I won’t go through it for Ubuntu, but if you follow this with openSUSE, you
should be able to interpolate and succeed with the other Linux distributions.
At KA7U, I am currently using an IBM Intellistation Zpro with dual XEON processors and an NVIDIA
6800 video card, for the radio control computer. I have also used an ACER Aspire One ZG5 to
interface to the radio. The IBM is quicker and the display is much better, but both of these computers
get the job done.
While this is not specifically for openSUSE 13.1, it is for openSUSE 12.1, the available software
should be similar. Pick and choose what you want to install.
You must install WINE, http://en.opensuse.org/Wine , the current version being used here today is
WINE version#1.7.8 . Both 32 bit and 64 bit versions are in use here and both run N4PY without
special consideration or addition of native Windows DLL files.
You will need to enable serial ports in the directory ~/.wine/dosdevices . One of my computers has a ~/.wine/dosdevices directory that lists the following:
ron@linux-i6yo:~/.wine/dosdevices> ls -l
lrwxrwxrwx 1 ron users 10 Nov 22 14:49 c: -> ../drive_c
lrwxrwxrwx 1 ron users 10 Nov 6 09:31 com1 -> /dev/ttyS0
lrwxrwxrwx 1 ron users 12 Nov 18 23:42 com3 -> /dev/ttyUSB0
lrwxrwxrwx 1 ron users 8 Nov 23 09:47 d:: -> /dev/sdb
lrwxrwxrwx 1 ron users 17 Nov 22 14:48 e: -> /sys/kernel/debug
lrwxrwxrwx 1 ron users 13 Nov 22 14:48 f: -> /proc/bus/usb
lrwxrwxrwx 1 ron users 8 Nov 5 09:46 g:: -> /dev/sdd
lrwxrwxrwx 1 ron users 9 Nov 22 14:48 h: -> /home/ron
lrwxrwxrwx 1 ron users 8 Nov 5 09:46 i:: -> /dev/sdg
lrwxrwxrwx 1 ron users 8 Nov 5 09:46 j:: -> /dev/sdf
lrwxrwxrwx 1 ron users 8 Nov 5 09:46 k:: -> /dev/sr1
lrwxrwxrwx 1 ron users 8 Nov 21 11:25 l:: -> /dev/sdh
lrwxrwxrwx 1 ron users 9 Nov 21 11:25 m:: -> /dev/sdh2
lrwxrwxrwx 1 ron users 9 Nov 21 11:25 n:: -> /dev/sdh5
lrwxrwxrwx 1 ron users 9 Nov 21 11:25 o:: -> /dev/sdh1
lrwxrwxrwx 1 ron users 8 Nov 23 09:47 p:: -> /dev/sdc
lrwxrwxrwx 1 ron users 8 Nov 23 09:47 q:: -> /dev/sde
lrwxrwxrwx 1 ron users 8 Nov 23 09:47 r:: -> /dev/sr0
lrwxrwxrwx 1 ron users 9 Nov 24 23:44 s:: -> /dev/sdc1
lrwxrwxrwx 1 ron users 9 Nov 24 23:44 t:: -> /dev/sdc2
lrwxrwxrwx 1 ron users 9 Nov 24 23:44 u:: -> /dev/sdc5
lrwxrwxrwx 1 ron users 55 Nov 28 10:42 v: -> /var/run/media/ron/babd3add-c7bf-422a-83e7-5955e9581a33
lrwxrwxrwx 1 ron users 9 Nov 24 23:51 v:: -> /dev/sdb1
lrwxrwxrwx 1 ron users 9 Nov 24 23:51 w:: -> /dev/sdb2
lrwxrwxrwx 1 ron users 9 Nov 24 23:51 x:: -> /dev/sdb5
lrwxrwxrwx 1 ron users 8 Nov 25 11:14 y:: -> /dev/sdi
lrwxrwxrwx 1 ron users 1 Sep 26 22:07 z: -> /
Notice that com1 is linked with /dev/ttyS0 , which is an actual serial port on this computer.
Notice that com3 is linked with /dev/ttyUSB0 which is a USB to Serial converter device.
When you plug in your USB to Serial converter it will be assigned a device name in the /dev directory.
You can find out what it is called by searching for it like so:
ron@linux-i6yo:~> dmesg |grep ttyUSB
[21825.616981] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0
You can further search for it in the /dev directory.
ron@linux-i6yo:~> cd /dev/
ron@linux-i6yo:/dev> ls -l ttyUSB*
crw-rw---- 1 root dialout 188, 0 Dec 12 16:14 ttyUSB0 # notice ownership is root:dialout
If you unplug a USB to Serial converter and plug it back in, the name assignment may increment up a
number. So generally don’t do that and if you do, think about needing to reboot the computer or relink
the com port.
So what do you do in the ~/.wine/dosdevices directory to link the Serial Ports?
It is important that you create these symbolic links while logged into the terminal as the normal user.
Otherwise, you will get an error message when trying to connect to the ports that they are busy or in
use. Which brings us to the need of our normal user belonging to the required groups in order to have
permission to access certain hardware items. So add your user to the user group “dialout”. The image
below should help you to get this done.
Once these things are accomplished, you should be able to install N4PY in the usual way as if you were
using Windows. I do use the WINE utility “Uninstall Software “ to add and remove programs
however. So I would download N4PY, and then run “Uninstall Software” from the WINE program
group in the start menu.
There are some minor anomalies in N4PY when it is running under WINE, but if you are willing to
overlook some minor font display issues, and possibly some other little details, you should find that
N4PY functions as expected working with Linux and WINE. http://wiki.winehq.org/FAQ
I find that other applications work well with N4PY using Linux, such as MixW, N4PY remote, IPSound,
and several other windows programs. Your experience may vary.
The Raspberry Pi2 makes a nice RTL_TCP server. You can place it anywhere on the network close to a good antenna. The sample rate requires good throughput on the Network and generally Ethernet has more throughput than WiFi and Ethernet is preferred for connectivity on the LAN. Fast WiFi will work however. So to setup the RPi2 for this service, you will first install Raspbian Jessie on the SanDisk card and boot the Pi with it. Once you have logged in to the Pi, open a terminal and do the following:
sudo apt-get update
sudo apt-get upgrade
log back into the Raspberry Pi
sudo nano rasp-blacklist.conf #and add the following, then save the file:
Log back into the Pi and start the RTL_TCP Service with:
rtl_tcp -a <the Pi's IP address>
Then using SDR# or HDSDR or whatever receiver you use on your local computer, configure the TCP interface for the server’s IP address and set the sample rate and other parameters as appropriate to start receiving from the RTL-DVB USB receiver served by the Raspberry Pi. https://www.youtube.com/watch?v=pSq39ydjlQU
Having the AllStarLink Radio controller installed and having the Asterisk ver. 13 installed, I needed to configure the two units to make a radio telephone system. I wanted the system to work over a HSMM-MESH network and the configuration files reflect this in as much as the addresses are using Host Names instead of static IP addresses. Changing from Host Name to static IP should be about the only thing needed to use these files over a standard LAN network. These configurations result in a radio telephone system with the following provisions:
AllStar Node 28174 controls a Yaesu FT-7800R simplex transceiver
The AllStar Node accepts incoming IAX calls from the WAN or LAN
The AllStar Node registers SIP Telephones on the LAN
The AllStar Node is linked with a SIP bridge to the Asterisk v.13 PBX
The AllStar Node has Auto-Patch and Reverse Auto-Patch to the simplex radio
The Asterisk v.13 PBX is linked with a SIP bridge to the AllStar Node
The Asterisk v.13 PBX is registered with http://voip.ms for inbound and outbound calls to the PSTN
The Dial Plan provides all telephones and radio Auto-Patch outbound calls to the PSTN
The Dial Plan only provides inbound telephone calls from the PSTN to 1 extension which is a DECT phone cluster
The Asterisk v.13 PBX is providing Voice Mail to the radio telephone system