Sub:

Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 2
2

Aim:
Aim: Exploring
Exploring and
and understanding
understanding TinyOS
TinyOS computational
computational concepts:
concepts: -- Events,
Events, Commands
Commands
and
and Task.
Task.
-- nesC
nesC model
model
-- nesC
nesC Components
Components

Explaination:
Explaination:

TinyOS:
TinyO S:

• TinyOS
TinyOS is is an
an open-source
open-source operating
operating system
system designed
designed for
for low-power
low-power wireless
wireless devices,
devices,
particularly those
particularly those used
used inin sensor
sensor networks
networks andand Internet
Internet of
of Things
Things (IoT)
(IoT) applications.
applications. It It
is
is characterized
characterized by by its
its lightweight
lightweight design,
design, efficiency,
efficiency, and
and flexibility,
flexibility, making
making it it suitable
suitable
for resource-constrained devices.
for resource-constrained devices.
• Originally
Originally developed
developed at
at the
the University
University of
of California,
California, Berkeley,
Berkeley, TinyOS
TinyOS is
is written
written in
in
the
the nesC
nesC (network
(network embedded
embedded systems
systems C) programming language,
C) programming which is
language, which is
specifically
specifically designed
designed for
for embedded
embedded systems
systems and
and sensor networks.
sensor networks.

1.
1. Events:
Events:

•¢ Definition:
Definition: Events
Events represent
represent asynchronous
asynchronous occurrences
occurrences such
such as
as sensor
sensor
readings,
readings, incoming
incoming messages,
messages, oror timer
timer expirations.
expirations. They
They are
are declared
declared within
within
interfaces of components using the event keyword.
interfaces of components using the event keyword.
•¢ Event
Event Handlers:
Handlers: Event
Event handlers
handlers are
are functions
functions that
that are
are called
called in
in response
response to
to
the
the occurrence
occurrence of
of an
an event.
event. They
They are
are defined using the
defined using the event
event qualifier.
qualifier.

•* Invocation:
Invocation: Events
Events areare raised
raised (or
(or fired)
fired) by
by components
components to
to signal
signal the
the
occurrence
occurrence of
of aa specific
specific event
event using
using the
the call
call statement.
statement.
•¢ Registration:
Registration: Components
Components can
can subscribe
subscribe to
to events
events raised
raised by
by other
other
components
components using
using the
the post
post statement.
statement.

•* Concurrency:
Concurrency: EventsEvents are
are scheduled
scheduled and
and executed
executed inin aa non-preemptive
non-preemptive
manner.
manner. It's
It's essential
essential to
to write
write event
event handlers
handlers efficiently
efficiently toto avoid
avoid blocking
blocking
operations.
operations.
2.
2. Commands:
Commands:
•* Definition:
Definition: Commands
Commands represent
represent actions
actions that
that can
can be
be performed
performed on
on aa
component.
component. They
They are
are declared
declared within
within interfaces
interfaces of
of components
components using
using the
the
command
command keyword.
keyword.
•* Command
Command Handlers:
Handlers: Command
Command handlers
handlers are
are functions
functions that
that implement
implement the
the
behavior
behavior associated
associated with
with aa command.
command. They
They are
are defined using the
defined using the command
command
qualifier.
qualifier.
•* Invocation:
Invocation: Commands
Commands areare called
called by
by other
other components
components or
or modules
modules to
to perform
perform
specific
specific actions
actions using
using the
the call
call statement.
statement.

Name:
Name: Roll
Roll No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

•¢ Execution:
Execution: Command
Command execution
execution is
is synchronous,
synchronous, meaning
meaning that
that the
the caller
caller waits
waits
for
for the
the command
command to
to complete before proceeding.
complete before proceeding.

•* Parameters
Parameters andand Return
Return Values:
Values: Commands
Commands cancan take parameters and
take parameters and return
return
values, allowing for communication of data between components.
values, allowing for communication of data between components.

3. Tasks:
3. Tasks:

•¢ Definition:
Definition: Tasks
Tasks represent units of
represent units of computation
computation that
that are
are executed
executed
asynchronously.
asynchronously. They
They are
are similar
similar to
to functions
functions or procedures in
or procedures in conventional
conventional
programming languages but are executed asynchronously.
programming languages but are executed asynchronously.

•* Task
Task Handlers:
Handlers: Task
Task handlers
handlers are
are functions
functions that
that define
define the behavior of
the behavior of a
a task.
task.
They
They are
are defined
defined using
using the
the task
task qualifier.
qualifier.

•* Scheduling:
Scheduling: TasksTasks are
are scheduled
scheduled for
for execution
execution by
by the
the TinyOS
TinyOS scheduler.
scheduler. They
They
can be scheduled to execute periodically, in response to events, or based
can be scheduled to execute periodically, in response to events, or based on on
other
other criteria.
criteria.
•* Concurrency:
Concurrency: TasksTasks can
can run
run concurrently
concurrently with
with other
other tasks
tasks and
and event
event handlers.
handlers.
It's
It's crucial
crucial to
to manage
manage concurrency
concurrency effectively
effectively to
to avoid
avoid race
race conditions
conditions and
and
ensure
ensure correct
correct behavior.
behavior.

•* Asynchronous
Asynchronous Execution:
Execution: Tasks
Tasks execute
execute asynchronously,
asynchronously, meaning
meaning that
that they
they
can be preempted
can be preempted by
by higher-priority
higher-priority tasks
tasks or
or events.
events.

A. nesC
nesC model:
model:

• nesC
nesC (network
(network embedded
embedded systems
systems C)C) is
is aa programming
programming language
language specifically
specifically
designed
designed for programming embedded systems and sensor networks, with
for programming embedded systems and sensor networks, with aa focus
focus on
on
efficiency
efficiency and
and modularity.
modularity. ItIt was
was developed
developed as part of
as part of the
the TinyOS
TinyOS project
project atat the
the
University
University ofof California,
California, Berkeley.
Berkeley. The
The language
language is primarily used
is primarily used in
in conjunction
conjunction with
with
TinyOS,
TinyOS, although
although itit can
can also
also be
be used
used independently.
independently.

• The
The nesC
nesC model
model encompasses
encompasses several
several key
key features
features and
and design
design principles:
principles:
1. Component-Based
Component-Based Architecture:
Architecture: nesC
nesC promotes
promotes aa component-based
component-based architecture,
architecture,
where
where software is divided into modular components that interact through well-defined
software is divided into modular components that interact through well-defined
interfaces.
interfaces. Components
Components encapsulate
encapsulate functionality
functionality and
and can be composed
can be composed to to build
build
complex
complex systems.
systems.

2. Interfaces:
Interfaces: Interfaces
Interfaces define
define the
the contracts between components.
contracts between components. They
They specify
specify aa set
set of
of
commands,
commands, events,
events, and
and sometimes
sometimes configuration
configuration parameters
parameters that
that aa component
component must
must
support.
support. Components
Components can can provide
provide or
or use
use interfaces,
interfaces, allowing
allowing for
for modularity
modularity and
and code
code
reuse.
reuse.

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

