|
Re: OM2M GSCL on Raspberry PI or Android possibility [message #1403811 is a reply to message #1403757] |
Mon, 28 July 2014 00:06 |
Mahdi Ben Alaya Messages: 229 Registered: November 2013 |
Senior Member |
|
|
Hello han,
I am usually using OM2M on Beaglebone Black as you can see in this demo: https://www.youtube.com/watch?v=pPTAdJZpnsk
OM2M is a java platform running on top of an Equinox OSGi runtime. So, nothing special to do to run OM2M on Raspberry PI, just be sure to have java version 7 and that's all. (Use the same command mentioned on the wiki)
We developed an android version of OM2M, not yet published on Eclipse cause we need to do more tests. We faced some issues with the JAXB library (XML object mapping) which is not included in android. As alternative, we replaced JAXB with the SimpleXML library.
Don't hesitate to give me some feedback about your experiments.
Mahdi
[Updated on: Mon, 28 July 2014 00:11] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: OM2M GSCL on Raspberry PI or Android possibility [message #1498317 is a reply to message #1496926] |
Thu, 04 December 2014 10:18 |
Mahdi Ben Alaya Messages: 229 Registered: November 2013 |
Senior Member |
|
|
Hello,
1) Yes this is a typical M2M scenario, that can be easily implemented using OM2M.
2) You have two choices depending on your need.
a) (Easy) Run a light HTTP or CoAP device application (including client and server) on Android for your home controller. This application will interact remotely with the NSCL or GSCL using the REST API. In this case the NSCL or GSCL should run in a separate machine.
b) (Advanced) Run the SCL on Android, then register your device applications locally. In this case, the Android becomes a part of the service layer (DSCL) and offers services to applications based on the REST API. However, the current version of OM2M do not natively support Android . Some changes should be made.
Hope this can help.
[Updated on: Thu, 04 December 2014 10:20] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05173 seconds