Tag Archives: farm network

Getting the most out of your router – part 2

2 Replies
RT-N66U

The ASUS RT-N66U – a modern, high-end home wireless router

In the last article in this series, I discussed what a home router is and a little bit about how it works, as well as providing guidance on how to set up the DHCP server.

IP addresses on your LAN are assigned one of two ways: either by the router’s DHCP server, which provides them out of the DHCP address pool (which I suggested should be 192.168.1.50 to 192.168.1.254) or by statically assigning them yourself (which I suggested should be out of the remaining 192.168.1.2 to 192.168.1.49 addresses). Assigning static addresses is very seldom necessary on modern routers, however, because most modern routers have a feature called “DHCP Reservations.” This allows you to specify the MAC address of a device and make sure it is assigned the exact same address via DHCP every time it is connected to the router. Using DHCP reservations, you can ensure that your laptop always gets the same IP address without having to configure a static address for it (which is a pain, since you’d have to re-configure it every time you go to the coffee shop).

Using either static addressing or DHCP reservations, you may want to make sure that “infrastructure” on your home network, like file servers, entertainment systems, or security devices always have the same IP address.

Your router’s NAT usually automatically closes off all the ports on your public IP address, making it impossible to access anything on your LAN from the Internet. In most cases, that’s a good thing – you don’t want the Internet able to reach your private network. But, in some cases, you want to make devices on your network available from the Internet (ALWAYS protected with strong passwords, of course!). The classic example is the IP camera set to watch something important on the farm – it could be the front drive, livestock, or your machine shed – you want to be able to access it from wherever you are so you can check up on it. But you might also want to be able to check and operate machinery like your grain dryer, pumps, irrigation systems, HVAC systems, etc. from a distance.

The IP camera has a webserver that uses port 80 (usually) for its interface, so the trick of port forwarding is to open one port on your public IP address and tell your router to “forward” all packets coming to that port automatically to port 80 (or whatever port you configure) on the camera. So you “knock a brick” out of the router’s firewall by specifying one port on the public side (I like to use ports 7001-7099, because very few services use these ports) and forward that public port to a port on your camera.

The way you do this varies from router to router, but the drill usually entails going to the “port forwarding” interface on your router and specifying the incoming or public port (7001), the device that’s receiving the packets (your camera’s IP address – 192.169.1.something), and the port on the device that will receive the packets (port 80). Then, if your public IP address is 101.102.103.104, you can access your camera on the Internet at http://101.102.103.104:7001 (the IP address, a colon, and the port number). Some routers allow you to specify only certain incoming IP addresses that can access the camera, but that’s usually not a good idea because, for instance, if you want to look at the camera from your smartphone, you won’t know the IP address of the smartphone.

NOTE: some routers (stupidly, in my opinion) require that the port numbers on the public side and the private side be the same – they won’t forward port 7001 on the public side to port 80 on your camera. If you have a router like that, you’ll need to reconfigure your camera (or whatever device you have) to the appropriate port (e.g. 7001) port before you can do the port forward. You shouldn’t forward ports under 1024 unless you know exactly what you’re doing, because you might be disabling something your router needs to function properly. Forwarding extremely popular ports like 80, 20, 21, 22, 23, 25, etc. can also attract password crackers and other undesirable elements to your network.

Let me emphasize at this point the importance of a strong password on anything that’s exposed to the Internet – if you can access it, so can anyone else, so make sure it’s locked down.

On my own home network, I have several ports forwarded to different IP cameras around my property, as well as ports forwarded to my desktop Windows machine (using VNC so I can access it easily when I’m away) and my Linux development machine (using SSH). I can actually access any of those devices using my smartphone, so I can stay on top of things anywhere I have an Internet connection.

Click here to go to Part 3

Getting the most out of your router – part 1

1 Reply

The venerable Linksys WRT54G – Courtesy of Linksys

The world of networking is complex, including that little bundle of technology sitting on your shelf – your router. It is actually a pretty amazing little device that can probably do more than you realize. In truth, the typical “consumer” router is a combination of three devices:

  1. A router – a router is a device with two or more ports that is used to connect two or more networks together. Typically, the consumer router has a “WAN” port that connects to the “Wide Area Network” of your Internet Service provider and “LAN” ports for your Local Area Network.
  2. An Ethernet switch – you may have noticed that your router doesn’t have two ports; most actually have five: one WAN port and four LAN ports. Inside the box is an Ethernet switch that turns the LAN port of the router into 4 LAN ports to which you can connect wired computers, servers, and even additional Ethernet switches if needed. Actually, it’s 5 LAN ports, because the fifth one is connected to…
  3. A WiFi Access Point – this is simply a wireless radio connected to an internal LAN port that provides a WiFi signal for computers, tablets, smartphones, IP cameras, entertainment systems, and all kinds of other things. This WiFi radio is usually optimized for short-range, indoor use, providing maximum throughput for a short distance.

One of the odd and important facts about a router is that it has two Internet Protocol (IP) addresses: one on the network to which its WAN port is connected (which should be a public IP address, visible from the Internet – e.g. 108.162.198.52, ayrstone.com’s address), and one on the LAN port, the network it creates for you (a private address, not usable from the Internet, e.g. 192.168.1.1). Its job is to take data packets from each network and move them to their destination network. So, if your computer is at 192.168.1.50 on the LAN, and it receives a packet on its WAN port destined for 192.168.1.50, it passes it to the LAN port where it finds its way to your computer. Similarly, if your computer creates a connection to 108.162.198.52, the router receives packets from your computer on its LAN port and routes them to the WAN port. When you print to your networked printer (at, say, 192.168.1.100), it receives packets from your computer and then just turns them around and sends them back down the LAN port, since they are not destined for the Internet.

The ability of the router to accept traffic on a single public IP address and enable several different computers at private IP addresses to have separate “conversations” with the Internet is called “Network Address Translation” or NAT. The way it does this is by using “ports” – simply numbers associated with every IP address.

Each IP address has 65,535 possible ports. Some ports have pre-assigned purposes, some are available for use by applications, and some are ephemeral – here’s a good explanation of which are which. NAT uses those ephemeral ports to keep the conversations between your network and the Internet straight; for instance, your computer’s conversation with this website might be using your public IP address’s port 55135, while another computer on your network might be having a conversation with another website on port 61234. To the two websites, it looks like the traffic is coming from a single computer, specifically your router. Your router then routes the responses from the websites to the correct computer based on the port on which the data comes in.

The private IP addresses on your network are usually assigned by your router using Dynamic Host Configuration Protocol or DHCP. When a computer connects to your network, it will ask the router for an address via DHCP, and the router will provide it one (assuming it has one to provide). The address is referred to as a “lease,” because it will expire at some point after the device leaves the network, so it can be used by another device. However, note that you can simply assign a static IP address to a device in your network, as long as (1) it is an IP address inside your network (usually meaning it has the same three first numbers as everything else on your local network, e.g. 192.168.1.x) and (2) it does not interfere with the DHCP settings on your router (if your DHCP server begins at 192.168.1.50 and your router is at 192.168.1.1, use static addresses between 192.168.1.2 and 192.168.1.49, and KEEP TRACK OF THEM WHEN YOU ASSIGN THEM!!!)

The first tip for getting the most out of your router is this: set up your router’s DHCP server carefully. I suggest setting your router’s IP address as 192.168.1.1 and setting your router’s DHCP range from 192.168.1.50 to 192.168.1.254 (204 addresses). The reason for this particular range is that, first, it allows for a large number of devices to automatically use your router, getting private IP addresses via DHCP (204) but still leaves you 48 addresses you can use for devices you want to statically assign. This gives you the flexibility to maintain, expand, and control your home network.

Alternately, most modern routers support DHCP Reservations, which allow you to ensure that the router ALWAYS provides the same IP address to a device on the network. That way you get the advantage of a static IP address (knowing where a device is at all times) with the advantage of DHCP (ease of configuring devices and the IP addresses being managed by the router).

Click here to go to part 2

Myths about Wireless Farm Networking

2 Replies

Myths are fun, but this guy won’t help you get the work done.

We have been talking about the myths of Wireless Farm Networking lately, and I wanted to add my own two cents worth here.

The article about the myths is excellent and stands on its own – I strongly suggest you read it. I thought I’d add a little about the topic here, by focusing on three aspects: Wireless, Farm, and Networking.