3. Wiring:
Wiring: Wiring
Wiring isis the
the process
process of
of connecting
connecting components
components together
together to
to form
form aa complete
complete
system.
system. It
It involves
involves specifying
specifying how
how interfaces
interfaces of
of different
different components
components are
are connected,
connected,
allowing
allowing them
them to
to communicate
communicate and
and interact.
interact.

4. Concurrency:
Concurrency: nesCnesC supports
supports concurrency
concurrency through
through event-driven programming.
event-driven programming.
Components
Components communicate
communicate asynchronously
asynchronously through
through events
events and
and commands,
commands, allowing
allowing
for
for efficient
efficient use
use of
of system
system resources
resources and
and responsiveness
responsiveness toto external
external events.
events.

5. Static
Static Configuration:
Configuration: Configuration
Configuration parameters
parameters can
can be
be used
used to
to customize
customize the
the
behavior of
behavior of components
components atat compile
compile time.
time. This
This allows
allows for
for flexibility
flexibility and
and optimization
optimization
while avoiding the overhead of runtime configuration.
while avoiding the overhead of runtime configuration.

6. Generic
Generic Programming:
Programming: nesC nesC supports
supports generic
generic programming
programming techniques,
techniques, allowing
allowing
components
components andand interfaces
interfaces to
to be
be parameterized
parameterized by by types
types and
and values.
values. This promotes
This promotes
code reuse and flexibility.
code reuse and flexibility.
7. Efficient
Efficient Resource
Resource Usage:
Usage: nesC
nesC isis designed
designed toto be
be highly
highly efficient
efficient in
in terms
terms of
of
memory usage and
memory usage and execution
execution speed.
speed. ItIt achieves
achieves this by providing
this by providing lightweight
lightweight
abstractions
abstractions and
and optimizations
optimizations tailored
tailored for
for resource-constrained
resource-constrained embedded
embedded systems.
systems.

B. nesC
nesC components:
components:
In
In nesC (network
nesC (network embedded
embedded systems
systems C),C), components
components are are the
the building
building blocks
blocks ofof the
the
software
software architecture.
architecture. They
They encapsulate
encapsulate functionality,
functionality, promote
promote modularity,
modularity, and
and enable
enable
code
code reuse.
reuse. Components
Components in in nesC
nesC follow
follow aa component-based
component-based architecture,
architecture, where
where
software
software isis divided
divided into
into modular
modular units
units that
that interact
interact through
through well-defined
well-defined interfaces.
interfaces.
Components
Components are defined using the module keyword in nesC. Components interact
are defined using the module keyword in nesC. Components interact
with
with each
each other
other through
through interfaces.
interfaces. Interfaces
Interfaces specify
specify aa set
set of
of commands,
commands, events,
events, andand
possibly configuration
possibly configuration parameters
parameters that
that aa component
component mustmust support.
support.

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 3
3

Aim: Understanding
Aim: Understanding TOSSIM
TOSSIM for
for
-- Mote-mote
Mote-mote radio
radio communication
communication
-- Mote-PC serial communication
Mote-PC serial communication

Explanation:
Explanation:
TOSSIM
TOSSIM stands
stands for
for TinyOS
TinyOS Simulator.
Simulator. It
It is
is aa simulation
simulation environment
environment forfor TinyOS-
TinyOS-
based wireless sensor networks. TOSSIM allows developers to test and debug their TinyOS
based wireless sensor networks. TOSSIM allows developers to test and debug their TinyOS
applications
applications without
without the
the need
need for physical hardware,
for physical providing aa convenient
hardware, providing convenient and
and efficient
efficient way
way
to
to experiment
experiment with
with different
different network
network configurations,
configurations, algorithms,
algorithms, and protocols.
and protocols.

Mote-Mote
Mote-Mote RadioRadio Communication
Communication
Mote-to-mote
Mote-to-mote radio radio communication
communication refers refers to
to the
the wireless
wireless communication
communication between between
individual
individual sensor
sensor nodes
nodes or or motes
motes within
within aa wireless
wireless sensor
sensor network
network (WSN).
(WSN). In In aa WSN,
WSN, sensor
sensor
nodes, often referred to as motes, are small, resource-constrained
nodes, often referred to as motes, are small, resource-constrained devices equipped with devices equipped with
sensors,
sensors, processing
processing units,
units, and
and wireless
wireless communication
communication capabilities.
capabilities. Mote-to-mote
Mote-to-mote
communication
communication enables
enables these
these devices
devices to to exchange
exchange data
data and
and collaborate
collaborate in in various
various sensing
sensing and
and
monitoring
monitoring tasks.
tasks. Each
Each mote
mote is is equipped
equipped withwith aa radio
radio transceiver
transceiver that
that allows
allows it it to
to transmit
transmit and
and
receive
receive radio
radio signals.
signals. Mote-to-mote
Mote-to-mote communication
communication can can occur
occur inin different
different network
network
topologies,
topologies, such
such asas point-to-point,
point-to-point, mesh, mesh, or or multi-hop
multi-hop networks.
networks. Motes
Motes communicate
communicate using using
communication
communication protocols
protocols designed
designed for for WSNs.
WSNs. Motes
Motes areare typically
typically assigned
assigned unique
unique identifiers
identifiers
or
or addresses that allow them to communicate with each other. In multi-hop networks, routing
addresses that allow them to communicate with each other. In multi-hop networks, routing
protocols are
protocols are used
used toto determine
determine the path data
the path data should
should take
take to reach its
to reach its destination,
destination, considering
considering
factors
factors such
such asas link
link quality
quality andand energy
energy efficiency.
efficiency. Energy
Energy efficiency
efficiency is is aa critical
critical consideration
consideration
in
in mote-to-mote
mote-to-mote communication.
communication. Motes Motes often
often employ power-saving techniques
employ power-saving techniques such such as
as duty
duty
cycling, where they alternate between active and sleep states to
cycling, where they alternate between active and sleep states to conserve energy while conserve energy while
maintaining
maintaining communication
communication capabilities.
capabilities.

