As I build out new MeshAP there are a number of items I go through prior to customer installation. One of the biggest problem is to ensure that the hardware that you provide is going to work.  One of the worst thing you can do is quickly put together a node and hope it actually works with out testing.

If you are building more than one box you will have to make equal time to ensure that every box works.  The time it takes to test a MeshAP is as little as a few hours.  However, using name brand PC as Dell,  Compaq etc. go through the process to ensure that every component is tested. In most case the quality of a use PC is very good.  In almost all my PC that I use for MeshAP no components were required to be swapped out due to failure.

The problem with most of the open source solution is the software is flashed from a CD onto your IDE drive.  When making 20 machines the process can be very time consuming!

When you are building your own MeshAP from off the shelf components it takes extra time to determine if your device is actually working properly.  In the Eighties a term called "Burn test" was used to verify if the PC was work properly prior to delivery.  Similarly every MeshAP that is made should run a burn test.  

Here is my version of a Burn test

Building out a MeshAP is quite simple. Most people are able to construct the basic unit as shown below.

However the problem is before final assembly some testing should be done to verify that all the components are working properly.  This may sound stupid with all the off the shelf parts but many parts are faulty.  It is better to catch the problem prior to assembly rather than after installation.

First the assumption is that you have assemble the basic pieces and the IDE drive has been flash with the latest version of your software.  

Connect a basic PC connection.  If you can connect a standard monitor, mouse, keyboard and internet connection.  This is the time to do it.  For Wrap boards you may only have a power and internet connection available.

The purpose is to setup your MeshAP as a gateway. If you are starting out for the first time or even if you have a network this basic step is required.  

Before you turn on the unit ensure the unit is grounded properly and that the motherboard is not touching a metallic surface.

Initial Test

1. Turn on Monitor and mother board.
2. Watch the screen boot up.
3. When the initial unit boots up successful it normally goes into GUI mode.
4. Register the unit into Wiana.  See Wiana 
5. Once Registered configure setting in Wiana.
6. The unit will reboot after the setting have downloaded.  This normally takes about 30 minute's.

Testing communication between Wiana and your MeshAP in Gateway node

1. First test, you are going to run is remotemanagement.  This command informs Wiana that you up and running and to exchange any updates it has for you.  This command normally happens every 30 minutes.
2. Next test is a leechtest that takes approximately 10 Meg files and downloads this to your MeshAP.  Here you can witness the internet gateway speed.
3. Most MeshAP either use a hard disk, CF Flash card with IDE adapter or a DOM (Disk on Module or chip). What you are trying to test here is if the IDE drive can upgrade and downgrade.
4. To test for upgrade type command getandverify tobuild25dev88 (as an example)
5. You may need to watch the monitor because messages may appear indicating that you must first install another component.
6. Once install you can verify that you are on that build by looking in Wiana and see what it reports.

Testing communication between Mesh nodes, Gateway and Wiana

1. If you have Mesh network you way want to determine if the performance of your radio card. The assumption is that you MeshAP is configure properly to your network.
2. Install the antenna
3. Remove the RJ45 connection
4. Be with in distance of another MeshAP and boot up the MeshAP
5. Run reporter.  This will show you many things.  If everything's running well it will show you that you are meshed with another node.
6. Ping the gateway to see connectivity. Ping outside the gateway to a known url. like www.yahoo.com
7. Run leechtest to see connection speed.
8. Run sigspy to see the noise and antenna strength. To mesh you should have at least 8 differences between signal strength and noise.

Test hardware reliability

Most hardware is reliable however there are times when you turn on your MeshAP and it starts failing after a while of operations.

1. What you are trying to do is turn on your MeshAP and ensure it mesh or is gateway node.  To want it to run through many cycles with Wiana.
2. You are trying to see continuous operation with out rebooting.  The longer you can test the better.

Testing MeshAP is not difficult however it is time consuming.  That time you spend testing does help and provides more confidence when you actually are deploying your network. You use the testing of the MeshAP as a benchmark prior to deploying it at a customer site.