salam, hello,
i think this link will help you
http://docs.tinyos.net/tinywiki/index.php/Running_a_XubunTOS_Virtual_Machine_Image
_in_VMware_Player
good luck and best regards
meriam
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https
hello,
can you plz help me !!
when i exe mviz i dont get the window with the topology of the network
so what do you think?
thank you in advance
meriam
--
View this message in context:
http://tinyos-help.10906.n7.nabble.com/Why-some-wrong-mote-join-the-MViz-example-network-tp16951p22679.ht
hello,
i just want to ask you some questions cause i m really getting confused and
cant figure this out.
i am working with AODV protocol, and i want to visualize the topology network
and msg transferring mechanism
so
1) is there a tool that visualize my protocol working
2) MViz is it just a vi
Actually, no. The old XubunTOS images are hideously outdated. TinyOS 2.0
or TinyOS 2.1. Also a very old version of Xbuntos as well.
The original poster asked explicitly for installing TinyOS (I assume the
current 2.1.2 release) on 12.04.
The Xbuntos VM image does neither of these things. An
Hi all
I have an issue with TKN154 implementation of the IEEE 802.15.4 standard. I am
trying to perform an energy detection scan with a PAN coordinator device over
four pre-defined channels (e.g., 16, 19, 21, and 26) for later, select the one
which best fits some application requirements. The pr
Hi everybody,
when I compile a simple program with 'make mica2' , I get
Unknown target mica2
/tosn targets for TinyOS directory /opt/tinyos-2.x
and the specified include directories are:
none.
make: *** [exe0] Error 2
I tried
export TOSDIR=opt/tinyos-2.x/tos/
which did not help either.
as my
edit: I am using cygwin.
cheers,
tim
--
View this message in context:
http://tinyos-help.10906.n7.nabble.com/Unknown-target-mica2-but-the-tosdir-seems-to-be-set-correctly-tp22683p22684.html
Sent from the TinyOS - Help mailing list archive at Nabble.com.
Hi David,
MLME_SCAN.request() returns a parameter ieee154_status_t, can you take
a look at its value to check whether it is IEEE154_SUCCESS (only in
this case the confirm event will be signalled).
Jan
On Thu, Feb 21, 2013 at 11:31 AM, David Rodenas wrote:
> Hi all
>
> I have an issue with TKN15
shows that the FCS is OK. Is there some other filter which is
ausing the packet to be rejected.
Thanks,
ou
- next part --
n HTML attachment was scrubbed...
RL:
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130221/d10d5d4a/attachment-0001.htm
-
Hi Jan
I solved the problem. This was due to the fact of including
PANDescriptorListNumEntries and PANDescriptorList variables when the MLME_SCAN
is requested. I've not dedicated time in examining this problem more in detail,
which a priori, I thing this should not occur. But you are the develop
If you have serial working, then you can define RADIO_DEBUG_MESSAGES
which will print out the received messages via the DiagMsg protocol.
You should connect your mote to a PC, and there run the "java
net.tinyos.utils.DiagMsg" application. Take a look at
RF230DriverLayerP.nc line 677, you can also p
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
wrote:
> Hi Miklos,
> Thank you very much. I do not even get the interrupt from the radio if i use
> RX_AACK mode. If use the basic mode , it works fine.
> I used a TI (CC2430) sniffer and was able to see teh messages being. The
> data i i
Hi Miklos,
Thanks for the quick response.
i made the following changes to support 64 bit addressing
/*** File Ieee154PacketLayer.h*/
typedef nx_struct ieee154_header_t
{
nxle_uint16_t fcf;
nxle_uint8_t dsn;
nxle_uint16_t destpan;
#ifdef RF230_EXTENDED_AD
Looks good! Let me know if you run into problems. If it works, then I
will merge it back to the mainline. Miklos
On Thu, Feb 21, 2013 at 10:54 AM, Roadstar Runner
wrote:
> Hi Miklos,
> Thanks for the quick response.
> i made the following changes to support 64 bit addressing
>
> /***
So far no luck :-(
I was under the impression that this is all i should need. Are there any
other quirks in the RF230 that might be causing a problem?
On Thu, Feb 21, 2013 at 11:57 AM, Miklos Maroti wrote:
> Looks good! Let me know if you run into problems. If it works, then I
> will merge it ba
Ok, I have started to look into this. Do you want to use the
ActiveMessageC framework, right? How do you want to eventually handle
the 64-bit address vs the 16-bit address defined in AM.h? Maybe we
should change am_addr_t to 64-bit? Miklos
On Thu, Feb 21, 2013 at 10:59 AM, Roadstar Runner
wrote:
Hi,
Yes i would like to use the ActiveMessageC framework.
I hope that eventually a define in the makefile will upgrade the am address
to a 64 bit version .
Thanks,
On Thu, Feb 21, 2013 at 12:15 PM, Miklos Maroti wrote:
> Ok, I have started to look into this. Do you want to use the
> ActiveMes
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
wrote:
> Hi,
> Yes i would like to use the ActiveMessageC framework.
> I hope that eventually a define in the makefile will upgrade the am address
> to a 64 bit version .
> Thanks,
>
>
>
>
Take a look at this tree:
https://github.com/mmaroti/tinyos-main/commits/rfxlink-64bit
You should try it out with software acknowledgements, so RX_AACK
should be turned off. You should define "RFXLINK_64BIT_ADDR" macro.
Let me know how far you get with this. Once the software ack works,
then we c
I used the broadcast address 0x since the 802.15.4 spec
specifies the boradcast address as 0x
I did not use the ULL postfix cos i was just using the lower 2 bytes of
the address
On Thu, Feb 21, 2013 at 12:25 PM, Miklos Maroti wrote:
> Is the broadcast address 0xFF
Thanks, I did not know. I have updated the git repo. Miklos
On Thu, Feb 21, 2013 at 12:13 PM, Roadstar Runner
wrote:
> I used the broadcast address 0x since the 802.15.4 spec
> specifies the boradcast address as 0x
> I did not use the ULL postfix cos i was just using the lowe
did it work?
Can i have a copy pf the modifications?
On Thu, Feb 21, 2013 at 1:25 PM, Miklos Maroti wrote:
> Thanks, I did not know. I have updated the git repo. Miklos
>
> On Thu, Feb 21, 2013 at 12:13 PM, Roadstar Runner
> wrote:
> > I used the broadcast address 0x since the 80
I never tried, I do not have the motes nor the time unfortunately. The
code is here:
https://github.com/mmaroti/tinyos-main/commits/rfxlink-64bit
Can you please try it out and see what happend? Miklos
On Thu, Feb 21, 2013 at 12:29 PM, Roadstar Runner
wrote:
> did it work?
> Can i have a copy pf
I have a sensor board that has humidity/temperature/light sensor on it. How
is possible to gather temperature readings from the environment and send it
to the gateway I am using? Is there a ready application by someone who
manage to do that before?
--
View this message in context:
http://tinyos
he problem. You can try to hack every piece of
> >> code to make it work, but that is not easy. If you decide to go ahead
> >> with that, then I can give some pointers. Basically, you want only
> >> 64-bit addresses, so no mixing should be allowed, otherwise the
> >>
only with 16-bit
> >> addresses, so that is the problem. You can try to hack every piece of
> >> code to make it work, but that is not easy. If you decide to go ahead
> >> with that, then I can give some pointers. Basically, you want only
> >> 64-bit addresses, s
work through the tutorials... docs.tinyos.net
yes these kinds of programs already exist. you should go look for them.
hint... somewhere in apps...
On Thu, Feb 21, 2013 at 1:50 PM, pirusaez wrote:
> I have a sensor board that has humidity/temperature/light sensor on it. How
> is possible
ses, so that is the problem. You can try to hack every piece of
> >> code to make it work, but that is not easy. If you decide to go ahead
> >> with that, then I can give some pointers. Basically, you want only
> >> 64-bit addresses, so no mixing shoul
28 matches
Mail list logo
