Eclipse Community Forums: OM2M » Porting OM2M hardware requirement

Home » Eclipse Projects » OM2M » Porting OM2M hardware requirement(Porting the GSCL on our hardware device requirement)

Show: Today's Messages :: Show Polls :: Message Navigator

Porting OM2M hardware requirement [message #1651638]

Thu, 05 March 2015 12:19

Owen Wu

Messages: 4
Registered: March 2015

Junior Member

Hi,

I have a question about the OM2M porting requirement.
We want to porting the GSCL on our hardware device, what is the hardware requirement?

E.X.: CPU clock, Memory size, DDR ...etc.

Thanks,
Owen

[Updated on: Fri, 06 March 2015 02:06]

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1653747 is a reply to message #1651638]

Fri, 06 March 2015 11:14

Mahdi Ben Alaya

Messages: 229
Registered: November 2013

Senior Member

Hello Owen,

The average hardware requirement for the gateway are:
- CPU: 500 MHz
- RAM: 128 MB
- Storage: 100 MB

However, the hardware requirement depends on your scenario.
For example, if you need to
- store all your sensor data locally in the gateway, then you have to increase the storage capacity, otherwise you can even work with very small storage memory.
- handle a big number of request by the gateway, then you have to increase the CPU and RAM capacity.

Actually, I am using OM2M with Beaglebone Black and Raspberry Pi and I am happy with it since it shows good performance.

Last point, in the next release of OM2M planned for 31 of march 2015, the current database DB4O will be replaced with a JPA layer based on EclipseLink to enable our users to chose their own database solution. By default OM2M will come with the H2 database that provides better performance.
You can take a look at our roadmap for more details: https://wiki.eclipse.org/OM2M/Roadmap

Hope this can help,
Mahdi

[Updated on: Fri, 06 March 2015 11:15]

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1655614 is a reply to message #1653747]

Sat, 07 March 2015 05:41

Owen Wu

Messages: 4
Registered: March 2015

Junior Member

Hi Mahdi,

Many thanks for your reply.
The average HW requirement information is helpful for us.
We will evaluate the requirement on our scenario.

Thanks,
Owen

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1662958 is a reply to message #1655614]

Tue, 10 March 2015 07:40

Owen Wu

Messages: 4
Registered: March 2015

Junior Member

Hi Mahdi,

One more question, we want to run OM2M on our device, but we still have some own application/function on our gateway device.
Do you have any suggestion to integrate the OM2M and own application/function on the same gateway device?
Our application/function is not Java API.

Thanks,
Owen

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1665431 is a reply to message #1662958]

Wed, 11 March 2015 08:19

Owen Wu

Messages: 4
Registered: March 2015

Junior Member

Hi Mahdi,

Or using the Java Native Interface(JNI) to integrate both?
Does OM2M has any integration OM2M and Linux C API/Driver document or SDK?

Thanks,
Owen

[Updated on: Thu, 12 March 2015 08:58]

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1671461 is a reply to message #1665431]

Fri, 13 March 2015 16:15

Mahdi Ben Alaya

Messages: 229
Registered: November 2013

Senior Member

Hello Owen Wu,

A direct answer is no.
However, the question you are raising here is dealing more with programming language interoperability.
In OM2M, we provided a tutorial explaining how to extend OM2M with new JAVA/OSGi plugins: http://wiki.eclipse.org/OM2M/Developer
Then, you can implement any mechanism in your new plugin to get data or to send command from/to your specific devices.
Concretely to share data between a C and a JAVA program, there is at least 4 solutions:
1 - Store data on files,
2 - Send data using sockets,
3 - directly call C code from Java using the Java Native Interface (JNI).

However, if you have the possibility to update the code of your device(which is not always the case), then there is no need to add a new plugin.
You can simply add a HTTP or CoAP client to your device which will create required resources on OM2M.

If you need more information, you can give more details about your devices and scenario.

Mahdi

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1701260 is a reply to message #1671461]

Fri, 10 July 2015 10:23

Martin Weiss

Messages: 1
Registered: July 2015

Junior Member

there are a lot of microporcessors that do not have the capability to run java...some seriously constrained devices....Like the processors inside the Sierra Wireless GSM modules for example..and a host of other Atmel and Coretex processors used as embedded controllers for telemetry devices.

So running a GSCL on a C based processor is very important to the hardware community to enable them to use appropriate hardware ...where a Raspberry or Beaglebone will just not be appropriate.

A GSCL C library would be fantastic. Are you aware of anyone that is or has ported the GSCL to C?

PS its not a question of data exchange between languages here...its implementing the sensor electronics, the control logic as well as the communications (say GSM on a single piece or hardware with a single microprocessor that typically has no OS...or a very limited one.....(not like the Raspberry which is typically orders of magnitude more expensive if you going to mass produce devices)..

I hope this helps somewhat ...from a hardware perspective Smile

regards

Martin

Report message to a moderator

Re: Porting OM2M hardware requirement [message #1701344 is a reply to message #1701260]

Sun, 12 July 2015 09:07

Mahdi Ben Alaya

Messages: 229
Registered: November 2013

Senior Member

Hello Martin,

I got your point. You are absolutely right.
I will talk with my team about a lightweight C version of OM2M with minimal capabilities.
I have to check also how to minimize the maintenance work required to maintain this version.

Thank you for your valuable comment.
Mahdi

Report message to a moderator

Previous Topic:	CoAP interworking, actuation methods.
Next Topic:	Usage of om2m middleware

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 27 03:57:47 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter