[Tinyos-help] How to display sensor data using Moteview
Hai, I am using crossbow Professional kit consisting of Micaz motes,MIB520 programming board and MTS400 sensor board. I want to know whether I have to program Micaz mote to collect data from sensor using Moteview.If so how I have to program Micaz mote. -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to display sensor data using moteview
Hai, I am using crossbow Professional kit consisting of Micaz motes,MIB520 programming board and MTS400 sensor board. I want to know whether I have to program Micaz mote(connected to mib520) to collect data from sensor using Moteview.If so how I have to program Micaz mote. I Connected one micaz mote to mib520 programming board and programmed it using moteconfig as follows: 1) In Moteview I clicked Tools-Program Motes 2)In MoteConfig window I clicked Settings-Interface Board. In Interface board settings window I selected MIB520 and changed com port to 5 (lower port)and clicked Apply. 3)Then I clicked select button under select file to be uploaded. I selected XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase 4)Then I clicked Program button. 5)After finishing program I clicked File-Connect to WSN. In that new window I selected MIB520 board and com6(higher port) and XMTS400 board. 6)After completing all these steps sensor data is not displaying in PC. If my steps are wrong means please correct me. -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Minimizing RAM consmption
The maximum is 256 bytes of payload because the TinyOS radio code uses uint8_t length values; your radio may have a smaller maximum. Given a certain bit error rate, I suppose a packet twice as long is twice as likely to be corrupted. I'm sure there's publications on this topic, but I don't know of any I'm afraid. Google is your friend :) Michiel From: Flavio Pompermaier [mailto:[EMAIL PROTECTED] Sent: woensdag 9 april 2008 0:02 To: Michiel Konstapel Subject: RE: [Tinyos-help] Minimizing RAM consmption I've already noticed this..In my code I was using some Pool (with respective Queues) for manage receiving and sending (from/to radio, from/to flash and sending to serial), but as I increment MSG_SIZE the RAM consumption explodes...For a MSG_SIZE=40 the RAM consuption was about 5K, with MSG_SIZE=100 (if it makes sense..) typing make telosb the compiler tell me that bss section overflows..(more than 10K)! So I understood that MSG_SIZE is a very important parameter.. Since we touched the MSG_SIZE argument, is there an adviced maximum value for it in Telosb? I know that there's a maximum size (I don't remember precisely now), but as the number of neighbor nodes increases, it's a good idea to send BIG packets as FEW TIMES as possible (to avoid collision). But how much does increases the integrity of received packet as MSG_SIZE increases..? Is there any reference about it? --- Mar 8/4/08, Michiel Konstapel [EMAIL PROTECTED] ha scritto: Da: Michiel Konstapel [EMAIL PROTECTED] Oggetto: RE: [Tinyos-help] Minimizing RAM consmption A: Flavio Pompermaier [EMAIL PROTECTED], Tinyos tinyos-help@millennium.berkeley.edu Data: Martedì 8 Aprile 2008, 11:56 Tweak your TOSH_DATA_LENGTH to be just big enough for your payloads so you don't waste memory on packet buffers. Michiel ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to display sensor data using moteview
Hi, I programmed the mote(supposed to be the base station that is connected to mib520) with XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase. But still I am not able to display sensor data in pc. Regards, Dhivya. On Wed, Apr 9, 2008 at 1:48 PM, Marco Antonio Lopez Trinidad [EMAIL PROTECTED] wrote: What is the program you use? 1. TinyOS SerialForwarder uses the next port you use to connect the programmer. 2. MoteWorks applications suite recognises automatically the right ports to program (com_i) and inject or read packets (com_i+1). I hope it helps, --marco. Hi Anil, I am getting 2 ports(com5 and com6) while connecting MIB520 to pc. In step 2, I am programming my mote that is connected to Mib520. So while Programming I have to give lower port(com5). In step 5, I am getting data from sensors and have to display it in PC.So for communication part I have to use higher port(com6). This is wht I did earlier. I also tried your idea.But I am getting following error. Can not connect to Mote correctly. Please check your Mote. Regards, Dhivya On Wed, Apr 9, 2008 at 12:47 PM, Anil Karamchandani [EMAIL PROTECTED] wrote: Hi Dhivya, the port number should be the port through which your gateway device is connected to the PC. Usually the port number in step 2 and step 5 is the same. check for the port which is communicating with the sensor and the PC and give that port number .. hope this helps anil On Wed, Apr 9, 2008 at 12:34 PM, Dhivya G [EMAIL PROTECTED] wrote: Hai, I am using crossbow Professional kit consisting of Micaz motes,MIB520 programming board and MTS400 sensor board. I want to know whether I have to program Micaz mote(connected to mib520) to collect data from sensor using Moteview.If so how I have to program Micaz mote. I Connected one micaz mote to mib520 programming board and programmed it using moteconfig as follows: 1) In Moteview I clicked Tools-Program Motes 2)In MoteConfig window I clicked Settings-Interface Board. In Interface board settings window I selected MIB520 and changed com port to 5 (lower port)and clicked Apply. 3)Then I clicked select button under select file to be uploaded. I selected XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase 4)Then I clicked Program button. 5)After finishing program I clicked File-Connect to WSN. In that new window I selected MIB520 board and com6(higher port) and XMTS400 board. 6)After completing all these steps sensor data is not displaying in PC. If my steps are wrong means please correct me. -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Regards Anil Karamchandani -- G.Dhivya -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Minimizing RAM consmption
Title: RE: [Tinyos-help] Minimizing RAM consmption Ok..thanks for the replies however..--- Mer 9/4/08, Michiel Konstapel [EMAIL PROTECTED] ha scritto:Da: Michiel Konstapel [EMAIL PROTECTED]Oggetto: RE: [Tinyos-help] Minimizing RAM consmptionA: [EMAIL PROTECTED]Cc: tinyos-help@millennium.berkeley.eduData: Mercoledì 9 Aprile 2008, 09:17 The maximum is 256 bytes of payload because the TinyOS radio code uses uint8_t length values; your radio may have a smaller maximum. Given a certain bit error rate, I suppose a packet twice as long is twice as likely to be corrupted. I’m sure there’s publications on this topic, but I don’t know of any I’m afraid. Google is your friend :) Michiel From: Flavio Pompermaier [mailto:[EMAIL PROTECTED] Sent: woensdag 9 april 2008 0:02 To: Michiel Konstapel Subject: RE: [Tinyos-help] Minimizing RAM consmption I've already noticed this..In my code I was using some Pool (with respective Queues) for manage receiving and sending (from/to radio, from/to flash and sending to serial), but as I increment MSG_SIZE the RAM consumption "explodes"...For a MSG_SIZE=40 the RAM consuption was about 5K, with MSG_SIZE=100 (if it makes sense..) typing "make telosb" the compiler tell me that bss section overflows..(more than 10K)! So I understood that MSG_SIZE is a very important parameter.. Since we touched the MSG_SIZE argument, is there an "adviced" maximum value for it in Telosb? I know that there's a maximum size (I don't remember precisely now), but as the number of neighbor nodes increases, it's a good idea to send BIG packets as FEW TIMES as possible (to avoid collision). But how much does increases the integrity of received packet as MSG_SIZE increases..? Is there any reference about it? --- Mar 8/4/08, Michiel Konstapel [EMAIL PROTECTED] ha scritto: Da: Michiel Konstapel [EMAIL PROTECTED] Oggetto: RE: [Tinyos-help] Minimizing RAM consmption A: "Flavio Pompermaier" [EMAIL PROTECTED], "Tinyos" tinyos-help@millennium.berkeley.edu Data: Martedì 8 Aprile 2008, 11:56 Tweak your TOSH_DATA_LENGTH to be just big enough for your payloads so you don't waste memory on packet buffers. Michiel Inviato da Yahoo! Mail. La casella di posta intelligente. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to display sensor data using moteview
Have you programmed other motes with the XMTS400 app? I think they don't come preprogrammed from factory. Regards, Harri From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dhivya G Sent: Wednesday, April 09, 2008 11:50 AM To: Marco Antonio Lopez Trinidad Cc: TinyOS_Help Subject: Re: [Tinyos-help] How to display sensor data using moteview Hi, I programmed the mote(supposed to be the base station that is connected to mib520) with XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase. But still I am not able to display sensor data in pc. Regards, Dhivya. On Wed, Apr 9, 2008 at 1:48 PM, Marco Antonio Lopez Trinidad [EMAIL PROTECTED] wrote: What is the program you use? 1. TinyOS SerialForwarder uses the next port you use to connect the programmer. 2. MoteWorks applications suite recognises automatically the right ports to program (com_i) and inject or read packets (com_i+1). I hope it helps, --marco. Hi Anil, I am getting 2 ports(com5 and com6) while connecting MIB520 to pc. In step 2, I am programming my mote that is connected to Mib520. So while Programming I have to give lower port(com5). In step 5, I am getting data from sensors and have to display it in PC.So for communication part I have to use higher port(com6). This is wht I did earlier. I also tried your idea.But I am getting following error. Can not connect to Mote correctly. Please check your Mote. Regards, Dhivya On Wed, Apr 9, 2008 at 12:47 PM, Anil Karamchandani [EMAIL PROTECTED] wrote: Hi Dhivya, the port number should be the port through which your gateway device is connected to the PC. Usually the port number in step 2 and step 5 is the same. check for the port which is communicating with the sensor and the PC and give that port number .. hope this helps anil On Wed, Apr 9, 2008 at 12:34 PM, Dhivya G [EMAIL PROTECTED] wrote: Hai, I am using crossbow Professional kit consisting of Micaz motes,MIB520 programming board and MTS400 sensor board. I want to know whether I have to program Micaz mote(connected to mib520) to collect data from sensor using Moteview.If so how I have to program Micaz mote. I Connected one micaz mote to mib520 programming board and programmed it using moteconfig as follows: 1) In Moteview I clicked Tools-Program Motes 2)In MoteConfig window I clicked Settings-Interface Board. In Interface board settings window I selected MIB520 and changed com port to 5 (lower port)and clicked Apply. 3)Then I clicked select button under select file to be uploaded. I selected XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase 4)Then I clicked Program button. 5)After finishing program I clicked File-Connect to WSN. In that new window I selected MIB520 board and com6(higher port) and XMTS400 board. 6)After completing all these steps sensor data is not displaying in PC. If my steps are wrong means please correct me. -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Regards Anil Karamchandani -- G.Dhivya -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Error compiling Oscilloscope with IRIS mote
Thanks, the problema is solved. Eva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] python configuration
Hi , I encountered a blocking problem when compiling Tossim application in Tinyos 2. I found that there are other persons who got the same error and the answer was : you should configure your python Unfortunately, I didn't find how. please help me ( I am blocked) this is the error /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3236: error: syntax error before `-' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3238: error: ISO C++ forbids declaration of `Py_INCREF' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3238: error: redefinition of ` int Py_INCREF' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3194: error: `int Py_INCREF' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3238: error: ISO C++ forbids declaration of `resultobj' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3238: error: redefinition of ` int resultobj' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3221: error: `int resultobj' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3239: error: parse error before `return' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3240: error: syntax error before `:' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3245: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3247: error: redefinition of ` Tossim*arg1' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3230: error: `Tossim*arg1' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3248: error: conflicting types for `bool result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3219: error: previous declaration as `int result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3249: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3253: error: ISO C++ forbids declaration of `result' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3253: error: conflicting types for `int result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3248: error: previous declaration as `bool result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3255: error: ISO C++ forbids declaration of `resultobj' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3255: error: redefinition of ` int resultobj' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3238: error: `int resultobj' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3255: error: `PyInt_FromLong' was not declared in this scope /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3256: error: parse error before `return' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3257: error: syntax error before `:' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3262: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3264: error: redefinition of ` Tossim*arg1' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3247: error: `Tossim*arg1' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3265: error: conflicting types for `MAC*result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3253: error: previous declaration as `int result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3266: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3270: error: ISO C++ forbids declaration of `result' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3270: error: conflicting types for `int result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3265: error: previous declaration as `MAC*result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3272: error: ISO C++ forbids declaration of `resultobj' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3272: error: redefinition of ` int resultobj' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3255: error: `int resultobj' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3272: error: `SWIG_NewPointerObj ' was not declared in this scope /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3273: error: parse error before `return' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3274: error: syntax error before `:' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3279: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3281: error: redefinition of ` Tossim*arg1' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3264: error: `Tossim*arg1' previously defined here /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3282: error: conflicting types for `Radio*result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3270: error: previous declaration as `int result' /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3283: error: syntax error before `*' token /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3287: error: ISO C++ forbids declaration of `result' with no type /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:3287: error: conflicting types
[Tinyos-help] Radio models
Hello, Are there a difference between radio models in TinyOS 1 and TinyOS 2. Thanks ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Error on executing CntToLedsAndRfm
Hi all, I tried to run CntToLedsAndRfm as mentioned in http://www.tinyos.net/tinyos-1.x/doc/tutorial/lesson5.html But I am getting the message as given below. 0: ERROR: Unable to create EEPROM backing store file. 0: ERROR: Unable to create anonymous EEPROM region. SIM: EEPROM system initialized. SIM: event queue initialized. SIM: Random seed is 606984 SIM: Initializing sockets SIM: Created server socket listening on port 10584. SIM: Created server socket listening on port 10585. SIM: eventAcceptThread running. SIM: Time for mote 0 initialized to 19285942. 0: BOOT: Scheduling for boot at 0:0:4.82148550. 0: Popping event for mote 0 with time 0:0:4.82148550. 0: Setting TOS_LOCAL_ADDRESS to 0 0: BOOT: Mote booting at time 0:0:4.82148550. 0: LEDS: initialized. 0: LEDS: Red off. 0: LEDS: Yellow off. 0: LEDS: Green off. 0: CLOCK: Setting clock rate to interval 231, scale 3 0: malloc data entry for clock event: 0xa05cb18 0: UART initialized. 0: RANDOM_LFSR initialized. 0: malloc channel mon event. 0: malloc Channel Mon event data. 0: AM Module initialized 0: CLOCK: Setting clock rate to interval 231, scale 3 0: malloc data entry for clock event: 0xa05cb90 0: UART started. SIM: commandReadThread running. 0: Popping event for mote 0 with time 0:0:4.82153550. 0: Setting TOS_LOCAL_ADDRESS to 0 0: RADIO: Channel Mon event handled for mote 0 at 0:0:4.82153550 with interval of 200. 0: RFM: Mote 0 got bit 0 0: Popping event for mote 0 with time 0:0:4.82158550. 0: Setting TOS_LOCAL_ADDRESS to 0 0: RADIO: Channel Mon event handled for mote 0 at 0:0:4.82158550 with interval of 200. 0: RFM: Mote 0 got bit 0 0: Popping event for mote 0 with time 0:0:4.82163550. 0: Setting TOS_LOCAL_ADDRESS to 0 0: RADIO: Channel Mon event handled for mote 0 at 0:0:4.82163550 with interval of 200. 0: RFM: Mote 0 got bit 0 0: Popping event for mote 0 with time 0:0:4.82168550. 0: Setting TOS_LOCAL_ADDRESS to 0 0: RADIO: Channel Mon event handled for mote 0 at 0:0:4.82168550 with interval of 200. 0: RFM: Mote 0 got bit 0 0: Popping event for mote 0 with time 0:0:4.82173550. 0: Setting TOS_LOCAL_ADDRESS to 0 CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS***___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TsyncC and Deluge
Hi, I want to measure time that Deluge T2 use for disseminating a new image. For this scope I need that motes are time syncronized so I can measure what I need. (Once motes are syncronized, BaseStation before disseminate -d command read current time and last mote that receiving image read current time immediatly after receiving image. The difference between this two times give me total time for disseminating an image) For syncronizing motes I need to include component of time syncronization into Deluge code. I chose component TsyncC as time syncronizing component (proposed from tinyos-2.x-contrib/iowa/T2. tsync). The problem is that Deluge (without component TsyncC) is: 32726 ROM 1239 RAM While component TsyncC is: 21748 ROM 912 RAM My motes are tmote sky (48KByte of ROM), when I include component TsyncC in Deluge I can't compile because I have an error: msp430-ld: address 0x111e8 of build/telosb/main.exe section .text is not within region text msp430-ld: section .vectors [ffe0 - ] overlaps section .text [4a00 - 000111e7] msp430-ld: build/telosb/main.exe: section .vectors lma 0xffe0 overlaps previous sections make: *** [exe0] Error 1 If I don't wrong, this error means that my application is too big, go over maximum size of my motes ROM (48Kbyte). How can I solve this problem? Thanks. Elisa ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Fw: error making Blink application .. fixed
After I sent this email, I located the information in the archives that I needed to fix this error. While Cygwin was not very cooperative, I finally was able to remove the old TinyOS tools then use the --ignoreos option to force the newer versions of these tools onto the system. The following is taken from the archive: rpms: avr-binutils-2.13.2.1-1 avr-gcc-3.3tinyos-1 avarice-2.0.20030825cvs-1 avr-insight-pre6.0cvs.tinyos-1.3 These are the old TinyOS tools. avr-binutils-2.15tinyos-3 avr-gcc-3.4.3-1 avr-libc-1.2.3-1 avr-insight-6.3-1 avarice-2.4-1 These are the new TinyOS tools. ... thank you David for this information. Calvin Bebermeyer [EMAIL PROTECTED] - Original Message - From: Calvin Bebermeyer To: tinyos-help@millennium.berkeley.edu Sent: Tuesday, April 08, 2008 11:41 PM Subject: [Tinyos-help] error making Blink application Unfortunately, I have had troubles getting TinyOS 2 to correctly run. I am getting this error: mkdir -p build/micaz compiling BlinkAppC to a micaz binary ncc -o build/micaz/main.exe -Os -finline-limit=10 -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -DIDENT_PROGRAM_NAME=\BlinkAppC\ -DIDENT_USER_ID=\calvin\ -DIDENT_HOSTNAME=\amd64\ -DIDENT_USER_HASH=0x5dd41d5bL -DIDENT_UNIX_TIME=0x47fc474cL -DIDENT_UID_HASH=0xf3703cd8L -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm In file included from /opt/tinyos-2.x/tos/system/TinySchedulerC.nc:41: In component `McuSleepC': /opt/tinyos-2.x/tos/chips/atm128/McuSleepC.nc: In function `McuSleep.sleep': /opt/tinyos-2.x/tos/chips/atm128/McuSleepC.nc:102: implicit declaration of function `pgm_read_byte' make: *** [exe0] Error 1 I have found some reference to an include problem referring to pgmspace.h being able to fix this problem but I am not certain how to include this file into the program. thanks for your assistance, Calvin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TsyncC and Deluge
I know this isn't really hugely helpful ... but what you'll have to do is use a less-complex time sync. Depending on the accuracy you are interested in (~1us, ~1ms, ~1s) maybe the recently-discussed time sync stuff in tinyos-devel will be more compact/useful? Or, if you can accept some error in the measurement you could transmit a time field that gets updated at each mote... e.g. mote 1 transmits with time=0 mote 2 starts a ms counter N2 on receiving this message mote 2 transmits the message with time=0 + t(N2) mote 3 starts a timer... ... last mote receives the time = sum(all the intermediate node's counters) which is the total number of counter ticks (ignoring skew between motes) from start to finish? This would result in some (~8ms ave error for micaz is quite likely) error for each hop but should give you an end to end time that isn't too far off depending on the accuracy required (depending how you transmit the time and when you start the counter you could be more accurate) Cheers, Ben -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: 09 April 2008 14:05 To: tinyos-help@millennium.berkeley.edu Subject: [Tinyos-help] TsyncC and Deluge Hi, I want to measure time that Deluge T2 use for disseminating a new image. For this scope I need that motes are time syncronized so I can measure what I need. (Once motes are syncronized, BaseStation before disseminate -d command read current time and last mote that receiving image read current time immediatly after receiving image. The difference between this two times give me total time for disseminating an image) For syncronizing motes I need to include component of time syncronization into Deluge code. I chose component TsyncC as time syncronizing component (proposed from tinyos-2.x-contrib/iowa/T2. tsync). The problem is that Deluge (without component TsyncC) is: 32726 ROM 1239 RAM While component TsyncC is: 21748 ROM 912 RAM My motes are tmote sky (48KByte of ROM), when I include component TsyncC in Deluge I can't compile because I have an error: msp430-ld: address 0x111e8 of build/telosb/main.exe section .text is not within region text msp430-ld: section .vectors [ffe0 - ] overlaps section .text [4a00 - 000111e7] msp430-ld: build/telosb/main.exe: section .vectors lma 0xffe0 overlaps previous sections make: *** [exe0] Error 1 If I don't wrong, this error means that my application is too big, go over maximum size of my motes ROM (48Kbyte). How can I solve this problem? Thanks. Elisa ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/t inyos-help *** Please consider the environment before printing this email. *** This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may not be divulged to any third party without the express permission of the originator. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thales Research Technology (UK) Limited. *** ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Sending msg type from pc
Hi, I have the problem, that for verification I have to send the same message I have received via Java from the motes back to the motes. This means I use the same message type. Problem is I can't forward the original message because I get a NullPointerException (This problem was send by someone else in the past and not answered). So I tried to save the data values I received and create a new message to send, but I still get the Nullpointeexception when using moteIF.send. Can anyone help? Thanks in advance Nicole Neureiter -- ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Sending msg type from pc
I'm just making things up because I haven't seen your code, but are you trying to send back the same message packet that you just received? My thought is that the packet is being deallocated before you send it. The solution would be to allocate your own packet, copy, and then send the copy. Maybe my answer is stupid enough that someone that knows what they are talking about will answer this time. Eric On Wed, Apr 9, 2008 at 9:52 AM, Nicole Neureiter [EMAIL PROTECTED] wrote: Hi, I have the problem, that for verification I have to send the same message I have received via Java from the motes back to the motes. This means I use the same message type. Problem is I can't forward the original message because I get a NullPointerException (This problem was send by someone else in the past and not answered). So I tried to save the data values I received and create a new message to send, but I still get the Nullpointeexception when using moteIF.send. Can anyone help? Thanks in advance Nicole Neureiter -- ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] msp430 platform bootstrap
Kami Amaterasu wrote: Also, I would like to try this app on a Telos B. Is there any way to debug an app on this platform with msp430-gdb (on Linux)? TI sells a USB debugging interface (MSP-FET430UIF) that can be used with the TelosB, and they include a proxy application that lets you use it with msp430-gdb on Cygwin and Linux. Unfortunately, you'll need to solder a JTAG connector onto the TelosB's JTAG header if you want to connect the debugging interface. Also note that the MSP-FET430UIF uses a 14-pin connector whereas the header on the TelosB is 8 pins, so you'll also need to buy/make an appropriate adapter. Greg Hackmann ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] SPI: Flash and Radio concurrency on Tmote sky
Hi to all,I've a question about the shared SPI bus between Radio and Flash modules on Tmote Sky:is there any problem if a node is writing to flash while another mote is sending a packet to it? Could the radio loss the packet if I do not use the Packet Link layer of TinyOs and setting retries threshold long enough? Does Low Power Listening Interface influence this concurrency? Thanks in advance,Flavio Inviato da Yahoo! Mail. La casella di posta intelligente. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Sending msg type from pc
With Java Garbage Collection, this, supposedly, can't happen. If you have an active reference (pointer) to an object, the object does not get 'deallocated'. NullPointer usually means just that, a reference that is zeroed out. So, we'd have to see the code and the actual error messages to make any progress. However these sort of things can often be solved using a debugger to poke around at the error location. Eclipse has a pretty good Java debugger if you don't have one handy. MS Eric Keller wrote: I'm just making things up because I haven't seen your code, but are you trying to send back the same message packet that you just received? My thought is that the packet is being deallocated before you send it. The solution would be to allocate your own packet, copy, and then send the copy. Maybe my answer is stupid enough that someone that knows what they are talking about will answer this time. Eric On Wed, Apr 9, 2008 at 9:52 AM, Nicole Neureiter [EMAIL PROTECTED] wrote: Hi, I have the problem, that for verification I have to send the same message I have received via Java from the motes back to the motes. This means I use the same message type. Problem is I can't forward the original message because I get a NullPointerException (This problem was send by someone else in the past and not answered). So I tried to save the data values I received and create a new message to send, but I still get the Nullpointeexception when using moteIF.send. Can anyone help? Thanks in advance Nicole Neureiter -- ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Platform: WinXP/Cygwin TinyOS version: 1.x, Boomerang Programmer: MIB510 Device(s): Mica2, MicaZ, Tmote Sensor board: homebrew ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] compiling with tossim
Hi, Please, I installed TinyOS 2 on windows using cygwin and when I compiled Blink app by this command: make micaz sim no error msg appeared (*** Successfully built micaz TOSSIM library.) But when I compile with this command make micaz sim-cygwin I had this error: Couldn't execute avr-gcc make: *** [exe0] Error 2 please help me thank you very much _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] What is the maximum timer interval?
Dear all, I have a question regarding the maximum timer interval for the TimerC. I am implementing a measurement which needs the long time interval. Do you know the maximum value of the time interval with MicaZ? TimerC uses the Timer which is 16 bits, so I guess that's a theoretical max. Can you confirm with that for me? If it is, do you know how to build another timer with longer time interval (perhaps as long as we want)? I am using TinyOS 1..1 .15, and MicaZ mote. Many thanks! Ruoshui ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Including/embedding C code in a nesC application
Hey all,
I want to use a precise timer so that I would like to use the Unix struct
timeval to get the time in microseconds
The small code bellow gets the time in microseconds
#include stdlib.h
#include sys/time.h
struct timeval tv;
unsigned long getTime(){
gettimeofday(tv, NULL)
return tv.tv_usec;
}
int main(){
printtf(Time in u_seconds: %3d\n, getTime());
return 0;
}
I want to embed or call the function getTime() in the nesC App. I created a .h
file and a .c file which contains the function getTime(). How should I modify
my Makefile to compile and link the c code with the nesC app?
COMPONENT = MyComponentC
BUILD_EXTRA_DEPS = utime.o
utime.o: utime.c
gcc -g -o -Wall -pedantic utime.c
include $(MAKERULES)
utime.h
#include stdlib.h
#include sys/time.h
struct timeval tv;
--
utime.c
--
#include utime.h
unsigned long getTime(){
gettimeofday(tv, NULL);
return tv.tv_usec;
}
.nc File
#include utime.h
module myModule{
}
When I try to compile I get several error massages.. one of them is
sys/time.h file not found
Thanks in advance...
_
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] one question about MultihopOscilloscope
Hi, I tried the following with one micaz mote coupled with mts300 sensor board: 1. I upload Oscilloscope application to this micaz+mts300. I can see the green light toggling. That is, whenevern one message is sent, led1 toggles; Everything is fine here. 2. Then I upload MultihopOscilloscope application to this micaz+mts300. I cannot even see the green light toggling. What are the possible errors? Thanks, Chris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Including/embedding C code in a nesC application
I think maybe you are doing that for doing simulation in TOSSIM.
By default, nesc does not include the the directories such as /sys..
You just need to add those directories in makefile: PFLAGS += -I...
An intermediate product of NESC compiler is app.c, that means all code are
tranlated into c code first.
On 4/9/08, antonio gonga [EMAIL PROTECTED] wrote:
Hey all,
I want to use a precise timer so that I would like to use the Unix struct
timeval to get the time in microseconds
The small code bellow gets the time in microseconds
#include stdlib.h
#include sys/time.h
struct timeval tv;
unsigned long getTime(){
gettimeofday(tv, NULL)
return tv.tv_usec;
}
int main(){
printtf(Time in u_seconds: %3d\n, getTime());
return 0;
}
I want to embed or call the function getTime() in the nesC App. I created
a .h file and a .c file which contains the function getTime(). How should I
modify my Makefile to compile and link the c code with the nesC app?
COMPONENT = MyComponentC
BUILD_EXTRA_DEPS = utime.o
utime.o: utime.c
gcc -g -o -Wall -pedantic utime.c
include $(MAKERULES)
utime.h
#include stdlib.h
#include sys/time.h
struct timeval tv;
--
utime.c
--
#include utime.h
unsigned long getTime(){
gettimeofday(tv, NULL);
return tv.tv_usec;
}
.nc File
#include utime.h
module myModule{
}
When I try to compile I get several error massages.. one of them is
sys/time.h file not found
Thanks in advance...
--
Invite your mail contacts to join your friends list with Windows Live
Spaces. It's easy! Try
it!http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
Renjie Huang
Sensorweb Research Laboratory
http://sensorweb.vancouver.wsu.edu/
Washington State University
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to send a message from PC to mote through UART?
Hi all,
I am trying to send control messages from PC to motes through UART. Since
the program run on PC was written in C#, I could not use the java code
directly. I tried to confirm the package form by modifying the TestSerial
application as follows:
/*TestWriteSerial.h*/
#ifndef TEST_WRITE_SERIAL_H
#define TEST_WRITE_SERIAL_H
typedef nx_struct test_serial_msg {
nx_uint8_t counter;
} test_serial_msg_t;
enum {
AM_TEST_SERIAL_MSG = 9,
};
#endif
/*TestWriteSerialAppC.nc*/
#include TestWriteSerial.h
configuration TestWriteSerialAppC {}
implementation {
components TestWriteSerialC as App, LedsC, MainC;
components SerialActiveMessageC as AM;
App.Boot - MainC.Boot;
App.Control - AM;
App.Receive - AM.Receive[AM_TEST_SERIAL_MSG];
App.Leds - LedsC;
}
/*TestWriteSerialC.nc*/
#include TestWriteSerial.h
module TestWriteSerialC {
uses {
interface SplitControl as Control;
interface Leds;
interface Boot;
interface Receive;
}
}
implementation {
event void Boot.booted() {
call Control.start();
}
event message_t* Receive.receive(message_t* bufPtr,
void* payload, uint8_t len) {
call Leds.led0On(); //indicate the mote have received a msg form UART
if (len != sizeof(test_serial_msg_t)) {return bufPtr;}
else {
test_serial_msg_t* rcm = (test_serial_msg_t*)payload;
if (rcm-counter 0x1) {
call Leds.led0On();
}
else {
call Leds.led0Off();
}
if (rcm-counter 0x2) {
call Leds.led1On();
}
else {
call Leds.led1Off();
}
if (rcm-counter 0x4) {
call Leds.led2On();
}
else {
call Leds.led2Off();
}
return bufPtr;
}
}
event void Control.startDone(error_t err) {
if (err == SUCCESS) {
}
}
event void Control.stopDone(error_t err) {}
}
And then I send a package 00 FF FF 00 00 01 00 09 05 from UART, but
nothing happened, even the red light that indicates having receive a message
from UART did not on at all. I modified the package as the the format of
UART receiving message from mote, that is 7E 45 00 FF FF 00 00 01 00 09 05
DD 1D 7E, the mote still did not work.
I have also tried to find how the java application send the data package,
but what I found in AbstractSource.java is a function that always
return TRUE ( writeSourcePacket(byte[] packet) ). So I did not know what
happened during the sending process.
Anyone has any idea?
Thanks in advance!
Jennifer
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to display sensor data using moteview
Hai, Thanks for your reply. That guide is very useful for me. Regards, Dhivya On Wed, Apr 9, 2008 at 9:00 PM, Giri Baleri [EMAIL PROTECTED] wrote: Please refer to the attached programming guide for step-by-step details. Regards, Giri -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Dhivya G *Sent:* Wednesday, April 09, 2008 1:50 AM *To:* Marco Antonio Lopez Trinidad *Cc:* TinyOS_Help *Subject:* Re: [Tinyos-help] How to display sensor data using moteview Hi, I programmed the mote(supposed to be the base station that is connected to mib520) with XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase. But still I am not able to display sensor data in pc. Regards, Dhivya. On Wed, Apr 9, 2008 at 1:48 PM, Marco Antonio Lopez Trinidad [EMAIL PROTECTED] wrote: What is the program you use? 1. TinyOS SerialForwarder uses the next port you use to connect the programmer. 2. MoteWorks applications suite recognises automatically the right ports to program (com_i) and inject or read packets (com_i+1). I hope it helps, --marco. Hi Anil, I am getting 2 ports(com5 and com6) while connecting MIB520 to pc. In step 2, I am programming my mote that is connected to Mib520. So while Programming I have to give lower port(com5). In step 5, I am getting data from sensors and have to display it in PC.So for communication part I have to use higher port(com6). This is wht I did earlier. I also tried your idea.But I am getting following error. Can not connect to Mote correctly. Please check your Mote. Regards, Dhivya On Wed, Apr 9, 2008 at 12:47 PM, Anil Karamchandani [EMAIL PROTECTED] wrote: Hi Dhivya, the port number should be the port through which your gateway device is connected to the PC. Usually the port number in step 2 and step 5 is the same. check for the port which is communicating with the sensor and the PC and give that port number .. hope this helps anil On Wed, Apr 9, 2008 at 12:34 PM, Dhivya G [EMAIL PROTECTED] wrote: Hai, I am using crossbow Professional kit consisting of Micaz motes,MIB520 programming board and MTS400 sensor board. I want to know whether I have to program Micaz mote(connected to mib520) to collect data from sensor using Moteview.If so how I have to program Micaz mote. I Connected one micaz mote to mib520 programming board and programmed it using moteconfig as follows: 1) In Moteview I clicked Tools-Program Motes 2)In MoteConfig window I clicked Settings-Interface Board. In Interface board settings window I selected MIB520 and changed com port to 5 (lower port)and clicked Apply. 3)Then I clicked select button under select file to be uploaded. I selected XMeshBase_2420_hp under C:\Program Files\Crossbow\MoteView\xmesh\micaz\XMeshBase 4)Then I clicked Program button. 5)After finishing program I clicked File-Connect to WSN. In that new window I selected MIB520 board and com6(higher port) and XMTS400 board. 6)After completing all these steps sensor data is not displaying in PC. If my steps are wrong means please correct me. -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Regards Anil Karamchandani -- G.Dhivya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] How to send a message from PC to mote through UART?
Li Jianfeng wrote: And then I send a package 00 FF FF 00 00 01 00 09 05 from UART, but nothing happened, even the red light that indicates having receive a message from UART did not on at all. I modified the package as the the format of UART receiving message from mote, that is 7E 45 00 FF FF 00 00 01 00 09 05 DD 1D 7E, the mote still did not work. You should read TEP 113 (http://www.tinyos.net/tinyos-2.x/doc/html/tep113.html). It gives the format of serial messages and describes the rules for delimiting and escaping packets. I have also tried to find how the java application send the data package, but what I found in AbstractSource.java is a function that always return TRUE ( writeSourcePacket(byte[] packet) ). So I did not know what happened during the sending process. The code for sending packets in the TinyOS serial format is in net.tinyos.packet.Packetizer. Greg Hackmann ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
