Re: [Tinyos-help] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb
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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Why some wrong mote join the MViz example network?
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.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
Re: [Tinyos-help] mviz
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 visualazation of collection protocol 3) do you have any idea about jTossim thank you in advance and i appreciate any help best regards meriam From: Eric Decker [via TinyOS - Help] ml-node+s10906n22629...@n7.nabble.com To: meriam merioum...@yahoo.com Sent: Tuesday, February 19, 2013 9:33 AM Subject: Re: mviz On Mon, Feb 18, 2013 at 11:38 PM, Dang Thi Hai Ha [hidden email] wrote: Hello, I never work with mviz so I don't know what problem you're having. Maybe you should try to look at this: https://tinyos-main.googlecode.com/svn/trunk/apps/MViz/README.txt tinyos-main.googlecode.com/svn is DEPRECATED. The current TinyOS 2 release (2.1.2) can be found at https://github.com/tinyos/tinyos-release/ The development trunk is at https://github.com/tinyos/tinyos-main An archive can be found at https://github.com/tinyos/tinyos-release/archive/release_tinyos_2_1_2.zip or https://github.com/tinyos/tinyos-release/archive/release_tinyos_2_1_2.tar.gz MViz lives at apps/MViz but is over 3 years old and I don't think it is maintained any more. I suppose that you was running tos-mviz MVizMsg I think that your command is to display some .gif image at local directory (or working directory). And if mviz find no .gif image, it just stops (i.e. close the window instantly). That's my guess. I can't be any more useful... Good luck! Ha. On Mon, Feb 18, 2013 at 11:32 PM, meriam [hidden email] wrote: thank you very much !! but it still a little problem i hope !! the window is closed so fast that i can't see any thing! any help will be precious thank you in advance :) From: Dang Thi Hai Ha [via TinyOS - Help] [hidden email] To: meriam [hidden email] Sent: Monday, February 18, 2013 5:21 PM Subject: Re: mviz Hello, It seems that you have not compile the support java. Go to the folder /opt/tinyos-2.1.0/support/sdk/java/ then run make to compile those java classes then check back with your mviz thing. Good luck! Ha. On Mon, Feb 18, 2013 at 5:13 PM, meriam [hidden email] wrote: hello, i just want to ask you how to run mviz !! i tape the command tos-mviz MVizMsg , but i got error :/opt/tinyos-2.1.0/support/sdk/java exception in thread main java.lang.NoClassDefFoundError:net/tinyos/mviz/DDocument when i am under the directory mviz and i tape make micaz sim then i got 3 errors /opt/tinyos-2.1.0/support/sdk/java/net/tinyos/ message/Message.java:84:cannot find symbol /opt/tinyos-2.1.0/support/sdk/java/net/tinyos/ message/Message.java:676:cannot find symbol /opt/tinyos-2.1.0/support/sdk/java/net/tinyos/ message/Message.java:684:cannot find symbol any help will be precious thank you in advance -- View this message in context: http://tinyos-help.10906.n7.nabble.com/mviz-tp2048p22617.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list [hidden email] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list [hidden email] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help If you reply to this email, your message will be added to the discussion below: http://tinyos-help.10906.n7.nabble.com/mviz-tp2048p22618.html To unsubscribe from mviz, click here. NAML View this message in context: Re: mviz Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list [hidden email] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list [hidden email] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list [hidden email] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help If you reply to this email, your message will be added to the discussion below: http://tinyos-help.10906.n7.nabble.com/mviz-tp2048p22629.html To unsubscribe from mviz, click here. NAML -- View this message in context: http://tinyos-help.10906.n7.nabble.com/mviz-tp2048p22680.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
Re: [Tinyos-help] [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb
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. And at best is a sideways step. Currently, I have detailed instructions for getting started at https://github.com/tp-freeforall/prod/blob/tp-master/00b_Development_Environment But instead of pulling from gh:tp-freeforall/prod one should use the tinyos/tinyos-release repository. The above procedure have been done on a 12.04 Ubuntu installation (I'm currently running it on 11.10). And should also work on Debian. Eric On Thu, Feb 21, 2013 at 1:10 AM, meriam merioum...@yahoo.com wrote: 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://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TKN154: Energy detection scan
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 problem arises when the
command MLME_SCAN.request is called. It seems to me that the proccess regarding
this kind of scan falls in a blocked state because the event MLME_SCAN.confirm
is never issued. Here there is part of the code I am using:
---implementation { void function_1() {
ieee154_PANDescriptor_t m_PANDescriptor[4];int8_t EDList [4];
ieee154_phyChannelsSupported_t ScanChannels = 0;
ScanChannels += ((uint32_t) 1) 16; // CH 1ScanChannels +=
((uint32_t) 1) 19; // CH 2ScanChannels += ((uint32_t) 1) 21; //
CH 3ScanChannels += ((uint32_t) 1) 26; // CH 4
call MLME_SCAN.request (ENERGY_DETECTION_SCAN, // ScanType
ScanChannels, // ScanChannels
5, // ScanDuration
0x00, // ChannelPage
4, //
EnergyDetectListNumEntriesEDList,
// EnergyDetectList
4, // PANDescriptorListNumEntries
m_PANDescriptor,// PANDescriptorList
0 // security
);}event void
MLME_SCAN.confirm ( ieee154_status_t status,
uint8_t ScanType, uint8_t ChannelPage,
uint32_t UnscannedChannels,
uint8_t EnergyDetectListNumEntries, int8_t*
EnergyDetectList, uint8_t PANDescriptorListNumEntries,
ieee154_PANDescriptor_t* PANDescriptorList) {
// It is never issued call Leds.Led0On();
}}---
I appreciate all the help possible.
Regards,
David ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Unknown target mica2, but the tosdir seems to be set correctly
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 investigation told me (I spent a couple of hours on searching a solution), that this should be the correct path (there is the 'platforms' subdirectory), but I can't get it to work. It is a common path problem, but as I see it, the path is correct! Can someone please help me with this? Appreciate your help, tim -- View this message in context: http://tinyos-help.10906.n7.nabble.com/Unknown-target-mica2-but-the-tosdir-seems-to-be-set-correctly-tp22683.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
Re: [Tinyos-help] Unknown target mica2, but the tosdir seems to be set correctly
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. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TKN154: Energy detection scan
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 drod...@outlook.com wrote:
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 problem arises
when the command MLME_SCAN.request is called. It seems to me that the
proccess regarding this kind of scan falls in a blocked state because the
event MLME_SCAN.confirm is never issued. Here there is part of the code I am
using:
---
implementation {
void function_1()
{
ieee154_PANDescriptor_t m_PANDescriptor[4];
int8_t EDList [4];
ieee154_phyChannelsSupported_t ScanChannels = 0;
ScanChannels += ((uint32_t) 1) 16; // CH 1
ScanChannels += ((uint32_t) 1) 19; // CH 2
ScanChannels += ((uint32_t) 1) 21; // CH 3
ScanChannels += ((uint32_t) 1) 26; // CH 4
call MLME_SCAN.request (ENERGY_DETECTION_SCAN, // ScanType
ScanChannels, // ScanChannels
5, // ScanDuration
0x00, // ChannelPage
4, // EnergyDetectListNumEntries
EDList,// EnergyDetectList
4, // PANDescriptorListNumEntries
m_PANDescriptor,// PANDescriptorList
0 // security
);
}
event void MLME_SCAN.confirm (
ieee154_status_t status,
uint8_t ScanType,
uint8_t ChannelPage,
uint32_t UnscannedChannels,
uint8_t EnergyDetectListNumEntries,
int8_t* EnergyDetectList,
uint8_t PANDescriptorListNumEntries,
ieee154_PANDescriptor_t* PANDescriptorList)
{
// It is never issued
call Leds.Led0On();
}
}
---
I appreciate all the help possible.
Regards,
David
___
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-help Digest, Vol 118, Issue 66
Hello All, Can some one tell me how to synthesis Verilog and VHDL code into the TINYOS? It seems nesC is just VHDl coding. Right? An Feng anderson.an.f...@aol.com -Original Message- From: tinyos-help-request tinyos-help-requ...@millennium.berkeley.edu To: tinyos-help tinyos-help@millennium.berkeley.edu Sent: Thu, Feb 21, 2013 5:56 pm Subject: Tinyos-help Digest, Vol 118, Issue 66 Send Tinyos-help mailing list submissions to tinyos-help@millennium.berkeley.edu To subscribe or unsubscribe via the World Wide Web, visit https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help or, via email, send a message with subject or body 'help' to tinyos-help-requ...@millennium.berkeley.edu You can reach the person managing the list at tinyos-help-ow...@millennium.berkeley.edu When replying, please edit your Subject line so it is more specific han Re: Contents of Tinyos-help digest... oday's Topics: 1. Iris using 64 bit address filtering (Roadstar Runner) 2. blip 2 ppprouter problem (Sheikh Jaaved) 3. Re: Iris using 64 bit address filtering (Roadstar Runner) 4. Re: [Tinyos-URGENT] Need help installing TinyOS on Ubuntu 12.04 and load a program over Telosb (meriam) 5. Re: Why some wrong mote join the MViz example network? (meriam) 6. Re: mviz (meriam) - Message: 1 ate: Thu, 21 Feb 2013 00:19:00 -0500 rom: Roadstar Runner redstripe...@gmail.com ubject: [Tinyos-help] Iris using 64 bit address filtering o: tinyos-help@millennium.berkeley.edu essage-ID: CAN3Ao+wXSmRzzpBD-i=k1xokdapzx7oncz5namgkz9-7aa9...@mail.gmail.com ontent-Type: text/plain; charset=iso-8859-1 Hi, am trying to implement a 64 bit IEEE address frame for the RF230 using he RX_AACK mode. The problem is that i the receiver does not receive any ata. If i use RF230_RX_ON, i am able to receive the data. I used a sniffer nd was able to capture the following raw data Sender address = 1 est address = Broadcast an ID = 0x22 The last block of data is the MAC payload 41 CC 1122 00FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 0 3F 08 0B 03 00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 0 00 The sniffer 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 - Message: 2 ate: Thu, 21 Feb 2013 11:14:39 +0530 rom: Sheikh Jaaved sheikh.jaa...@gmail.com ubject: [Tinyos-help] blip 2 ppprouter problem o: tinyos-help@millennium.berkeley.edu essage-ID: CAB05r+RF0+8YKTPMdTVc=fXoNEBYOOTkNJTgSQr3DEk=-vi...@mail.gmail.com ontent-Type: text/plain; charset=iso-8859-1 hi, i have compiled the program on tiny os 2.1.2 and following the instruction f http://docs.tinyos.net/tinywiki/index.php/BLIP_2.0_Tutorial and getting he output as follows oot@jaaved-HP-Pavilion-dv2500-Notebook-PC:/opt/tinyos-2.1.2/apps/PppRouter# udo pppd debug passive noauth nodetach 115200 /dev/ttyUSB1 nocrtscts ocdtrcts lcp-echo-interval 0 noccp noip ipv6 ::23,::24 sing channel 8 sing interface ppp0 onnect: ppp0 -- /dev/ttyUSB1 ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] cvd [LCP ConfReq id=0x7 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfAck id=0x7 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] cvd [LCP ConfReq id=0x8 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfAck id=0x8 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] cvd [LCP ConfReq id=0x9 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfAck id=0x9 mru 1280 asyncmap 0x0 accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] cvd [LCP ConfReq id=0xa mru 1280 asyncmap 0x0 accomp] ent [LCP ConfAck id=0xa mru 1280 asyncmap 0x0 accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] ent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0x458e71d1 pcomp accomp] CP: timeout sending Config-Requests CTerminating on signal 2 onnection terminated. any help will be appreciated hanks in advance - Regards* Sheikh Jaaved Hassan* - next part -- n HTML attachment was scrubbed... RL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130221/6aad2765/attachment-0001.htm - Message: 3 ate: Thu, 21 Feb 2013 01:20:20 -0500 rom: Roadstar Runner redstripe...@gmail.com ubject: Re: [Tinyos-help] Iris using 64 bit address filtering o: tinyos-help@millennium.berkeley.edu essage-ID: can3ao
Re: [Tinyos-help] TKN154: Energy detection scan
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 developer so I
ber there is a reason.
Thanks
David
Date: Thu, 21 Feb 2013 12:25:35 +0100
Subject: Re: [Tinyos-help] TKN154: Energy detection scan
From: ha...@tkn.tu-berlin.de
To: drod...@outlook.com
CC: tinyos-help@millennium.berkeley.edu
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 drod...@outlook.com wrote:
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 problem arises
when the command MLME_SCAN.request is called. It seems to me that the
proccess regarding this kind of scan falls in a blocked state because the
event MLME_SCAN.confirm is never issued. Here there is part of the code I am
using:
---
implementation {
void function_1()
{
ieee154_PANDescriptor_t m_PANDescriptor[4];
int8_t EDList [4];
ieee154_phyChannelsSupported_t ScanChannels = 0;
ScanChannels += ((uint32_t) 1) 16; // CH 1
ScanChannels += ((uint32_t) 1) 19; // CH 2
ScanChannels += ((uint32_t) 1) 21; // CH 3
ScanChannels += ((uint32_t) 1) 26; // CH 4
call MLME_SCAN.request (ENERGY_DETECTION_SCAN, // ScanType
ScanChannels, // ScanChannels
5, // ScanDuration
0x00, // ChannelPage
4, // EnergyDetectListNumEntries
EDList,// EnergyDetectList
4, // PANDescriptorListNumEntries
m_PANDescriptor,// PANDescriptorList
0 // security
);
}
event void MLME_SCAN.confirm (
ieee154_status_t status,
uint8_t ScanType,
uint8_t ChannelPage,
uint32_t UnscannedChannels,
uint8_t EnergyDetectListNumEntries,
int8_t* EnergyDetectList,
uint8_t PANDescriptorListNumEntries,
ieee154_PANDescriptor_t* PANDescriptorList)
{
// It is never issued
call Leds.Led0On();
}
}
---
I appreciate all the help possible.
Regards,
David
___
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] Iris using 64 bit address filtering
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 put some LED commands there the verify that you get messages. The RF230 does not do any hardware filtering, only the FCS (even snooping works, and CRC check is done in software). Miklos On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner redstripe...@gmail.com wrote: The data i had posted seems to have lost its formatting, so i am re posting the raw data captured by the sniffer 41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F 08 0B 03 00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00 ___ 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] Iris using 64 bit address filtering
Hi Lou, On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner redstripe...@gmail.com 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 included is from the sniffer. If i set the filter on the sniffer to 802.15.4 packets, it shows all the fields as i expect I have attached a screenshot of the sniffer capture. Does tinyos support 64bit 802.15.4 addressing at the hardware level ? The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the address of other fields in the packet need to be calculated dynamically. Miklos Thanks once again, Lou On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti mmar...@math.u-szeged.hu wrote: 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 put some LED commands there the verify that you get messages. The RF230 does not do any hardware filtering, only the FCS (even snooping works, and CRC check is done in software). Miklos On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner redstripe...@gmail.com wrote: The data i had posted seems to have lost its formatting, so i am re posting the raw data captured by the sniffer 41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F 08 0B 03 00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00 ___ 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] Iris using 64 bit address filtering
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/** Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti mmar...@math.u-szeged.huwrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows all the
fields as i expect I have attached a screenshot of the sniffer capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware level ?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F 08
0B
03
00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00
___
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] Iris using 64 bit address filtering
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/** Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows all the
fields as i expect I have attached a screenshot of the sniffer capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware level ?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F 08
0B
03
00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00
___
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] Iris using 64 bit address filtering
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 mmar...@math.u-szeged.huwrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/** Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware level ?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F
08
0B
03
00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Iris using 64 bit address filtering
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
redstripe...@gmail.com wrote:
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 mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware level
?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am
re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00
Re: [Tinyos-help] Iris using 64 bit address filtering
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 mmar...@math.u-szeged.huwrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows
all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware
level
?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get
Re: [Tinyos-help] Iris using 64 bit address filtering
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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 mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows
all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware
level
?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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
Re: [Tinyos-help] Iris using 64 bit address filtering
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 can make the hardware ack work too.
Miklos
On Thu, Feb 21, 2013 at 11:25 AM, Miklos Maroti
mmar...@math.u-szeged.hu wrote:
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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 mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows
all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware
level
?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet
Re: [Tinyos-help] Iris using 64 bit address filtering
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 mmar...@math.u-szeged.huwrote:
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows
all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware
level
?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the
Re: [Tinyos-help] Iris using 64 bit address filtering
Thanks, I did not know. I have updated the git repo. Miklos
On Thu, Feb 21, 2013 at 12:13 PM, Roadstar Runner
redstripe...@gmail.com 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 lower 2 bytes of the
address
On Thu, Feb 21, 2013 at 12:25 PM, Miklos Maroti mmar...@math.u-szeged.hu
wrote:
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it
shows
all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware
level
?
The current ActiveMessageC for the RF230 works 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
Re: [Tinyos-help] Iris using 64 bit address filtering
did it work?
Can i have a copy pf the modifications?
On Thu, Feb 21, 2013 at 1:25 PM, Miklos Maroti mmar...@math.u-szeged.huwrote:
Thanks, I did not know. I have updated the git repo. Miklos
On Thu, Feb 21, 2013 at 12:13 PM, Roadstar Runner
redstripe...@gmail.com 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 lower 2 bytes of
the
address
On Thu, Feb 21, 2013 at 12:25 PM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF,
DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp
8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it
shows
all
the
fields as i expect I have attached a screenshot of the
sniffer
capture.
Does tinyos support 64bit
Re: [Tinyos-help] Iris using 64 bit address filtering
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
redstripe...@gmail.com wrote:
did it work?
Can i have a copy pf the modifications?
On Thu, Feb 21, 2013 at 1:25 PM, Miklos Maroti mmar...@math.u-szeged.hu
wrote:
Thanks, I did not know. I have updated the git repo. Miklos
On Thu, Feb 21, 2013 at 12:13 PM, Roadstar Runner
redstripe...@gmail.com 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 lower 2 bytes of
the
address
On Thu, Feb 21, 2013 at 12:25 PM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Is the broadcast address 0xULL? Miklos
On Thu, Feb 21, 2013 at 11:20 AM, Roadstar Runner
redstripe...@gmail.com 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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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
mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT
IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT
IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF,
DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call
ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp
8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp
8);
#endif
Right now i am only using the lower 2 address bytes for
testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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
[Tinyos-help] Telosb motes temperature/humidity readings
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-help.10906.n7.nabble.com/Telosb-motes-temperature-humidity-readings-tp22701.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
Re: [Tinyos-help] Tinyos-help Digest, Vol 118, Issue 69
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
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F
08
0B
03
00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
-- next part --
An HTML attachment was scrubbed...
URL:
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130221/93ed5c53/attachment-0001.htm
--
Message: 3
Date: Thu, 21 Feb 2013 11:15:22 -0600
From: Miklos Maroti mmar...@math.u-szeged.hu
Subject: Re: [Tinyos-help] Iris using 64 bit address filtering
To: Roadstar Runner redstripe...@gmail.com
Cc: tinyos-help@millennium.berkeley.edu
Message-ID:
CAEUdg=BMhE7oQcUo5fcUKPRV1wDrdS0x6J4G_XhjBcfs=nb...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
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
redstripe...@gmail.com wrote:
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 mmar...@math.u-szeged.hu
wrote:
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
redstripe...@gmail.com wrote:
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_ADDR_MODE
nxle_uint64_t dest;
nxle_uint64_t src;
#else
nxle_uint16_t dest;
nxle_uint16_t src;
#endif
} ieee154_header_t;
/**
Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am
Re: [Tinyos-help] Tinyos-help Digest, Vol 118, Issue 73
) | (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE), IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA IEEE154_FCF_FRAME_TYPE) | (1 IEEE154_FCF_INTRAPAN) #ifdef RF230_EXTENDED_ADDR_MODE | (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE) | (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE), #else | (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE) | (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE), #endif IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK IEEE154_FCF_FRAME_TYPE), IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK IEEE154_FCF_FRAME_TYPE), }; /** RF230DriverHwAckP.nc ***/ temp = call ActiveMessageAddress.amAddress(); #ifdef RF230_EXTENDED_ADDR_MODE writeRegister(RF230_IEEE_ADDR_0, temp); writeRegister(RF230_IEEE_ADDR_1, temp 8); #else writeRegister(RF230_SHORT_ADDR_0, temp); writeRegister(RF230_SHORT_ADDR_1, temp 8); #endif Right now i am only using the lower 2 address bytes for testing. Thanks, Lou On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti mmar...@math.u-szeged.hu wrote: Hi Lou, On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner redstripe...@gmail.com 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 included is from the sniffer. If i set the filter on the sniffer to 802.15.4 packets, it shows all the fields as i expect I have attached a screenshot of the sniffer capture. Does tinyos support 64bit 802.15.4 addressing at the hardware level ? The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the address of other fields in the packet need to be calculated dynamically. Miklos Thanks once again, Lou On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti mmar...@math.u-szeged.hu wrote: 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 put some LED commands there the verify that you get messages. The RF230 does not do any hardware filtering, only the FCS (even snooping works, and CRC check is done in software). Miklos On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner redstripe...@gmail.com wrote: The data i had posted seems to have lost its formatting, so i am re posting the raw data captured by the sniffer 41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F 08 0B 03 00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- next part -- An HTML attachment was scrubbed... URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130221/93ed5c53/attachment-0001.htm -- Message: 3 Date: Thu, 21 Feb 2013 11:15:22 -0600 From: Miklos Maroti mmar...@math.u-szeged.hu Subject: Re: [Tinyos-help] Iris using 64 bit address filtering To: Roadstar Runner redstripe...@gmail.com Cc: tinyos-help@millennium.berkeley.edu Message-ID: CAEUdg=BMhE7oQcUo5fcUKPRV1wDrdS0x6J4G_XhjBcfs=nb...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 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 redstripe...@gmail.com wrote: 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 mmar...@math.u-szeged.hu wrote: Looks good! Let me know if you run into problems. If it works, then I
Re: [Tinyos-help] Telosb motes temperature/humidity readings
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 pa.lamb...@edu.cut.ac.cy wrote: 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-help.10906.n7.nabble.com/Telosb-motes-temperature-humidity-readings-tp22701.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 -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tinyos-help Digest, Vol 118, Issue 73
;
/** Ieee154PacketLayerP.nc**/
enum
{
IEEE154_DATA_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
| (IEEE154_ADDR_MASK IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_MASK IEEE154_FCF_SRC_ADDR_MODE),
IEEE154_DATA_FRAME_VALUE = (IEEE154_TYPE_DATA
IEEE154_FCF_FRAME_TYPE)
| (1 IEEE154_FCF_INTRAPAN)
#ifdef RF230_EXTENDED_ADDR_MODE
| (IEEE154_ADDR_EXT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_EXT IEEE154_FCF_SRC_ADDR_MODE),
#else
| (IEEE154_ADDR_SHORT IEEE154_FCF_DEST_ADDR_MODE)
| (IEEE154_ADDR_SHORT IEEE154_FCF_SRC_ADDR_MODE),
#endif
IEEE154_ACK_FRAME_LENGTH = 3,// includes the FCF, DSN
IEEE154_ACK_FRAME_MASK = (IEEE154_TYPE_MASK
IEEE154_FCF_FRAME_TYPE),
IEEE154_ACK_FRAME_VALUE = (IEEE154_TYPE_ACK
IEEE154_FCF_FRAME_TYPE),
};
/** RF230DriverHwAckP.nc
***/
temp = call ActiveMessageAddress.amAddress();
#ifdef RF230_EXTENDED_ADDR_MODE
writeRegister(RF230_IEEE_ADDR_0, temp);
writeRegister(RF230_IEEE_ADDR_1, temp 8);
#else
writeRegister(RF230_SHORT_ADDR_0, temp);
writeRegister(RF230_SHORT_ADDR_1, temp 8);
#endif
Right now i am only using the lower 2 address bytes for testing.
Thanks,
Lou
On Thu, Feb 21, 2013 at 11:40 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
Hi Lou,
On Thu, Feb 21, 2013 at 10:36 AM, Roadstar Runner
redstripe...@gmail.com 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 included is from the sniffer.
If i set the filter on the sniffer to 802.15.4 packets, it shows all
the
fields as i expect I have attached a screenshot of the sniffer
capture.
Does tinyos support 64bit 802.15.4 addressing at the hardware level ?
The current ActiveMessageC for the RF230 works 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, so no mixing should be allowed, otherwise the
address of other fields in the packet need to be calculated
dynamically.
Miklos
Thanks once again,
Lou
On Thu, Feb 21, 2013 at 11:22 AM, Miklos Maroti
mmar...@math.u-szeged.hu
wrote:
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 put some LED commands
there the verify that you get messages. The RF230 does not do any
hardware filtering, only the FCS (even snooping works, and CRC check
is done in software). Miklos
On Thu, Feb 21, 2013 at 12:20 AM, Roadstar Runner
redstripe...@gmail.com wrote:
The data i had posted seems to have lost its formatting, so i am re
posting
the raw data captured by the sniffer
41 CC 11 22 00 FF FF 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 3F
08
0B
03
00 F8 00 0F 10 00 AA 01 F8 00 00 00 00 00 00 00 00 00
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
-- next part --
An HTML attachment was scrubbed...
URL:
https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130221/93ed5c53/attachment-0001.htm
--
Message: 3
Date: Thu, 21 Feb 2013 11:15:22 -0600
From: Miklos Maroti mmar...@math.u-szeged.hu
Subject: Re: [Tinyos-help] Iris using 64 bit address filtering
To: Roadstar Runner redstripe...@gmail.com
Cc: tinyos-help@millennium.berkeley.edu
Message-ID:
CAEUdg=BMhE7oQcUo5fcUKPRV1wDrdS0x6J4G_XhjBcfs=nb...@mail.gmail.com
Content-Type: text/plain; charset=UTF-8
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
redstripe...@gmail.com wrote:
So far no luck :-(
I was under the impression