Mote-PC
Mote-PC Serial
Serial Communication
Communication
Mote-to-PC
Mote-to-PC serial serial communication
communication involves involves establishing
establishing aa communication
communication link link
between aa sensor
between sensor node
node (mote)
(mote) andand aa personal
personal computer
computer (PC) (PC) using
using serial
serial communication
communication
protocols. This
protocols. This setup
setup allows
allows for
for data
data exchange
exchange between
between the the mote
mote and and the
the PC,
PC, enabling
enabling taskstasks
such
such as sensor data retrieval, configuration, and monitoring. Both the mote and the PC must
as sensor data retrieval, configuration, and monitoring. Both the mote and the PC must
have
have serial
serial interfaces
interfaces for for communication.
communication. The The mote
mote typically
typically uses
uses aa UART
UART (Universal
(Universal
Asynchronous
Asynchronous Receiver-Transmitter)
Receiver-Transmitter) module module to to interface
interface with
with its
its microcontroller,
microcontroller, while while thethe
PC usually connects
PC usually connects to to the
the mote
mote viavia aa USB-to-serial
USB-to-serial adapteradapter or or aa built-in
built-in serial
serial port.
port. Serial
Serial
communication
communication between between the the mote
mote and and the
the PC
PC follows
follows aa specific
specific protocol.
protocol. TheThe mote
mote andand the
the
PC
PC are
are connected
connected physically
physically using
using aa serial
serial cable
cable oror aa USB
USB cable
cable with
with appropriate
appropriate connectors.
connectors.
Both
Both the
the mote
mote and
and thethe PC
PC must
must be be configured
configured to use the
to use the same
same serial
serial communication
communication
parameters, such as baud rate, data bits, parity, and stop bits. These parameters ensure
parameters, such as baud rate, data bits, parity, and stop bits. These parameters ensure proper
proper
communication
communication synchronization
synchronization betweenbetween the the mote
mote andand the
the PC.
PC. Once
Once thethe serial
serial connection
connection is is
established,
established, data
data exchange
exchange can can occur
occur between
between the the mote
mote andand the
the PC.
PC. Error
Error handling
handling
mechanisms,
mechanisms, such such as as checksums
checksums or or error
error correction
correction codes,
codes, may
may be be employed
employed to to ensure
ensure data
data
integrity during transmission.
integrity during transmission.

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 4
4

Aim: Create
Aim: Create and
and simulate
simulate aa simple
simple adhoc
adhoc network.
network.

Steps:
Steps:
Step
Step 1:
1: Open
Open OMNet++
OMNet++ and
and Goto
Goto File
File and
and click
click on
on Import
Import the
the Select
Select Existing
Existing Project
Project into
into
Workspace.
Workspace.

File Edit Navigate Search Project Run Window Help

E Import o X
New Alt+Shift+N> p> ~ @@ | of
Open File... Select \
Close CtrleW Create new projects from an archive file or directory. [=]
Close Al Ctrl+ Shift+

Save Ctrl+S Select an import source:

