Hello if you are near eastern Tennessee to the north or the south and even the west drop in and please give us your location we are on a 20 unit setup in process, contact us and 73's

KD4YSH

Hello Newbee here ok I have flashed 3 out of my 12 wrt54g routers and have them plugged in and from any of my computers it does not see them. Do I need to load any type of software on my laptop that is 200 feet away to connect or see the nodes and communicate and see the traffic? Please any help will be much appreciated.

73's

You are correct. I have looked into this for a considerable time. To summarize, UBNT 3.4GHz radios are merely UBNT 5GHz devices with a 2GHz downconverter. The 3.4GHz US hamband (before downconverting) falls between the 5GHz "Lower Band" (5150-5320MHz) and the 5GHz "Middle Band" (5500-5850MHz). The PA on the M3 devices are rated from 3.5GHz to 3.7GHz Furthermore, the output power drops off considerably outside the PA's range. So much so that the devices do not even see eachother on 5320MHz even when they are touching with the antennas pointed directly at each other. Simply put, it is not easy, but I am sure we will get there eventually.

Thanks Graham

My email is my call @gmail.com

I appreciate the straightforward answer.

I remember seeing a poll question asking about 3.3 Ghz mesh net nodes. I did a quick search on this site and came up empty. So, either I did not use an appropriate search term or it is an unexplored area.

So, is there any development on using the Ubiquity 3.3 Ghz equipment as Broadband Hamnet nodes? (Rocket M @ 3/3.6 Ghz listing as an example)

IIRC (I'm not at my PC at moment) there was a couple variables inside the script that had an effect of some sorts ( though not the way I expected ) on the X-Y dimensions.  I also think there was a font size variable too.

It wasn't controllable from the command flags it had to be done inside the script IIRC. 

I did see it becoming an issue myself a while back, I know I tweaked it enough so it worked for where I was but at the moment I'm not sure what changes I put in.  

I know I tweaked it so the line color between nodes changed based on the ETX but that's about all I recall off hand without being at my desk.

And brother, was there ever progress <GRIN>.  For this ol' cowboy, there's been a real learning experience.  First time with a Raspberry which I received this past Tuesday 11/25.

I can't tell you how many times I reformatted the SD microdisk or rewrote to the card the Raspbian software.  I could not get the Raspberry to boot!  Spent the better part of 11/23 - 11/24 working with it to no avail.  Now, it seemed to me that I received either a bad Raspberry or a defective micro SD card. I even went so far as to advise Newegg of the matter for info and some guidance.

I have been working with Ted G4ELM (hmmm, ELM is the beginning for "Elmer") and good guidance.  Was locked up with this matter, so started browsing around for info.  Went to all the sites of importance but got nowhere as such.  There is a possible 1%, maybe <1% chance the PI was to blame.  More than likely it was the mcro SD card because all Raspberries are given a pretty thorough checkout prior to shipment.  If they left the door, they were working, component failure not withstanding.

Finally the suggestion brought up in dialogue with Ted in email and Lot K6IRF in the message group called Raspberry_Pi_4-Ham_RADIO about the vagaries of that little micro SD card slot.  Fragile stuff there.  To cut to the chase, I found out what the true problem was - I did not have the micro card fully seated and LOCKED into place.  Simply because of unfamiliarity - the little micro SD card does indeed "lock" into position within the slot.

When I realized what was going on, I put power back onto the PI with all the USB cables and HD TV attached and VOILA!  IT WORKED!  What a relief.  So, word to the wise for newbes.  Be careful but do check and make sure your micro SD card is really seated.

Now, I can proceed onward with Broadband.  Working now with the Web server software on the PI. That seems to be the easiest thing to accomplish right now, per se. All three WRT54G nodes are working and talking to each other - been running 24/7 the past couple of weeks now with no problems showing.  

I do need to check into Headless operation now too.  I have a 24Dbi grill ant arriving today, Friday 11/28 but I need a couple of OMNIs as well.

Thank you,

kicking myself on that one. Thank you ,I have used it so much. Is there a way to sharpen the image. I have noticed as the system has grown with additional nodes they become more and more unreadable. I have used the view double size. only makes it worse. I have experimented with different options but to this point I have not been very successful.

Mike

It appears you may be using python to execute the script which was written to be interpreted by perl. Switching over to perl should clear it up for you, if not a few libraries may be missing as well but should be easy enough to add in.

Good Morning,

I hope everyone had a good thanksgiving and didn't get over stuffed.

This has worked for me recently. as we build out the network I rerun a new map. 

I'm running Ubuntu 14.04 I have installed the required programs  graphviz and ImageMagick. however a few days ago I went to rerun an update on our mesh network here in Virginia and I get this error and its not just on one machine that I have connected to the mesh but three now.

This could be a patch issue with Ubuntu or something else.I have run this as user , sudo and as root. They all give the same error on any one of the three boxes that I put on the mesh.

root@radio-HP-Pavilion-dv4-Notebook-PC:/home/radio# python olsr-topology-view.pl  File "olsr-topology-view.pl", line 8
use IO::Socket;

SyntaxError: invalid syntax

I am hoping to put up a UBNT Bullet soon, just wanted to see if there were any others near by.

the code didn't seem to be attached ... will try again

Aha.  It doesn't like .doc or .txt files,  willl try PDF. Doesn't like that either.

Dan, give me your email address and I'll mail it.

73, Graham

Hi Dan

Some time ago I put GPS on my nodes.  I wrote to Jim  giving my code, and he was going to  add it to his article.  Other things have probably taken precedence.

It is simple, but you will need to  get local help.  You need to get SSH  access to the nodes to edit the "status" file in the "cgi-bin" directory.   Lost you already? ;<)

 That's why you need someone local who knows Linux ,  and "vi".

To put location in the status page is simple.

After the heading info in the "status" file insert:

    print "Location 43.5S 172.6E";

    print "<hr>\n";

(use your latitude and longitude, not mine) and it's done.

I am attaching my code for the GPS device.  You will need to use "croned" to read the GPS device

every 5 minutes.  

You do need someone who knows Linux.

Cheers,  Graham ZL3GSL

)

Looks like the page hasn't been updated to show the older release.

Here is a link that currently works to get you the GS 1.1.2 firmware. 

http://www.broadband-hamnet.org/download/firmware/link/bbhn-1.1.2-wrt54gs-2.4-squashfs.bin

Hopefully the website will be updated soon with the older firmware as they are suppose to remain posted and  available as I understand it.

Of course standard notice that I'm sure you have seen if you have read  the forums:

I recommend encouraging your local mesh to upgrade to 3.0.0 as soon as you can as issues were found in 1.1.x where networks as they grew would start crashing once the network became larger in size (one node could be the difference between a stable and unstable network)

Hello,

where can I get the firmware file for the GS ver 1.1 I need it to integrate a router into a current mesh and they have all not been upgraded to 3.0.0 yet.

Is there a link for the older firmware?

73

Chris

Owning one of these devices, yes it is still usable. However, you will need to install other packages and configure it through the command prompt. Details can be found on Google.

This should point you in the right direction:
Enabling 3G/UMTS: http://josefsson.org/openwrt/internet.html
https://forum.openwrt.org/viewtopic.php?id=20063