[Tinyos-help] TOSSIM interface and top view
Hello all, I would like to add multiple channel capabilities to TOSSIM, but I don't know how to modify the TOSSIM code. Is there documentation for TOSSIM for TinyOS2.0? I found a paper for TinyOS 1.0, but was wondering if there is any difference between the two. I found a multiple channel implementation for TinyOS 1.0 and I would like to know what it takes to get it to work on TinyOS 2.0. If someone could please send me some references or tips, I would appreciate it. Thank you, Ali ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] RSSI with tinyos-1.x and mica2
Hi,I am using the mica2 motes with tinyos-1.x. I want measure the RSSI value at the receiver. My motes emit at 433MHz. From the datasheets I have been reading I think that everytime a packet is received the following should be done:-read the ADC_Count value from chan[7] of the ADC and use it to obtain Vbatt in: Vbatt= Vref x ADC_FS / ADC_Count-read the ADC_Count value from chan[0] of the ADC and use it to obtain Vrssi in: Vrssi= Vbatt x ADC_Count / ADC_FS-in the end obtain the RSSI value in dBm in this way: RSSI (dBm)=-51.3 x Vrssi - 49.2Is this process correct? If so, is there a way to make the calculation of the RSSI (dBm) on the mote? And last can I assume the RSSI value computed to be the received power at the receiver or there is a conversion I need to do? Thanks in advance,Giacomo ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Help programming runaway mote (should be easy)
Will u please tell me how to run a sample file and where to write code ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Need advices and suggestions for hardware selection!
Hello All! I am new to WSN (Wireless Sensor Network). I am planning to do a project based on WSN. I already checked hardware for WSN but i didn't know how to choose hardware for my project... What i want to do is designing a light-weighted access control mechanism in a sensor node or base station. i think it is possible to write a program in there... So base on my work, which hardware will suit to write a program? I am interested to buy a Lotus mote, but it is quite expensive.. I also interested in MICAz and IR*IS*0 but i didn't know how to choose from these two because both of them have advantage over each other llike more memory space in IRIS and hardware security (AES-128) is provided in MICAz.. So i don't know, how to decide it. Are there any major problems to write a program in MICAz, IRIS and Lotus or any sensor node? If all of you have any idea and solution based on my work, you are more than welcome to give me advices, ideas and suggestions.. thanks in advance! regards pho thar ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] RSSI with tinyos-1.x and mica2
Here's the battery section right out of the MPR/MIB User’s Manual: -- 6.4 MICA2 Battery Voltage Monitor The MICA2 units have an accurate voltage reference that can be used to measure battery voltage (Vbatt). Since the eight-channel, ATMega128L ADC uses the battery voltage as a full scale reference, the ADC full scale voltage value changes as the battery voltage changes. In order to calibrate the battery voltage a precision external voltage reference is required. The MICA2 uses an LM4041 (Mfg: National Semiconductor) 1.223 V reference (Vref) attached to ADC channel 7. NOTE: ADC channel 7 is also used for JTAG debugging on the Atmega128 processor. MICA2s and MICA2DOTs ship with the JTAG fuse enabled. When this fuse is enabled the input impedance of channel 7 is lowered which affects the voltage reference measurement. The fuse must be disabled if ADC channel 7 is used. See below for information on setting ATMega128L fuses. To compute the battery voltage: 1. Set the BAT_MON processor pin (PA5/AD5) to HI. 2. Program the application code to measure ADC Channel 7. 3. Compute battery voltage, Vbatt, from Channel 7’s data by: Vbatt = Vref × ADC_ FS ADC_Count where: Vbatt = Battery voltage ADC_FS = 1024 Vref = External voltage reference = 1.223 V ADC_Count = Data from the ADC measurement of Channel 7 -- So it looks like you have it mostly right. And, yes, the final result is the power at the receiver. Make sure you notice that the Battery Voltage calculation is inverted from what you'd expect: Full-Scale/Count because what you are measuring is a fixed voltage using the battery as the ADC reference...It does actually work once you puzzle it out... I think you can probably ignore the NOTE about Jtag and maybe just add a fudge factor to the battery calculation. Or even just ignore the whole battery thing and use 3.0... Also, if you are just measuring the RSSI of received messages, a measurement is appended to each message in TOS_Msg.strength. However I forget if this is the raw count from ADC-0 or if it has been massaged into Vrssi or even RSSI. Searching the radio code for "strength" should elucidate this. Note that floating point calculations are rather costly as they are done in software so you might want to use some other methodology, or just the raw Vrssi... MS giacomo_gioacch...@libero.it wrote: > Hi, > > I am using the mica2 motes with tinyos-1.x. I want measure the RSSI > value at the receiver. My motes emit at 433MHz. From the datasheets I > have been reading I think that everytime a packet is received the > following should be done: > > -read the ADC_Count value from chan[7] of the ADC and use it to obtain > Vbatt in: Vbatt= Vref x ADC_FS / ADC_Count > > -read the ADC_Count value from chan[0] of the ADC and use it to obtain > Vrssi in: Vrssi= Vbatt x ADC_Count / ADC_FS > > -in the end obtain the RSSI value in dBm in this way: RSSI (dBm)=-51.3 x > Vrssi - 49.2 > > Is this process correct? If so, is there a way to make the calculation > of the RSSI (dBm) on the mote? And last can I assume the RSSI value > computed to be the received power at the receiver or there is a > conversion I need to do? > > Thanks in advance, > > Giacomo > > > > > > > ___ > 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] Error compiling TestSerial
Hi Varun,
It seems your CLASSPATH variable contains
/opt/tinyos-2.1.1/support/sdk/java instead of
/opt/tinyos-2.1.1/support/sdk/java/tinyos.jar
Andris
On Mon, Mar 5, 2012 at 3:47 PM, Varun Agrawal wrote:
> When I try to make the TestSerial application I get the following output:
>
> ubuntos@ubuntu:~/TinyOS/TestSerial$ make micaz sim
> mkdir -p simbuild/micaz
> javac -target 1.4 -source 1.4 *.java
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/message/MessageListener.java:52:
> error while writing net.tinyos.message.MessageListener:
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/message/MessageListener.class
> (Permission denied)
> public interface MessageListener {
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/message/Sender.java:95: cannot
> find symbol
> symbol : variable Serial
> location: class net.tinyos.message.Sender
> fullPacket[0] = Serial.TOS_SERIAL_ACTIVE_MESSAGE_ID;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/message/Receiver.java:166:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.message.Receiver
> if (packet[0] != Serial.TOS_SERIAL_ACTIVE_MESSAGE_ID)
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:85:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int SYNC_BYTE = Serial.HDLC_FLAG_BYTE;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:87:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int ESCAPE_BYTE = Serial.HDLC_CTLESC_BYTE;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:93:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int P_ACK = Serial.SERIAL_PROTO_ACK;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:95:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int P_PACKET_ACK = Serial.SERIAL_PROTO_PACKET_ACK;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:97:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int P_PACKET_NO_ACK = Serial.SERIAL_PROTO_PACKET_NOACK;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:99:
> cannot find symbol
> symbol : variable Serial
> location: class net.tinyos.packet.Packetizer
> final static int P_UNKNOWN = Serial.SERIAL_PROTO_PACKET_UNKNOWN;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:334:
> possible loss of precision
> found : int
> required: byte
> escaped[escapePtr++] = SYNC_BYTE;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:345:
> possible loss of precision
> found : int
> required: byte
> escaped[escapePtr++] = ESCAPE_BYTE;
> ^
> /opt/tinyos-2.1.1/support/sdk/java/net/tinyos/packet/Packetizer.java:353:
> possible loss of precision
> found : int
> required: byte
> escaped[escapePtr++] = SYNC_BYTE;
> ^
> 12 errors
> make: *** [TestSerial.class] Error 1
>
>
>
>
> Earlier I was also getting the SerialPacket symbol not found error but that
> was fixed by downloading and copying the SerialPAcket.java file to the
> required directory.
>
> Any help?
> --
> Yours faithfully,
> Varun Agrawal
>
> B.Tech-III
> Computer Science and Engineering
> National Institute of Technology
> Surat, India.
> About Me
> computerCalledVarun()
>
>
> ___
> 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] Need advices and suggestions for hardware selection!
Hello, The question is not trivial. First of all you need to have your specifications clear. The most critical are usually RAM size, processing power, consumption, price, portability to your preferred operating system and good development tools (reliable toolchain and debugging). Cheers! Sergio On Tue, Mar 6, 2012 at 4:38 PM, pho thar wrote: > Hello All! > > I am new to WSN (Wireless Sensor Network). I am planning to do a project > based on WSN. I already checked hardware for WSN but i didn't know how to > choose hardware for my project... > What i want to do is designing a light-weighted access control mechanism > in a sensor node or base station. i think it is possible to write a program > in there... > > So base on my work, which hardware will suit to write a program? > > I am interested to buy a Lotus mote, but it is quite expensive.. I also > interested in MICAz and IR*IS*0 but i didn't know how to choose from > these two because both of them have advantage over each other llike more > memory space in IRIS and hardware security (AES-128) is provided in MICAz.. > So i don't know, how to decide it. > > Are there any major problems to write a program in MICAz, IRIS and Lotus > or any sensor node? > > If all of you have any idea and solution based on my work, you are more > than welcome to give me advices, ideas and suggestions.. > > thanks in advance! > regards > pho thar > ___ > 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] Pro-active (table-driven) routing
an implementation for wireless sensor node will also be useful -- View this message in context: http://old.nabble.com/Pro-active-%28table-driven%29-routing-tp33391764p33451979.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] [Researchers] 16th IEEE/ACM* International Symposium onDistributedSimulation and Real Time Applications, Dublin, 25-27/10/2012.
Please accept our apologies if you have received multiple copies. Call for Papers - DS-RT 2012 16th IEEE/ACM* International Symposium on Distributed Simulation and Real Time Applications http://ds-rt.com/2012/ October 25-27, 2012 Dublin, Ireland * IEEE/ACM pending approval *** The Symposium *** In its sixteenth year, the 2012 IEEE/ACM International Symposium on Distributed Simulation and Real Time Applications (DS-RT 2012) will take place in Dublin, Ireland. DS-RT 2012 serves as a forum for simulationists from academia, industry and research labs, for presenting recent research results in Distributed Simulation and Real Time Applications. DS-RT 2012 targets the growing overlap between large distributed simulations and real time applications, such as collaborative virtual environments, pervasive and ubiquitous application scenarios, motor-, controller-, sensor- and actuator systems. The conference features prominent invited speakers as well as papers by top researchers in the field. DS-RT 2012 will include contributed technical papers, invited papers, and panel discussions. The proceedings will be published by IEEE-CS press. *** Call for Papers *** DS-RT provides an international forum for the discussion and presentation of original ideas, recent results and achievements by researchers, students, and systems developers on issues and challenges related to distributed simulation and real time applications. Authors are encouraged to submit both theoretical and practical results of significance. Demonstration of new tools/applications is very desirable. The scope of the symposium includes, but is not limited to: o Paradigms, Methodology and Software Architectures for Large Scale Distributed and Real-Time Simulations (e.g. Parallel and Distributed Simulation, Multi-Agent Based Distributed Simulation, HLA/RTI, Web, Grid and cloud based Simulation, hardware-software co-design for extreme scale simulations) o Paradigms, Modelling, Architecture and Environments for Large Scale Real-time Systems and Concurrent Systems with hard and soft Real-Time Contstraints o Non-functional Properties of Distributed Simulation and Real-Time Systems (e.g. Dependability, Availability, Reliability, Maintainability, Safety, Security, Trustworthiness, QoS) o Theoretical Foundations of Large Scale Real-Time and Simulation Models (e.g. Event Systems, Causality, Space-Time Models, Notions of Time, Discrete and Continuous Systems, Simulator Coordination) o Simulation Studies at Large and Very Large Scale (e.g. Industrial, Commercial, Ecological and Environmental, Societal, Power and Energy, Pervasive and Ubiquitous Computing Systems) o Performance and Validation of Large Scale and Distributed Simulations (e.g., benchmarking and analytical results, empirical studies DIS, HLA/RTI studies; o Languages and Tools, Development Environments, Data Interfaces, Network Protocols and Model Repositiories that address Very Large Simulations o Data Management and Distribution Issues, Interest Management, Semantic Modeling, Multi-resolution Modeling, Dead-Reckoning Mechanisms o Pervasive and Ubiquitous Computing Architectures and Applications that involve Simulations and/or adhere to Real-Time Constraints o Simulation based Virtual Environments and Mixed Reality Systems (e.g. Interactive Virtual Reality, Human Communication through Immersive Environments) o Collaborative Virtual and Augmented Reality, Shared Interaction Spaces, Telepresence Systems and Shared Workspaces, 3D Video and Acoustic Reconstruction, Shared Object Manipulation o Serious Gaming and Massive Multiplayer Online Games (MMOG) applications, architectures and scalability issues. o Visual Interactive Simulation Environments (e.g., Generic Animation, Visual Interactive Modeling, Interactive Computer Based Training and Learning; Scientific Visualization; High-End Computer Graphics; o Design Issues, Interaction Designs, Human Comuter Interaction Issues raised by Large Scale DS-RT Systems o Media Convergence (e.g. New Technologies, Media Theory, Real-Time considerations of Multi Modality, etc.) o Innovative Styles of Interactions with Large Scale DS-RT Systems (e.g. Implicit, Situative and Attentive Interaction, Tangible Interaction, Embedded Interaction, etc.) o Technologies for Living Labs (e.g. Mirror World Simulation, Interoperability, Large Scale Multi Sensor Networks, Global Wireless Communication, Multi Stakeholder Understanding and Innovation) o Environmental and Emerging Simulation Challenges (e.g. Growth of Human Population, Climate Change, CO2, Health Care, Ecosystems, Sustainable Development, Water and Energy Supply, Human Mobility, Air Traffic, World Stock Markets, Food Supply Chains, Megacities, Smart Cities, Disaster Planning, etc.) *** Important Dates Paper Submission Deadline: May 15, 2012 Short pape