S , itype filter text]
5 Ctrl+Shift+S
= (= General
(G Archive File
Move = Existing Projects into Workspace
Rename... F2 (3, File System
Refresh FS (7) Preferences
Convert Line Delimiters To > & C/C++

Print Ctrl+P & Git

C& Install
Switch Workspace > (2 OMNeT++
Restart @& Run/Debug
Sra (= Team

iA Export...

Properties Alt+ Enter

Exit

|
[7 Properties 22 B= Outline =D

® < Back Finish Cancel

Step
Step 2:
2: Open
Open OMNet++
OMNet++ and
and Goto
Goto File
File and
and click
click on
on Import
Import the
the Select
Select Existing
Existing Project
Project into
into
Workspace
Workspace ..
E Import o x

Import Projects =
Select a directory to search for existing Eclipse projects. eZ,

© Select root directory: | E:\IDM\inet-2.1.0-sre | Browse...

O Select archive file: Browse...

Projects:

inet (E:\[DM\inet-2.1.0-src\inet) Select All

Deselect All

Refresh

(1 Copy projects into workspace

Working sets

(Add project to working sets

Working set Select...

@ < Back Next > Cancel

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 3:
3: Create
Create aa new
new folder
folder inside
inside inet
inet >
> samples
samples >
> adhoc
adhoc folder
folder ..
E Simulation - OMNeT++ IDE
File Edit Navigate Search Project Run Window Help
ci~ | Hy Or Q~'S 9~@ US hl oor
Ss Project Explorer £3 l =g ||
BS
v ES inet A
(aw Includes
> £8 sre
(& 3rdparty
> & doc
& etc
v @ examples
v & adhoc
> S New Pj Project...
> & Go Into S =
= 7 File
& bat . . =
= dhe Open in New Window [7 File from Template
& diff Copy Ctrisc | Felder
&emeth
& Paste Ctrl+V\ | fj . Analysis—_File (anf)
= htt; % Delete Delete & Class
& ine Source > Class (OMNeT++)
eS _ Move... [Sj Compound Module
bd ‘pv Rename... F2 | Header File
ma
@ m/z. Import Dy Initialization File (ini)
S mo 24 Export... {ey Message Definition (msg)
@ mp Network
—
(TE Properties 38) Refresh F5 | § Network Description File (NED)
Index [—Bi Simple Module
aera Make Targets Eþj Simulation
fanetexamph Resource Configurations [& Source File
Resource Pre Run As 6&5 Source Folder
Debug As 3 Wizard
Profile As cee) C Project
Team C++ Project
Compare With 3) OMNeT++ Project...
| Restore from Local History... TY Other... Ctrl+N
8 Run C/C++ Code Analysis
Properties Alt+Enter
mM

Step
Step 4:
4: Create
Create aa new
new .NED
.NED file
file inside
inside the
the folder
folder you
you created
created ..
E Simulation - OMNeT++ IDE
File Edit Navigate Search Project Run Window Help
[whe | BwrYOvrQar Ev -@ Orr Sw eror
[> Project Explorer £3 > =a
es
v iS inet |
fl Includes
- Ber
(& 3rdparty
(2 doc
& etc
v > examples
v @ adhoc
Ez hostautoconf
= ieees0211
& Pract
S bgpv4 New Tj Project...
> = dhep Go Into Eile
& diffser
& emule Open in New Window File from Template

= ethem Copy Ctrl+C GED

= nitpte Paste Ctrl+V Analysis File (anf)
i
S interne X Delete Delete Class
& ipv6 Source Class (OMNeT++)
& manet Move... Compound Module
@ mobile Rename... F2 Header File
——— Initialization File (ini)
| Properties 53 wo
Export...
Message 9 Definition (msg)9
dE Network
/inet/examples) © Weise re Network Description File (NED)
Þ Index Simple Module
Resource _ Pe
rope
Make Targets Simulation
in
Resource Configurations Source File
pois Source Folder
Debug As
57
©”
l
Wizard

Profile As [© C Project
Team © C++ Project
Compare With fi] OMNeT++ Project...
Restore from Local History... r4 Other.. a
3” Run C/C++ Code Analysis r
Properties AlteEnter fichy [753 NED Parameters | fg NED Inheritance | E] Cons
f
CDT Bui ia Console [inet]

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 5:
5: After naming file
After naming file click
click on
on next
next and
and select
select the
the following
following options.
options.

E New
NED File o Xx El New NED File ia} x El New NED File
. New NED File Initial Contents Options
Choose NED file Select one of the options below Select options below

Enteror select the parent folder: Select template: Managed mobility wireless wizard.
inet/examples/adhoc/Pract | [= Empty NED file Network parameters
= 2) NED file with one item Number of hosts: [5 =
L — , Vv > Generated Wizards
= ro a 2 New Adhoc Mobility Wireless Network Wizard NED Topology Type
ba bred [2 New Managed Mobility Wireless Network Wizard fie
aS diffsev
ance Se
Topology
ca
Generation
nat Network for testing the TEEE 802.
11 model in managed
:
O Parametric
& emulation Topology Impo mode.
& ethernet [Template contributed by project "inet” Traffic parameters
& httptools TCP traffic
G inet
internetcloud
Pres'S [Dataata traffic
traffic (on
(on TCP)
&

& ipvs Server TCP layer: |TCP v

(= manetrouting
& mobileipvé Client TCP layer: TCP v
2 mobility bs
[Ping traffic
(Video Stream traffic
Advanced >>
Add content template by URL

©) < Back Next> Cancel

< Back
| a] ® ID nc

Step
Step 6:
6: After
After clicking
clicking finish
finish this
this topology
topology will
will be
be appeared.
appeared.

File Edit Source View Navigate Search Project Run

ft. IB %-OvQ- 60-8 fae Ons sy 23 (7 Simulation
1 Project Explorer 32 = 0) Bnewned £3 =o

a‘ Wag atecamplesaahoc hack Poke þ

jS inet a '; Selector
i ewe i New » A Connection
(> Irdpany © pes >
© es - BES
& cxumpls ome
" & adhoc channeKControl configurator S Submodules 2 <
hostautoconf @ AB WirelessHost (u
ieeed0211 a "
Pract hostd AccessPoint
‘ (i. .
— host! ChannelContr..
& bgp4
dhep x fp Adhocttest (i.
(S diftsery 6
(> emulation ap of) @ecPRovte (in.
S heme host Þ® Comesponden..
tea
Briomedgents .
® intemetcloud 8 Host (inetexa.
& ips A
© manetrouting Gi Mobileriost6(.
(& mobileipvé Ca 2 (J] NodeBaze (ine.
(= mobility » has (DJ Node
© Properties 12 "2 Outline © 7 W 05?FRouter(3
ox
Property Value
© StandardHost ..
{fi StanderatHost
Þ WirelessHost..
@ acPRouter (in...
@ E6PRouters,
JttheBus (inet.
Gethetiost (ne...
@ ftheHon (in..
© ftheryb ſine
Design Source,
'®\ Problems [7] FE "7 Bi console £2 { NET.
COT Build Console [inet]

==
P Type here to search =.

Name:
Name: Roll
Roll No:
No
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 7:
7: Then
Then Right-click
Right-click on
on our
our .NED
.NED file
file and
and Goto
Goto Run
Run as
as >> Omnet++
Omnet++ Simulation.
Simulation.

tty " $-0-&%- 7° Wo Jl > LOR ty 7) EB Simulation

SS Project Explorer £ 7 [8 new.ned o

# WH be laP dP IH FS + '[-[t8 MW
Brent 2294 Running,
Mags creates: 229 Megs present: 2
far: Simzec/rec: n/ EE
S Pract =o sendPrebe
stag Handywo =
resu BE Bi Der wu uw |O; MF *
tonal
ornn
EB New (New [Equeve size 0.1 = 0, medium
is free, scheduled
AIFS are 00, scheduled backeff ave 00 = | ff inet.examples adhoc.PractNew) New (ids 1) (ptrO821F288)
}# currentAC: 0, oldcurrentAC: 0
& bgpet BM scheduled-events |y current trancmission: none 4-
hep + Event #234 Tx0.244916113782 New hoztOumlan{0] radio (lece8021 Radio, i924) on wise
aes 248us(112bits)
cee Frame (eee8021 1ACKFrame)wian-ack will be transmitted at 2bps
= sending, changing RadioStateto TRANSMIT
@ ethemet |** Notification at T=0.244916113782 to New.hot0.wian[0].mac: RADIO-STATE TRANSMIT, cf
hitptools = DEF, state « IDLE, backoff 0.1 =
@ inet
internetclowd # retryCounter 01 = 0, radioState= 2, nav = Otxop is 0
7h queue size 0.1 = 0, medium is bury, scheduled AIFS are 0, scheduled backoff are 0)
& ips | = currentAC; 0, oldcurrentAC:
rms FN EO = current transmission: none
= | processing event in state machine leee80211Mac State Machine
leaving handleWahFSM
| # state information: made = DCF, state = IDLE, backoff 0.
inet/examples/.../Pra¢ |= backolfPericd 0.1 = 0
| tadioState = 2, ne i =
Resource Propety W Jequeve size 0.1 = 0, medium is busy, scheduled
AFS are 0, scheduled backoff are 00 Fal a Ml
info s CurrentAC: 0, oldeurremtAC: 0

=ifake Maree eveur—

oor
tart
link
** Notificationot T=0.244916113722
to New-host0.wlen{0], mgmt: RADIO-STATE TRANSMIT,
E
loce ENDM\inet-2
nan new.ned 70%);
pati /inet/example. )
size 1,703 bytes y

1 B console £ rn K = D-r1-=0
New [OMNeT-- Simulation] e\VDM\omnetpp-4.2.2\bin/opp.run-exe
(3/22/26 1:3) PM - run #0)
Leading images from e:\IDM\cmnerpp-4 abatract/*: 4 plock/*: on rs
Plugin pati 9;./plugins
Loading tel files

B inet/examples/adhoc/Pract/newined Run #0 - Scheduled: (50%) =e

File £68 Source View Navigate Search Project Run Window Help
ti @l® {$-0-Q- BH-o FB d-iji- “27 5 7 Bi Simulation
Project Explorer SB pewined £3 J
x package a
If Binaries a
15) bncludes
rkconfigurar:
© Irparty

parancters:
submodales
host0: WirelessHost
$a19play ("z=, , #707070") :
sci: KL
“we sdisplay (*z=, ,#
btptools
inet host2:
. WirelessHost

SOe leaded
ips v ) $dtaplay("z=, ,#
Tl Properties 170 BE Outinel 5 hoata: Wireless
| @display(" 1707
Property Value “ 1
tee host4: WixelessHost
display p= 140,50 ‘ "r= 70707
dynamic false 0dioplay ("r= , 0
gates = totak 0 (inherited: 0)
like-expr
ie
:
ap: AccessPoin'

name = configurator dateptay (*p=213, 274

parameter totak 11 (inherited: 11
type PuiNetworkConfigurat
icon ©
icon
icon size Design | Source
icon tint
icon tint 9 Þ Problems | zi k D console [1] mo @Orrm~"o
overlay ict New [OMNeT++ Simulation] e'\|DM\omnetpp-4.2.2\bin/opp.run.exe (3/22/24 1:31 PM - run $0)
overlay it >
ovetay it Loading images from e:\IDM\omnetpp-4.2 *: 90 backgrouna/*: 4 55 old/*: 111 aratus/*: 26
Polygon
border col Plug!
border wit Loading

Writoble Insert 62:9 Run#0 - Scheduled: (50%) e

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 5
5

Aim: Understanding, Reading

Aim: Understanding, Reading and
and Analyzing
Analyzing Routing
Routing Table
Table of
of aa network.
network. Routing
Routing Table
Table is
is
given we need
given we need draw
draw the
the topology.
topology.

Routing
Routing Table:
Table:

1.Router
1.Router 00 CLI
CLI Command:
Command: --
Router>en
Router>en
Router#config
Router#config tt
Enter
Enter configuration
configuration commands,
commands, one per line.
one per line. End with CNTL/Z.
End with CNTL/Z.
Router(config)#int fa0/0
Router(config)#int fa0/0
Router(config-if)#ip
Router(config-if)#ip address
address 100.0.0.1
100.0.0.1 255.0.0.0
255.0.0.0
Router(config-if)#no
Router(config-if)#no shut
shut

Router(config-if)#
Router(config-if)#
%LINK-5-CHANGED:
%LINK-5-CHANGED: Interface
Interface FastEthernet0/0,
FastEthernet0/0, changed
changed state
state to up
to up

Router(config-if)#int
Router(config-if)#int fa0/1
fa0/1
Router(config-if)#ip
Router(config-if)#ip address
address 10.0.0.1
10.0.0.1 255.0.0.0
255.0.0.0
Router(config-if)#no shut
Router(config-if)#no shut

Router(config-if)#
Router(config-if)#
%LINK-5-CHANGED:
%LINK-5-CHANGED: Interface
Interface FastEthernet0/1,
FastEthernet0/1, changed
changed state
state to up
to up

%LINEPROTO-5-UPDOWN:
%LINEPROTO-5-UPDOWN: Line protocol on
Line protocol on Interface
Interface FastEthernet0/1,
FastEthernet0/1, changed
changed state
state to
to
up
up

Router(config-if)#exit
Router(config-if)#exit
Router(config)#ip
Router(config)#ip route
route 192.18.0.0
192.18.0.0 255.255.255.0
255.255.255.0 100.0.0.2
100.0.0.2
Router(config)#
Router(config)#
%LINEPROTO-5-UPDOWN:
%LINEPROTO-5-UPDOWN: Line protocol on
Line protocol on Interface
Interface FastEthernet0/0,
FastEthernet0/0, changed
changed state
state to
to
up
up

Router(config)#^Z
Router(config)#"Z
%SYS-5-CONFIG_I:
%SYS-5-CONFIG1: Configured
Configured from
from console
console by
by console
console

Router#config
Router#config tt
Enter
Enter configuration
configuration commands,
commands, one
one per
per line.
line. End
End with
with CNTL/Z.
CNTL/Z.
Router(config)#^Z
Router(config)#"Z
Router#
Router#
%SYS-5-CONFIG_I:
%SYS-5-CONFIGI: Configured
Configured from
from console
console byby console
console

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

e Router
Router 0:
0:
Router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
Nl - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
El - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i = IS-IS, Ll - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
inter area
* - candidate default, U - per-user static route, © - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 1 subnets

10.0.0.0 is directly connected, FastEthernet0/1l
mang

100.0.0.0/8 is directly connected, FastEtherneto/0

192.168.0.0/24 [1/0] via 100.0.0.2

2.Router
2.Router 11 CLI
CLI Command:
Command: --
Router>en
Router>en
Router#config
Router#config tt
Enter
Enter configuration
configuration commands,
commands, one per line.
one per line. End with CNTL/Z.
End with CNTL/Z.
Router(config)#int
Router(config)#int fa0/0
fa0/0
Router(config-if)#ip
Router(config-if)#ip address
address 100.0.0.2
100.0.0.2 255.0.0.0
255.0.0.0
Router(config-if)#no
Router(config-if)#no shut
shut
Router(config-if)#
Router(config-if)#
%LINK-5-CHANGED:
%LINK-5-CHANGED: Interface
Interface FastEthernet0/0,
FastEthernet0/0, changed
changed state
state to up
to up
%LINEPROTO-5-UPDOWN:
%LINEPROTO-5-UPDOWN: Line protocol on
Line protocol on Interface
Interface FastEthernet0/0,
FastEthernet0/0, changed
changed state
state to
to
up
up
Router(config-if)#int
Router(config-if)#int fa0/1
fa0/1
Router(config-if)#ip
Router(config-if)#ip address
address 192.168.0.1
192.168.0.1 255.255.255.0
255.255.255.0
Router(config-if)#no shut
Router(config-if)#no shut
Router(config-if)#
Router(config-if)#
%LINK-5-CHANGED:
%LINK-5-CHANGED: Interface
Interface FastEthernet0/1,
FastEthernet0/1, changed
changed state
state to up
to up
%LINEPROTO-5-UPDOWN:
%LINEPROTO-5-UPDOWN: Line protocol on
Line protocol on Interface
Interface FastEthernet0/1,
FastEthernet0/1, changed
changed state
state to
to
up
up
exit
exit
Router(config)#ip
Router(config)#ip route
route 10.0.0.0
10.0.0.0 255.0.0.0
255.0.0.0 100.0.0.1
100.0.0.1
Router(config)#^Z
Router(config)#"Z
Router#
Router#
%SYS-5-CONFIG_I:
%SYS-5-CONFIGI: Configured
Configured from
from console
console by
by console
console

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

e Router
Router 1:
1:

Router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, HM - mobile, B -
BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
Nl - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
El - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i = IS-IS, Ll - IS-IS level-1l, L2 - IS-IS level-2, ia - IS-IS
inter area
* — candidate default, U - per-user static route, © - ODR
P - periodic downloaded static route

Gateway of last resort is not set

5 10.0.0.0/8 [1/0] via 100.0.0.1

c 100.0.0.0/8 is directly connected, FastEthernet0/0
Cc 192.168.0.0/24 is directly connected, FastEthernet0/1l

Topology
Topology Diagram:
Diagram:

f-
100.0.0.0

100.0.0.1 @Gpax—--—--—— mae FF 100.0.0.2

1441 1441
Royter0 Router 1

10.0.0.1 192.168.0.1
10.0.0.0 192.168.0.0

-
I #£ SY
PC-PT
=
PC-PT
PC-PT PC2 PC3
PCO
10.0.0.2 192.168.0.2 192.168.0.3

XY S

Name:
Name: Roll
Roll No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 6
6

Aim: Create
Aim: Create aa basic
basic MANET
MANET implementation
implementation simulation
simulation for
for Packet
Packet animation
animation and
and Packet
Packet
Trace.
Trace.

Steps:
Steps:
Step
Step 1:
1: Create
Create aa new
new folder
folder “manetPract”
*manetPract” in
in “inet/example/manetrouting”.
“inet/example/manetrouting”.

E Simulation - OMNeT++ IDE

File Edit Navigate Search Project Run Window Help

[wide | BwrOvrQ- vg S:©

[7 Project Explorer £3 =2f

(1 hypercube
v iS inet
4 Binaries
(pp! Includes
@ sre
(= 3rdparty
& doc
@ etc
v © examples
@ adhoc
& bgpv4
> dhep
& diffserv
(a emulation
= ethernet
& httptools
(a inet
= internetcloud
@ ipv6
v (= manetroutinn
& fg80211 New Fj Project...
& grid_aoc Go Into
File
G& hna
Open in New Window File from Template
2] Properties N gt c
[=] Copy Ctrl+C LESS
Paste Ctrl+V By Analysis File (anf)
/inet/examples/mal % Delete Delete G Class

Resource Property Source G@ Class (OMNeT++)

Info Move... [5 Compound Module
deri Rename... F2 hy HeaderFile
=i I ee [57 Initialization File (ini)
link| 2A Export... {ny Message Definition (msg)
locz Fi Network
nan 2] Refresh F5
pat} Index E New Folder oO X
Make Targets Folder
Resource Configurations
Create a new folder resource.
Team
Compare With
Enter or select the parent folder:
Restore from Local History...
Run C/C++ Code Analysis inet/examples/manetrouting

Properties Alt+Enter th =)

(= manetrouting
< > (2 mobileipv6
& /inet/examples/manetrouting (= mobility

26H
&® mpls
FH © Type here to search & ospfv2
& tp
& sctp
traci
traci_launchd
@ voip
& voipstream
{> wireless
© minrate

Folder name:

Advanced >>

Finish Cancel

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 2:
2: Create
Create aa new
new “.NED(Network
“.NED(Network Description
Description File)”.
File)”.
v @ manetrouting
> (2 fg80211
> @ grid_aodv
> & hna
> > manetMultiradio
(= manetP---* =
> & multirac New > FJ Project...
> & net8021 Go Into * File

> &
> =mobileipvé
net9021 .
Open in New Window
. =
| ¥ File from Template
> & mobility 2) Copy Ctrl+C (C5 Folder

- me Paste Ctrl+V Analysis File (anf)

> os

Haqam
Leen en Delete Delete Class
Properties 23 oF C Source > Class (OMNeT++)

SRAM
Move... Compound Module
/inet/examples...inc Rename... F2 Header File
] Initialization File (ini
Recource Property Dy Import... nitialization File (ini)

EBR Hee
Info 4 Export... Message Definition (msg)

deri Network
edit, ©) Refresh ue Network Description File (NED)
2

last Index > Simple Module

_ Make Targets > Simulation
oce
a Resource Configurations > Source File
pat! = > Source Folder

Compare With > Wizard

Restore from Local History... ſe C Project
be Run C/C++ Code Analysis ſe C++ Project m=_ =
Alt+Enter fey] OMNeT++ Project... R/24 1::
Properties
vr V v ins
I Loading tcl files from E Bj Citi Gabe ins:

Step
Step 3:
3: Enter the name
Enter the name of
of the
the file
file and
and click
click on
on “Next
*Next >”
>”

E New NED File oa X

New NED File

Choose NED file

Enter or select the parent folder:

inet/examples/manetrouting/manetPract

i
(= manetPract A
(= multiradio
(2 net80211_aodv
(2 net80211_control
(2 mobileipv6
(2 mobility
& mpls
& ospfv2
& rtp
& sctp
traci
(A traci_launchd
© vain

File name: | Mage)

Advanced >>

©) < Back Next > Cancel

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 4:
4: Select
Select Generated
Generated Wizards
Wizards >> New
New Adhoc
Adhoc Mobility
Mobility Wireless Networ.
Wireless Networ.

E New NED File oO x

Initial Contents
Select one of the options below

Select template:
=] Empty NED file
|=] NED file with one item
v (= Generated Wizards
|=] New Adhoc Mobility Wireless Network Wizard
|=] New Managed Mobility Wireless Network Wizard
> (=> Topology Generation
> (2 Topology Import

Add content template by URL

® ck || tn Cancel

Step
Step 5:
5: Select
Select options No. of
options No. of hosts=
hosts= 5,
5, Topology
Topology type
type =
= static.
static.

E New NED File

Options
Select options below

Ad hoc mobility wireless wizard.

Network parameters
Number of hosts: | 5 +>

NED Topology Type

© Static
O Parametric

® cn | Net Cancel

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 6:
6: We will get
We will get the predefined topology
the predefined topology with
with 5 hosts.
5 hosts.

// numOfHosts:
// parametric: false
// static: true

import inet. ayer ipv4.t ronfi :

import inet.nodes.inet.AdhocHost;
import inet.world.radio.ChannelControl;

host0: AdhocHost
{
parameters:
Q@display ("z=, , #707070");
}
hostl: AdhocHost
{
parameters:
@display ("z=, , #707070"):
»
host2: AdhocHost
{
parameters:
£display ("z=, , #707070"):
}
host3: AdhocHost
{
parameters:
@display ("z=, , #797070") ;
}
host4: AdhocHost
{
parameters:
edisplay "r=, , #707070");

Step
Step 7:
7: Right
Right Click
Click on
on the
the .NED
.NED file
file and
and select
select Run
Run as
as >
> 11 OMNet++
OMNet++ Simulation.
Simulation.
4] 1 9=a8

ad BH ov et+/Trenv- Manet? _ a x + DiOof;: ou, -O: MMC, «\=[>

ad File Edit Simulate Trace Inspect View Options Help = = DEED Gap GED
RGB? Bi atu[d MAD @ A Ree es il — S
Iv [Run 20: ManetP [Event #222 |[7=3.372389353603 [Running...
! scheduled: 14 |[Msgs created: 94 |[Msgs present: 61 |
ul Ev/sec: 8.47158 | Simsec/5ec: 0.000176648 |[Ev/simsec: 479574
ts | awan-ack FIESD movenove sendBing”™
+1e-8 +le-7 +le-b +le-5__+1e-4 © +0.001 £0.01 +04 +1 = 1Gec
k Manet? (Manet) |” Event #222 T=3,372389353603 ManetP.hostl.wlan{O]-radio (Ieee20211Radio, id=32), on \ |
Bp ance) © |RadiorframeDuration=248us(112bits)
io Frame (Ieee80211ACKFrame)wlan-ack will be transmitted at 2Mbps
1; sending, changing RadioState to TRANSMIT
1 ** Notification at T=3.372389353603 to ManetP.host1,wlan[0],mac: RADIO-STATE TRANSMIT
' state information: mode = DCF, state = WAITAIFS, backoff 0.1 = 1
A=-1
0, radioState= 2, nav= 0,txop is 0
#queue size 0..1 = 1, medium is busy, scheduled AIFS ‘heduled backoff i
[# currentAC: 0, oldcurrentAC: 0
# current transmission: 90
ing event in state machine leee80211Mac State Machine
FSM leee80211Mac State Machine: leaving state WAITAIFS
Dut firing Busy transition for leee80211Mac State Machine
= canceling AIFS period
FSM leee80211Mac State Machine: entering state DEFER
r leaving handleWithFSM
th #state information: mode = DCF, state = DEFER, backoff 0..1 = 1
= # backoffPeriod
= retryCounter0..1 = 0, radioState= 2, nav= 0,txop is 0
=queue size 0..1 = 1, medium is busy, scheduled AIFS are 0(), scheduled backoff are 0()
[# currentAC: 0, oldcurrentAC: 0
# current transmission: 90 - | Dil
Ml

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 7
7

Aim: Create
Aim: Create aa wireless
wireless network
network of
of multiple
multiple PCs using appropriate
PCs using appropriate AccessPoints.
AccessPoints.

Steps:
Steps:

Step
Step 1:
1: Create
Create the
the following
following topology using the
topology using the component
component (i.e
(i.e AccessPoint-PT-A,
AccessPoint-PT-A,
AccessPoint-PT, AccessPoint-PT-N,
AccessPoint-PT, AccessPoint-PT-N, 2PCs,
2PCs, Laptop
Laptop and
and Server).
Server).

Eile Edit Options View Tools Extensions Help

2] Physical|x 815, y: 554 Ra $5 Je | <> [Laat Jeg 07-1129

AccessPoint-PT-A AccessPoint-PT AccessPoint-PT-N

Access PointO Access Point! Access Point2

[=] & 2 |
Server-PT
Laptop0 Server0

Time: 00:14:20[ (1) |] p> | esi

eae sect ei laeze Jetaice2

Step
Step 2: Now add
2: Now the required
add the required modules
modules asas given below ::
given below
1.)
1.) Add
Add PT-HOST-NM-1W-A
PT-HOST-NM-1W-A to to PC0
PCO and
and PC1
PC1 as
as soon
soon as
as you
you turn
turn on
on the
the PCs
PCs after
after
Adding the module
Adding the module it
it will
will form
form association
association with
with AccessPoint-PT-A.
AccessPoint-PT-A.
2.)
2.) Add
Add PT-HOST-NM-1W
PT-HOST-NM-1W to
to Laptop
Laptop and
and Server
Server as
as soon
soon as
as you
you turn
turn on
on the
the machines
machines after
after
adding
adding the
the module
module it
it will
will form
form association
association with
with AccessPoint-PT.
AccessPoint-PT.

File Edit Options View Tools Extensions Help

601,y- 563 Row |@ [<>] at ge 19:19:29

ace Per FIN... AccessPoint-PT-N |

‘Access Point) Access Paint! Access Point2

' =a Laptop-PT
PC-PT Server-PT
PCO 1 Laptop0 ServerO

Time: 00:26:22| ( || > | |. Simulation

28m soot sZi b= 42 e0¢Lee- Quy i &

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 3: Now turn
3: Now turn off
off the
the port
port 11 or
or add
add WEP
WEP key
key for port 11 of
for port of AA AccessPoint-PT
AccessPoint-PT after
after
adding the
adding Key the
WEP Key
the WEP the laptop
laptop and
and the
the server
server will
will form
form association
association with
with
AccessPoint-PT-N.
AccessPoint-PT-N.
® access Point PT _ [m] X

Physical Config Attributes

GLOBAL |*® Port 1

Settings Port Status On
INTERFACE SSID Default
2.4 GHz Channel 6 v
Port O
Coverage Range (meters) 140.00 S|
Port 1
Authentication
© Disabled O wep WEP Key 1111111111
© WPA-PSK © WPA2-PSK PSK Pass Phrase
User ID
Password
Encryption Type 40/64-Bits (10 Hex digits) v

Vv

(7 Top

Þ Cisco Packet Tracer

File Edit Options View Tools Extensions Help

E Physical] x 1128, y 254 (Root [| @ || <=> | a8 [7 18:13:00

AccesgPéint-PT-A AccessPointPT
Accgss Point) Access Point PT

S - Re
S z R
S Z w
J
SD == JH
V

E Z RQ

fi PC-PT Laptop-PT
PC-PT Server-PT
PCO PCI Laptopo Server0

Time: 00:32:19{
© || >> | (Reaitime| | Simulation
Pe We Peer a a |
2gusoord
zie ses Veczeee |
ELITE Lapiop-PT

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 8
8

Aim: Implement
Aim: Implement aa Wireless
Wireless sensor
sensor network
network simulation.
simulation.

Steps:
Steps:
Step
Step 1:
1: Create
Create the
the topology
topology using
using the
the component
component mention
mention in
in the
the aim.
aim.
® Cisco Packet Tracer = a x
File Edit Options View Tools Extensions Help

SMARTPHONE-PT DLC100
Home Gateway0 Webcam
Smartphone)

Time: 00:05:35] ©) || > | (GReattime|.®. Simulation]

29a
- oem wo =yT | i=.) a) om ezemt’ Tl
EL = &. [ Garage Door

Step
Step 2: Now copy
2: Now the “Home
copy the “Home Gateway
Gateway SSID”
SSID” and paste itit in
and paste in the
the “Smart
“Smart Device
Device
SSID”.
SSID”.

Cisco Packet Tracer a x

E Q View te He

Re & Physical|x 904, y: 159 [Root] * || |) +> aw

© HomeGateway - og Xx (
Physical Config GUI Attributes
GLOBAL n Wireless Settings Light
Settings S810 TD Light
Algorithm Settings | | 2-4 GHz Channel 6 - 2.437GHz
INTERFACE Coverage Range (meters) 250.00
Internet Authentication
LAN © Disabled © WEP WEP Key
Wines | | | © WPA-PSKO WPA2-PSK PSK Pass Phrase
CWPA © WPA2
RADIUS Server Settings
IP Address
SMART ENE ET Shared Secret Lin Webcam
martphone Encryption Type Disabled Webcam

® smartphone - o

Physical Config Desktop Programming Attributes

GLOBAL = WirelessO
Settings Port Status
Top Algorithm Settings Por SM _
ress:
INTERFACE SSID HomeGateway
WirelessO Aron
entication
SE/AGICaD © Disabled © WEP WEP Key
Bluetooth
Time: 0607-56]
) |> © WPA-PSK © WPA2-PSK PSK Pass Phrase
>= oo 1 mw==t7 mB -o.c6 Ow OW un
© 802.1X Method: MDS
oJ (| 4&4 = A User Name
[ Garage Door Password
Encryption Type Disabled

IP Configuration
© DHCP
OY Static

© Top

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 3:
3: Go
Go to
to “Smart
“Smart Device
Device >> Desktop
Desktop > > IoT
IoT Monitor
Monitor Enter
Enter the Username and
the Username and
password if
password if signed
signed in
in or
or else
else create
create the Username as
the Username as “admin”
“admin” and password as
and password as
“admin”.
“admin”.

=
© Smartphone = o x i

Physical Config Desktop Programming Attributes ©

( LID Light
RY | Light

Ariel ©
SMARTPHONE-PT mill | © Smanohone ~ ©
Smartphone Physical Config Desktop Programming Attributes
loT Monitor

IoT Server Address: 192.168.25.1

User Name: |admin
Password: admin
Login
op

Time: 00:10:30|
©) | ÞÞ |
_
SIJn-
goon gwgo=yT] AUi-£=.ae7
D T a | ' >

ELITES =

Step
Step 4: Now Go
4: Now to IoT
Go to IoT Devices
Devices enable
enable Advance
Advance option
option in bottom right
in bottom right corner
corner and
and add
add
the PT-IOT-NM_1W
the Network Adapter.
PT-IOT-NM_1W Network Adapter. Repeat
Repeat this
this step
step for
for all
all IoT
IoT Devices.
Devices.

© light = o x
Specifications VO Config = Physical Config Thing Editor Programa b >
Network Adapter None = Light
eek Ne € Prior MAGE Light
Digital Slots PT-OT-NM-1CFE
‘Analog Slots PT-IOT-NM-1CGE

| SS PTIOTNM 346
USB Ports PTHOT-NM-1W-AC

TO Deskop [7 Show
Usage © Smart Device © Component
SMARTPHONE-PT Webcam
Smartphone | Webcam

Ee GS 88

(6p Garage Door

Door

Time: 00:12:31] © | p> | (Realtime. Simulation]

CELESTE) Fx
= =
MMHLEFELECEHER-L
] L 3 ©9150

af Si ot ea [ Power Meter

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 5: Now Go
5: Now Go to
to IoT
IoT Devices
Devices >
> Config
Config >
> IoT
IoT Server
Server and
and choose
choose Home
Home Gateway.
Gateway.

Ce CIP
® light - o x

Specifications Physical Config Attributes

GLOBAL © once
Settings © Auto Config
Algorithm Settings © Static
Files By
INTERFACE
2 Wireless0 IF DNS Server
CECE
loT Server
SMARTPHONE-PT © None
Smartphone1 © Home Gateway
© Remote Server n
Server Addrass a
User Name
Password
Connect j
-

oor
(Top Advanced

Time: 00:25:59] (2) | > | |S, Simulation|

2J=-oo ngwuo=y Affi-2.c 5 em ©k-om9tr[ll

JO&SS4 | SMARTPHONE-PT

Step
Step 6: Now Go
6: Now to SmartDevice
Go to SmartDevice >
> Desktop
Desktop >
> IoT
IoT Monitor
Monitor and
and Login.
Login.

Roo] ||@ |] <=> [at lege 14:02:30]

—
® Smartphone! = o x

Physical Config Desktop Programming Attributes

JT Monitor

IoT Server - Devices Home | Conditions | Editor | Log Out

@ Light (yTT08106511-) Light

. | @ webcam (PTTO8100BSK-) Webcam

4 PCO
4 @ Door (PTTOS10FNLC-) Garage Door
SMARTPHONE-PT
Smartphone 1
1

or

OTop

Time: 00:27:52] ©) | be | (GRealtime| 3, simuiation]

23m
- oo gu ny Ea ao. .to tom 20971 4

ELITES SMARTPHONE-PT

Name:
Name: Roll
Roll No:
No:
Sub: Wireless Sensor
Sub: Wireless Sensor Network
Network Class:
Class: TYCS
TYCS

Step
Step 7: Now you
7: Now you can
can control
control your
your IoT
IoT Devices
Devices with
with your
your smart
smart phone,
phone,

E Physical|x 769, 589 tRoot || @ |<?» || ast ||@F 16:12:30]

® Smartphonet = o x

Physical Config Desktop Programming Attributes wy

\
ToT Server - Devices Home | Conditions | Editor | Log Out | W Wo i
Light
| Light
@ Light (PTTo8106511-) Light

; Status _off
| vim |
aill © Webcam (err00:0085K-) Webcam | Mmmm
ebcam 3
SMARTPHONE-PT
Smartphone1 @ Door (PTTOS10FNLC-) Garage Door Webcam
Webcam
Wy,
0
WR
= 22 22

Garage Door
DO top Door

Time: 00:32:08]
(O |[ dd | [@Reattime] [, Simulation

29m secocubmgoe2r!) T'Hi-=. C6 om eanen ert

H/@|&S = 3 SMARTPHONE-PT

Step
Step 8: Now you
8: Now you can
can control
control your
your IoT
IoT Devices
Devices with your smart
with your smart phone,
phone,
IR isco Packet Tracer

Physical]x 703, » 453

® smartphonet = o x

Physical Config Desktop Programming = Attributes .

V
loT Server - Devices Home | Conditions | Editor | Log Out \ RY Light

@ Light (PTTOB10651-) .
Light | yw" ww i
Light
@ Webcam (PTTO8100BSK-) Webcam
@ Door (PTTOS10FNLC-) Garage Door
VCC

on
Webcam
NY, 7
Wn Webcam
MN WIA
"1
WIN
Ul,

Garage Door
Door

® Smartphone1 = o x

© Tp Physical Config Desktop Programming Attributes

Time: 00:38:23] (2) || D>

2Heasecutm@ge=+!) TH -o. 4 Name Door_open

mm Enabled #

If:
Match | All ¥ [+ Condition + Group
| Door 7 On? is true ¥ -

Then set: + Action |

Light 7 Status 7 to|On ¥ le]

Il

OTop

Name:
Name: Roll
Roll No:
No:
Sub:
Sub: Wireless
Wireless Sensor
Sensor Network
Network Class:
Class: TYCS
TYCS

Practical
Practical No:
No: 9
9

Aim: Create
Aim: Create aa mobile
mobile network
network using
using Cell
Cell Town
Town and
and Central
Central Office
Office Server.
Server. Simulate
Simulate
connection between them.
connection between them.

Steps:
Steps:
Step
Step 1:
1: Take
Take Smart
Smart Phone,
Phone, WRT300N,
WRT300N, PT-HUB,
PT-HUB, Cell
Cell Tower,
Tower, Central-Office
Central-Office Server
Server and
and
Router for forming the topology.
Router for forming the topology.

—S
L | 0/0 Fad pn
Ss
oS WRT3OON
| Huff PT EAN
«Wireless Router0
WV >
DV

R
“Ny,

SMARTPHONES;
Smartphone0 “Ny,
My,
My,
My,

ZS»)
—_ _—_—_——

Cell-Tower Central-Office-Server
Cell Tower0 Central Office Server0

Step
Step 2:
2: Configure
Configure the
the Router
Router 0.
0.

Step
Step 3:
3: Ping
Ping the
the Router
Router 00 from
from the
the Smart
Smart Phone.
Phone.

Name:
Name: Roll
Roll No:
No: