Categories
Popular Posts
RSS Feeds
ArchivesUsing Your PC Sound Card As an Oscilloscope in Linux
June 6th, 2006If you a home hobbiest such as myself, having an oscilloscope is ideal, but may not be economically feasible. However, there is a free option available. xoscope For Linux is a GTK application which allows you to view signals through your PC's sound card (thus limiting the range to audio frequencies dependent upon the sound card being used). This can come in handy for robotics type hobby projects. Additionally, the author (Tim Witham) has provided a buffer hardware circuit to buffer the proble similar to a true oscillosope and protect your PC's Line In from excessive voltages.
Installing xoscope
- Download xoscope For Linux.
- Extract the tarball.
- Configure, Make, and Install:
./configure
make
su
make install - Enable capture from your Line-In audio jack (Gnome):
Open the Gnome Volume Control from the menu: System > Preferences > Volume Control.
Click Capture tab.
Enable capture for the Line-In channel by clicking the "Toggle Audio Capture from Line In" button.
Posted on
Tuesday, June 6th, 2006 at 8:49 am
Categories
Linux Robotics/Electronics
Related Posts
Technorati Tags
July 15th, 2008 at 8:11 pm
Do you proof read you text?
July 26th, 2008 at 8:01 am
Works! Thanks... I was looking for something like for a while now and... well... I just "stumbled" on it.
Jerry
July 26th, 2008 at 6:51 pm
Do you proofread you text?
Do you proof read your text?
Do you proofread your text?
Apparently not
July 26th, 2008 at 10:45 pm
"Do you proofread your text"?
No, this is a blog. That should be enough of an explanation... but... I write this very, very quickly in what very little free time I have. I write this to share information, for free, to the community.
When writing books or articles or papers, yes, I proof read my work and write multiple drafts. When I write on my personal blog, sharing information in my free time, I do not proff red my work. I rely on my readers to put the mistakes into context and determine the meaning and appreciate the fact that I took time to share what I've learned.
That being said, I appreciate emails pointing out mistakes, and if/when I have time, I'll make the correction. But if it's not a technical error I don't give it much priority.