Asterisk@home now Trixbox

OK so I just spent the last month working on Asterisk@home and working to configure Wireless Mesh to link it. Now the the change the name and are calling Asterisk@home "Trixbox" http://www.trixbox.org/

Great. Now I have to go back and figure everything out again. I believe there is a migration path from Asterisk@home to Trixbox. It like I have nothing to do just to start figuring this stuff out again. Well I should stop complaining and get to it.

I wonder if Locustworld will upgrade their Asterisk modules to Trix?

Little PC Wrap Board Still Kicking after going for a swim

The PC Wrap Board that I just reported that went for a swim is still working. After air and sun drying out the wrap board and there is little evidence of corrosion and the unit is still working. I will continue to use it until it dies. I believe the life expectancy of this board is now shorter.

But it always amaze me that something went completely under water will still work. Swimming Wrap boards what next.

Inquires to Moskaluk.com

I have recieve many inquiries on Wireless Mesh technology from my website at www.moskaluk.com . As you may realize this is now a very popular site and I receive many inquires relating to the site. Regarding developing in the Locustworld environment. The type of development I have done is basically adding other application to work on the kernel; however, there are limitations. I give you a brief overview.

First in Locustworld experiment I used the free open source license version rather than the pro version. The software development is minor i.e. change some Linux scripts or adding some scripts, adding HTML, flash etc. in terms of customization the splash page. I have not change or modified any of the source code or applications. The reason is Locustworld software since 2002 has transform over 107 times. Locustworld keeps coming out with improvements and new features. It is hard to pick a baseline on developing and application when the software keeps changing, you will need to develop a change control script. My approach has been to develop software not on the same kernel. I have use other application on a different OS and system and either linked them to wireless mesh AP using either Ethernet or wireless connections.

The hardware I using is either a Via mini-itx board or Intel Shelton or wrap board. The have tried to keep the Locustworld operation as wireless mesh. The hardware speed ranges from 266 MHz to 1 GHz. Since Locustworld tries to make it difficult for people to reverse engineer the system i.e. not providing documentation I have not tried to add or modify the distro but to work around it!

I'm interested in changing kernel to upgrade all the Locustworld open source components i.e. change it Ipv6, update the latest Linux kernel etc. As for adding additional application, yes I see significant benefit for adding on additional software. After writing my paper http://www.moskaluk.com/digital_marketing.htm I showed a benefit from using the wireless mesh as the first and last mile approach. Let me tell you this has sparked a lot of interest from people developing application write on MeshAP. All the other paper I have written http://www.moskaluk.com/papers.htm also have led to many question.

I believe the timing to develop is excellent. In the last six months the development of Locustworld build has not involved and has stabilized. It is a good opportunity to reverse engineer the product. Here are some links you can use. Please note they are all available on the Locustworld website:

Locustworld's download page

http://locustworld.com/modules.php?op=modload&name=Downloads&file=index

Locustworld's source software

http://locustworld.com/modules.php?op=modload&name=Downloads&file=index&req=viewdownload&cid=3

Locustworld's public software

http://locustworld.com/modules.php?op=modload&name=Downloads&file=index&req=viewdownload&cid=2


If you want try some experiment you may want to use Windows for development. I provide a few sources for the AODV component


AODV Open Source

http://w3.antd.nist.gov/wctg/aodv_kernel/

AODV Open Source for Windows

http://moment.cs.ucsb.edu/AODV/aodv-windows.html


Please keep me inform, I'm always interested in what other people are doing.

Solar experiment died

Since 2003 I have been working with Wireless Mesh. And the latest experiment I have been running is solar powered. In the last two weeks I have intermittent problems and assumed that it was due to the solar array. I assumed wrong. As we have been getting a lot of rain I did not check to see how the motherboard was doing. Well it was swimming in water. Yep the white metal Demarctech case I used sprung a leek. Now before we start going down on Demarctech we have look at the root of the problem. First the case was installed upside down to take advantage of the antenna positioning. Second the plastic CAT 5 inlet came unsecured. I believe this was cause by the temperature variation that we had and this being a metal box the plaster didn't have a chance. And how is my wrap board doing. Well it done. Sure it working for now but I seen swimming Mesh nodes before and this is done.

Solar Experiment terminated. Damn I have to come up with another wrap board and another solution!

Fourth solar panel added with no results

I have added a fourth solar panel to the solar array. The objective was to increase the regeneration time of the battery. As indicated the new solar panel did not provide any additional benefit. The battery currently is now getting old and I believe it is loosing it's efficiency. I noticed that the additional solar panel did not make a difference as the math indicated that it would improve the speed of regeneration. I would think that this real world type of experiment using off the shelve products is good indication that solar and battery operation are maturing; however, one can see after a few years of operations that maintenance on the battery is required. Yes the array is working a higher level but I thinking as well I have provide more power than the power box can administrate.

I will pickup a dedicated high cycle 12 V long lasting (100 hour) battery. I will also have to add a new controller and now add an inverter. The inverter is optional but necessary to test other MOBO.