[New User] Using Minicom and a USB/Serial cable to talk to your KPC 3+
Over the weekend, I was showing Linux and Packet radio and for some reason I could not talk to my TNC, a KPC 3+. It was at this point that I realized I had forgotten more about Linux (and minicom) than I had about the commands needed to control the TNC. So, in the interest of helping save you some time, here is a quick write up on using minicom with a USB/Serial adapter to talk to your TNC, specifically, a KPC.
Minicom is an old school program that is available for most of the distributions but may not be installed by default. The good news: it is in all the repositories, so you can pull it down and install it quickly.
It is a serial terminal program that runs from the command line, but can sometimes be a little fussy to get working, and I will admit that I have not used minicom with a USB/Serial converter.
First, you have to know what tty port your USB/Serial converter is
on. So, plug it in, give it a minute and then type at a console port:
dmesg | grep tty
You should get something like this back:
kg4giy@kauai:/$ dmesg | grep tty
[ 0.001982] console [tty0] enabled
[ 686.529224] usb 2-2: pl2303 converter now attached to ttyUSB0
In this case, the converter is attached to ttyUSB0, you when you
configure minicom, you want to use /dev/ttyUSB0 as the serial port
To start minicom then (assuming you have not configured it, but you
know the modem speed of the TNC) type:
$ sudo minicom -s
Note that minicom requires root privileges. You will be prompted for
Select "Serial port set up" from the list with the cursor keys and set
the serial device and the Bps/par/bits (8/N/1 and whatever the speed
of your TNC is). Press , Save setup as dfl to save your
settings and then select Exit to enter minicom.
Turn on the TNC. Press once or twice if you do not get the
TNC cmd: prompt and you should now have control of the TNC.
When you are done, A then Z will bring up the help menu and you
can exit by pressing Q or A Q to exit.
One thing to note. Minicom has a much smaller set of connection speeds. For overall interoperability, it is best to set the baud rate of your TNC to 9600, with 8-n-1 for parity. This will facilitate connectivity with a multitude of devices, including a simple VT220.
I hope this saves you all a few minutes!
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide