Re: [Tinyos-help] Question
Hi, Which distribution of linux you are using (or cigwin)? I haven't complied TOS since 1.1 but as the error shows, apparently the makefiles are not made yet (don't you have to call configure first?). Cheers, M. On 23 September 2010 10:43, farzaneh baghche band f.baghcheb...@gmail.comwrote: Hi i have a question , I `m new with the tinyos-2.x, i want to start and as it`s written in document the first step is to work with blink/make file but i can`t do it, this is the error $make micaz sim make: *** No rules to make target 'micaz' is it possible for u to help me on this error? Regards Farzaneh ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 http://homepage.usask.ca/~smh002/default.html ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC2420 Transmitter power can not be set to MAX!
Hi all, I want to set the transmission power of CC2420 to maximum in MicaZ nodes. When I call CC2420Control.SetRFPower(TXPOWER_MAX), it fails (result_t != SUCCESS) and sets the power to 15 (I got this value from CC2420Control.GetRFPower(). Does anyone knows why? I think it's supposed to be set to TXPOWER_MAX as well (0x1F) thanks, Mohammad ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Transmitter problem in Micaz
One other common thing between all the failed motes is that as I said they've been carried by humans, and here in the place that I live, the outside temperature is usually between -20 to -30 or even -40 (unbelievable, I know LOL) and the people are usually outside for at least 15 or 20 minutes per day. Can this causes electric discharge on the mote and therefore the failure of the receiver module of the mote? Thanks, Mohammad 2010/1/4 Mohammad S. Hashemian m.hashem...@gmail.com Thanks Paul, Actually I found one more thing. The common point with all of the failed motes (currently 22 motes) is that the send part of all of them works fine, but the receiver doesn't operate! I checked the board to see if there is any obvious problem, but nothing. I think as you said the best way is to contact the company and ask them to do the diagnostics, hopefully this helps. Thanks again for your help, Mohammad 2010/1/3 Paul Johnson oewyn...@gmail.com Unfortunately, i'm not sure what else could be the problem. Maybe compare a working board with a non-working one and see if any components have fallen off or become loose? The people who have be using the broken boards, is there anything they have done in common? Dropped board, static discharge, improperly secured (put inside of purse/backpack with no protection) etc? At first glance, it appeared as if the boards were not able to communicate because the antenna was not working properly, but from what you've done, it doesn't seem to be. As a last resort, you may want to look into having one mote diagnosed by Crossbow. If they can find out the problem, it may be possible that you can do the repairs yourself in-house. Sorry I couldn't be of much help. -Paul On 1/3/2010 2:30 PM, Mohammad S. Hashemian wrote: Hello again, I'm still waiting for any answer from your side Paul (or anyone else). Can you think about any other problem in the mote that might cause the problem (or anything which goes wrong in the current case)? Thanks alot for your help, Mohammad 2009/12/30 Mohammad S. Hashemian m.hashem...@gmail.com Hi Paul, I tested this case with some help, but apparently this is not the reason for failure. I took one new mote out of the pack and a broken one. The broken one could xmit the packet at most over 20 cm with antenna, but if you would detach the whole antenna (with MMCX connector) from the board, it would xmit at most over 2 or 3 cm. While with the new one, it could xmit the packets over even 1.5 or two meters after detaching the whole antenna part (antenna + MMCX connector). So I did one more test, I swapped the antenna and MMCX connector of the new mote with the old one and re-soldered it, so the new mote had the antenna + MMCX connector of the broken mote and vice versa. But still the problem was there, the new mote could work fine and the old one couldn't transmit more then 10 or 20 cms!!! Do you have any idea what part of the board may have the problem? Thanks, Mohammad 2009/12/23 Mohammad S. Hashemian m.hashem...@gmail.com Thanks again, actually I have a software background and I'm not very good in this soldering thing, especially with this small board and limited tools we have in our lab. I'll try these ways and I'll tell you what happens. Mohammad 2009/12/23 Paul Johnson oewyn...@gmail.com Mohammad, Yes, I believe the problem is with the actual connector that is MMCX adapter soldered to the board, i've had problems with them coming completely off the board and taking the PCB lines with them. I would first try re-soldering that piece first. If this doesn't work, then an alternative solution would be to use the through-hole connectors for the antenna. It should be located near the MMCX connector. Using the through-hole connectors may be a little bit tricky since the antennas have an MMCX connector attached to the end. You may want to try making a very simple dipole(you won't get as good of a performance as the actual antenna because of impedance mis-matching) using a wire of the appropriate length, or you can use one of the female MMCX connectors to interface with the through-hole connector and the existing antenna. Let me know what happens, -Paul On 12/22/2009 10:23 PM, Mohammad S. Hashemian wrote: Thanks Paul, you're right, most likely the problem is with the antenna. But the point is that as you know for Micaz, the antenna is a 2.4 ghz pcb antenna! how can I re-solder it? by now I've cut the antenna of one of the motes totally and re-soldered it, but it didn't work and also I resolder another mote (without cutting the antenna first, just by adding more solder to it board), but it didn't work either! any suggestions how can I do it? And also do you think if the problem is with the connection between MMCX female part and board or the female part itself is damaged? (the antenna should be fine, I tested it by changing a new mote's antenna
Re: [Tinyos-help] Transmitter problem in Micaz
Hi Paul, I tested this case with some help, but apparently this is not the reason for failure. I took one new mote out of the pack and a broken one. The broken one could xmit the packet at most over 20 cm with antenna, but if you would detach the whole antenna (with MMCX connector) from the board, it would xmit at most over 2 or 3 cm. While with the new one, it could xmit the packets over even 1.5 or two meters after detaching the whole antenna part (antenna + MMCX connector). So I did one more test, I swapped the antenna and MMCX connector of the new mote with the old one and re-soldered it, so the new mote had the antenna + MMCX connector of the broken mote and vice versa. But still the problem was there, the new mote could work fine and the old one couldn't transmit more then 10 or 20 cms!!! Do you have any idea what part of the board may have the problem? Thanks, Mohammad 2009/12/23 Mohammad S. Hashemian m.hashem...@gmail.com Thanks again, actually I have a software background and I'm not very good in this soldering thing, especially with this small board and limited tools we have in our lab. I'll try these ways and I'll tell you what happens. Mohammad 2009/12/23 Paul Johnson oewyn...@gmail.com Mohammad, Yes, I believe the problem is with the actual connector that is MMCX adapter soldered to the board, i've had problems with them coming completely off the board and taking the PCB lines with them. I would first try re-soldering that piece first. If this doesn't work, then an alternative solution would be to use the through-hole connectors for the antenna. It should be located near the MMCX connector. Using the through-hole connectors may be a little bit tricky since the antennas have an MMCX connector attached to the end. You may want to try making a very simple dipole(you won't get as good of a performance as the actual antenna because of impedance mis-matching) using a wire of the appropriate length, or you can use one of the female MMCX connectors to interface with the through-hole connector and the existing antenna. Let me know what happens, -Paul On 12/22/2009 10:23 PM, Mohammad S. Hashemian wrote: Thanks Paul, you're right, most likely the problem is with the antenna. But the point is that as you know for Micaz, the antenna is a 2.4 ghz pcb antenna! how can I re-solder it? by now I've cut the antenna of one of the motes totally and re-soldered it, but it didn't work and also I resolder another mote (without cutting the antenna first, just by adding more solder to it board), but it didn't work either! any suggestions how can I do it? And also do you think if the problem is with the connection between MMCX female part and board or the female part itself is damaged? (the antenna should be fine, I tested it by changing a new mote's antenna with a damaged one, and it still was working fine)! thanks again for your help, Mohammad 2009/12/22 Paul Johnson oewyn...@gmail.com Mohammad, One thing you may want to check out is the antenna connection to the micaz board. The board-mounted connector can be pretty fragile and can be easily broken off if the antenna catches on anything, or you attempt to remove the antenna by pulling at an angle. What I would do is try to re-solder the antenna one one of the boards that are malfunctioning and see what happens. 10cm is about the range I've seen micaz/mica2 nodes work w/out an antenna connected at all, so the antenna is likely the cause of this problem. Hopefully re-soldering the connections fixes this and you don't have to buy new boards, -Paul On 12/22/2009 4:53 PM, Mohammad S. Hashemian wrote: Hi All We have run a project using micaz modules. In this project there are 8 nodes which are fixed in a certain locations and 40 nodes which are carried by different people (some of these motes are in XBow boxes and some other are just in small pouches). There are 3 motes which are used as base stations through the environment. The problem we have now is that the transmitter of the mobile motes gets damaged after a while. For example we pick a new mote out of the pack, program it, and give it to one of the people, after a while (sometimes even after 3 days!!!) the transmitter (either sender or receiver) stops working. I realize the transmitter of a mote has stopped working when I don't receive any signal from it for a couple of days. In this case I test the mote with CountSend and CountReceive (shipped with XBow MoteWorks) against another new mote. Usually the result is that either the sender part or receiver part of the mote has become so weak that the packet can be transferred only if the motes are less than 10 cm away!!! further than that the packet either can not be sent or be received. I've called the company regarding this issue and they told me if the mote doesn't work with CountSend and CountReceive, you should send them back here for diagnosis and because by now
Re: [Tinyos-help] Transmitter problem in Micaz
Thanks again, actually I have a software background and I'm not very good in this soldering thing, especially with this small board and limited tools we have in our lab. I'll try these ways and I'll tell you what happens. Mohammad 2009/12/23 Paul Johnson oewyn...@gmail.com Mohammad, Yes, I believe the problem is with the actual connector that is MMCX adapter soldered to the board, i've had problems with them coming completely off the board and taking the PCB lines with them. I would first try re-soldering that piece first. If this doesn't work, then an alternative solution would be to use the through-hole connectors for the antenna. It should be located near the MMCX connector. Using the through-hole connectors may be a little bit tricky since the antennas have an MMCX connector attached to the end. You may want to try making a very simple dipole(you won't get as good of a performance as the actual antenna because of impedance mis-matching) using a wire of the appropriate length, or you can use one of the female MMCX connectors to interface with the through-hole connector and the existing antenna. Let me know what happens, -Paul On 12/22/2009 10:23 PM, Mohammad S. Hashemian wrote: Thanks Paul, you're right, most likely the problem is with the antenna. But the point is that as you know for Micaz, the antenna is a 2.4 ghz pcb antenna! how can I re-solder it? by now I've cut the antenna of one of the motes totally and re-soldered it, but it didn't work and also I resolder another mote (without cutting the antenna first, just by adding more solder to it board), but it didn't work either! any suggestions how can I do it? And also do you think if the problem is with the connection between MMCX female part and board or the female part itself is damaged? (the antenna should be fine, I tested it by changing a new mote's antenna with a damaged one, and it still was working fine)! thanks again for your help, Mohammad 2009/12/22 Paul Johnson oewyn...@gmail.com Mohammad, One thing you may want to check out is the antenna connection to the micaz board. The board-mounted connector can be pretty fragile and can be easily broken off if the antenna catches on anything, or you attempt to remove the antenna by pulling at an angle. What I would do is try to re-solder the antenna one one of the boards that are malfunctioning and see what happens. 10cm is about the range I've seen micaz/mica2 nodes work w/out an antenna connected at all, so the antenna is likely the cause of this problem. Hopefully re-soldering the connections fixes this and you don't have to buy new boards, -Paul On 12/22/2009 4:53 PM, Mohammad S. Hashemian wrote: Hi All We have run a project using micaz modules. In this project there are 8 nodes which are fixed in a certain locations and 40 nodes which are carried by different people (some of these motes are in XBow boxes and some other are just in small pouches). There are 3 motes which are used as base stations through the environment. The problem we have now is that the transmitter of the mobile motes gets damaged after a while. For example we pick a new mote out of the pack, program it, and give it to one of the people, after a while (sometimes even after 3 days!!!) the transmitter (either sender or receiver) stops working. I realize the transmitter of a mote has stopped working when I don't receive any signal from it for a couple of days. In this case I test the mote with CountSend and CountReceive (shipped with XBow MoteWorks) against another new mote. Usually the result is that either the sender part or receiver part of the mote has become so weak that the packet can be transferred only if the motes are less than 10 cm away!!! further than that the packet either can not be sent or be received. I've called the company regarding this issue and they told me if the mote doesn't work with CountSend and CountReceive, you should send them back here for diagnosis and because by now they are out of warranty, it costs 100$ per each for diagnosis (The motes have been bought more than a year ago, but they haven't been used at all). On possibility was that the motes that we got have been produced using a bad batch in the manufacture for transmitter, and that's why they keep dying in work. But it's not very likely because the problem is just exist with the mobile ones, not with the base stations or with the fixed motes. Also the currently used motes have been purchased in two separate orders, and probably two separate manufacturing series. The other possibility is that they die because of the static electricity (people are supposed to change the mote's battery every couple of days). Can it be a reason? But this even happens for the mobile motes with XBow boxes which they look safe for this. and if it's the reason, why just the transmitter gets damaged and no other part in the mote? By now we have lost more
[Tinyos-help] Transmitter problem in Micaz
Hi All We have run a project using micaz modules. In this project there are 8 nodes which are fixed in a certain locations and 40 nodes which are carried by different people (some of these motes are in XBow boxes and some other are just in small pouches). There are 3 motes which are used as base stations through the environment. The problem we have now is that the transmitter of the mobile motes gets damaged after a while. For example we pick a new mote out of the pack, program it, and give it to one of the people, after a while (sometimes even after 3 days!!!) the transmitter (either sender or receiver) stops working. I realize the transmitter of a mote has stopped working when I don't receive any signal from it for a couple of days. In this case I test the mote with CountSend and CountReceive (shipped with XBow MoteWorks) against another new mote. Usually the result is that either the sender part or receiver part of the mote has become so weak that the packet can be transferred only if the motes are less than 10 cm away!!! further than that the packet either can not be sent or be received. I've called the company regarding this issue and they told me if the mote doesn't work with CountSend and CountReceive, you should send them back here for diagnosis and because by now they are out of warranty, it costs 100$ per each for diagnosis (The motes have been bought more than a year ago, but they haven't been used at all). On possibility was that the motes that we got have been produced using a bad batch in the manufacture for transmitter, and that's why they keep dying in work. But it's not very likely because the problem is just exist with the mobile ones, not with the base stations or with the fixed motes. Also the currently used motes have been purchased in two separate orders, and probably two separate manufacturing series. The other possibility is that they die because of the static electricity (people are supposed to change the mote's battery every couple of days). Can it be a reason? But this even happens for the mobile motes with XBow boxes which they look safe for this. and if it's the reason, why just the transmitter gets damaged and no other part in the mote? By now we have lost more than 30 micaz motes this way and if it wants to continue we will much more. Does anyone has any idea what can be the reason and how we can stop it? Any idea is highly appreciated. Thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Transmitter problem in Micaz
Thanks Paul, you're right, most likely the problem is with the antenna. But the point is that as you know for Micaz, the antenna is a 2.4 ghz pcb antenna! how can I re-solder it? by now I've cut the antenna of one of the motes totally and re-soldered it, but it didn't work and also I resolder another mote (without cutting the antenna first, just by adding more solder to it board), but it didn't work either! any suggestions how can I do it? And also do you think if the problem is with the connection between MMCX female part and board or the female part itself is damaged? (the antenna should be fine, I tested it by changing a new mote's antenna with a damaged one, and it still was working fine)! thanks again for your help, Mohammad 2009/12/22 Paul Johnson oewyn...@gmail.com Mohammad, One thing you may want to check out is the antenna connection to the micaz board. The board-mounted connector can be pretty fragile and can be easily broken off if the antenna catches on anything, or you attempt to remove the antenna by pulling at an angle. What I would do is try to re-solder the antenna one one of the boards that are malfunctioning and see what happens. 10cm is about the range I've seen micaz/mica2 nodes work w/out an antenna connected at all, so the antenna is likely the cause of this problem. Hopefully re-soldering the connections fixes this and you don't have to buy new boards, -Paul On 12/22/2009 4:53 PM, Mohammad S. Hashemian wrote: Hi All We have run a project using micaz modules. In this project there are 8 nodes which are fixed in a certain locations and 40 nodes which are carried by different people (some of these motes are in XBow boxes and some other are just in small pouches). There are 3 motes which are used as base stations through the environment. The problem we have now is that the transmitter of the mobile motes gets damaged after a while. For example we pick a new mote out of the pack, program it, and give it to one of the people, after a while (sometimes even after 3 days!!!) the transmitter (either sender or receiver) stops working. I realize the transmitter of a mote has stopped working when I don't receive any signal from it for a couple of days. In this case I test the mote with CountSend and CountReceive (shipped with XBow MoteWorks) against another new mote. Usually the result is that either the sender part or receiver part of the mote has become so weak that the packet can be transferred only if the motes are less than 10 cm away!!! further than that the packet either can not be sent or be received. I've called the company regarding this issue and they told me if the mote doesn't work with CountSend and CountReceive, you should send them back here for diagnosis and because by now they are out of warranty, it costs 100$ per each for diagnosis (The motes have been bought more than a year ago, but they haven't been used at all). On possibility was that the motes that we got have been produced using a bad batch in the manufacture for transmitter, and that's why they keep dying in work. But it's not very likely because the problem is just exist with the mobile ones, not with the base stations or with the fixed motes. Also the currently used motes have been purchased in two separate orders, and probably two separate manufacturing series. The other possibility is that they die because of the static electricity (people are supposed to change the mote's battery every couple of days). Can it be a reason? But this even happens for the mobile motes with XBow boxes which they look safe for this. and if it's the reason, why just the transmitter gets damaged and no other part in the mote? By now we have lost more than 30 micaz motes this way and if it wants to continue we will much more. Does anyone has any idea what can be the reason and how we can stop it? Any idea is highly appreciated. Thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list tinyos-h...@millennium.berkeley.eduhttps://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 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Timer accuracy in MicaZ
Hi all, In the application I'm working on, I need to know the exact time of a specific event, so I recorded the time turned on the mote, and I programmed the mote to put the time value in the packet as well (using Time.getLow32() and Time.getHigh32, Time is SimpleTime.Time interface), using this value and adding it to the base time (the time I turned the mote on) I should be able to compute the time which event occured. The problem is that this time increases faster than it should. For example suppose the event is firing a timer in code which occur every 4 seconds, and in the timer event handler, I put the time value and send it to the server PC. In such a test, the difference between time that server receives the packet and the computed time (time value in the packet + base time which I turned the mote on) is zero, but after 15 minutes the reported time is 20 seconds ahead of the current time, and this value increases that for example in 2 days, the reported time by mote is 64 minutes ahead of the current time. The procedure of computing time (recording the mote start time and adding the reported time to it) seems straight forward and correct, so the only problem I can think about is inaccuracy of clock in the mote. I tested this on couple of motes but all of them had the same problem, so do you think if the problem is in the way I implemented my test or it's just some inaccuracy in mote's clock? BTW I use MicaZ motes with TOS 1.1 Thanks all, Mohammad ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] RSSI in MoteWorks (or TOS 1.1)
Hi all I need to know the RSSI value for arrived packet in MoteWorks (which is based on TOS 1.1, so it should be the same). I searched the archive but I couldn't find anything for this. Does anyone know how I can measure RSSI value for an arrived packet? Thanks in advance, Mohammad -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Different behaviour from the ame image but on different motes
well I thought a little bit about that and I'm thinking the problem might be because of receive hardware issue with the mote itself. but anyway I think the best way is to ask the XBow guys themselves to see what they say about it. Thanks Michael 2009/10/15 Michael Schippling sc...@santafe.edu Sorry I can't help further. I've used Xmesh with only two nodes (Base and re-Mote) to develop a sensor program so I haven't observed the net construction behavior. I also believe the Xmesh source is not open so you'll probably have to have a go-round with Xbow support. MS Mohammad S. Hashemian wrote: I also should include that if I wait for a long time (15 or 30 minutes) finally the mote becomes the member of the mesh, but this me it sends the health packet many times instead of once (for example 8 or 10 times) and therefore moteView shows 10 rows of health packet from this mote very time. So do you have any idea why this happens? 2009/10/14 Mohammad S. Hashemian m.hashem...@gmail.com mailto: m.hashem...@gmail.com I monitored the network at most for half an hour, and during this period I turned some other motes on and off as well. while those other motes were on, the mote was sending many copies of the health packets (with different sequence mber, fo example from 180 to 188) to one of those motes as the destination address instead of bcasting them (I say this based on details in XSniffer). thanks for your answer though 2009/10/14 Michael Schippling sc...@santafe.edu mailto:sc...@santafe.edu Sounds like the BCASTing mote may not have been allowed into the mesh-fold yet. I haven't looked at XMESH carefully but it seems to take a while for nodes to become integrated. How long have waited for messages? MS Mohammad S. Hashemian wrote: Hi all, I have two MicaZ nodes and I've installed the same image of MTS310 XMesh application (from MoteWorks framework) on both. MoteView can receive and show health packet from one of them, but not from t other one. When I use XSniffer to sniff the network, I can see both of the motes send health packets but one of them send's the packet to the Base as destination, so the moteView can show it, butthe other one sends the packet as a broadcast and therefore the MoteViiew is unable to show it (it might not be the resaon though, but it's the only difference between the packets these two motes send). Considering that the sapacket is installed on , doe anyone have any idea what is the problem? Thanks, --Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu mailto:Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help --Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Different behaviour from the ame image but on different motes
Hi all, I have two MicaZ nodes and I've installed the same image of MTS310 XMesh application (from MoteWorks framework) on both. MoteView can receive and show health packet from one of them, but not from t other one. When I use XSniffer to sniff the network, I can see both of the motes send health packets but one of them send's the packet to the Base as destination, so the moteView can show it, butthe other one sends the packet as a broadcast and therefore the MoteViiew is unable to show it (it might not be the resaon though, but it's the only difference between the packets these two motes send). Considering that the sapacket is installed on , doe anyone have any idea what is the problem? Thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Different behaviour from the ame image but on different motes
I monitored the network at most for half an hour, and during this period I turned some other motes on and off as well. while those other motes were on, the mote was sending many copies of the health packets (with different sequence mber, fo example from 180 to 188) to one of those motes as the destination address instead of bcasting them (I say this based on details in XSniffer). thanks for your answer though 2009/10/14 Michael Schippling sc...@santafe.edu Sounds like the BCASTing mote may not have been allowed into the mesh-fold yet. I haven't looked at XMESH carefully but it seems to take a while for nodes to become integrated. How long have waited for messages? MS Mohammad S. Hashemian wrote: Hi all, I have two MicaZ nodes and I've installed the same image of MTS310 XMesh application (from MoteWorks framework) on both. MoteView can receive and show health packet from one of them, but not from t other one. When I use XSniffer to sniff the network, I can see both of the motes send health packets but one of them send's the packet to the Base as destination, so the moteView can show it, butthe other one sends the packet as a broadcast and therefore the MoteViiew is unable to show it (it might not be the resaon though, but it's the only difference between the packets these two motes send). Considering that the sapacket is installed on , doe anyone have any idea what is the problem? Thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Different behaviour from the ame image but on different motes
I also should include that if I wait for a long time (15 or 30 minutes) finally the mote becomes the member of the mesh, but this me it sends the health packet many times instead of once (for example 8 or 10 times) and therefore moteView shows 10 rows of health packet from this mote very time. So do you have any idea why this happens? 2009/10/14 Mohammad S. Hashemian m.hashem...@gmail.com I monitored the network at most for half an hour, and during this period I turned some other motes on and off as well. while those other motes were on, the mote was sending many copies of the health packets (with different sequence mber, fo example from 180 to 188) to one of those motes as the destination address instead of bcasting them (I say this based on details in XSniffer). thanks for your answer though 2009/10/14 Michael Schippling sc...@santafe.edu Sounds like the BCASTing mote may not have been allowed into the mesh-fold yet. I haven't looked at XMESH carefully but it seems to take a while for nodes to become integrated. How long have waited for messages? MS Mohammad S. Hashemian wrote: Hi all, I have two MicaZ nodes and I've installed the same image of MTS310 XMesh application (from MoteWorks framework) on both. MoteView can receive and show health packet from one of them, but not from t other one. When I use XSniffer to sniff the network, I can see both of the motes send health packets but one of them send's the packet to the Base as destination, so the moteView can show it, butthe other one sends the packet as a broadcast and therefore the MoteViiew is unable to show it (it might not be the resaon though, but it's the only difference between the packets these two motes send). Considering that the sapacket is installed on , doe anyone have any idea what is the problem? Thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] convert from MTS310 raw data to Celsius
Hey guys, does any one know how can I convert the thermistor raw data for temperature from ADC to Celsius degrees? I receive MTS310 thermistor reading data in my program and I want to convert them to Celsius degrees, but I don't have the converting algorithms, I found some functions like the one here: https://www.millennium.berkeley.edu/pipermail/tinyos-commits/2004-August/004926.htmlbut it wasn't helpful, I implemented mts300_convert_thermistor_temperature function but the result was different than the one which MoteView shows!!! Thanks, Mohammad -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] problem with transmission
Thanks Urs for your reply, I don't think if this would be the case, because first of all if this problem was because of XMesh sequence number, this would happen for every mote, while this problem just happened for 7 or 8 motes out of 10. The second point is that after this problem happens to a mote, regardless of the program that I install on that mote afterward (either my own program or XMTS310) and the mote id which I assign to it, the mote can not find the basestation and send the data, so it somehow shows that something happens to the mote's hardware or My own idea was that maybe in some part of my program, I change the transmission power of the mote incidentally and it causes lower sending and receiving power, so the mote can not receive server messages anymore and the sent messages by the mote are not strong enough to receive to the server. Do you think if this can be the case, and is there any way to check it? BTW if you think my problem is still ambiguous, I can redescribe it in a better (and probably longer :D) way. Mohammad 2009/6/12 Urs Hunkeler u...@gmx.ch Hi Mohammad, After reading your original description of the problem, I think that an intermediate node (e.g. the basestation) does not realize that the nodes have been reset. I think that XMesh uses sequence numbers in their packets. After a node has been reset, maybe it starts over again with the sequence numbers and the basestation thinks that the transmissions are in fact old retransmissions and discards them. Cheers, Urs Mohammad S. Hashemian wrote: Hello again guys, No reply for this problem? even any thoughts or clues? maybe I wrote it too long, my guess is the transmission range and communication power of the nodes gets less and less by passing time. has anyone faced with such a situation ever? does anyone has any thoughts about this? BTW I do lots of broadcasting in my program (one at every 6 seconds) can this be a reason for the problem? 2009/6/5 Mohammad S. Hashemian m.hashem...@gmail.com Hi all, I ran into a very weird problem recently. I was using Crossbow MoteWorks framework for writing a program and installing it on some MicaZ motes. The program was sensing some data from MTS310 sensor board and report them to the base station. After writing the code, I picked some new MicaZ motes and installed the program on them, everything was working fine. After one day I had to reset the motes to change their battery, when I turned them on again, most of them (around 80%) couldn't join the network alone, i.e. if I was just turning that mote on alone with server, the mote couldn't find the server, even though they were right next to each other! But when I was picking another fresh new mote and installing my program on it and putting it between the old mote and the server, the old mote could create a two-hop network and send it's data to the server via the new mote! I checked the old motes with XMTS310 program (the one which ships with MoteWorks framework), but the old motes were just collecting the data and sending the packets, but server never could receive those packets from old motes (probably because the wireless transmission power of the old motes were too low that server couldn't receive them!) Does any one have any idea or any clue that what might be the source of this problem? I really appreciate any response. Thanks in advance, Mohammad -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] problem with transmission
Hello again guys, No reply for this problem? even any thoughts or clues? maybe I wrote it too long, my guess is the transmission range and communication power of the nodes gets less and less by passing time. has anyone faced with such a situation ever? does anyone has any thoughts about this? BTW I do lots of broadcasting in my program (one at every 6 seconds) can this be a reason for the problem? 2009/6/5 Mohammad S. Hashemian m.hashem...@gmail.com Hi all, I ran into a very weird problem recently. I was using Crossbow MoteWorks framework for writing a program and installing it on some MicaZ motes. The program was sensing some data from MTS310 sensor board and report them to the base station. After writing the code, I picked some new MicaZ motes and installed the program on them, everything was working fine. After one day I had to reset the motes to change their battery, when I turned them on again, most of them (around 80%) couldn't join the network alone, i.e. if I was just turning that mote on alone with server, the mote couldn't find the server, even though they were right next to each other! But when I was picking another fresh new mote and installing my program on it and putting it between the old mote and the server, the old mote could create a two-hop network and send it's data to the server via the new mote! I checked the old motes with XMTS310 program (the one which ships with MoteWorks framework), but the old motes were just collecting the data and sending the packets, but server never could receive those packets from old motes (probably because the wireless transmission power of the old motes were too low that server couldn't receive them!) Does any one have any idea or any clue that what might be the source of this problem? I really appreciate any response. Thanks in advance, Mohammad -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Setting the CC2420 radio range
Hi all, I have a program running on MICAz motes with TOS 1.x (the one which ships with MoteWorks by Crossbow). I want to set the CC2420 radio range to the highest value (31), so at first I used CC2420Controller.SetRFPower to set the power, but after setting the rate again the power drops to 15 (which seems to be the default value, right?). why it changes and how can I set it for the whole program life time? is there any way to set this value at compile time? Thanks Mohammad ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem with transmission
Hi all, I ran into a very weird problem recently. I was using Crossbow MoteWorks framework for writing a program and installing it on some MicaZ motes. The program was sensing some data from MTS310 sensor board and report them to the base station. After writing the code, I picked some new MicaZ motes and installed the program on them, everything was working fine. After one day I had to reset the motes to change their battery, when I turned them on again, most of them (around 80%) couldn't join the network alone, i.e. if I was just turning that mote on alone with server, the mote couldn't find the server, even though they were right next to each other! But when I was picking another fresh new mote and installing my program on it and putting it between the old mote and the server, the old mote could create a two-hop network and send it's data to the server via the new mote! I checked the old motes with XMTS310 program (the one which ships with MoteWorks framework), but the old motes were just collecting the data and sending the packets, but server never could receive those packets from old motes (probably because the wireless transmission power of the old motes were too low that server couldn't receive them!) Does any one have any idea or any clue that what might be the source of this problem? I really appreciate any response. Thanks in advance, Mohammad -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Temp in MTS310 returns 0
Hi everyone, I use the sample program XMTS310 which is provided by xbow for sampling light and temprature, it works fine for light but not for temperature. For temperature, it always returns 0. I read all previous posts about the problem with temperature with MTS310, but non of them could help me make it work. Does anyone knows what's the reason? thanks, -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] probelm with viewing the data in xserve or MoteView
Hi fellows, I was working on a program for MicaZ and I wanted to see all the data that server receives in MoteView, everything was fine and even the program was close to the end, but all of the sudden once that I tried to test my program again, Moteview or XServe didn't show any result anymore. The LEDs on the motes were blinking which meant that everything work fine in motes, but no result in xserve or MoteView. I tested many things, even I installed a fresh version of MoteWorks and MoteView on another PC, and tried to install the lesson_2 example of MoteWorks on a mote to see if it works or not, but still nothing was shown by xserve or moteview. does anyone have any clue about the problem? I thought the programmer (MIB510) or Serial-to-USB cable might has problem, but if they have proble, so why I can program any motes correctly? thanks a lot -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Difference between MODE_ONE_HOP_BROADCAST MODE_UPSTREAM
Hi all,
I use following function in TOS 1.1 to send a packet to the base station:
call MhopSend.send(TOS_BCAST_ADDR,*MODE_ONE_HOP_BROADCAST,*tos_send_msg_ptr,
sizeof(XDataMsg));
and I can catch the sent packet in the base station via receive event as
follow:
event TOS_MsgPtr Receive.receive(TOS_MsgPtr msg, void* payload, uint16_t
payloadLen)
{
// codes for handling received packet
}
but when I change the send function to the following one (change the second
parameter):
call MhopSend.send(TOS_BCAST_ADDR,*MODE_UPSTREAM,* tos_send_msg_ptr,
sizeof(XDataMsg));
the receive event in base station cannot catch the sent packet anymore,
while some softwares like MoteView can show that the packet is received in
the base!!!
My wiring for Receive component is as follow:
GeminiBaseM.Receive - MULTIHOPROUTER.Receive[AM_XMULTIHOP_MSG];
and wiring for MHopSend in mote's code is:
GeminiMotesM.MhopSend - MULTIHOPROUTER.MhopSend[AM_XMULTIHOP_MSG];
Does anyone have any clue about how can I catch the sent packet in base
station, while I'm sending the packet using MODE_UPSTREAM as second
parameter?
thanks very much
--
Mohammad S. Hashemian
Research Scholar/DISCUS Lab
Department of Computer Science
254.2 Thorvaldson Building
University of Saskatchewan
(306)966-1947
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with gathering data at base
Hi all, I have a program that senses some data and sends them to a base station. I installed the base station program on a mote which is attached to the MIB510 and via that is connected to a computer. But I don't know how can I see the data that my base station receives. I tried MoteView and XSniffer softwares but non of them showed me the received data (while I tried to write my program based on XMesh samples). By the way, I use Micaz. thanks ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problem with gathering data at base
Thanks Peter, I'm sure that I receive data, coz related LED blinks and also I receive sent ACK in source node. Actually I used XMTS310 source code in XMesh sample application of Crossbow and changed it in order to sense my desired data and send them back to the server. I deleted some parts of code like these lines: command result_t PowerMgrEnable(); command result_t PowerMgrDisable(); command void health_packet(bool enable, uint16_t intv); command HealthMsg* HealthMsgGet(); now I installed the application in one mote and the original XMTS310 application in another mote. The MoteView can receive data from the original one, but not from mine!! Do you have any idea that what can be the problem? I'm also somehow in rush to finishing this program and I haven't enough time to write a new application from scratch to listen to data from base, so I have to use MoteView or other softwares like XSniffer! Thank you very much 2009/2/26 Peter Jun ju...@uc.edu first try java net.tinyos.tools.Listen If you are not getting anything that means you are not receiving anything. On Thu, Feb 26, 2009 at 1:20 PM, Mohammad S. Hashemian m.hashem...@gmail.com wrote: Hi all, I have a program that senses some data and sends them to a base station. I installed the base station program on a mote which is attached to the MIB510 and via that is connected to a computer. But I don't know how can I see the data that my base station receives. I tried MoteView and XSniffer softwares but non of them showed me the received data (while I tried to write my program based on XMesh samples). By the way, I use Micaz. thanks ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Jung Hyun JUN Ph.D Student University of Cincinnati ECECS Dept CDMC Lab, PO Box 210030 Cincinnati, OH 45221-0030 -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] how to find out sendDone is for which send command?
Hi all, In my program I use send command (in MhopSend component) three or more times. When the sendDone event is fired, I want to know that this sendDone is for which send command. How can I figure out this? In other words, how can I access the sent data in sendDone command? I tried to use data field of TOS_MsgPtr argument (m-data), but it seems that its data is different than what I expect! thanks ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] The problem with reading and writing constantly to/from EEPROM
Hello everyone, I'm working on a program which senses some data and writes them on EEPROM (one line per one set of data) via LoggerWrite.append and right after writing, I read them and send them to another mote via LoggerRead.read and MHopSend. every thing work fine at first 2 or 3 minutes, but after that, the data that I read from EEPROM is not correct and is corrupted! even when I write some constant numbers instead of sensed data, after 2 or 3 minutes the data which I read is not the same constant numbers. Does anyone have any clue about the reason? Am I supposed not to write in special places of EEPROM? I forgot to say that I use Micaz and TinyOS 1.1 Thanks very much for your help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] The problem with reading and writing constantly to/from EEPROM
Hello everyone, I'm working on a program which senses some data and writes them on EEPROM (one line per one set of data) via LoggerWrite.append and right after writing, I read them and send them to another mote via LoggerRead.read and MHopSend. every thing work fine at first 2 or 3 minutes, but after that, the data that I read from EEPROM is not correct and is corrupted! even when I write some constant numbers instead of sensed data, after 2 or 3 minutes the data which I read is not the same constant numbers. Does anyone have any clue about the reason? Am I supposed not to write in special places of EEPROM? I forgot to say that I use Micaz and TinyOS 1.1 Thanks very much for your help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Ask multicast routing Syntax on TinyOS V1.0 / v1.1.10 (Urgent needed)
Well, there is lots of tutorial out there, like the documentations by Crossbow which has some samples about this, or documentation of tinyOS. I don't know exactly how many features you want to write for your program, but just a program that sends a packet through some nodes is not very hard, you can easily find some samples about this in Crossbow documentation. 2009/2/11 ma. pratama spidol_perma...@yahoo.com Hi My name is Arif and now i'm working on my final project on multicast routing in wireless sensor networks.. Can you tell me how to program the mote and the base station for doing multicast ?? i'll be first try to use 5 mote which is 1mote for source node, 2 mote for middle node, and 2 base station as receiver. I confuse on how to use the program on TinyOS that this is my first time using the program. For your information my TinyOS version is v1.0. and i'll use the MicaZ as the mote and MIB600 as the base staion. Can you give me the program tutorial or the exact program for the multicast on TinyOS v1.0. Can u please help me with this??I really really need the syntax program... I'll be very appreciating your help..thank you.. Regards Arif ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Mohammad S. Hashemian Research Scholar/DISCUS Lab Department of Computer Science 254.2 Thorvaldson Building University of Saskatchewan (306)966-1947 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Sending packet by a node outside of base's tranmission range
Hi everybody, I wanted to create a regular network of micaz sensors that each node should create a packet and send it to the base. Well, it seems very simple, while each node is in base's transmission range and can send the packet directly to the base every thing is okey. But when the distance between node and base increases, the node couldn't send any packet, while based on XMesh's manual it should use other existing nodes in network as hops and send the packet to the base. I don't know what's wrong with the application? I used the provided sample XMeshCountToLeds application with 3 nodes and tried to send the counter's number in one node to the base via an intermediate node (a route like: SourceNode - IntermedNode - BaseStation) but I wasn't successful! I even tried to implement Intercept and Receive events in intermediate node to see if it can capture the packet from source node or not, but these events didn't fired at all. Can anybody tell me what I'm doing wrong? how I can do this? Many thanks, Mohammad ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
