High Performance Node - Specification: Difference between revisions

From WirelessAfrica
 
(74 intermediate revisions by 3 users not shown)
Line 2: Line 2:


== High Performance Node Development & Test Network ==
== High Performance Node Development & Test Network ==
'''(Note)''' This is not the proper page for this discussion, will move it later. Keeping it here as much of the discussions currently happening, is around topics on this page
moved to [[High Performance Node - Dev and Test Network]]


*Development
== Hardware ==  
** Lab development platforms
migrated to wireless dev
 
*Locally deployed Test network
** Installation of a 10 node network on the CSIR campus
** Tx power set on minimum and attenuators used to minimise transmission distance
** Sites on the campus need to be selected
** Equipment for test network needs to be procured - suppliers?
***Enclosures - Poynting Antennas
***Gateworks boards -
***Dual WiFi cards -
***Power over Ethernet(poE)injectors -
 
*Demo nodes
**The thinking is around something the size of a linksys, using a small patch antenna ( This can use used when the demo needs to travel).
 
== Hardware ==
[[Image:Bokkie_Router_Pic.png|right|thumb|80px|Current Bokkie router]]
'''HPN based on current “Bokkie” router, to become “Bokkie v2”'''
 
=== Block Diagram of HPN ===
[[Image:HPN_Block Diagram_v2.png|left|thumb|300px|Block diagram of HPN]]
<br clear=all>
 
=== Enclosure ===
* Based on Poynting Enclosure ([http://www.poynting.co.za/productdisplay.php?id=186&cat_id=3 Product code:WLAN-A0033])
* Modification: swap 1x 2.4 GHz omni-directional antenna for 1x 5.8 GHz omni-directional antenna
 
=== Electronics ===
* 1x Gateworks [http://www.gateworks.com/products/avila/gw2348-4.php Avila GW2348-4] Network Platform
* 3x 802.11a/b/g mini PCI Atheros based WiFi cards - [http://www.miro.co.za/detail.aspx?pid=208&p=2&sp=&spp= CX-WLM54AG23 Complex High Power dual-band Mini PCI Card] (It maybe worthwhile to search and evaluate some of the new cards on the market, but our current "bokkie" routers use this one from Miro)
** 2x configured at 5.8 GHz
** 1x configured at 2.4 GHz
* 1x 1GB compact flash card
* 3x [http://en.wikipedia.org/wiki/U.FL U.FL to SMA connectors]
 
=== Enclosure - Other ===
* 1x External weatherproof Ethernet connector with Ethernet pigtail for POE (install on left side – looking at bokkie – keeping with current standard)
* 4x Gateworks board mounting standoffs
* External Mounting bracket
 
=== Accessories ===
* Powered 48V power-over-Ethernet injector
*Ethernet Cables
** 1x UV resistant outdoor CATV cable [have different lengths available (5m, 10m, 20m)]
** 1x indoor CATV cable [have different lengths available (5m, 10m, 20m)]
** Need for longer cables, custom make ?
* Some type of surge protection on the power side.
**Thinking of a product from http://www.clearline.co.za/. Still need to investigate
 
=== Other ===
* Wall mounting bracket (different types depending on type of wall - specification)
* Mounting pole (different types - spec)
* M10\M12 Coach Screws and fisher plugs (# depending on wall mounting bracket)
* 10x pack Cable ties
* Earthing kit Webb Industries have earthing kits that can be used. see http://www.webb.co.za/index.php?nav=news&ID=50
**Clamp\lug on one end of earthing cable for attachment onto wireless installation mounting bracket
**Earthing cable: Length (?), Gauge (?) - 10-15mm diameter
**Clamp on spike for other end of earthing cable for attachment onto earthing spike
**Earthing spike - 1m (driven into the ground at base of wall of the wireless installation)


== Software ==
== Software ==
=== Firmware: "bokkie1 mesh distribution" ===
Moved to [[High Performance Node - Software]]
This software specification is based on the current free BSD version of the firmware. I have named it "bokkie1 mesh distribution" as a working title (for want of a better name - please provide a nice snazzy one)
 
* A script is used to build the current firmware build based on the platform. Please insert the list of packages\utilites\etc used to make this build.
 
* Additional
** IPv4 over IPv6
*** Allows for automatic configuration of the tunnels
*** Automatic DHCP of IPv4
** Supports HTTPS and HTTP
** Runs mini_httpd web server
 
=== GUI ===
The GUI has two main links, Status and Administration(basic). The Status link is unencrypted, however, the Administrion link(s) are encrypted and authenticated.
*Status link provides for the user to view:
**The configuration status of the Node
**The routing table
**The link/signal strength with respect to other nodes in the vicinity
*Administration
**Change hostname
**Set the NTP server (remote/local)
**Set DNS server (remote/local)
**Create a cluster
**Command line interafce
 
=== Remote upgradeable ===
What current functionality exists?
 
What further development is needed?
 
What limitations exits?
* Cannot be remotely upgraded if there is a protocol change
 
=== Further development to functionality ===
* GSM modem to the development network and first nodes in the field
 
* Watchdog
**Problem with native watchdog on Gateworks Avila board
***Boot failure resuscitation
**Specific to Gateworks Avila Board
**PCB to be developed that plugs into the JTag connector
 
* WEP security


* Mechanism to get the GPS co-ord configured in the HPN. This can later be used in the visualisation tool on the gateway with a Google plot of the nodes.
==Further Developments to Functionality==


[[Image:Indicator_v2.png|right|thumb|150px|LED type indicator system]]
migrated to wireless dev
* Indicator:
**Visual: Example of indicator system (using LEDs mounted at the bottom of the enclosure) for alignment, type of box (ie. red or green, which is an indication of the channel being used), power to box
***1 - Left most LED can be either RED or GREEN, showing type of box - this can be configured in the setup and commissioning of the router(indication of the channel being used), ie. this is either a red box or a green box
***1 - Right most LED shows power
***2 - 5 Used as 4 point scale for signal strength
**Audible: with a buzzer used for alignment

Latest revision as of 13:53, 5 June 2009


High Performance Node Development & Test Network

moved to High Performance Node - Dev and Test Network

Hardware

migrated to wireless dev

Software

Moved to High Performance Node - Software

Further Developments to Functionality

migrated to wireless dev