Hello again, I have debugged the program. Fortunately it is a C based client and I can use GDB. However what I see is that data from the pdu is coming back empty, “0”. How can I know that I am sending the proper request?. I see different choices depending on the versión of CoAP. Any idea on that?. I am using this: coap-client -m get coap://[fec0::2]:61616/sen/temp -T 3a -t binary but I took it directly from the examples, I don’t know what those options mean. I can’t find the meaning anywhere.
Any idea on that?. Thanks. De: Eric Decker Enviado: 05 November 2018 23:30 Para: julio.cal...@gmail.com CC: Tinyos-Help Asunto: Re: [Tinyos-help] Getting temperature using Ppp Router and CoapBlip The remote mote is essentially a block box that is very hard to gain visibility into. the way I deal with this kind of problem is either: 1) put a debugger on the remote mode, set a break point where it does the command processing, capture receiving the command. this will let you bifurcate the problem. or 2) instrument the remote tag so you can grab information from it. You can clearly talk to it. Either way you need to understand what the remote mote is doing. On Mon, Nov 5, 2018 at 3:58 AM Julio Calvo <julio.cal...@gmail.com> wrote: Hello, I have a simple mote network using one telosB as Ppp Router connected to the computer. Then, there is another one running, wireless connected, using CoapBlip application. They are properly talking each other, I can, for example, turn the leds ON (on the remote wireless mote) executing a coap-client command on the PC. This turn on leds representing a 5: echo -e -n \\x05 | ./coap-client -m put coap://[fec0::2]:61616/l -T 3a -t binary -f - However, if I try to GET temperature from that same mote, I am getting no result. The temperature service is properly activated in the makefile: CFLAGS += -DCOAP_RESOURCE_TEMP This is the command I am using ./coap-client -m get coap://[fec0::3]:61616/st -t binary and this is the answer: ./coap-client -m get coap://[fec0::2]:61616/st -t binary \x42\x01\xD6\x42\x11\x2A\x82\x73\x74 send to [fec0::2]:61616: pdu (9 bytes) v:1 t:0 oc:2 c:1 id:54850 o: 1:'*' 9:'st' Nov 05 12:53:47 ** received from [fec0::2]:61616: pdu (4 bytes) v:1 t:2 oc:0 c:164 id:54850 Nov 05 12:53:47 *** removed transaction 54850 ** process pdu: pdu (4 bytes) v:1 t:2 oc:0 c:164 id:54850 Indeed, I don’t really know what would be a good answer and how to “understand” what I am getting in return. Any help would be appreciated. Thank you so much!!. Julio. _______________________________________________ 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
