We would like to thanks all participants who made themselves available for the seminar. They were coming as far as Kelantan and Johor to be in the seminar. As the organiser, we're really grateful for all of them and when we planned for this seminar, we did not expect that we're going to get more than 40 participants, but the seats were booked quite fast and we added another ten seats extra.
For those who were not able to attend/register for this time, we've posted the videos and can be found in the following youtube playlist:
Was looking for the best AC wifi router to replace my Buffalo WHR-G300NH and found that TP-Link has just released an Archer C7 V2 which has wifi card supported by ath10k driver based on the information found here.
Here is the packaging, it says that it supports Unifi & Maxis Fiber but the support is not out of the box. You need to ask the seller a beta firmware which has VLAN support but I couldn't get mine working using even the beta firmware on my Maxis Fiber. Emailed TP-Link support but got a reply saying that they don't have Unifi/Maxis Fiber ready firmware and asked if I want to swap with one that already have, but nah, I bought the router not for running the stock firmware anyway.
Ver 2.0 hardware as per the sticker.
Anyway, I waited for a week or so and someone came up with the new hardware profile which creates the correct firmware image for OpenWrt. If you've this new V2.0 hardware and wanted to run OpenWrt on it but couldn't wait to get the patches into the trunk, check this patches:
To build your own OpenWrt firmware for this ver 2.0 hardware, followed these steps:
1. Have Debian 6.0 or any development system which could cross-compile the OpenWrt firmware. There are many guides available on the net, but for me, I've a VMWare Debian 6.0 VM ready on my Hackintosh machine.
3. To generate the image, I was using the following command, I need the ath10k and luci support in the image:
$ make image PROFILE=ARCHERC7V2 PACKAGES="ath10k luci"
4. The generated image ready to be flashed can be found in the bin/ar7xxx/ as openwrt-ar71xx-generic-archer-c7-v2-squashfs-factory.bin
5. Go and flash the firmware, do remember, the default IP address for OpenWrt router is 192.168.1.1.
To get Maxis Fiber to run, just go to network->vlan and have the following, surely don't forget to set the PPPOE userid and password:
Kami akan mengajurkan pembentangan teknikal berkenaan dengan APRS pada 3/5/2014 bertempat di RSM. Antara tajuk-tajuk yang akan dibentangkan pada hari tersebut ialah:
1. Apakah itu APRS? 2. Sejarah perlaksanaan dan penggunaan APRS di Malaysia. 3. Mod Digital di dalam radio amatur. 4. Demonstrasi alat2 dan penggunaan APRS/mod digital: - UiView/agwpe/tnc - Router/aprx/tnc - RaspberryPi/RTLSDR - WX station - WinLink, SSTV etc.
Setiap pembentangan akan diadakan selama 45 minit dan demonstrasi akan diadakan disebelah petang.
Pembentang pendek ini akan berjalan selama sehari sahaja dan kami amat berharap agar rakan-rakan peminat radio amatur akan mengambil kesempatan ini untuk menambahkan ilmu dan mengenali dengan lebih dekat lagi apakah itu APRS dan mod digital.
We are going to have a technical talk on APRS. The talk will be on the 3rd of May, 2014 at RSM. We have come up with the following topics which will be presented on that day:
1. What is APRS? 2. Usage and implementation of APRS in Malaysia from our experience. 3. Digital modes in amateur radio. 4. Demonstration on the equipment and how to use them, APRS/digital mode: - UiView/agwpe/tnc - Router/aprx/tnc - RaspberryPi/RTLSDR - WX station - WinLink, SSTV etc.
Each presentation could be around 45 minutes or less except for the demonstration which will be done in the afternoon.
This will be a one day event and we hope we and many other ham radio enthusiasts will take this chance to enhance our knowledge on APRS and digital mode.
9:30 - 10:00AM Registration 10:00 - 10:15AM Opening 10:15 - 11:00AM Introduction – What is APRS? – Mr Fadzil Omar (9W2SMF) 11:05 - 11:35AM Usage and implementation of APRS in Malaysia – from our experience – Mr Faizi (9W2WEE), Mr Arman (9W2CEH), Mr Alias (9W2ALS) 11:40 - 12:30AM Digital mode in amateur radio – tentatively by 9M2CQC 12:30 - 01:30PM Lunch break 01:30 - 05:00PM Various demonstrations on the usage of APRS and digital modes including APRS, SSTV, WinLink, etc. – Mr Weerut (9W2RUT) and team.
My Argentdata Tracker 3 Mini, it's been lying around for almost a year,
before I start to play with it again. Our group ordered few units in
bundle and most of it have been dispatched to top mountain digipeater.
Following the success of OT2m, the T3 mini also worked well. I've test
with 3-4 type GPS receiver, but none of it work with T3 mini...something
must be wrong.
The T3 is lying around because it not capable to use
it as tracker. I've tested with the larger version of T3, and it working
well as expected. When swap with the mini version, it can't run. The T3
mini is not accepting the GPS data.
After swapping the RX and TX line of serial port and changing to port B
it still not go through... Then I start to email Scott, and he guided me
through a few troubleshooting method. I report back every his opinions.
And yet still no success.One of his guide is to monitor incoming data
string from Port A using terminal via Port B, I use the GPS simulator,
and I could see GPS string coming in.The T3 mini led blinking! I swap to
GPS receiver,no data coming in. Led also stop blinking.
Suddenly I remember when I'm troubleshooting the KF-163 ( from Jancorver
Museum), the KF-163 also not transmitting even I've tried many GPS
receiver. The I refer back to the manual, and I see they only using the
GPS TX data line only, they didn't connect the GPS RX data, just leave
I heat up my soldering iron, and remove the GPS RX data, plug it
back to T3 mini, and power it up...and I can see the GPS string in the
terminal, LED also blinking. YES!! it can work as tracker now.
I wrap the wire, put the T3 mini back in a box, move it to my car, replace it with my current OT1+, and start tracking again.
I email Scott and notify him the problem.
What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:
For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD card
A USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.
Here is the configuration on how to get the things working together, courtesy of svxlink.de website:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zip
Unzip the file and copy it to your SD card using the following instructions that can be found here.
Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connect the RasPi to your router via CAT5 cable.
To find the IP address of your RasPi, just go to your router status and look for the hostname raspberrypi.
Use SSH connection, logon to the RasPi using the default username/password which should be: pi/raspberry
If you've bigger SD card then the 2GB image, you may want to use fullest capacity of the SD card, run the raspi-config command as sudo:
$ sudo raspi-config
Choose the first option to expand rootfs. Exit when done.
Edit the following config files for svxlink (command):
$ sudo nano /etc/svxlink/svxlink.d/ModuleEchoLink.conf (edit the callsign - use sysop -L callsign, password, sysop, location and description)
$ sudo nano /etc/svxlink/svxlink.conf (edit the callsign), if you're using echolink interface that uses VOX, just leave the others as is. Edit the APRS info too as required.
To tune the mic/speaker, use alsamixer:
$ sudo alsamixer (use the up/arrow to tune the volume, right/left to move between speaker and mic sliders).
If the slider has MM underneath them, it means that they're muted, press 'M' to unmute.
You should be done with the configuration, you may run the svxlink now to test it out.
$ sudo svxlink
Your node should appear in the echolink now. Try to use your PC or android client to connect to your node and see if it is working. You may need to configure your router to allow echolink to work, use port forwarding and forward the UDP port 5198-5199 and TCP port 5200 to your RasPi IP address.
If everything is working as expected and you want to run svxlink as a service, follow the steps here. The link to auto start the server has been vanished, so the best to do an autostart of the svxlink is by running the following command (if the /etc/init.d/svxlink is not present, copy the script over from the source under distribution/debian/etc/init.d/):