OpenICE Community Support Forum

Hi,

First thank you very much Vasanth for helping Usharani to get started. Our intent in setting up this community site was to help people (including ourselves) learn from one another so that's exciting to see.

To build on Vasanth's answer since we are building a 'platform' it can be confusing because there is no singular use for the system. What you are seeing when you run the supervisory software now are a number of apps we've developed as demonstrations of the capability of the platform. We are working on documentation of these apps to coincide with our version 0.6.2 release this week or next. However these apps are exemplars and are not the end goal of our project in and of themselves.

Currently a number of people are interested in using our prototype platform to develop their own clinical applications. We do offer one of the only open source projects for connecting to medical devices of which I'm aware; but more importantly than mere integration we allow people to tap directly into a near realtime data stream from those devices for their own purposes. Another unique characteristic of our program is that we are actively seeking the feedback from those developers to guide the future development of the platform to understand what is required of a next generation platform to support next generation applications. The process is chaotic but in the end the answer to "what is required of this platform?" cannot be found in our lab alone; it can only be answered by the creativity of future application developers.

A necessary precursor to the development of a wide variety of applications is the collection of clinical data. A number of community members are pursuing data collection projects and we are helping to develop apps to serve this purpose practically (beyond basic demonstrations and examples). Ourselves we are engaged with a couple of clinical centers directly to help show the utility of OpenICE for bootstrapping itself; i.e. collecting high resolution, time-aligned, near real-time data that will be needed to develop newer apps that make use of such data.

There is more overview information available on our website. For example we have videos including an overview that helps to lay out the landscape in which our work resides that you might find helpful.
https://www.openice.info/#videos

And to reiterate what Vasanth already said please feel free to post questions about any specific objectives you might have so that the community can help provide you with guidance and help.

Thank you
Jeff Plourde

The IDL is found in our git repo - the IDL is found under /master/data-types/x73-idl/src/main/idl/ice/ice.idl.

To generate code for the IDL, we use rtiddsgen. The code generator is documented here.

At the command line, enter:

rtiddsgen -language C -inputIdl /path/to/repo/data-types/x73-idl/src/main/idl/ice/ice.idl

Vasanth,

Thank you very much for answering your own question! Did it take any unusual steps to succeed? afaik the newer beagles with stock debian will automatically boot from the microsd (without depressing the "option" button)... has that been your experience as well? Also when you get a moment could you add a link to the windows disk imager tool you used? or it is built into newer windows versions?

For anyone else reading it the disk image Vasanth is referring to is posted here:
https://www.openice.info/device-adapter-setup.html#required-software


Thank you
Jeff Plourde

Hi Hyungi,

DDS is a distributed system abstraction layer that passes messages between the OpenICE nodes. DDS is technically a standard with commercial implementations distributed by RTI and PrismTech (OpenSplice). OpenICE is distributed with a community edition of RTI DDS.

More information about how we use DDS in OpenICE can be found in the working-draft of OpenICE App Architecture Description.

Thanks,
Jeff

Hi Alejandro

We don't recommend building the codebase directly on embedded devices. It would be technically possible except that earlier this year Oracle withdrew JavaFX support from the JDK for embedded ARM devices in 8u33. More information about their decision can be found here.

That said we *do* recommend running "device adapters" on the beaglebone black platform from the console. In this mode JavaFX is not required at runtime. This is why OpenICE built on an x86_64 platform can run on a beaglebone black. So the problem, really, is that our console-oriented code and JavaFX code are both housed in the interop-lab/demo-apps project and the build process expects JavaFX (hence the error you have received).

We'd like, in the future, to segregate JavaFX components in a separate artifact and provide build options that exclude those JavaFX components to allow a build on ARM. Based on our current workload and available resources it will be a few months before anyone here is able to take on this project. We'd welcome help from anyone in the community who would like to help refactor the codebase in this way.

For more information on building on an x86_64 machine and deploy to an ARM device see a previous answer:
http://community.openice.info/topic/805647-how-to-build-openice-source-on-bbb/

Thank you very much
Jeff Plourde