| Re: [wakaama-dev] Small help required in wakama test client |
|
Hi Hari, maybe you update the LWM2M-TS to „OMA-TS-LightweightM2M-V1_0-20150422-D.doc“, which is the current draft. In that version of LWM2M-TS section c5.1.1
is about „attributes“. The “Name” you want, is the name of the resource. Clear. But I can’t see something in
the LWM2M-TS that describes how a LWM2M client transfers this resource name to the LWM2M server. Do you see something? If not, a LWM2M client seems not to be responsible for the name of a resource displayed by the LWM2M server. So for leshan (LWM2M server displaying the resource names), see Juliens answer. Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn Von: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Hari Hi Achim,
Just to clarify , by 'Name' i mean the 'SMS Tx Counter' under the Connectivity Statistics . But if you see the Object 1024(which is test object) , its resource does not have the name , instead it is just mentioned as Resource 1 , Resource 3. So
this is the name i am talking about. Cheers Hari On Tue, May 5, 2015 at 12:50 PM, Kraus Achim (INST/ESY4) <Achim.Kraus@xxxxxxxxxxxx> wrote: Hi Hari, the „name“ mentioned in TS 5.1 .1 seems for me to be the name of the attribute e.g. „Greater Than“,
not the resource. I can’t see, how the name of the resource is transferred in LWM2M. So the „(yet)“ may be for a „little“
longer : - ) … Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn Von:
wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Hari
Hi Achim ,
Thanks for the hint. Yes now I got the question cleared about the Name attribute. So as of now waakama does not support it (yet)
and changing of the json will help me. But let me see how that works. As for the second, yea now i understood as to how the system works. I will try implementing it from the client code. I actually dont
want to monitor the system time. i was just trying to create a dynamic resource for testing and the easiest one was the sys time and hence used that.
I will get back with the updates !! Thanks a lot people :)
Cheers
Hari
On Tue, May 5, 2015 at 11:47 AM, Kraus Achim (INST/ESY4) <Achim.Kraus@xxxxxxxxxxxx> wrote: Hi Hari, your first question is related to leshan, not wakaama. So just a hint: There is a json file, containing the definitions of the supported objects. /leshan-core/src/main/resources/oma-objects-spec.json Add your definition accordingly. May be Julien can help you more. Your second question: The wakaama core implements the communication, the resource are intended to be implemented in the client, and wakaama includes a „test“ client for that. Though the client maintains the resources, the client is responsible to inform the wakaama core of changes (e.g. sensor values) as David explained. According that, you may call lwm2m_resource_value_changed for the system time every second, if your application want really to observe the system time. But I’m not sure, if you really want to spend your CPU power and bandwidth for observing the system time. Mit freundlichen Grüßen / Best regards Achim Kraus Bosch Software Innovations GmbH Communications (INST/ESY4) Stuttgarter Straße 130 71332 Waiblingen GERMANY Tel. +49 711 811-58139 Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn Von:
wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Hari Hi David ,
Thanks for the warm welcome and the quick reply. Really appreciate it. :) Now let me briefly explain what I am trying to
do.
The battery level change is being done normally. But for instance u have to observe a particular resource and in that case how will
u dynamically do it ? PS: Sorry for the rookie type questions. I am learning. Thanks in advance ! On Mon, May 4, 2015 at 7:28 PM, Navarro, David <david.navarro@xxxxxxxxx> wrote: Hi Hari and welcome, I’m not sure to understand your first question. If you are talking about the “Name”
attribute (LWM2M TS §5.1), wakaama does not support it (yet). Otherwise Resources in LWM2M Objects are identified by a 16-bit unisigned integer. When a Resource value changes, you need to call
lwm2m_resource_value_changed(lwm2m_context_t
* contextP, lwm2m_uri_t * uriP);
with the URI of the resource, its instance or its object. The core will then send notifications to any server monitoring this resource. If you look at the test client code, when the battery level is updated or when the user enter the command-line
command “change”, the function handle_value_changed() is called. This function calls lwm2m_value_changed() at line 180. Regards, David Navarro From:
wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hari Dear All ,
It is wonderful to see wakama developed. I have been following it right from the days when it was called 'liblwm2m'.
I have been trying to port it to embedded devices like the Arduino , Open Picus and others.
Great to see the wakama project up and running with observable properties too. I am in a process of creating a
custom object with some static and dynamic resources and have a few questions on. Please help me with those. here are the problems that i am facing :
Please let me know about these two
Thanks and regards Hari Raghav
--------------------------------------------------------------------- This e-mail and any attachments may contain confidential material for
|