Re: [Tinyos-help] Ubuntu 9.10 + TinyOS 2.x VirtualBox Image + SBT80v2
Hi Wolfgang, I think that your problem is that the sample application was written for TinyOS 1.x and you are running TinyOS 2.x. Interfaces and general architecture have much evolved between TOS 1.x and TOS 2.x and some interfaces no longer exist or have been renamed/extended. Newer interfaces have also been added. I had a quick look at EasySen support website and it seems they also have TinyOS 2.x support at http://www.easysen.com/support/TinyOS_2/ and at the related documentation http://www.easysen.com/support/TinyOS_2/docs/Guide_to_TinyOS20_code_for_EasySen_SensorBoards.pdf Kind regards from Switzerland, Romain On Wed, Apr 20, 2011 at 8:31 PM, Wolfgang Zweimuller zweim...@uwm.edu wrote: Hello! I am an German speaking guy, who is currently in the US. I have to develop a software to get the acceleration data of this board: http://www.easysen.com/SBT80.htm I have an example code which should make this easy for me: http://www.easysen.com/support/SBT80v2/samplecode_SBT80v2/ I am using Virtual Box with the Ubuntu-Image from this site: http://systembash.com/content/ubuntos-ubuntu-9-10-tinyos-2-x-virtualbox-image/ --- But if I enter the command 'make tmote' it gives me this error message: --- mkdir -p build/telosb compiling MobileNode to a telosb binary ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DIDENT_APPNAME=\MobileNode\ -DIDENT_USERNAME=\wcu\ -DIDENT_HOSTNAME=\wcu-desktop\ -DIDENT_USERHASH=0xae794e66L -DIDENT_TIMESTAMP=0x4daf2189L -DIDENT_UIDHASH=0x4f1f5062L MobileNode.nc -lm In file included from MobileNode.nc:2: SBT80ADCmap.h:9: warning: implicit declaration of function `ASSOCIATE_ADC_CHANNEL' SBT80ADCmap.h:10: `INPUT_CHANNEL_A0' undeclared here (not in a function) SBT80ADCmap.h:11: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:12: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:12: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC0_PORT' not integer constant SBT80ADCmap.h:16: `INPUT_CHANNEL_A1' undeclared here (not in a function) SBT80ADCmap.h:17: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:18: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:18: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC1_PORT' not integer constant SBT80ADCmap.h:22: `INPUT_CHANNEL_A2' undeclared here (not in a function) SBT80ADCmap.h:23: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:24: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:24: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC2_PORT' not integer constant SBT80ADCmap.h:28: `INPUT_CHANNEL_A3' undeclared here (not in a function) SBT80ADCmap.h:29: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:30: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:30: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC3_PORT' not integer constant SBT80ADCmap.h:34: `INPUT_CHANNEL_A6' undeclared here (not in a function) SBT80ADCmap.h:35: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:36: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:36: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC6_PORT' not integer constant SBT80ADCmap.h:40: `INPUT_CHANNEL_A7' undeclared here (not in a function) SBT80ADCmap.h:41: `REFERENCE_VREFplus_AVss' undeclared here (not in a function) SBT80ADCmap.h:42: `REFVOLT_LEVEL_2_5' undeclared here (not in a function) SBT80ADCmap.h:42: enumerator value for `TOSH_ACTUAL_ADC_EXTERNAL_ADC7_PORT' not integer constant In component `MobileNode': MobileNode.nc:7: component Main not found In file included from MobileNode.nc:8: In component `MobileNodeM': MobileNodeM.nc:10: too few arguments to interface `SampleTimer' MobileNodeM.nc:11: too few arguments to interface `SwitchTimer' In file included from MobileNode.nc:8: MobileNodeM.nc:14: interface ADC not found MobileNodeM.nc:22: interface MSP430GeneralIO not found MobileNodeM.nc:25: interface ADCControl not found MobileNodeM.nc:27: interface SendMsg not found MobileNodeM.nc:36: syntax error before `msg' MobileNodeM.nc:42: syntax error before `StdControl' MobileNodeM.nc:57: warning: type defaults to `int' in declaration of `sampledChannelNo' MobileNodeM.nc:57: conflicting types for `sampledChannelNo' MobileNodeM.nc:35: previous declaration of `sampledChannelNo' MobileNodeM.nc:57: warning: data definition has no type or storage class MobileNodeM.nc:58: warning: type defaults to `int' in declaration of `sampleTime' MobileNodeM.nc:58: conflicting types for `sampleTime' MobileNodeM.nc:34:
[Tinyos-help] How to define dbg(X, fmt, args ...) since the printfUART.h not available to IRIS platform
Hi everyone! I want to use dbg() macro to print out some debug information. So I set CFLAG += DPRINTFUART_ENABLED. the dbg macro works fine on telsb platform, but when I want to use IRIS mote, and the PrintfUART.h was not available to IRIS platform. I find that the function printf() in lib/printf/printf.h work fine on IRIS mote. is there someone can told me how to use printf to define dbg(X, fmt, args ...) ? the example of dbg(X, fmt, args ...) is dbg( Boot, booted with ID : %i\n, TOS_NODE_ID); ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [tinyos-msp430] rfxlink for Telos
Hi Michiel, I think creating another platform is a very bad idea. I would like to use the fast SPI interface on both the shimmer2 and shimmer2r platforms, and possibly get the cc2420x driver working to improve the throughput. Do you think one needs to have a new platform for those as well? Miklos On Wed, Apr 20, 2011 at 6:32 PM, Michiel Konstapel m.konsta...@sownet.nl wrote: I will put together a telos-specific code that allows for choosing compile time whether a) SMCLK should be DCO or DCO/4 (default), and b) selecting the timer configurations (timerB-32khz timerA-micro being the default). Why compile time? I would think given a platform configuration it should just always be that way for the given platform. Certainly so for new platforms, but not for the telos. There's just too many applications that depend on the current cc2420 stack. So choosing the cc2420x stack must be a compile time option. If we assume a platform is hardware plus software (including configuration of said hardware), couldn't you just define a new platform (say, telosx) which has telosb (or similar) hardware, but the cc2420x radio stack, faster default DCO, etc.? That way, you don't break any old code and you're free to implement improvements on top of the old hardware. If people want the new features, they'd have to explicitly port over their app to the new platform, or at least check that their assumptions still hold when they type make telosx instead of make telosb. Michiel ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [TinyOS-Help]Does anyone know how many routing protocols are there in MoteWorks?
Hi everyone, I am now working on MoteWorks and IRIS motes. I want to find routing schemes for IRIS motes to join the network. But I only find one: MULTIHOPROUTER. Are there any other routing protocols in MoteWorks? Thanks very much! Xavier Zhong ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] oscilloscope make error
Hi Roberto, /usr/lib/ncc/nesc_nx.h:16:22: error: inttypes.h: No such file or directory You probably don't have the standard C library headers installed on you host... On a Debian/Ubuntu system, try sudo apt-get install build-essential from the command line or choose the build-essential package from your package management application (synaptic,...). If you are on another Linux distribution or on cygwin, find out how you can install the standard C library header files. Regards, Romain On Thu, Apr 21, 2011 at 11:38 AM, roberto pagliari rpagliari...@gmail.com wrote: Hi All, I have issues building the GUI for Oscilloscope application. My environment variables are the following bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $CLASSPATH /opt/tinyos-2.1.1/support/sdk/java/ bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $MAKERULES /opt/tinyos-2.1.1/support/make/Makerules bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $TOSROOT /opt/tinyos-2.1.1/ bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $TOSDIR /opt/tinyos-2.1.1/tos/ Did I forget to include something? Below is reported the error when issuing make command. bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ make mig -target=null -java-classname=OscilloscopeMsg java ../Oscilloscope.h oscilloscope -o OscilloscopeMsg.java /usr/lib/ncc/nesc_nx.h:16:22: error: inttypes.h: No such file or directory /usr/lib/ncc/nesc_nx.h:235: syntax error before `__nesc_ntoh_uint8' /usr/lib/ncc/nesc_nx.h:240: syntax error before `__nesc_hton_uint8' a lot of other similar lines here. SchedulerBasicP: `Scheduler.taskLoop' not implemented SchedulerBasicP: `Scheduler.bool' not implemented In C file: commandline: Scheduler `TinySchedulerC' has no scheduling interface named `TaskBasic' ../Oscilloscope.h:28: syntax error before `nx_uint16_t' ../Oscilloscope.h:28: warning: no semicolon at end of struct or union ../Oscilloscope.h:29: syntax error before `interval' ../Oscilloscope.h:30: syntax error before `id' ../Oscilloscope.h:31: syntax error before `count' ../Oscilloscope.h:32: syntax error before `readings' ../Oscilloscope.h:33: warning: data definition has no type or storage class failed to parse message file ../Oscilloscope.h make: *** [OscilloscopeMsg.java] Error 1 bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ ___ 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] [tinyos-msp430] rfxlink for Telos
That depends - if the change is backwards compatible, then it should be fine to change the existing platform, but I got the impression that since there is such a large body of code out there for the telosb, that significant changes cannot be made without the risk of breaking a lot of existing applications: Certainly so for new platforms, but not for the telos. There's just too many applications that depend on the current cc2420 stack. So choosing the cc2420x stack must be a compile time option. Of course, you can always #ifdef the change and maintain the old code, but that only scales up to a certain point, and without knowing the magic #defines to invoke, people would still get the old, presumably worse, behaviour/performance. Michiel -Original Message- From: mmar...@gmail.com on behalf of Miklos Maroti Sent: Thu 21/04/2011 10:50 To: Michiel Konstapel Cc: Janos Sallai; Eric Decker; Markus Becker; Peter A. Bigot; TinyOS Msp430; tinyos-help@millennium.berkeley.edu Subject: Re: [tinyos-msp430] [Tinyos-help] rfxlink for Telos Hi Michiel, I think creating another platform is a very bad idea. I would like to use the fast SPI interface on both the shimmer2 and shimmer2r platforms, and possibly get the cc2420x driver working to improve the throughput. Do you think one needs to have a new platform for those as well? Miklos On Wed, Apr 20, 2011 at 6:32 PM, Michiel Konstapel m.konsta...@sownet.nl wrote: I will put together a telos-specific code that allows for choosing compile time whether a) SMCLK should be DCO or DCO/4 (default), and b) selecting the timer configurations (timerB-32khz timerA-micro being the default). Why compile time? I would think given a platform configuration it should just always be that way for the given platform. Certainly so for new platforms, but not for the telos. There's just too many applications that depend on the current cc2420 stack. So choosing the cc2420x stack must be a compile time option. If we assume a platform is hardware plus software (including configuration of said hardware), couldn't you just define a new platform (say, telosx) which has telosb (or similar) hardware, but the cc2420x radio stack, faster default DCO, etc.? That way, you don't break any old code and you're free to implement improvements on top of the old hardware. If people want the new features, they'd have to explicitly port over their app to the new platform, or at least check that their assumptions still hold when they type make telosx instead of make telosb. Michiel ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with TelosB mote on Ubuntu 10.10
Hello, I am using a TelosB sensor mote for a college project. I was able to install TinyOS on Ubuntu 10.10 and install the Blink application onto the mote. However, since then, when I have tried to install anything, whether just reinstalling Blink, or a different example application, I get a wide variety of errors when I run make telosb reinstall They have included: Port not open [Errno 19] No such device [Errno 62] Timer expired [Errno 108] Cannot send after transport endpoint shutdown [Errno 5] Input/output error I have searched around a lot, and all I could find was one thread on this mailing list with a similar problem, in which the person was advised to just keep trying and it would work eventually. I have been attempting to load the program on and off since yesterday, and the variety of errors continue to occur. I have permission to write to the /dev/ttyUSB0 file which is listed, and I am not using a USB hub. Does anyone have any suggestions for what I could do, or where I could look? I have searched for information on the TelosB but all I could find was one 2-page PDF datasheet, which was not helpful. Thank you in advance, Eric Willisson ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] noinline attribute
Hello!
I'm working with Tmote Sky motes.
I'm using the external flash memory component: ConfigStorageC(VOLUME_ID). It
provides a interface called 'ConfigStorage'.
I've seen in a example code
(tinyos2.x\apps\tutorials\BlinkConfig\BlinkConfigC.nc) the event 'readDone' has
a attribute:
event void Config.readDone(storage_addr_t addr, void* buf, storage_len_t
len, error_t err) __attribute__((noinline)) {
...
}
What's the meaning of '__attribute__((noinline))' ? Is it strictly neccesary
to add it?
Thanks!
Regards,
Jose A.
╔══╗
║José A. Tarifa Galisteo
║
║ Estudiante Ingeniería de Telecomunicación
║ Escuela Superior de Ingenieros - U. Sevilla
║ http://alumno.us.es/j/jostargal/
╚══╝
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] oscilloscope make error
it worked, thanks! On Thu, Apr 21, 2011 at 4:42 AM, Romain Bornet bornet.r...@gmail.comwrote: Hi Roberto, /usr/lib/ncc/nesc_nx.h:16:22: error: inttypes.h: No such file or directory You probably don't have the standard C library headers installed on you host... On a Debian/Ubuntu system, try sudo apt-get install build-essential from the command line or choose the build-essential package from your package management application (synaptic,...). If you are on another Linux distribution or on cygwin, find out how you can install the standard C library header files. Regards, Romain On Thu, Apr 21, 2011 at 11:38 AM, roberto pagliari rpagliari...@gmail.com wrote: Hi All, I have issues building the GUI for Oscilloscope application. My environment variables are the following bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $CLASSPATH /opt/tinyos-2.1.1/support/sdk/java/ bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $MAKERULES /opt/tinyos-2.1.1/support/make/Makerules bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $TOSROOT /opt/tinyos-2.1.1/ bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ echo $TOSDIR /opt/tinyos-2.1.1/tos/ Did I forget to include something? Below is reported the error when issuing make command. bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ make mig -target=null -java-classname=OscilloscopeMsg java ../Oscilloscope.h oscilloscope -o OscilloscopeMsg.java /usr/lib/ncc/nesc_nx.h:16:22: error: inttypes.h: No such file or directory /usr/lib/ncc/nesc_nx.h:235: syntax error before `__nesc_ntoh_uint8' /usr/lib/ncc/nesc_nx.h:240: syntax error before `__nesc_hton_uint8' a lot of other similar lines here. SchedulerBasicP: `Scheduler.taskLoop' not implemented SchedulerBasicP: `Scheduler.bool' not implemented In C file: commandline: Scheduler `TinySchedulerC' has no scheduling interface named `TaskBasic' ../Oscilloscope.h:28: syntax error before `nx_uint16_t' ../Oscilloscope.h:28: warning: no semicolon at end of struct or union ../Oscilloscope.h:29: syntax error before `interval' ../Oscilloscope.h:30: syntax error before `id' ../Oscilloscope.h:31: syntax error before `count' ../Oscilloscope.h:32: syntax error before `readings' ../Oscilloscope.h:33: warning: data definition has no type or storage class failed to parse message file ../Oscilloscope.h make: *** [OscilloscopeMsg.java] Error 1 bob@bob-laptop:/opt/tinyos-2.1.1/apps/Oscilloscope/java$ ___ 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] Help Needed
On Wed, Apr 6, 2011 at 8:08 AM, ashish bhagat bhagat_kumar_ash...@yahoo.co.in wrote: Hi, I am working with TinyOS 2.x from a long time. 1. I have found the Timer interface as a non-premptive interface. In two way communication, a timer was set between the time the sender sends a packet and waits for the acknowledgement to be received. The sender is not able to receive the acknowledgement since the timer is non preemptive event and thus does not allow the mote to preempt in between to receive the packet. Is this conclusion correct. Or am I doing something wrong. If the conclusion is correct, what else can a use for check on timeout. 2. On Zigbee kit, I want the kit to have some ID, how can one associate the kit with these IDs. 3. The CTP protocol implemented does not work. Can you suggest the reason for the same. You should provide more details before someone can help you determine why CTP does not work. - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Collection Tree Protocol change root in runtime
On Fri, Apr 1, 2011 at 7:28 AM, 439...@uni-wuppertal.de wrote: Hi I'm using the collection tree protocol to collect data at one root mote in a quite small network of about 5 motes. Currently I'm simulating it in TOSSIM. The collection works fine, all data is received by the mote that is set as root. But since my network is supposed to be able to change the station that collects data, I want to change the root. So, at some time, the destined new root calls the setRoot command and the former base unsets itself shortly after. (they are comminicating via the DYMO protocol) But the problem is that the new base doesn't get data from all the other motes. The Topology is in a line, so if the new root is on the other end of the line, it only receives data from its neighbour. But if this mote is initially set as root it receives all data, so the topology is not faulty. So is the change of the root not possible using the ctp or am I doing something wrong? Any ideas? If you are collecting data at the root, tree protocols such as CTP might work better for you. CTP is known to work to some extent with mobile roots. - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Change MAC address
On Thu, Mar 31, 2011 at 3:34 AM, Ruben Rios ru...@lcc.uma.es wrote: Dear all, I am wondering whether it is possible to change the MAC address of the packets before sending them. In case it is possible, can you tell me where may I find the file/information to do it? This paper will point you in the right direction: http://www.eecs.umich.edu/eecs/about/articles/2010/dutta10amac.pdf - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] abt CTP
On Thu, Mar 31, 2011 at 12:55 AM, niraj nake nirajnak...@gmail.com wrote: Hello all, I hv a question regarding CTP. Is it possible to send the message from root to other nodes using multihop communication.? becoz in ctp every node send d msg to root... is the reverse true plz reply .. No. You cannot send message in the reverse direction using CTP. - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to make the BaseStation only send the payload of radio msg to uart?
I want to modify the BaseStation code, so that the modified basestation can
only send the payload of its received radio msg.
Payload means the second part (data) of message_t.
Which code has to be modified? Any help will be appreciated!
typedef nx_struct message_t {
nx_uint8_t header[sizeof(message_header_t)];
nx_uint8_t data[TOSH_DATA_LENGTH];
nx_uint8_t footer[sizeof(message_footer_t)];
nx_uint8_t metadata[sizeof(message_metadata_t)];
} message_t;
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] [tinyos-msp430] rfxlink for Telos
hi miklos, in the meantime, on shimmers you can certainly wire in FastClockC, which uses the platform's 8mhz xt2 and runs smclk at 4mhz, which will divert data bottlenecks away from the spi bus... $0.02, steve On 04/21/2011 04:50 AM, Miklos Maroti wrote: Hi Michiel, I think creating another platform is a very bad idea. I would like to use the fast SPI interface on both the shimmer2 and shimmer2r platforms, and possibly get the cc2420x driver working to improve the throughput. Do you think one needs to have a new platform for those as well? Miklos On Wed, Apr 20, 2011 at 6:32 PM, Michiel Konstapel m.konsta...@sownet.nl wrote: I will put together a telos-specific code that allows for choosing compile time whether a) SMCLK should be DCO or DCO/4 (default), and b) selecting the timer configurations (timerB-32khz timerA-micro being the default). Why compile time? I would think given a platform configuration it should just always be that way for the given platform. Certainly so for new platforms, but not for the telos. There's just too many applications that depend on the current cc2420 stack. So choosing the cc2420x stack must be a compile time option. If we assume a platform is hardware plus software (including configuration of said hardware), couldn't you just define a new platform (say, telosx) which has telosb (or similar) hardware, but the cc2420x radio stack, faster default DCO, etc.? That way, you don't break any old code and you're free to implement improvements on top of the old hardware. If people want the new features, they'd have to explicitly port over their app to the new platform, or at least check that their assumptions still hold when they type make telosx instead of make telosb. Michiel ___ tinyos-msp430 mailing list tinyos-msp...@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-msp430 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [Researchers] 14th ACM* MSWiM 2011 - Miami Beach, Oct31-Nov04, 2011.
Apologies if you receive multiple postings - Call for Papers ACM* MSWiM 2011 14th ACM* International Conference on Modeling Analysis and Simulation of Wireless and Mobile Systems October 31 - November 4, 2011, Miami, USA http://mswimconf.com/2011/ Submission deadline: May 15, 2011 [*ACM Sponsorship pending upon Approval] Note: Extended versions of selected papers will be considered for publication in a special issue of Computer Communications. MSWiM is an international forum dedicated to high level discussion of Wireless and Mobile systems, networks, algorithms and applications, with an emphasis on rigorous performance evaluation. MSWiM is a highly selective conference with a long track record of publishing innovative ideas and breakthroughs. Authors are encouraged to submit full papers presenting new research related to the theory or practice of all aspects of modeling, analysis and simulation of mobile and wireless systems. Submitted papers must not have been published elsewhere nor currently be under review by another conference or journal. -- Topics of Interests -- Papers related to wireless and mobile network Modeling, Analysis, Design, and Simulation are solicited on, but not limited to, the following topics in mobile and wireless systems: * Performance evaluation and modeling * Analytical Models * Simulation languages and tools for wireless systems * Wireless measurements tools and experiences * Formal methods for analysis of wireless systems * Correctness, survivability and reliability evaluation * Mobility modeling and management * Models and protocols for cognitive radio networks * Models and protocols for autonomic, or self-* networks * Capacity, coverage and connectivity modeling and analysis * Wireless network algorithms and protocols * Wireless PANs, LANs * Ad hoc networks * Sensor and actuator networks * Vehicular ad hoc networks * Integration of wired and wireless systems * Pervasive computing and emerging models * Wireless multimedia systems * QoS provisioning in wireless and mobile networks * Security and privacy of mobile/wireless systems * Algorithms and protocols for energy-efficiency and power control * Mobile applications, system software and algorithms * RF channel modeling and analysis * Design methodologies, tools, prototype and testbeds * Parallel and distributed simulation of wireless systems -- Organizing Commitee: -- General Chair: Ahmed Helmy (University of Florida, USA) TPC Co-Chairs: Bjorn Landfeldt (The University of Sydney, Australia) Luciano Bononi (University of Bologna, Italy) - Paper Submission, Publication and Important Dates: - High-quality original papers are solicited. Papers must be unpublished and must not be submitted for publication elsewhere. All papers will be reviewed by Technical Program Committee members and other experts active in the field to ensure high quality and relevance to the conference. Short papers will be included in the technical program to complement mature results and foster discussion and exchange of novel ideas at an early stage. Accepted papers will appear in the conference proceedings to be published by ACM Press. Extended versions of selected papers will be considered for publication in a special issue of Computer Communications. Submission Deadline: May 15, 2011 Notification of Acceptance: July 15, 2011 Conference Dates: October 31 - November 04, 2011 For more information about the conference, organizing committee, submission instructions, and venue please see the conference website: http://mswimconf.com/2011/ - Profa Dra Mirela Sechi Moretti Annoni Notare http://lattes.cnpq.br/8224632340074096 mir...@ieee.org USJ – Sao Jose Municipal University www.usj.edu.br UFSC - Distributed Mobile Computing Network Security CNPq Research Group (co-leader) http://dgp.cnpq.br/?grupo=00431033AKW5DM IEEE Latin America Transactions, Editor-in-chief http://www.ewh.ieee.org/reg/9/etrans ___ Researchers mailing list research...@mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/researchers ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu
