Author Topic: Lwmesh stack range  (Read 4790 times)

0 Members and 1 Guest are viewing this topic.

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Lwmesh stack range
« on: March 28, 2017, 04:49:40 am »
Hi
    I would like to know the maximum range that Lwmesh supports in line of sight and non-line of sight .
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #1 on: March 28, 2017, 05:15:22 am »
in line of sight
That does not depend on the stack, it is up to your hardware.

and non-line of sight .
In theory, number of hops is unlimited. In real life you probably don't want to go more than 7-10 hops. So whatever your hardware can do on a single hop, multiply than by 10 to get realistic distance with routing.
Alex
 
The following users thanked this post: vishal

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #2 on: March 28, 2017, 12:14:01 pm »
I read that TxPower set in the software has dependency to range.is that true? if yes what is the TxPower value set in the stack.
Also we have atmega256rfr2 MCU devices with 1.5dBi whip antenna and another ducky antenna of 2.2dBi ,50ohm.when we checked the range we could see that the both antenna gives us the same result.So we are confused whether there are any other external parameter to be configured in the software.
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #3 on: March 28, 2017, 04:07:37 pm »
I read that TxPower set in the software has dependency to range.is that true?
TX power does affect the range.

if yes what is the TxPower value set in the stack.

It is up to the application to set it via PHY_SetTxPower().

we checked the range we could see that the both antenna gives us the same result.
0.7 dB of difference is nothing, you will not see any difference, especially if your measurements done in a real world, and not in anechotic chamber.
Alex
 
The following users thanked this post: vishal

Offline senso

  • Frequent Contributor
  • **
  • Posts: 951
  • Country: pt
    • My AVR tutorials
Re: Lwmesh stack range
« Reply #4 on: March 29, 2017, 01:14:28 am »
With a 25x5mm patch antenna and some tips from this forum about the pcb layout I'm getting around 250m range.
 
The following users thanked this post: vishal

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #5 on: March 29, 2017, 03:28:35 am »
Quote
It is up to the application to set it via PHY_SetTxPower().
we set it as PHY_SetTxPower(0x00)..Hope that this is the maximum.?
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #6 on: March 29, 2017, 03:30:22 am »
Hope that this is the maximum.?
Yes, it is. It is all in the datasheet.
Alex
 
The following users thanked this post: vishal

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #7 on: March 29, 2017, 03:39:06 am »
We could achieve a long distance in line of sight.now we are testing the range in a filed of having  so many trees and plants..and we see that the range decrease by half of that in line of sight.
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #8 on: March 29, 2017, 03:41:02 am »
With a 25x5mm patch antenna and some tips from this forum about the pcb layout I'm getting around 250m range.

is 250m in line of sight?what about non line of sight?can you post  those tips for the pcb layout
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #9 on: March 29, 2017, 03:41:23 am »
We could achieve a long distance in line of sight.now we are testing the range in a filed of having  so many trees and plants..and we see that the range decrease by half of that in line of sight.
Sounds about right. You are next to a big mass of water, it absorbs radiation real well. Same goes for heavy rain.

You will probably get further reduction if you put devices close to the ground. This effect may not be as prominent in 2.4 GHz band, but it is obvious in sub-GHz.

That's how the real world works, nothing you can do about it.
Alex
 
The following users thanked this post: vishal

Offline senso

  • Frequent Contributor
  • **
  • Posts: 951
  • Country: pt
    • My AVR tutorials
Re: Lwmesh stack range
« Reply #10 on: March 29, 2017, 11:40:52 pm »
This is my topic:
https://www.eevblog.com/forum/projects/2-4ghz-antenna-selection(help-needed)/25/

I dont have any RF test equipment, so the only values that I will reference are the ones that the stack report via the rssi parameter, with a tiny modification in the pcb I gained 20dB of headroom that allow the 250m LOS range, indoors it works up to around 100-150m, BUT this is in a very "dirty" space, all the 2.4Ghz WiFi bands are used with more than 30 AP's all broadcasting around -50dBi(at least that's what InSSIDer says).

The cooper is pulled back from the trace around 0.6-0.7mm.

The antenna connector is: http://eu.mouser.com/ProductDetail/Molex/73412-0110/?qs=%2fha2pyFadujLTscqrHEzZKoebpXGm3FHnOiat6RQzC5AUik2Y9KcqA%3d%3d
And the balun is the recommended one: http://eu.mouser.com/ProductDetail/Johanson/2450BM15A0015E/?qs=%2fha2pyFadugKbg2QqA0U%2foXMs42LDSzJ1lnJ71N1hqrlzObBcRaQKkcltMVmHQzj

Ignore the pad footprint, its only there because there was a remote possibility of having a borrowed VNA to try to tune the antenna.
« Last Edit: March 29, 2017, 11:43:06 pm by senso »
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #11 on: March 31, 2017, 09:32:37 am »
Now I am testing the range with Lwmesh WSNDemo application.In config file i defined NWK_ENABLE_ROUTING.i have one coordinator and 8 routers connected to it.two of them are used to extend range(repeater).Is my scenario correct.Do I have to set anything in addition to enable routing.
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #12 on: March 31, 2017, 04:19:43 pm »
Based on this description - you are fine.
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #13 on: April 24, 2017, 03:39:27 am »
When I tried to use hoping, the network hangs.I tried WSNDemo application.why it happens so?are there any buffer size issue??
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #14 on: April 24, 2017, 03:40:55 am »
How exactly did you try hopping? How exactly does it "hang"? And how would I know if you have problems with buffers, if you have not provided your configuration?
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #15 on: April 24, 2017, 03:50:49 am »
This is my configuration
Code: [Select]
#define APP_SENDING_INTERVAL 500
#define HAL_UART_CHANNEL 1
#define HAL_UART_RX_FIFO_SIZE 10
#define HAL_UART_TX_FIFO_SIZE 100
#define SYS_SECURITY_MODE 0
#define NWK_BUFFERS_AMOUNT 10
#define NWK_DUPLICATE_REJECTION_TABLE_SIZE 50
#define NWK_DUPLICATE_REJECTION_TTL 2000
#define NWK_ROUTE_TABLE_SIZE 100
#define NWK_ROUTE_DEFAULT_SCORE 3
#define NWK_ACK_WAIT_TIME 500
#define NWK_GROUPS_AMOUNT 3
#define NWK_ROUTE_DISCOVERY_TABLE_SIZE 5
#define NWK_ROUTE_DISCOVERY_TIMEOUT 1000
#define NWK_ENABLE_ROUTING
This is my configuration.I have four level sensors that send data to a central coordinator.In between level sensor and coordinator i have placed one router for hoping.The coordinaotr receives data without break for 10minutes,.after that it required to reset the network.
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #16 on: April 24, 2017, 04:03:23 am »
This is my configuration
This looks fine.

The coordinaotr receives data without break for 10minutes,.after that it required to reset the network.
That is something you should have mentioned in the original message.

Which device needs to be reset? Have you tried to do any debugging at all?  I can tell you right away, there is no way you can work with wireless stuff without a lot of debugging, so you might as well get set up for that.
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #17 on: April 25, 2017, 03:18:46 am »
The device that is placed on the level sensor for sending data needed to be reset.It is an avr-atemega256rfr2 device and is coded as a router (used wsndemo application).When the routers and coordinator is near,  no issue is showing.The coordinator receives data without any break.But when we placed routers far from coordinator and used another router for hopping the network hangs.
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #18 on: April 25, 2017, 03:24:23 am »
The device that is placed on the level sensor for sending data needed to be reset.
I don't know what "level sensor" is. I don't know anything about your network setup. Can you name them A, B and C in some order and tell which device has to be reset?

But when we placed routers far from coordinator and used another router for hopping the network hangs.
So it works in that configuration for some time, and then breaks, or it breaks as you move things around?

Does this intermediate router send the data? Can it still send it?

What status code is returned on the device that fails to send the data?
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #19 on: April 25, 2017, 03:39:02 am »
I don't know what "level sensor" is. I don't know anything about your network setup. Can you name them A, B and C in some order and tell which device has to be reset?
'A' be the coordinator ,'B' be the router(for hopping).C is a sendind device.B is placed between A and C.When these are kept in a distance ,the sending data from C is not received in A
Quote
So it works in that configuration for some time, and then breaks, or it breaks as you move things around?
yes it works when A,B,C are placed in near and it breaks when we move things around.
Quote
Does this intermediate router send the data? Can it still send it?
No router sends data until we reset device 'C'

 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #20 on: April 25, 2017, 03:44:01 am »
yes it works when A,B,C are placed in near and it breaks when we move things around.
So what was that thing about working for 10 minutes and then stopping?

Quote
Does this intermediate router send the data? Can it still send it?
No router sends data until we reset device 'C'

So you need to reset the last router in a chain without touching any other device and then it works again?

You really need to start running things under a debugger and observing status codes returned on sending devices. There is not a whole lot of you can do without a debugger.
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #21 on: April 25, 2017, 03:54:38 am »

So what was that thing about working for 10 minutes and then stopping?

Whcih is unknown to us


Quote
So you need to reset the last router in a chain without touching any other device and then it works again?
Yes .the statement is true and now it works exaclty like what the satement says.

Quote
You really need to start running things under a debugger and observing status codes returned on sending devices. There is not a whole lot of you can do without a debugger.
Will do debugging .checking return status code is the only the way of debugging.I suppose.right??
 

Online ataradov

  • Super Contributor
  • ***
  • Posts: 11238
  • Country: us
    • Personal site
Re: Lwmesh stack range
« Reply #22 on: April 25, 2017, 03:57:26 am »
Whcih is unknown to us
What is unknown? Can you clearly say if things stop working after some time or after moving the deivices around?


Okay .checking return status code is the only the way of debugging.I suppose.right??
That's the first step to know what sending device thinks about this situation.

What's the configuration on the device 'C'?
Alex
 

Offline vishalTopic starter

  • Regular Contributor
  • *
  • Posts: 102
  • Country: in
Re: Lwmesh stack range
« Reply #23 on: April 25, 2017, 04:04:00 am »
What is unknown? Can you clearly say if things stop working after some time or after moving the deivices around?
It will stop after moving devices around.


Quote
That's the first step to know what sending device thinks about this situation.
Will debug it by response status

Quote
What's the configuration on the device 'C'?
The configuration is same for all 3 devices A,B,C that I posted earlier. A is the coordinator and having device address '0' .B and C are routers.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf