- \n
- Any linux machine with a USB port and a Linux based operating system with\u00a0FTDI USB-Uart driver<\/a>.\u00a0During the development we have used Alix 2d13 from\u00a0PcEngines<\/a>. And during development we have installed Voyage-Linux on them. But radiotftp is also tested on\u00a0Bifrost OS<\/a>.<\/li>\n
- Radiometrix UHX1<\/a>\u00a0or similar devices, one for the server one for the client.<\/li>\n
- Interface card for Uhx1. These cards are not sold anywhere but you can build one very easily on your own. The schematic of such a card is below. If you are only planning to use the card for radiotftp you don’t need the audio components (i.e. any component\/wire that is connected to the audio block). You can also download pcb designs for geda and proteus from\u00a0my github repository<\/a>.<\/li>\n
- A USB TTL UART cable that allows CTS\/RTS signalling with 3.3 V or 5 V signal level. We prefer using\u00a0FTDI cables<\/a>\u00a0for the purpose.<\/li>\n
- A matched antenna for 2m band (144 Mhz band). A simple and good antenna is a 2 2m long wire antenna, but you can use a 50 cm wire antenna if you want to keep it short. We have used CR8900 antenna from Yaesu<\/a>.<\/li>\n
- You will also be needing the uhx1_programmer from my github<\/a> if you want to program the uhx1 frequency and power parameters in a simple way.<\/li>\n
- And finally you have to clone the\u00a0radiotftp software from github<\/a>.<\/li>\n<\/ul>\n
\n- \n
- \n
![\"Uhx1](\"https:\/\/alpenian.alpsayin.com\/blog\/wp-content\/uploads\/2013\/04\/Uhx1_schematic-300x211.png\")
<\/a>Uhx1 Uart\/Soundmodem Interface Card<\/figcaption><\/figure>\n<\/dt>\n - Bim2a UART Interface Card Schematic<\/dd>\n<\/dl>\n<\/div>\n
Setup:<\/h1>\n
- \n
- We will start the setup by first demonstrating how to program the Uhx1. First, clone the uhx1_programmer<\/a> into your home directory.<\/li>\n<\/ul>\n
git clone\u00a0https:\/\/github.com\/alpsayin\/uhx1_programmer.git<\/pre>\n
- \n
- Then make clean -for good practice- and make && sudo make install to install the uhx1_programmer.<\/li>\n<\/ul>\n
cd ~\/uhx1_programmer\r\nmake clean\r\nmake && sudo make install<\/pre>\n
- \n
- Now you are ready to program you Uhx1 in a very simple way. You should note that this software doesn’t allow you to program every aspect of the Uhx1, but it suits the requirements of most users. Type in uhx1_programmer to terminal to get the help message.<\/li>\n<\/ul>\n
uhx1_programmer device_name\r\ndevice_name : i.e. \/dev\/ttyUSB0\r\nBuild Date: Apr 4 2013 16:16:24<\/pre>\n
- \n
- If you see this message, you are good to go. It is a very simple menu driven software so all that is left to do is to invoke the program with the correct usb device.<\/li>\n<\/ul>\n
uhx1_programmer \/dev\/ttyUSB0<\/pre>\n
[1] - Read Mode\r\n[2] - Set Mode\r\n[3] - Set Default Channel\r\n[4] - Set Default Power\r\n[5] - Jump to Channel (volatile)\r\n[6] - Select Tx Power (volatile)\r\n[7] - Read RSSI\r\n[8] - Dump Eeprom Contens\r\n[9] - Exit (or Ctrl-C)\r\nEnter a selection [1-9]<\/pre>\n
- \n
- When you get to the menu it us up to you to set the parameters. But you should note that both the server side and the client side MUST be programmed to the same frequency in order to communicate. Apart from that, if you USB port is a low power port, then setting the TX power to maximum is not a good idea, since trying to draw higher current than the port can handle can cause distortion, hence loss of range, QoS etc.<\/li>\n
- Do this settings for both (or rest) of the Uhx1s that you have.<\/li>\n
- Alright! You are now ready to set up the radiotftp and sensd if you are interested.<\/li>\n
- Assuming that you cloned the radiotftp software to your home directory, cd into the radiotftp folder.<\/li>\n<\/ul>\n
cd ~\/\r\ngit clone https:\/\/github.com\/alpsayin\/radiotftp.git\r\ncd ~\/radiotftp<\/pre>\n
- \n
- You should select the ax25 build, so cd into the ax_25 build folder.<\/li>\n<\/ul>\n
cd ax25_build\/<\/pre>\n
- \n
- It is always good practice to clean and then make. So clean and make.<\/li>\n<\/ul>\n
make clean && make<\/pre>\n
- \n
- If you are seeing “Finished building target: radiotftp<\/em>“, you are almost good to go. Now \u00a0we are going to create symbolic links to binary files so that we access them anywhere.<\/li>\n<\/ul>\n
sudo ln -s ~\/radiotftp\/ax25_build\/radiotftp \/usr\/sbin\/radiotftp<\/pre>\n
- \n
- Go to your home directory again and try typing radiotftp, if you get the help text, then you are good to go<\/li>\n<\/ul>\n
radiotftp sends or listens for a tftp request<\/pre>\n
legal invocations:\r\n radiotftp_uhf\r\n radiotftp_vhf\r\nBuild Date: Apr 4 2013 12:54:33\r\nUses ax25 link layer\r\nradiotftp mode [-dst] [-b] [-f] terminal [command filename] \r\n mode uhf or vhf -b run in background (EXPERIMENTAL, do NOT use this!)\r\n -f defines a different local filename for put and get\r\n and defines a different remote filename for append and appendline\r\n -dstXXX.XXX.XXX.XXX sends the request to XXX.XXX.XXX.XXX\r\n default is broadcast Local address settings are read from a 'radiotftp.conf' file\r\n Examples: \r\n radiotftp uhf \/dev\/ttyUSB0 \r\n radiotftp uhf -flocalphoto.jpg \/dev\/ttyUSB0 get remotephoto.jpg\r\n radiotftp uhf -flocalmusic.mp3 \/dev\/ttyUSB0 put remotemusic.mp3\r\n radiotftp vhf -dst10.0.0.1 \/dev\/ttyUSB0 appendfile logfile.txt\r\n radiotftp vhf -fremote_sensors.dat \/dev\/ttyUSB0 appendline '{TELEMETRY BATTERY=3.3V}'\r\nexiting...<\/pre>\nUsage:<\/h1>\n
SERVER SIDE:<\/h3>\n
- \n
- Radiotftp can send and receive files\u00a0only\u00a0from the directory that it is running in. It is possible to try to use relative upper directories, but it’s not advised. Unpredictable things might happen. For the purposes of hosting I create a directory in my home folder called radiotftp_host<\/li>\n<\/ul>\n
mkdir -p ~\/radiotftp_host<\/pre>\n
- \n
- Then cd into that directory and create a file called ‘radiotftp.conf<\/a>‘. This file contains the hardware address (Amateur Call Sign) and your IPv4 address in two lines. An example is below. Note that this file needs a new line at the end of file to work properly.<\/li>\n<\/ul>\n
cd ~\/radiotftp_host\r\nnano radiotftp.conf<\/pre>\n
TA2IAS4\r\n44.140.1.4<\/pre>\n
- \n
- Then run the radiotftp server with suitable parameters. Since we are using radiotftp with Uhx1, we are going to invoke radiotftp with vhf parameter and assuming that your FTDI Usb Uart is mounted at \/dev\/ttyUSB0 we type in the command below. If you have more than 2 nodes in your network you should also specify a destination with -dst parameter or else the network is most likely to fail.<\/li>\n<\/ul>\n
radiotftp vhf \/dev\/ttyUSB0<\/pre>\n
Running with UHF band 19200 baud version\r\nAX.25 Callsign: TA2IAS4\r\nUSING AX25 LINK LAYER!!!\r\nIPv4 Address: 44.140.1.4\r\nhello radio world!\r\nstarted listening...\r\ntransmit_length=130<\/pre>\n
- \n
- If you can’t open the device, the most probable cause is that you dont have the right permissions for \/dev\/ttyUSB0. To set them right type in the command below. This command will give read+write access to every user.<\/li>\n<\/ul>\n
sudo chmod 666 \/dev\/ttyUSB0<\/pre>\n
- \n
- Your radiotftp server is up and running, now we can now set the client. But before that, many users ask how to invoke radiotftp on the background during boot. Easiest practice is to add a few lines into \/etc\/rc.local to cd into your home directory and run radiotftp from there.<\/li>\n<\/ul>\n
cd ~\/radiotftp_host\r\nradiotftp vhf \/dev\/ttyUSB0 &<\/pre>\n
- \n
- Add the above lines to your rc.local file and during boot radiotftp should be started with root priveleges (no permission issues). Now, you are completely ready to set up the client.<\/li>\n<\/ul>\n
CLIENT SIDE:<\/h3>\n
- \n
- Client side setup is not so different than the server side. For good practice, I prefer creating a folder called radiotftp_client in my home directory.<\/li>\n<\/ul>\n
mkdir -p ~\/radiotftp_client<\/pre>\n
- \n
- Like for the server side, you again need a ‘radiotftp.conf<\/a>‘ file for hardware address and IPv4 address setup. Again note that this file needs a new line at the end of the file to work properly.<\/li>\n<\/ul>\n
cd ~\/radiotftp_host\r\nnano radiotftp.conf<\/pre>\n
TA2IAS15\r\n44.140.1.15<\/pre>\n
- \n
- Again for good practice it is a good idea to test connectivity by running the radiotftp as server, on the client side. If there is a connection, the simple hello world protocol should help the server side to discover the client side. If the client side is discovered, you should see a new neighbour message in server side.<\/li>\n<\/ul>\n
New neighbour:\r\nIP = 44.140.1.15<\/pre>\n
- \n
- \u00a0To send a single file execute a command like below. If you don’t specify a destination address the software will automatically broadcast the requests. This works just fine if you have only 2 nodes. But if you have more than 2 nodes in your network you MUST specify a destination address or else the software will behave unstable, because logically it is irrational to make connection with broadcast IP.<\/li>\n<\/ul>\n
radiotftp vhf \/dev\/ttyUSB0 put localfile.txt<\/pre>\n
radiotftp vhf -dst44.140.1.4 \/dev\/ttyUSB0 put localfile.txt<\/pre>\n
Client Side Stdout:<\/p>\n
Running with UHF band 19200 baud version\r\nAX.25 Callsign: TA2IAS15\r\nUSING AX25 LINK LAYER!!!\r\nIPv4 Address: 44.140.1.15\r\nput\r\ndestination = 255.255.255.255\r\nlocal-filename = ''\r\nremote-filename = 'alpsayin.txt' -> 12\r\nfilename-check = 0x02\r\nempty local filename, copying remote filename\r\ntftp src port = 236\r\nremote_filename = 'alpsayin.txt'\r\nstarted listening...\r\ntransmit_length=156\r\ntftp wrq ack #0 received\r\nsent data size = 34\r\ntransmit_length=174\r\ntftp error received -> TRANSMISSION COMPLETE: Closing in 10 seconds\r\nexiting...<\/pre>\n
Server Side Stdout:<\/p>\n
filename: 'alpsayin.txt'\r\nmode: netascii\r\ncomment: \r\ntftp src port = 25313\r\ntftp WRQ connection received 12:37:23.433.952\r\nopening alpsayin.txt\r\nsent ack size = 4\r\ntransmit_length=114\r\nblock #1 length=34 written=30\r\nsize=34 -> EOF\r\ntransmit_length=202\r\nconnection closed<\/pre>\n
- \n
- Great! Now, you have sent your first file over a UHF radio link. During our development we used this link to send wireless sensor network data collected by a software called\u00a0sensd<\/a>. Sensd software is not off-the-shelf ready to be used with radiotftp so we forked it and modified it a little to buffer some messages and relay them to the radio link when the buffer is full. The modified\u00a0sensd<\/a>\u00a0can be cloned from\u00a0here<\/a>.<\/li>\n
- If you want to use the modified sensd with a KTH mote, you should clone sensd into your home directory and modify a few files after building it.<\/li>\n<\/ul>\n
cd ~\r\ngit clone https:\/\/github.com\/alpsayin\/sensd.git\r\ncd sensd\r\nmake\r\nsudo make install<\/pre>\n
- \n
- Now you have sensd ready to be invoked from wherever you want. How you use sensd is up to you, it does original job of collecting wireless sensor network data wherever or however you invoke it. But to make it relay the collected data to radio, you must put a shell script called\u00a0sendItAway.sh<\/a>\u00a0in the same directory you invoke it. For this purpose I recommend using the radiotftp_client directory that we created earlier. And then we can copy the example\u00a0sendItAway.sh<\/a>\u00a0file<\/li>\n<\/ul>\n
cd ~\/radiotftp_client\r\ncp ~\/sensd\/sendItAway.sh .\/\r\nnano sendItAway.sh<\/pre>\n
#!\/bin\/sh \r\nradiotftp vhf -fsensors.dat -dst255.255.255.255 \/dev\/ttyUSB2 appendline $@\r\n#echo $@ >> echo.txt<\/pre>\n
- \n
- The only modifications you need to do is to change the destination address if you have more than 2 nodes, setting the correct usb uart device as in the 4th parameter and finally using vhf mode instead of uhf.<\/li>\n
- After that you should invoke the sensd from this directory WITHOUT any file parameter, and all is set. If you type in a file parameter with ‘-f’ option sensd will NOT relay the data to radio, but instead it will save it to that file.<\/li>\n
- Finally, most users prefer invoking sensd in the boot, for this purpose you can add a few lines into the previously mentioned rc.local file in \/etc\/rc.local.<\/li>\n<\/ul>\n
sudo nano \/etc\/rc.local<\/pre>\n
cd ~\/radiotftp_client\r\nsensd &<\/pre>\n
- \n
- Now your client setup is complete. In the boot time, sensd will be started to collect data. And when its internal buffer is full, it will relay the buffered data by invoking radiotftp for a single time.<\/li>\n<\/ul>\n
Finally; remember that there isn’t much documentation about this on the internet. So if you have a question, ask it below and I’ll try to answer. In such way we can build up a knowledge base.<\/h2>\n
<\/h2>\n","protected":false},"excerpt":{"rendered":"
You want a simple manual to jump into packet radio networking with radiotftp? You have the Radiometrix Uhx1 devices ready at your hand with boards and everything? Just follow this guide thoroughly and you should have no problem. What you need for both sides: Any linux machine with a USB port and a Linux based […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":40,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"ngg_post_thumbnail":0,"footnotes":""},"class_list":["post-23","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/pages\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":3,"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/pages\/23\/revisions"}],"predecessor-version":[{"id":325,"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/pages\/23\/revisions\/325"}],"up":[{"embeddable":true,"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/pages\/40"}],"wp:attachment":[{"href":"https:\/\/alpsayin.com\/blog\/wp-json\/wp\/v2\/media?parent=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Now your client setup is complete. In the boot time, sensd will be started to collect data. And when its internal buffer is full, it will relay the buffered data by invoking radiotftp for a single time.<\/li>\n<\/ul>\n
- If you want to use the modified sensd with a KTH mote, you should clone sensd into your home directory and modify a few files after building it.<\/li>\n<\/ul>\n
- Great! Now, you have sent your first file over a UHF radio link. During our development we used this link to send wireless sensor network data collected by a software called\u00a0sensd<\/a>. Sensd software is not off-the-shelf ready to be used with radiotftp so we forked it and modified it a little to buffer some messages and relay them to the radio link when the buffer is full. The modified\u00a0sensd<\/a>\u00a0can be cloned from\u00a0here<\/a>.<\/li>\n
- \u00a0To send a single file execute a command like below. If you don’t specify a destination address the software will automatically broadcast the requests. This works just fine if you have only 2 nodes. But if you have more than 2 nodes in your network you MUST specify a destination address or else the software will behave unstable, because logically it is irrational to make connection with broadcast IP.<\/li>\n<\/ul>\n
- Again for good practice it is a good idea to test connectivity by running the radiotftp as server, on the client side. If there is a connection, the simple hello world protocol should help the server side to discover the client side. If the client side is discovered, you should see a new neighbour message in server side.<\/li>\n<\/ul>\n
- Like for the server side, you again need a ‘radiotftp.conf<\/a>‘ file for hardware address and IPv4 address setup. Again note that this file needs a new line at the end of the file to work properly.<\/li>\n<\/ul>\n
- Client side setup is not so different than the server side. For good practice, I prefer creating a folder called radiotftp_client in my home directory.<\/li>\n<\/ul>\n
- Add the above lines to your rc.local file and during boot radiotftp should be started with root priveleges (no permission issues). Now, you are completely ready to set up the client.<\/li>\n<\/ul>\n
- Your radiotftp server is up and running, now we can now set the client. But before that, many users ask how to invoke radiotftp on the background during boot. Easiest practice is to add a few lines into \/etc\/rc.local to cd into your home directory and run radiotftp from there.<\/li>\n<\/ul>\n
- If you can’t open the device, the most probable cause is that you dont have the right permissions for \/dev\/ttyUSB0. To set them right type in the command below. This command will give read+write access to every user.<\/li>\n<\/ul>\n
- Then run the radiotftp server with suitable parameters. Since we are using radiotftp with Uhx1, we are going to invoke radiotftp with vhf parameter and assuming that your FTDI Usb Uart is mounted at \/dev\/ttyUSB0 we type in the command below. If you have more than 2 nodes in your network you should also specify a destination with -dst parameter or else the network is most likely to fail.<\/li>\n<\/ul>\n
- Then cd into that directory and create a file called ‘radiotftp.conf<\/a>‘. This file contains the hardware address (Amateur Call Sign) and your IPv4 address in two lines. An example is below. Note that this file needs a new line at the end of file to work properly.<\/li>\n<\/ul>\n
- Radiotftp can send and receive files\u00a0only\u00a0from the directory that it is running in. It is possible to try to use relative upper directories, but it’s not advised. Unpredictable things might happen. For the purposes of hosting I create a directory in my home folder called radiotftp_host<\/li>\n<\/ul>\n
- Go to your home directory again and try typing radiotftp, if you get the help text, then you are good to go<\/li>\n<\/ul>\n
- If you are seeing “Finished building target: radiotftp<\/em>“, you are almost good to go. Now \u00a0we are going to create symbolic links to binary files so that we access them anywhere.<\/li>\n<\/ul>\n
- It is always good practice to clean and then make. So clean and make.<\/li>\n<\/ul>\n
- You should select the ax25 build, so cd into the ax_25 build folder.<\/li>\n<\/ul>\n
- If you see this message, you are good to go. It is a very simple menu driven software so all that is left to do is to invoke the program with the correct usb device.<\/li>\n<\/ul>\n
- Now you are ready to program you Uhx1 in a very simple way. You should note that this software doesn’t allow you to program every aspect of the Uhx1, but it suits the requirements of most users. Type in uhx1_programmer to terminal to get the help message.<\/li>\n<\/ul>\n
- Then make clean -for good practice- and make && sudo make install to install the uhx1_programmer.<\/li>\n<\/ul>\n
- Bim2a UART Interface Card Schematic<\/dd>\n<\/dl>\n<\/div>\n
- Radiometrix UHX1<\/a>\u00a0or similar devices, one for the server one for the client.<\/li>\n