Hello dear
I have TinyOS 2.1.2 installed on Ubuntu 16.04 correctly. Even when I run $
make telosb it does not return any errors.
But when I try to use the TOSSIM simulator, through $ make telosb, there are
several errors, as follows below the terminal:
$ make telosb sim
mkdir -p simbuild/tel
Hi James,
This error occurs with micaz too.
@note:~/tinyos-main/apps/Blink$ make micaz sim
mkdir -p simbuild/micaz
make: python2.72-config: Comando não encontrado
make: python2.72-config: Comando não encontrado
make: python2.72-config: Comando não encontrado
placing object files in simbuild/mic
Hello Eric,
I'm using TinyOS 2.1.2, openjdk version 1.8.0_111 and Python 2.7.12 on
Ubuntu 16.04 x64.
If you know a more stable previous version, please tell me, because I am new
to TinyOS and I do not know your options well.
I believe the problem may be in the Python variable that is not being
Thanks to Matthew Bradbury that with just one line altered in the file
sim.extra, solved my problem and some more people.
Thank you Matthew.
So that you still have the same problem, just change the line:
PYTHON_VERSION ?= $(shell python --version 2>&1 | sed 's/Python
2\.\([0-9]\)\.[0-9]+\{0,1\}/
Hello friends,
I have a problem with the nesC file.
I create 8 sensors that start in slot 0 and their time window slides to slot
183 (using Block Design [183,14,1].
Of these 183 slots, 14 are active and should send a packet (denominated in
code as padrao [X]).
My problem is that it activates the r
Hello friends,
I'm having a hard time making a sensor wait a while before running a
function.
event void TimerSlot.fired() {
slot=slot%numslots;
* if (padrao[slot]) *{
call AMControl.start(); //Call to start the radio
dbg("teste","SLOT_ATIVO: No %hu no slot [%hu] com tempo=%l
Hello friends,
I would like a help on TinyOS / TOSSIM how to setup the time slot in a
simulation.
I set up my time window with 183 slots, with only 14 active.
I have a call to function call type TimerSlot.startPeriodic (2); Which
checks which slot is in the loop and turns it on or off.
My question
Hi James, how are you?
Repair the code below:
include "Timer.h"
module testeC @safe() {
uses {
interface Boot;
interface Receive;
interface AMSend;
interface Timer as TimerSlot;
interface LocalTime as Clock;
interface SplitControl as AMControl;
interface Packet;
Hello friends,
I'm having trouble sending a data packet in the same time slot as a beacon
on TOSSIM.
I have a small implementation that activates 8 nodes with 183 time slots.
Being that of these 183, 14 slots are active and at the moment they send a
beacon of synchronization to the others. Until t
Hello friends, I was able to have my TOSSIM implementation send the package
in a certain time and receive this package (data) correctly. Apparently, it
compiles TOSSIM correctly, but I still get the warning:
Someone could tell me the reason, or how to adjust these "errors."
The warning is:
nesc1:
Hello friends,
After staying until dawn yesterday trying to understand the differences, I
decided to ask for help.
I have 4 files: gera-topologia.txt, linkagain1.txt and linkagain2.txt.
The file-topology file was taken from the TOSSIM tutorial itself and is
exactly the same as that used by a teach
Hello friends,
Again I came across a doubt. I inserted in my implementation the use of ACK.
In the function
AMSend.sendDone (message_t * bufPtr, error_t error) {
if (call PacketAcknowledgements.wasAcked (bufPtr)) {
dbg ("test", "SEND_ACK \ n");
}
}
And it's apparently working c
Hello friends,
I need some help.
I need to store in a variable (nodeid) the source node of a package, so that
this variable does not receive new value with each hop.
In summary, if a tree of height 3, where node 0 is the root, node 2 child of
the root and parent of node 7, need that when a packet
Actually nodeid is declared in the booted function, as nodeid = TOS_NODE_ID.
What I have to do is that when the startDone function is run, it loads the
varialvel nodeid with the value of the node and does not change.
What is happening now is that starDone executes on node 24 (for example) and
the
262/5000
Hello friends,
The old problems were solved, thanks to everyone's goodwill, especially
James Allan who helped me a lot.
Now I have encountered a problem that I believe may be a TOSSIM bug.
Notice that I run a simple script with the following two lines:
make micaz sim
python ${1}.py outpu
Hello friends,
I am having a question, my implementation is creating 32 nodes, and each
respects a time cycle of x slots, being only 1.03% of these assets (duty
cycle). I am using a t.runNextEvent () = 2200 or 8 and
TimerSlot.startPeriodic (11).
When I run the simulation in TOSSIM with
Hello friends,
I am having a question, my implementation is creating 32 nodes, and each
respects a time cycle of x slots, being only 1.03% of these assets (duty
cycle). I am using a t.runNextEvent () = 2200 or 8 and
TimerSlot.startPeriodic (11).
When I run the simulation in TOSSIM with
Hello friends,
after some time I returned to use the Tossim and already I came across a
difficulty. Is it possible to define the life of a package (TTL)? What
should I insert into my code to set the size of the package?
I believe I have the following problem: my topology has 36 nodes in GRID,
being
18 matches
Mail list logo
