Characteristics of LoWPAN's

-

Characteristics of LoWPAN's are as follows:


1.Small packet size: Maximum physical layer packet size=127 bytes.
                                Maximum frame size at the media aceess control layer=102 octets
                               Link-layer security imposes further overhead,which in the maximum case has 
                                 21 octets as overhead leaving 81 octets for data packets.

 2. Support for both 16-bit short or IEEE 64-bit extended media access control addresses.

 3.Low Data rates:  Data rates --->Physical Layer
                              250kbps  ---->2.4GHz
                              40kbps    ----> 915MHz
                              20kbps   ----->868MHz

 4.Topologies : Mesh,Star.

 5. Low Power: As most of the devices are battery operated.

 6.Low Cost:    As devices are typically associated with sensors,switches etc..so it requires less      
                         processing,low memory which in turn is nothing but lower cost.

 7.Location:  Location is typically not predefined. Sometimes, the location of these devices not be easily 
                      accessible. sometimes , they may move to a new location

 8.Devices sometimes may be unreliable due to uncertain radio connectivity,battery drain,etc

 9.Mostly the devices will be in sleep for long periods of time in order to conserve energy..and during this time they are unable to communicate with other devices.

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more