Wireless – I have seen “wired” farm networks – a number of livestock producers have trenched and buried fiber lines to their livestock buildings (Ethernet can only go 100 yards) for monitoring and control. However, it’s much cheaper now to go wireless, and it gives you much more flexibility. To build a good wireless network on your farm, you have to learn about “line of sight” (or, more correctly, Fresnel Zones) and position equipment so it has both power available and good radio signal from the rest of the network. It used to be that having a private wireless network across your farm was either technically impossible or cost-prohibitive, but we are proving that wrong every day.

Farm – A farm is pretty much defined as being in a rural area, and we’ve all seen that what works in town doesn’t necessarily work on the Farm, and vice-versa. The AyrMesh network is designed for farm use – relatively few people and machines spread out over a relatively large area. There are lots of good solutions for networking in town, where there are a lot of people in a small area, but they will never work as well as a solution designed specifically for the farm.

Network – The Internet Protocol (IP) network is the single, unified data communications medium for this century. I have seen farms that had a wireless link for their weather station, another wireless link for their GPS corrections, a home WiFI system and cellular coverage. Getting rid of the “point-to-point” solutions and putting everything on the network enables you to collect and transmit the data you need more easily, deliver what you need over the Internet, and gives you the option of adding new technologies to your operation quickly and easily.

Some people think this is revolutionary, but I would argue nothing could be further from the truth: this is the result of a clear evolution over time. In the 1970s academicians started tying computers together and transferring data over the first networks. In the 1980s networks came out of academia and started being used for business and even personal purposes; in the meantime, ham radio operators and researchers were starting to send digital data over radio waves. In the 1990s companies started to network their offices to share files and printers, as well as sending emails. Building-to-building microwave links became relatively common, and Industrial Automation moved to IP networks. In the 2000s the consumer internet became a reality, as did WiFi for wireless data, and we all got “on the net.” Now, in the 2010s, we have the Internet of Things and the low cost of high-power wireless networking, making this the decade of Wireless Farm Networking. The ability to monitor farm data and even control farm operations using a local network connected to the global internet will change agriculture forever.

Unmanned Aerial Vehicles (“Drones”) and Wireless Farm Networks

Leave a reply

One of the hottest topics in “Ag Tech” at the moment is Unmanned Aerial Vehicles (UAVs, also known as drones) and the role they can play for the farmer. Drones are hot right now, in Ag and other industries, because technology has made them much more adaptable and much lower in cost.

The possible benefits are tantalizing: an automatic, self-flying platform that can loft things into the air, take them where you need them, and take actions you prescribe. Just a few of the things drones can conceivably do for you:

  1. Take visible-light, near-infrared, and infrared photographs of all your fields at much higher resolution and in less time than satellite
  2. Get instant thermocline and other weather data (pop up 1000′ and check the temperature, wind speed, barometric pressure, etc.)
  3. “Run and get it” service for small items (see the beer drone and Amazon Prime Air)

When I was at the World Ag Expo a few weeks ago, there were several companies showing off drones and talking about drone-based ag services. Please make note of the distinction between drones and drone-based services, because, at the moment, it’s important. Or maybe not. I’ll explain as well as possible.

The Federal Aviation Administration has had a long-standing rule against the use of UAVs for “commercial purposes” – anything involving making money. Now, you can buy model airplanes with very sophisticated self-flying and video systems for fun or research, but not for any money-making purpose. However, a number of people couldn’t help themselves in making use of these amazing machines to enhance their businesses, and they have been getting “cease and desist” letters from the FAA. One guy named Raphael Pirker actually was fined by the FAA, giving him the opportunity to challenge the fine. He appealed to the National Transit Safety Board, and the administrative judge there ruled that the FAA did not have in place any actual regulations for the use of UAVs in non-navigable airspace, and therefore could not enforce the fine against Pirker. There’s a good article about this in Scientific American.

So, apparently, one currently can use UAVs for commercial pursuits, with some (not entirely clear) limitations. I’ll bet if you take your drone anywhere near a commercial airfield, for instance, you’ll get to meet some members of law enforcement and spend time with them. I’ll bet if you take your drone near any government installation, you will get to spend a serious amount of time with members of law enforcement and/or the military. In either case I’ll wager you’ll get to contribute a good amount of money to the government. And there are undoubtedly some private citizens who will happily shotgun your UAV out of the sky on sight.

I’ll also wager that the FAA (or some other part of the government) will create some rules about UAVs to protect people from stuff falling out of the sky on top of people and property, and having our neighbors peeking in 2nd (or 102nd)-story windows. But, for the moment, it looks like the skies are open, particularly out in the rural areas, and I expect farmers to be the first to benefit from UAVs. Some people like Chad Colby are already talking publicly about the opportunities.

Honestly, I think the current “state of the art” is mostly a plaything: the drones that are currently available are mostly manually radio-controlled and focused on live picture-taking. UAVs I have seen that might be put to use on the farm must be charged, taken to the field, flown around the field, and then the pictures (or other data) downloaded off the UAV (by bluetooth, WiFi, or transfer from some kind of flash card). This is a significant commitment of time, which limits how often you can really use the drone. A crop scout may be able to save a lot of the time he would normally spend by using a UAV to survey fields, but there’s benefit to the grower having a drone or drones that would continually survey fields.

The reason I am particularly interested in Ag Drones is because I believe they can become an important part of the day-to-day information-gathering apparatus. To be truly useful, however, I believe they must be:

  • Autonomous: flying over your fields automatically without intervention. Ideally, they would have a “home” out in the field where they would stay, and they would do their flying at specific times with no human interaction needed.
  • Smart: able to recognize problems and take appropriate action – recognize if there is something different in the fields, avoid danger, and report back
  • Connected: automatically uploading data collected and sending alerts to you as needed. For instance, a drone flying over your fields taking infrared photos might use the wireless farm network to automatically upload the pictures to a service that automatically scans them for anomalies indicating crop stress.
  • Self-maintaining: self-charging and self-monitoring, needing little maintenance and letting you know when it needs “help”

My own vision is that an Ag drone should be programmed with pre-configured flight paths and connected via WiFi with a wireless farm network for constant (or at least mostly constant) communication. It should be able to download changes to its schedule and pre-configured flight paths off the network, and It should also be able to land on a platform that will automatically charge the drone’s batteries for the next flight. Set up this way:

  • The grower, scout, or agronomist doesn’t have to go out and mess around with the drone – it can just do its thing as often as it needs to (pending charging of the batteries)
  • The data can be automatically collected on the grower’s PC or on a central server (on the farm or on the Internet) – it can even be automatically processed and problems (plant stress, aberrant weather conditions, etc.) can be automatically reported to the grower
  • The drone works for the farmer, not the other way around.

All the pieces exist today to create drones that can meet these criteria, but I’m not aware of any pre-built planes or copters that are ready-to-use. However, there are open-source software projects that have built auto-pilot systems for drones and other robots (e.g. the ArduCopter), and there is discussion of induction charging of quadcopters in the “DIY” forums. And heavier-lift copters (capable of picking up fairly heavy items and transporting them) are also in the works. Imagine being able to get out your cellphone and “tell” your copter to bring you the parts you forgot back at the workshop, then hearing it whirring its way toward you a few minutes later. And then, when it delivers them, it DOESN’T TELL YOU YOU’RE AN IDIOT for forgetting the parts. For me, that would be nearly priceless.

In short, I think there are a lot of possible benefits from using UAVs on the farm, and I’m eager to see them start to deliver those benefits. However, I think a lot of the benefits are greatly enhanced by having the UAVs connected to a wireless farm network – I believe the two technologies will work hand-in-hand, each enhancing the value of the other.

A day at World Ag Expo, Tulare, CA

Leave a reply

I spent the day of February 12 at the World Ag Expo in Tulare, California – one of the biggest farm shows in the world, it’s a good place to see some new stuff and talk to some interesting people. Click on the pictures below to see them “full-size.”

The morning dawned clear, warm, and sunny, like it always is in California… JUST KIDDING! It was cool and so foggy I had to slow down to 35 miles an hour driving across the valley – the infamous “Tule Fog” that occasionally causes huge pileups on Highway 99. However, it burned off around noon and it actually did turn warm and sunny, making it a rare delight for this time of year. The winter in California has been surprisingly – distressingly – warm and dry, and I saw almond trees starting to bloom in the fields on my way across the valley, which is not very common in mid-February.

The “big guys” were there, but I seldom find anything interesting about what they are displaying at farm shows. I went through the Deere tents but they seemed mostly focused on selling t-shirts and caps, and they had equipment for the kids to fall off of. I thought it was funny that the news van was parked right outside the John Deere booth, so I took a picture of it. However, that was the only thing of note there.

There are two companies selling “in-cab” systems that now have network connectivity. Raven‘s new displays actually have an Ethernet port on them, so they can be connected directly to an in-cab AyrMesh Hub and be on the network that way. (They are designed for use with Raven’s “Slingshot” system)

Many of their displays also have USB ports, and I believe you can use a WiFi adapter with them, although I’m not completely sure.

We have not been able to determine exactly what can be done with the Raven displays if they are connected to the network, and Raven has not been very helpful. We’d be very interested in talking to any AyrMesh users who have Raven Envisio Pro or Viper 4 displays.

The other company that has embraced network-connected displays, as mentioned in previous posts, is AgLeader. They were here, showing their WiFi AgFiniti product, and their booth seemed to be very busy. It seems to me that they are a company that has “gotten it” on the importance of network connection and collecting data wirelessly from the cab, so it was gratifying to see so many farmers looking at their solutions.

I mostly like to go into the halls to see the “small booths” that are populated by newer, smaller companies. In California, you see things that are quite different from what you see in the Midwest – sometimes they are only interesting in the odd agricultural climate of the west, but sometimes new things show up that will have a large effect on the general agricultural industry.

With California in a severe drought, a whole slew of companies were there talking about water: measuring it, storing it, and controlling it. Weather stations, soil moisture sensors, and irrigation control. As Mark Twain famously said about the west, “Whiskey’s for drinking and water’s for fighting over,” but the fighting is done and farmers are left to make do with what they can get. Companies like MeasureTek, shown at left here, and Western Weather, right next to them, are using “industrial grade” sensors to monitor weather and soil conditions. They have built “private cloud” solutions to capture the data from the sensors and present them to growers, and the sensor “pods” themselves can be connected to the Internet with cellular or satellite, or just connected to an AyrMesh Receiver or Remote Hub. PureSense, a company that provides not just monitoring but also control of irrigation systems for optimal water use, had a very busy booth. T-L Irrigation was also showing sensing solutions with their irrigation controllers, as well as displaying Internet control of irrigation systems. Valley, Reinke, and Lindsay were also there, but they were focused on irrigation equipment and controllers, less on tying in sensors to irrigation.

The other thing that caught my eye at the show was the flush of new companies that are getting into the Farm Management Software market. Of course, Trimble was showing their Connected Farm solutions, featuring FarmWorks software, and SST, a long-time player in this market, was there. However, FarmLogic did not seem to be in attendance, even though the program said they were. Newer, “cloud-centric” companies offer some unique advantages over the “old guard.” AgWorld is a company out of Australia; I saw them last year and thought they were interesting – theirs is a browser-based farm management application that runs on just about anything with a browser – computer, tablet, or phone. I can’t tell whether it’s really going to be a winner or not, but it has promise. OnFarm is another company that was displaying at WAE. Their premise isn’t to manage and store all your farm’s information, but rather to arrange and manage all the sources of your farm’s information. Once again, I think it’s too early to tell how useful it will be, but it is interesting. There are similar offerings, like FarmLogs, that are just as interesting (although I didn’t see them at WAE). While they all seem to be in their infancy, I expect some of them will “grow up” to be valuable tools for growers.

The one thing for sure is that they all increase the value of having a Wireless Farm Network like AyrMesh.

Two last notes about WAE: first, as shown at left, there are a LOT of people who come to the show. Not all are farmers, but most are connected to the ag industry in some way. Second, as shown at right, you see stuff here I don’t think you’ll see anywhere else, like these berry and grape harvesters. I think it’s a good day when you walk past something that makes you say, “What in the world is THAT???” We’re definitely not in Minnesota any more…

A new take on the “WiFi vs. Cellular” question

Leave a reply

Every so often I run into someone who asks, “Why would I want a WiFi network across my farm? I have a cellphone that will access the Internet anywhere I go…”

It’s kind of a funny argument, for a few reasons:

  1. If you have good cellular data access across your entire farm, you’re in the minority – most people in the rural U.S. and Canada have no or only very slow Internet access via the cellular network on some, most, or all of their properties.
  2. Even if you have Internet access via cellular, it’s almost always slower than WiFi. It’s been my experience that people appreciate WiFi a lot more after they get a smartphone.
  3. Having a local-area network (LAN) enables you to do more than just access the Internet – it allows you to use IP cameras, weather stations, soil sensors, and other devices to keep track of what’s happening on the farm, and even use network-connected relays, grain dryers, irrigation, lighting, and HVAC systems from anywhere on the farm

