Re: [Tinyos-help] make micaz sim problem
Hi, You can try modify "PYTHON_VERSION=2.*" to "PYTHON_VERSION=2.7" in "$TOSROOT/support/make/sim.extra" At 2013-03-12 23:13:35,mjmohiud...@cdac.in wrote: >i have phython 2.7.2+ version > >but when i do > >make micaz sim on Blink application > > >iam getting error > >mkdir -p simbuild/micaz > placing object files in simbuild/micaz > writing XML schema to app.xml > compiling BlinkAppC to object file sim.o >ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim >-fnesc-nido-tosnodes=1000 -fnesc-simulate >-fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow >-Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb >-DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 >-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"jumbo\" >-DIDENT_HOSTNAME=\"Jamal\" -DIDENT_USERHASH=0x8f700b47L >-DIDENT_TIMESTAMP=0x513fee28L -DIDENT_UIDHASH=0x3468b940L >-Wno-nesc-data-race BlinkAppC.nc -fnesc-dump=components >-fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs >-fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml >/opt/tinyos-main/tos/lib/tossim/sim_noise.c: In function >‘sim_noise_gen’: >/opt/tinyos-main/tos/lib/tossim/sim_noise.c:291:7: warning: variable >‘noiseIndex’ set but not used [-Wunused-but-set-variable] > compiling Python support and C libraries into pytossim.o, tossim.o, and >c-support.o >g++ -c -shared -fPIC -o simbuild/micaz/pytossim.o -g -O0 >-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"jumbo\" >-DIDENT_HOSTNAME=\"Jamal\" -DIDENT_USERHASH=0x8f700b47L >-DIDENT_TIMESTAMP=0x513fee28L -DIDENT_UIDHASH=0x3468b940L >/opt/tinyos-main/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.7 >-I/opt/tinyos-main/tos/lib/tossim -DHAVE_CONFIG_H >/opt/tinyos-main/tos/lib/tossim/tossim_wrap.cxx:139:20: fatal error: >Python.h: No such file or directory >compilation terminated. >make: *** [sim-exe] Error 1 > > >please provide me solution > >--- > >This e-mail is for the sole use of the intended recipient(s) and may >contain confidential and privileged information. If you are not the >intended recipient, please contact the sender by reply e-mail and destroy >all copies and the original message. Any unauthorized review, use, >disclosure, dissemination, forwarding, printing or copying of this email >is strictly prohibited and appropriate legal action will be taken. >--- > ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Telosb and weather sensor
Hello, I ask if someone use Telosb in the application" weather station "? So which Wind sensor you used?? Thanks in advance!! Sabrine ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] make micaz sim problem
i have phython 2.7.2+ version but when i do make micaz sim on Blink application iam getting error mkdir -p simbuild/micaz placing object files in simbuild/micaz writing XML schema to app.xml compiling BlinkAppC to object file sim.o ncc -c -shared -fPIC -o simbuild/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -fnesc-gcc=gcc -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=simbuild/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=10 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"jumbo\" -DIDENT_HOSTNAME=\"Jamal\" -DIDENT_USERHASH=0x8f700b47L -DIDENT_TIMESTAMP=0x513fee28L -DIDENT_UIDHASH=0x3468b940L -Wno-nesc-data-race BlinkAppC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml /opt/tinyos-main/tos/lib/tossim/sim_noise.c: In function âsim_noise_genâ: /opt/tinyos-main/tos/lib/tossim/sim_noise.c:291:7: warning: variable ânoiseIndexâ set but not used [-Wunused-but-set-variable] compiling Python support and C libraries into pytossim.o, tossim.o, and c-support.o g++ -c -shared -fPIC -o simbuild/micaz/pytossim.o -g -O0 -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"jumbo\" -DIDENT_HOSTNAME=\"Jamal\" -DIDENT_USERHASH=0x8f700b47L -DIDENT_TIMESTAMP=0x513fee28L -DIDENT_UIDHASH=0x3468b940L /opt/tinyos-main/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.7 -I/opt/tinyos-main/tos/lib/tossim -DHAVE_CONFIG_H /opt/tinyos-main/tos/lib/tossim/tossim_wrap.cxx:139:20: fatal error: Python.h: No such file or directory compilation terminated. make: *** [sim-exe] Error 1 please provide me solution --- This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. --- ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] help JTossim
Hi all, please can you help me in using JTossim. It works fine exept it don't display the tree built by the protocol, it displays only the topology. can anyone help me pleaase I will be grateful thank you in advance ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Including QueueC and PoolC components
Hi all
Maybe my following question either is a bit tricky or has no solution. Suppose
the following multi-hop scenario where we have an end-device (no routing
capabilities, it only transmits data to a unique destination), one or several
routing devices (their aim is to forward the data transmitted by the end-device
to one or several destinations), and one destination (sink):
End-Device --> Routing Device 1 --> ... --> Routing Device n --> Destination
I am implementing some libraries which ought to be the same regardless of the
type of device, namely end-device, routing device and/or destination. As I
briefly pointed out, the end-device has no routing capabilities, which implies
that its routing table only constains the node it used for joining the network
-parent node- and, additionally, it should not implement any message queue to
store data. On the contrary, this same features do have to be implemented by
the intermediate devices (routing ones), that is, routing tables of higher size
for storing more neighboring devices, and message_t queues.
I've "solved" the former using dynamic memory (I know this is supposed to not
be used, by I've tried to control the usage of memory). However, the issue
comes with the latter requirement of implementing the message_t queues. This is
explained below.
In my library, I employ a unique configuration file (I'll refer it hereafter as
main_conf.nc ) that wires everything and it is the same for end-devices and
routing-devices. It is worthy to remark that the final application running on
each device has a different configuration file that wires to this library.
Thus, in this file main_conf.nc, the QueueC and PoolC components ought to be
included. A priori, it should be done as follows:
In some .h file:
#define RX_QUEUE_SIZE 12
or
enum{ RX_QUEUE_SIZE = 12};
and in the confuguration file:
implements{...components new QueueC(message_t*, RX_QUEUE_SIZE),
new PoolC(message_t, RX_QUEUE_SIZE);...}
The easy way would be to change the RX_QUEUE_SIZE value to 1 (or eliminate the
QueueC and PoolC components of the code) every time I compile the code for an
end-device, being this slow and/or inefficient. So, is it possible to do this
in any way? Had both components been defined in the configuration file without
indicating the size of the queue, I may use again dynamic memory. But in this
case...
I hope all written above were easily understood!
Regards,
David
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TelosB and Zigbee network
On Mon, Mar 11, 2013 at 11:52 PM, Antonio wrote: > Hi Eric > Thanks for your answer, i wont only understand where is the different. i > am a newbie on the Wireless Sensor Network > No offense. Some of this is pretty basic. Basically, TinyOS uses 802.15.4 which implments the MAC and Physical Layers and puts its own Network/Routing/Application layers on top of the 802.15.4. ZigBee also uses the 802.15.4 MAC/PHY layers but has its own Network and upper layers that it uses. So while the MAC/PHY layers agree and interoperate, the upper layers are speaking differerent languages. This is basic networking stuff. If you don't understand and are trying to do WSNs you need to grab a book or take a class in basic Networking. best regads > Antonio > > > -- > *Da:* Eric Decker > *A:* Antonio > *Cc:* tinyos forum > *Inviato:* Martedì 12 Marzo 2013 4:30 > *Oggetto:* Re: [Tinyos-help] TelosB and Zigbee network > > > > On Mon, Mar 11, 2013 at 11:21 AM, Antonio wrote: > > in this site http://www.libelium.com/products/waspmote/ > you can see that it's use Zigbee / 802.15.4 / wifi protocol > > > I don't know why you are telling me something that you've already told me. > > > First, strictly speaking, 802.15.4 isn't WiFi. WiFi is used for 802.11 > which is a relatively high speed wireless local area network. 802.15.4 is > a WPAN. WiFi is a WLAN where W is for Wireless. > > 802.15 is used for Wireless Personal Area Networks. > > ZigBee refers to a protocol suite that is built above 802.15.4. > > 802.15.4 specs the Medium Access Control and Physical Layer protocols > > TinyOS only implements 802.15.4 and the protocols above this are not > ZigBee. > > So if the Waspmote expects Zigbee protocols then it won't interoperate > with a TinyOS mote. > > > > *Da:* Eric Decker > *A:* Antonio > *Cc:* tinyos forum > *Inviato:* Lunedì 11 Marzo 2013 19:12 > *Oggetto:* Re: [Tinyos-help] TelosB and Zigbee network > > what protocol is the Waspmote explicitly using for communications. > > TinyOS strictly speaking doesn't implement full Zigbee. > > On Mon, Mar 11, 2013 at 1:57 AM, Antonio wrote: > > Hi to all, i have this question, i have a Waspmote,( product link > http://www.libelium.com/products/meshlium/wsn/ ) > , it's work whit ZigBee protocol, now i have the Telosb but the Waspmote > don't see this telosB, > my question is: > can i use Waspmote for see the telosB sensor? > > > best regads > Antonio > > > > > ___ > Tinyos-help mailing list > Tinyos-help@millennium.berkeley.edu > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > > > > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > > -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
