Neodux.com

Continue Reading...

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

After the success of the DUX Yagi-Uda post and it finding its way to Hack-A-Day, I decided I should probably go in to more detail with each blog entry when I'm attempting to explain something technical.

In the past, I've tried be as succinct and just-the-fact-ma'am as I can so the article doesn't make the main page a mile long. I always assumed if you wanted to know more you could just ask me. But, more often than not, I ended up with an article that I think was too shallow or too "in-passing". So, for the sake of those that don't know me personally and would like more information, and in keeping with the spirit of information exchange on the web, I think it's best if I link to and explain all relevant information. To keep the main page short I've decided to limit the amount of words in a story that gets shown at a glance.
I've broken up the links to have the "Continue reading..." link on each article if it is longer than a preset length.

I'd really like to know what my core users think of this change. Is it for the better? Should I change the wording of the link? Should I display all information, longer or shorter at-a-glance summaries? You tell me.

DUX Homebrew Arrow Yagi

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

This summer I attended the TI-2 Space workshop put on by the ARRL and DARA in Dayton, OH. We spent 4 days learning how to make contacts with orbiting satellites like AO-27, AO-51 and the International Space Station, just to name a few. The antenna we used was the dual-band Arrow II Antenna. I've owned one for years and really like it. I wish more people had them, but I think most people think spending $140 for an antenna that can only handle 10W is a bit much.

My aim was to make a cheap alternative to the Arrow that is easy to break down for transport and storage. I really like the idea of using aluminum arrow shafts for elements; they are lightweight, straight, weather resistant, and fairly inexpensive. Another nice feature is the #8-32 threaded insert for broad heads that almost every arrow comes with.

I spent a couple of hours reviewing all the "cheap" and "ugly" yagi designs, as well as others like the "tape measure" and even a new-to-me "backpacker" design. They each have their own advantages and loyal followers.

I finally based my antenna design on one found in the ARRL Handbook from 1999. While not an exact replica, my design is very similar. I had decided to go with the through-boom design like the Arrow, as opposed to side-mounted because it is, in my opinion, cheaper. After buying 6 arrows and a quick trip to Lowe's I had a length of #8-32 all-thread and a piece of 3/4" conduit to use as the boom. I marked a straight line down the center of the boom to give me a point of reference, measured out the spacing holes, made sure I was drilling square and level and got to work. After the 3 holes were drilled, I cut 2.5" lengths of all thread for the director and reflector. Since I was going with the split driven element design of the IDX yagi, I would not need threading for the Driven Element, I'd use machine screws for that. Originally I planned to use nylon 8-32 all-thread to go through the boom for the driven element, and feed each side independently similar to the Tape Measure Yagi, but I couldn't find nylon all-thread, and the longest nylon screws to be found came up an inch too short.

I cut a length of RG-58 cable and soldered on two o-ring connectors to slip over the machine screws before screwing on an arrow.
Lastly I cut each arrow to the appropriate length, which worked out to:
- 19 5/8" for each Reflector arrow
- 18 1/8" for each Driven arrow
- 17 1/8" for each Director arrow
The measurements came from IDX's lengths, subtracting 3/4" (for the boom) and then divided by 2 to give me the necessary length for each arrow.
I used a cutoff wheel and my air compressor to cut the arrows to length instead of a hacksaw. The cutoff wheel leaves a clean cut as opposed to sawing.

After putting my MFJ-269 analyzer on the yagi, I found the lowest SWR to be about 1.4 right around the target frequency of 144.490 MHz. Not too shabby for a first yagi.
For those taking my lead, I found it helpful to feed the yagi as perpendicular to the boom as possible. It is also somewhat important for the O-ring feedline connectors to be on the same side of the boom as the arrow.

Here's a pic of me holding the 2m yagi. It's a bit larger than the commercially made Arrow.

update: I've been asked by more than one person why the split driven element. As you read above, it was semi forced on me by necessity. I needed it to be split for mechanical reasons. the screws going through the boom serve as a match, negating the need for the "hairpin" match from the tape measure yagi or a gamma match. The driven elements being split probably do affect the radiation pattern in the long-field, but perhaps only skew the pattern more in one direction.
(TLDR: it's easier that way and it just works!)

update #2: Hello Hack-A-Day! Yes, you can talk to the space station and many other amateur radio satellites.
update #3: Okay, for those that are interested, I'll be putting together kits if you want. Price to be determined based on what you want/need. You can email me at tommy@neodux.com for more info.

Kindle isn't kind anymore

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

I don't "get" the Kindle anymore. It's been almost 6 month since I got it, almost a dozen books later and I think I'm at the end of the road with this neat little device.
At first, I liked the idea of having free 3G internet available. Then low price point of books made it great for buying books without having to wait for the local bookstore to order them, or worse, paying the retail markup.

A couple months ago, Engadget broke this story which I just saw in the NYTimes: Target will begin selling the Kindle 2 in stores nationwide beginning on Sunday, June 6.

Funny, I was just at my local Target earlier this evening and found a book I've been wanting to read. I had read through the first chapter on my Kindle as a "sample", but never went beyond that. I checked the latest Kindle edition price... $12.99. Target's price for the book? $12.80!
Why would I want to buy the Kindle edition that I can't sell or share?!

To add insult to injury, I checked the same paperback on Amazon: $9.99. Amazon is selling the paperback for less than the electronic version! Now, they're going to sell the Kindle at Target in a matter of days and the electronic version of the book costs even more than the same book in the store!

I think the Kindle's business model is falling apart (and has been). I believe the Kindle is headed for the same fate as the other innovative e-ink device: The OLPC (XO) laptop. Both situations are sad, because each had so much potential. Neither will grow beyond a neat concept without completely reinventing itself (which the OLPC seems to be doing with its tablet).

Amazon has been too slow to act on customer ideas, lacked any sort of customization, and failed to cash in on an exploding community of Kindle owners. ...and I don't blame Apple either. The iPad won't replace the Kindle. (eInk is to easy on the eyes for reading - any who wants glossy ebooks?) Amazon let publishers push prices too high and, at least for me, is what kills the Kindle experience.

update: I emailed my concerns to Amazon and got an email reply very quickly. Here's an excerpt from the email:
The price you pay in the Kindle store is based on a number of factors, including the initial publisher price. Recently, several publishers modified their relationship with Amazon to a business model whereby the publisher, not Amazon, sells the Kindle book. In these cases the price is set by the publisher and you will see "This price was set by the publisher" on the product page.

We're working hard to build a successful digital book store and make every effort to provide you with the best prices possible. So hopefully they can get their business sorted out with the publishers and get back on track. We'll see.

Mr. Gober's Games

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

Most of the students where I teach have time in their computer labs to surf the web or play flash games. The IT department, in order to conserve bandwidth and filter "inappropriate material", need to block most games. Since most games are just mind-numbing wastes of time, most teachers support this. Students looking for games will scour the web searching for game sites that aren't blocked. As soon as one game site is discovered, the URL spreads like wildfire before the site is blocked in the next few days. The cycle repeats itself ad nauseum.

Seeing the problem from both sides, I decided to make an "approved games list" of games that at least feature some academic merit. I understand that games can be beneficial and educational while still being enjoyable. I asked my Computer Science class to find games they enjoy and add them to my games list. They needed to list the educational lessons found within the game and the supporting [wiki]TEKS[/wiki] on my games list.
The end result has grown into "Mr. Gober's Games". Several students use the site daily and it has received the approval of administration.
Ideally, the next step will be to house the site on the school network to reduce the bandwidth load and increase response speed for the user.

Recently I have added a page to add games, a method to report broken or inappropriate games and a new ratings system. The ratings system was my first successful foray into AJAX. I've attempted AJAX before but came up short. Fortunately jQuery made the effort much easier by abstracting most of the work for me. So, take a look at Mr Gober's Games and have fun - don't forget to vote for your favorites!

Programming Challenge: ROYGBIV

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

I'm not too sure why, but I always figured it was pretty straight forward, but I realize now that it isn't. As a personal challenge, I decided to see if I could make an HTML table with cells that are colored through the ROYGBIV color spectrum.
Strarting from Red, each row of cells would gradually change to Orange, Yellow, Green and so on. Simple enough right? I thought so too. It isn't.
Think you're good? See if you can come up with a block of code that achieves a gradual color gradient.

Must use web scripting language - output must be in HTML. (link us to your results(JavaScript, ColdFusion, etc are eligible.)
Must use a for-loop, while loop or combination thereof. Or explanation of what you did use.
Colors must displayed in an HTML table, rendered in a browser.
Color gradient must be in natural visible light color order, no jumping around.
No cop-outs, cheats or other tom-foolery. (Ex: If your language has a drawRainbow( ) function, that's off limits. hurr.)

Building a CPU

skaven — Thu, 01 Jan 1970 00:00:00 -0600

I've decided to take the plunge and start working on a project that has been sitting in the back of my head since college. I'm setting out to build a CPU from scratch.

I thought that the Neodux crew might want to follow along as I work on this insane project. But not too insane...I've already figured out how I'm going to do it. I just need to do it now.

Follow along and watch as I walk the thin line between avocation and insanity!

...And I know some of you guys are EEs -- maybe you can give me a hand when something eventually goes wrong...

Notes for web developers.

Mackieman — Thu, 01 Jan 1970 00:00:00 -0600

Attention website developers:

Have you spent the last six months living on Twinkies and jet fuel grade coffee to turn out your latest ~~abomination~~ creation? Does it incorporate validated syntax? Does it adhere to all of the W3C standards? Is it fully driven by CSS?

If so, that's great. You've worked hard to achieve what countless Geocities authors could only dream of.

However, this does not give you the right nor the justification to resize my browser without asking first. My personal window settings for my browser are just that: personal. Your content, while possibly revolutionary (but probably wholly unexceptional) is not special, and it does nothing to endear me to whatever your website is trying to tell me.

And woe be unto you if you're trying to sell me something. Not only will I never patronize your site again, I will post rants on websites explaining exactly how you should be publicly flogged for forcing your sizing preferences on the rest of us.

Stop being a butthorn and realize that your, "creatives" aren't anything more than some rendered text and a few pictures.

Kisses,

Mackieman

Kindle v iPad

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

I figure it's high time I publicly weighed in on this whole ebook wars thing. I was just reading and article over on Wired about the whole pricing dilemma currently plaguing Amazon.
I'll start off by saying that I am a Kindle owner/user, so take that as you will.

I was initially unimpressed with the launch of the iPad. the iPod blew us all away when it was announced, the iPhone blew us all away when it was announced. The iPad will take some getting used to. The screen still isn't e-ink like the most successful ebook readers, but it does have touch screen - something Amazon just realized customers want. It doesn't have the battery life of a Kindle, but it does have brand recognition.

The redeeming value about the Kindle, and I've said this all along, is that it adopts the UNIX mentality: "Do one thing and do it well". The Kindle is perfect for reading books. The great part is you can download the books via Whispernet wherever you happen to be. The iPad kinda offers this, but you have to pay more for the 3G device plus you have to pay for the data plan. (The Kindle data plan is free!) [sure, the basic iPad has wireless, but wifi may not always be available. it's not something I have to think about with the kindle]

Ok, so the iPad will let you surf the web, i'll give you that. Yes, the Kindle is essentially the links browser and Whispernet is slow compared to wifi, but remember, the Kindle is an ebook reader, first and foremost. It does that and it does it well, web is an after thought, the same way that iBooks was an afterthought to the enlarged iPod Touch.

There, I said it. The iPad is a grown up iPod Touch. It can surf the web, it can play apps, it has an ebook reader app - so does my iPhone. It does not have e-ink, long battery life, or instant free access anywhere. Is the iPad a Kindle killer? I think killer is too harsh a word for this situation. Capitalists: Competition is a good thing. The Kindle helped design the iPad, and the iPad will help redesign the Kindle. I'm excited to see what the next revision of the Kindle comes out looking like. I'm almost certain it will feature touch.

The iPad is definitely neat, but I think the Kindle will hold its niche - if Amazon can hold its publishers in place. I believe something definitely underhanded is going on between Mr. Jobs and book publishers, but I'll delve into that soon enough.

update: Well looks like gizmodo beat me to the punch with this article - however I'll expand on it with my thoughts later.

Neodux Mobile

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

As any of you reading this on a smartphone may have noticed. Neodux now comes in a leaner version: Neodux Mobile.

By examining $_SERVER['HTTP_USER_AGENT'] report for elements that reflect the most common mobile browsers, I can detect (usually) if you're viewing the page from a mobile device. (Blackberry, iPhone, Android, WinCE, PSP, Kindle are all supported.) As of this writing the layout is very spartan and only the main posts are displayed. Users cannot login to leave comments or shouts at the moment, but I hope to add that in the future. For now, it's just the core content of neodux but it loads much faster.

I'd label it alpha for the moment, but it should make reading any posts from a smartphone, Kindle or PSP much easier.

Texas is Growing (hands off)

Grendel — Thu, 01 Jan 1970 00:00:00 -0600

So the other night I was thinking about the map of our United States of America. I began to ponder just how states' boundaries are defined. Some states are defined by rivers, lakes and other bodies of water. Some states are defined by man-made boundaries (which can lead to some interesting disputes).

Currently, Texas' western boundaries are defined in the Compromise of 1850 as "that which is south of the 33rd parallel, and that which is south of the 36�30' parallel north and east of the 103rd meridian west." The eastern edge of the panhandle lies along the 100th meridian west. To the south, Texas has the natural boundaries: the Rio Grande and the Gulf of Mexico (src: Treaty of Guadalupe Hidalgo). Along the north, a natural border to Oklahoma exists along the Red River. To the East we have the Sabine River from the Gulf up to the 32nd parallel, then straight north to the Red River (Adams-On�s Treaty). Interesting, but so what? Plate Tectonics.

In the early 20th century, geologists developed a theory that described continental drift. They dubbed it Plate Tectonics. It has been discovered that continents do move, so naturally so does everything on them. Texas, and the vast majority of the United States "lower 48" (plus Alaska) ride on the North American plate. The North American Plate moves at about 1.5cm/yr more or less toward the Southeast. This means that Texas is slowly taking land away from New Mexico while losing land to Oklahoma and Louisiana. Texas will not lose land to Mexico, thanks to the natural boundary, the Rio Grande (which rides on the plate). Astronomical longitude/latitude lines do not move (they are based on the proximity to the poles and prime meridian (which is physically drifting too, but now there exist astronomical definitions to account for this) Because of this, the land that moves under the aforementioned longitude/latitude boundaries become, in essence, Texas.

Because of these findings, I hereby proclaim that at the time of this writing, I become sole owner of unclaimed lands that move into the boundaries of Texas. Hands off.

update: By my rough calculations, in 69,971 years I'll own all of present-day Texico, NM; and in 1,399,429 years I'll own present-day Clovis, NM. (I will cede Cannon AFB to the federal government.)

update #2: I also claim ownership of all lands that have entered the Texas boundaries dating back to the formation of said boundaries (1850). That should give me a strip of land about 6 ft of land about 241 miles long (assuming 1� is about 69mi) plus whatever land runs along the line from El Paso to the Pecos region.
2009-1850=159yrs, 159yr*1.15cm/yr=182.85cm ≈ 6ft