The cellular service providers (AT&T, Verizon, etc.) originally only used the cellular networks for both voice and data – but the data connections were at “modem-speed” – kilobits per second. Then smartphones (led by the Blackberry and Nokia phones) started to be capable of much more data usage – email and even some web browsing – and phone manufacturers started including WiFi connectivity. Later on, cellular providers offered faster cellular data options (“3G” and “4G”), but modern smartphones still use the cellular network for voice, and the voice network is still separate from the data network. The upshot is that, in many rural areas, you can make or receive voice calls and get or send text messages, but you may not be able to load a web page or send an email unless your have a nearby WiFi network.

A new article in Businessweek points out some new providers are actually turning that model on its head, introducing phones that use the WiFi network by default for voice and data, and only access the cellular network if there is no known WiFi network in range.

Now, I have a cellphone with a data plan, and I pay over $120 per month even though my phone is on WiFi about 90{8fd1ffa65f67a2e931916b3c1288d51eed07dc30586a565c92d055673de7c64e} of the time. If I weren’t traveling all over the place on Ayrstone business, I’d be very tempted to get one of these Republic Wireless or Scratch Wireless phones and save about $80-100 of that bill per month.

For people who have a Wireless Farm Networking system to provide farmwide WiFi, these new phone plans may be very tempting.

What do YOU want for Christmas???

Leave a reply

We were curious about that question ourselves, so we commissioned a survey of growers across the corn belt.

We got over 100 responses to our call from Minnesota to Tennessee and Ohio to Nebraska, all across the Midwest.

All things wireless top the list of technology-related gifts that farmers want for Christmas this year. More than 40 percent of those surveyed are putting wireless remote cameras and wireless remote weather station / soil sensors on their lists. And nearly 50 percent would like a wireless farm network that extends up to 7.5 miles from their homes.

Farmers are also frustrated by the lack of connectivity on their farms. In fact, nearly 80 percent of those surveyed said they are frustrated that their wireless network does not extend to sheds, grain bins or nearby fields.

Other technology-related gifts that farmers say they want according to the survey include wireless remote grain monitoring, an iPad or other tablet, a new router, and remote thermal imaging.

If you’re worried that Santa might not deliver this year, you might want to take care of yourself: go to ayrstone.com and start a new AyrMesh Network for yourself (or expand your existing network) so you have the wireless access you need!

Why AyrMesh.com?

Leave a reply

This is one of the questions we get in Ayrstone support from time to time: why do I HAVE to use AyrMesh.com? Why isn’t there just a setup menu on the device?

My answer is simple: if you’re using a single Hub, then it doesn’t much matter:  you have to set the configuration on the device or you have to set the configuration on AyrMesh.com. About the same amount of effort.

But, if you’re using more than one AyrMesh device – Hubs or Receivers – on your network, using AyrMesh.com saves you time, because all your devices automatically configure themselves from AyrMesh.com. Furthermore, because they check into AyrMesh.com every few minutes, you can always check there to make sure your AyrMesh devices are working properly.

Our entire goal in creating the AyrMesh System was to make it so easy that anyone could set it up and use it, and you’d spend as little time as possible fiddling with your network and as much time as possible enjoying its benefits. AyrMesh.com is an important part of that value

The hard part of wireless networking: the wires.

Leave a reply

It’s actually an old joke in the wireless networking world: what’s the worst part of wireless networking? The wires!

(OK, it’s an old dumb joke…)

While having WiFi all over the farm is incredibly useful, the only way to make it happen is using Ethernet cables. While Ethernet cables are very simple devices, there are an amazing number of variations and types of Ethernet cables, an choosing the wrong ones (or using them poorly) can cost you time and money.

What is an Ethernet cable?

Courtesy of WikiMedia

Ethernet cables all have some common characteristics: they contain 4 pairs of wires, with each pair twisted around each other (so they are called “twisted-pair” cables). They have an outer sheath to protect the wires inside and they use RJ-45 connectors to connect to networking devices.

The 4 pairs of wires inside the sheath are usually colored green, brown, blue, and orange – one solid and one striped for each color. The wires are usually 100{8fd1ffa65f67a2e931916b3c1288d51eed07dc30586a565c92d055673de7c64e} copper, but some cheaper cables are made of alloys. Alloy cable works OK for short lengths, but should not be used for cables longer than 25 feet. There is sometimes an uninsulated wire running down the middle of the cable called a “drain wire” – this is meant to provide a common ground for the equipment the cable is connected to.

The wires are usually about 24 gauge (AWG), but some cheaper cables use 26 gauge wire, and some more expensive cables use 22 gauge wire. Obviously, the bigger the wire the better, as long as it’s pure copper, but bigger wire also makes heavier cables. It makes a difference if you’re hauling it up a ladder, believe me.

Kinds of Ethernet Cables

Under the sheath, some cables have a shield made of metallic braid or foil. This shield keeps outside noise from penetrating the cable and disrupting the signal on the wires. Unshielded cables are designated as “UTP” (Unshielded Twisted Pair), while shielded cables are designated “STP” (Shielded Twisted Pair). Our experience shows that any cable over 25 feet should be shielded to prevent corruption of the data on the wires and maintain the speed of the data.

You will see, shopping for Ethernet cables, that there are several “Categories” of cable – Cat 5, Cat 5e, and Cat 6 are the common ones available now. The differences are in the speed rating of the cables – Cat 5 can pass data at 10 Mbps or 100 Mbps, Cat 5e can pass data at 10, 100, or 1000 Mbps, and Cat 6 can go up to 10 Gbps. Any of these will work well with AyrMesh equipment – we usually buy Cat5e cables because they are less expensive and widely available. The main physical differences in the cables is how tightly the wire pairs are twisted together.

Finally, the sheath itself can differ quite widely. The normal sheath is usually a form of polyolefin, which does not burn easily. “Plenum-rated” and “Riser-rated” sheaths are coated with a low-smoke PVC, which makes them even more flameproof and reduces the toxicity of the smoke if they do catch on fire. “Direct burial” cables generally have a very thick and heavy sheath, and they may contain a gel that prevents a nick or cut in the cable from admitting water into the cable. Obviously, if water gets into the cable, the wires can corrode and the cable will go bad, but direct burial cables are usually very stiff and very heavy, making them extremely difficult to work with.

Whichever cable you choose, it is imperative that you handle it correctly. Because the cable consists of a bunch of small wires, it is really no stronger than any of those wires. It’s very easy to get a kink in a cable when you’re pulling it through a hole, for instance, and break one of the wires. When that happens, the cable is generally useless.

General Guidelines for Ethernet cables used with AyrMesh products

  • Make sure the cables are all-copper and shielded (STP) if they’re 25 feet or longer.
  • Try to get 24 or 22 AWG wires in the cable.
  • Get plenum-rated or riser-rated cables for use indoors, but don’t use direct burial cables unless you’re going to bury them – they’re too hard to manage.
  • ALWAYS leave a “drip loop” when you’re bringing a cable run from outside to inside a building so water doesn’t run down the cable and ruin equipment!
  • Be VERY careful pulling cables – they are more fragile than they seem!

New Ayrstone Product: the AyrMesh Receiver

Leave a reply

Today we’re announcing a new product in the Ayrstone AyrMesh line: the AyrMesh Receiver.

The AyrMesh Receiver is actually, of course, more than a receiver – it transmits and receives data – but it is designed as a simple, low-cost way to put one or more “wired” (Ethernet) devices onto an AyrMesh network. It is very similar to our AyrMesh Hub, but with a couple of important differences:

  1. The AyrMesh Receiver connects to the Hub’s WiFi signal, not the wireless mesh signal.
  2. The AyrMesh Receiver does not create its own WiFi access point – it is a client device only
  3. The AyrMesh Receiver uses a directional antenna for maximum range – it can be positioned up to 2 miles away from an AyrMesh Hub (optimal conditions).

Typical uses for the AyrMesh Receiver include:

  1. Using high-end IP cameras or other network devices that do not have WiFi
  2. Bringing the AyrMesh network inside of metal buildings – an AyrMesh Receiver can be placed on the outside of the building and devices inside can be connected to the LAN port of the receiver. You can even put a WiFi access point inside the building so you have WiFi indoors as well as outdoors.
  3. Connecting devices like network-enabled weather stations in more distant fields – since the AyrMesh Receiver can be up to 2 miles from your furthest Hub, you can now include areas in your network that were previously unreachable.

The AyrMesh Receiver is available now from Ayrstone – please see our website for details.