Ubiquiti AirMAX LiteBeam M5 23 dBi (LBE-M5-23)

33 posts / 0 new

Wed, 01/18/2017 - 20:45

VE3OY

Greetings folks!

I've looked through the available downloads and supported hardware, but nothing is listed for the LiteBeam.

Is this piece of hardware similar to any other?
Can it be used?
If so, which firmware should be flashed into it?

Thanks!
Matt
VE3OY

Sun, 10/14/2018 - 13:14

VE7TFM

Litebeam firmware

Ok, I have a Litebeam M5. I have tried all of the XW images and the only one that actually boots up after the install is the image for the Nano-Loco XW.
I get the "Experamental" header on the unconfigured node web page. But
when I enter the call sign, password and distance end save it I get sent back to the unconfigured page. It is like it can't save anything.

I hope someone is working on this.

Sun, 10/14/2018 - 13:18

(Reply to #2) #3

AE6XE

VE7TFM, can you capture the

VE7TFM, can you capture the support download from the Administration page and attach. This will tell us what is going on and possible paths forward.

Joe AE6XE

Mon, 11/05/2018 - 01:03

(Reply to #3) #4

VE7TFM

Support Data File Attached

I uploaded the latest nightly image for the Loco-M-XW-factory to the LiteBeam M5
The Support File is attached

Support File Attachments:

Support Data Ubiquiti LiteBeam M5 XW running Nano Loco M XW image

Sun, 10/14/2018 - 18:52

(Reply to #4) #5

k1ky

Litebeam Firmware

Did you try a different browser? Make small changes in the configuration, like just the distance and anything else that may be required for first setup and see if it will save.

Mon, 11/05/2018 - 23:44

(Reply to #5) #6

VE7TFM

We have 18 nodes in operation

We have 18 nodes in operation. About half set up with this laptop. Never had a problem before. The latest Linux Mint. I use Chrome for a browser. I don't think the browser is going to make a difference. But, Just in case, I booted this laptop into Win7, it dual boots, Chrome windoz browser and , gasp, internet explorer 11, and no joy. Same result.

Sun, 10/14/2018 - 23:03

K5DLQ

(The LiteBeam is not

(The LiteBeam is not currently a supported device)

Mon, 11/05/2018 - 00:16

(Reply to #7) #8

VE7TFM

Maybe not supported. But

Maybe not supported. But almost there???

Can I be of any assistance? Test an Alpha firmware.

I'll see if i can get a "support data" file.

Tue, 11/06/2018 - 10:19

AE6XE

VE7TFM, OpenWrt has support

VE7TFM, OpenWrt has support for this device. It has a unique image. I'll turn the options on to create it on top of the nightly build. Should be able to do that this week. I'll send an image on the side to test and we can go from there.

Joe AE6XE

Tue, 11/06/2018 - 20:04

#10

AE6XE

board.info file?

board.info file?

See: https://github.com/aredn/aredn_ar71xx/issues/257

Does anyone have access to post the /etc/board.info file from AirOS on the lbe-m5? This is needed to know power settings and device ID.

Joe AE6XE

Tue, 11/06/2018 - 20:25

#11

AE6XE

Test image to try for the lbe

Test image to try for the lbe-m5. use tftp method to upload this image:

https://drive.google.com/file/d/1-5l11iuC2BsriGekfDSySfC3aXWPkG-d/view?u...

link will be time limited and no longer valid at some point in the future. I need the board.info to complete the settings for incorporating into the nightly build. please go to admin page and download the support data download, assuming it boots up correctly.

Joe AE6XE

Wed, 11/07/2018 - 10:31

(Reply to #11) #12

VE7TFM

Looks good so far.

Looks good so far.
I'll take the node out to a spot I can connect to another mesh node and let you know.

The board info file. that comes from the LiteBeam running AirOS?
Ill boot back with the original factory image an see If I can find it.
Thanks. This is great.
Ted

Image Attachments:

Support File Attachments:

supportdata-VE7TFM-501-LiteBeam-201808160058.tgz

Wed, 11/07/2018 - 13:28

(Reply to #12) #13

VE7TFM

/etc/board.info from AirOS 6

/etc/board.info from AirOS 6.1.8 (XW) on LiteBeam M5

Image Attachments:

File Attachment:

board.info_.txt

Thu, 11/08/2018 - 00:03

#14

AE6XE

VE7TFM and anyone with a

VE7TFM and anyone with a litebeam M5,

The definitions for the Litebeam M5 are now submitted to github and the lbe-m5 images will be created in the nightly build and available in the AM on Nov 8, 2018. Please upgrade your devices and give everything a good work out.

Joe AE6XE

.

Thu, 11/08/2018 - 00:43

(Reply to #14) #15

VE7TFM

Joe, Thats Awesome. Can't

Joe, Thats Awesome. Can't wait for morning.
Cheers
Ted, VE7TFM

Thu, 11/08/2018 - 12:54

(Reply to #15) #16

VE7TFM

aredn-416-18098a6-ubnt-lbe-m5-factory.bin

Morning Joe.
Loaded nightly build aredn-416-18098a6-ubnt-lbe-m5-factory.bin
Is it possable the vlan2 is broken? the dtd never resolves the node name. just the ip address. This usually happens when the vlan2 is broken.
I have seen this in a misconfigure switch.
But, the only change here is the firmware.
the dtd in aredn-ae6xe-lbe-861de15-ubnt-lbe-m5-factory worked properly.
the dtd in aredn-416-18098a6-ubnt-lbe-m5-factory.bin does not.

Support data file attached.

Support File Attachments:

Nightly Build support data file

Thu, 11/08/2018 - 14:48

(Reply to #16) #17

AE6XE

VE7TFM, the support data

VE7TFM, the support data shows vlan 2 dtdlink working Ok, it has established links across vlan 2. When only IP addresses are showing, this is generally related to olsr or dns issues. It's possible you ran into this issue: https://github.com/aredn/aredn_ar71xx/issues/204 . If so, reboot the node and/or "/etc/init.d/olsrd restart" to see if the names start showing. This isn't prevalent, but does occur occasionally and is not unique to these new device. Everything can be accessed directly by IP address to get to a remote node, just doesn't have a hostname communicated around the mesh.

Thu, 11/08/2018 - 15:12

(Reply to #17) #18

VE7TFM

Hi Joe.

Hi Joe.
Restarting the olsrd fixed it.
Good to know. I have seen olsrd related info.
I run linux by default on my primary desktop so familiar with linux processes.
I am stoked.
Thanks for your help!!!!!

Ted, VE7TFM

Fri, 11/09/2018 - 00:08

(Reply to #18) #19

VE7TFM

Hi Joe

Hi Joe
Another question
the board.info file says:

radio.1.txpower.max=25
radio.1.txpower.min=-4

The ubiquiti spec sheet for the litebeam says 25 dBm
the Max power I can get from the litebeam on AREDN is 19dBm
channels below 5850 might be limited by UNII or something but above there should be no limit.
from the SupportDataFile
HT TX/RX MCS rate indexes supported: 0-7
MCS0 is 25 dBm
Is this just the way it is or can this be adjusted???

Is this what you ment by hammering away at it?
Cheers
Ted
----got me thinking...
Looking at the same info for a pbe-m5-400 we have in our system.
The Basic Setup page shows 26 dBm, the data file in the support data shows 22 dBm
Is this a bigger problem? Or am I reading it wrong?
Ted

Image Attachments:

Fri, 11/09/2018 - 12:25

(Reply to #19) #20

AE6XE

Hang on, just noticed

Hang on, just noticed something. This is a single antenna device, not a MIMO device since only goes to MCS7 rates. I didn't realize that. his may be the problem. need to make a change accordingly and push an update to the nightly build. A file on your device can be edited to manually make the correction.

In /www/cgi-bin/perlfunc.pm , make the following change:

'0xe865' => {
'name' => 'LiteBeam M5',
'comment' => 'Testing LiteBeam M5',
'supported' => '-1',
'maxpower' => '19',
'pwroffset' => '6',
'usechains' => 1, # < change this "1" to a "0" for single antenna device
'rfband' => '5800ubntus',
},

Fri, 11/09/2018 - 13:02

(Reply to #20) #21

AE6XE

The definitions in AREDN for

The definitions in AREDN for max power are not what one might expect. The value stated for maxpower, need to add the power offset value to determine the real max power.

Joe AE6XE

Fri, 11/09/2018 - 13:27

(Reply to #21) #22

VE7TFM

Thanks

Thanks
Ok, Power settings make sense.
What is the Power Offset value used for? I see it is all over the place on different devices.
Cheers
Ted

Fri, 11/09/2018 - 20:56

(Reply to #22) #23

AE6XE

On Ubiquiti devices there

On Ubiquiti devices there must be some built in hardware offset between the wireless chipset and the Power Amp. The linux kernel has no knowledge of this offset and all the commands to set tx power using the "iw" command are (real_max_power - offset). So in the litebeam case, when setting the power in linux, "iw dev wlan0 set txpower fixed 1900" would really mean the max power ( in mBm ) is 2500 . It is 600 (the offset) higher.

If you do the command "iw phy phy0 info", I'd expect linux to report (19.0 dBm) as the max power for all channels. But this is really 25dBm with the 6dBm offset. Is this where you pulled the 19 dBm value originally. If so, then all is as it should be.

Joe AE6XE

Sat, 11/10/2018 - 23:44

(Reply to #23) #24

VE7TFM

Joe, Do I need to TFTP a new

Joe, Do I need to TFTP a new "factory" nightly build or can I use the "sysupgrade" build via the admin GUI?

Sun, 11/11/2018 - 11:12

(Reply to #24) #25

AE6XE

Yes, upload the nightly build

Yes, upload the nightly build sysupgrade image from the Admin page and keep settings. tftp of the factory image still works, but longer path to retype in the settings.

Joe AE6XE

Tue, 11/13/2018 - 00:52

(Reply to #25) #26

VE7TFM

Thanks

Tue, 11/13/2018 - 09:48

(Reply to #26) #27

VE7TFM

I notice that the LightBeam

I notice that the LightBeam node does not show up on the OLSR-Topology map. is that because it is still experimental?
I certainly appears to work and shows on all mesh status displays.
I have it up and aimed at one of the main 5.9Ghz nodes in the local mesh network.

Support File Attachments:

supportdata-VE7TFM-501-LiteBeam-201811131442.tgz

Tue, 11/13/2018 - 10:49

(Reply to #27) #28

AE6XE

Both OLSR-topology and mesh

Both OLSR-topology and mesh status pull data from the same source, OLSR. If OLSR-topology is run from a given node, grab the support dump from that node and also confirm if the litebeam is showing in mesh status or not. I'm assuming OLSR-topology was not run direct on the litebeam in the current example? I'd want the support dump on both the litebeam and the remote node where OLSR-topology was run to see the state of OLSR data on both sides of the fence.

Joe

Joe AE6XE

Tue, 11/13/2018 - 15:50

(Reply to #28) #29

VE7TFM

Files attached

Image Attachments:

Support File Attachments:

supportdata-VE7TFM-501-LiteBeam-201811131759.tgz

supportdata-VE7TFM-300-201811130958.tgz

File Attachment:

topology-2018-11-13-10-08-13.dot_.txt

Tue, 11/13/2018 - 20:55

(Reply to #29) #30

AE6XE

Ted, Is it possible the

Ted, Is it possible the olsr topology data was captured when the litebeam had just been booted are was not yet booted - a timing issue? OLSR is showing in the support dump the litebeam in the topology and HNA tables on VE7TFM-300. The data is in the same order in the dot_draw output, except the missing litebeam.

Why the litebeam is not showing in the olsr topology output from the dot_draw plugin is still a mystery. If you rebooted everything in unison, waited ~3 min, can the problem be reproduced?

Wed, 11/14/2018 - 00:22

(Reply to #30) #31

VE7TFM

Hi Joe

Hi Joe
the LiteBeam is in the output from the olsrd_dot_draw plugin
I have been playing with the perl script.
The LiteBeam is in the olsrd dump that the script gets from the VE7TFM-300 or if you "telnet localnode 2004".
I hacked the script to to get the resolved dump that is handed to imagemagick, the litebeam is in that list.
so for some reason imagemagick or graphviz is unhappy with that input????
still digging.

File Attachment:

VE7TFM-501-LiteBeam-dump.txt

Wed, 11/14/2018 - 15:45

(Reply to #31) #32

VE7TFM

The issue is with the perl

The issue is with the perl script i am using.
it wasn't saving the .dot file to pass to imagemagick so was using an old file.
it must have worked at some time??? It is working now.

Image Attachments:

Support File Attachments:

topology2.png_.tgz

Wed, 05/15/2024 - 02:32

#33

ae7et

Hate to revive an old thread, but.... LBE-M5 support?

Any update on the Litebeam M5? Is there an image that works?

Amateur Radio Emergency Data Network

Menu SF

You are here

Ubiquiti AirMAX LiteBeam M5 23 dBi (LBE-M5-23)

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Ubiquiti AirMAX LiteBeam M5 23 dBi (LBE-M5-23)