OpenICE Community Support Forum

Welcome to the OpenICE community support forum. Use this forum for submitting bugs, asking for help, and solving problems you are having with OpenICE software. For ideas, general questions, and conversation please use the discussion forum.

Where is the IDL and how do I use it to generate code?

Jeff Peterson 2 years ago • updated 2 years ago 1
A common question:

Where is OpenICE's IDL and how do you run the tool to generate the C interfaces for the IDLs?
Jeff Peterson 2 years ago
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
Under review

Reading a DeviceIdentity that has a blank model field

Bradford Needham 2 years ago in OpenICE • updated by Jeff Plourde 2 years ago 6
I'm writing an OpenICE app designed to report the on/off state of various Devices. So far I've successfully modified Hello OpenICE code to Subscribe to HeartBeat and DeviceIdentity Topics. The HeartBeat data seems to arrive fine, but the DeviceIdentity data has problems.

In the received DeviceIdentity, the model name is blank, rather than being something like "Pulse Ox (simulated)". I've seen some symptoms that suggest that the model string gets filled in later, but I'm not certain of that.

I wanted to double-check with you that I'm using the correct pattern to read the DeviceIdentity data: I substituted class names in Hello OpenICE code based on some guesswork, so something may be incorrect. Based on the symptom I'm wondering whether I'm not properly telling DDS that I want to read the data contents. I haven't found an example of reading DeviceIdentity in the mdpnp git.

Here is the relevant code (adapted from - I apologize for the formatting. Note that on reception of a Pulse Ox (simulated) DeviceIdentity, the model field is blank.

Thanks for your help,

public void on_data_available(DataReader reader) {
ice.DeviceIdentitySeq deviceIdentitySeq = new ice.DeviceIdentitySeq();
SampleInfoSeq infoSeq = new SampleInfoSeq();
DeviceIdentityDataReader diReader = (DeviceIdentityDataReader) reader;
try {, infoSeq, ResourceLimitsQosPolicy.LENGTH_UNLIMITED, SampleStateKind.NOT_READ_SAMPLE_STATE, ViewStateKind.ANY_VIEW_STATE, InstanceStateKind.ALIVE_INSTANCE_STATE);
* Bug: the model number info seems blank. Example output:
* 2015-09-24 13:50:11 DEBUG IceQos:50 - Loaded default ice_library QoS
* 2015-09-24 13:51:30 ERROR DeviceIdentityListener:75 - Empty model in received DeviceIdentity
* 2015-09-24 13:51:30 INFO HelloIce:75 - ON: manuf: , model: , serial:
* 2015-09-24 13:51:47 INFO HelloIce:75 - OFF: manuf: , model: , serial:
Date now = new Date();
for(int i = 0; i < infoSeq.size(); i++) {
SampleInfo si = (SampleInfo) infoSeq.get(i);
ice.DeviceIdentity data = (ice.DeviceIdentity) deviceIdentitySeq.get(i);
if(si.valid_data) {
if (data.model.length() == 0) {
logger.error("Empty model in received DeviceIdentity");

tracker.sawIdentity(data, now);

} catch (RETCODE_NO_DATA noData) {
// No Data was available to the read call
} finally {
// the objects provided by "read" are owned by the reader and we must return them
// so the reader can control their lifecycle
diReader.return_loan(deviceIdentitySeq, infoSeq);


Under review

How to find Device model number from unique device ID

Bradford Needham 2 years ago in OpenICE • updated by Jeff Plourde 2 years ago 3
I'm writing an OpenICE application to keep track of what Devices are running, and note (on a UI) when they come and go.

So far, I've successfully written code to Subscribe to and Read HeartBeatTopic data, and filtered out the Supervisor data vs. Devices' data. Now that I have unique device IDs from the HeartBeat, I want to ask the model number (and more if I can) of the Device that sent the HeartBeat.

How do I do that?


How to build OpenICE source on BBB

Hyungi Kim 3 years ago in OpenICE • updated by zhangtan 2 years ago 22
Hi, guys!

I was installed Revision C Disk Image and gradle-2.4 and sync to a NTP clock on BBB.
but, jdk 8u33 in Rev.C disk image is not build OpenICE source on BBB. (./gradlew)
The reason is 8u33 is not supported JavaFx. so I reinstalled jdk 8u6.
but OpenICE source is not build on BBB....
I want to build OpenICE source on BBB.
help me how to build OpenICE source on BBB or build reference.

p.s - Your device adapter(BBB) have a rs-232 serial port. my BBB don't have a serial port. T.T

OpenICE device-adapter
Under review

Issues logging in from corporate network

Bradford Needham 2 years ago • updated 2 years ago 2
When I try to login to from our corporate network, the login doesn't fail, but doesn't seem to authenticate - it's as if I'm not logged in.

Logging in from my phone-as-hotspot (no proxy or firewall) works fine.

So I need to find what about or corporate proxy or firewall is preventing my logging into the community site. More info as I find it.
Under review

mindray monitors

Tav Pritesh Sethi 2 years ago • updated by Jeff Peterson 2 years ago 1
Hello, can we expect support for Mindray Beneview series of Patient monitors anytime soon?

Getting waveform data from the Puritan Bennett 840

Rado 3 years ago in OpenICE • updated by Jeff Peterson 2 years ago 6
Hi everyone,

Sorry to keep asking questions, but this one has actually bugged us for a while now. Do you know how to make the Puritan Bennett 840 ventilator output waveform data?

We have tried all ports but all we get is the miscf message with numeric data only. We can't see any options on the ventilator itself either. As far as I understand from the code, the PB demo is also only set up to ask for numeric data.

Any insight you might have will be appreciated.


OpenICE demo-apps
Under review

Alaris PC Infusion Pump

Rado 2 years ago in OpenICE • updated by Tim 2 years ago 3
Do you guys have any experience with Alaris pumps? We have one in the lab but I can't get it to export data. The manuals are not very helpful either - apparently there is some software (also developed by Alaris) that seems to be the only way to export data.


How to host openice ( locally on Win-7

Jegan Kunniya 3 years ago in OpenICE • updated by Alejandro Figar 2 years ago 6
I have cloned the OpenICU (master) branch on my Win-7 and hosted it on IIS7.5. When I visit the OpenICU Webdemo page of hosted website (http://localhost/openice/demo.html), the 'Connecting..' status never changes.

Upon debugging, figured out that the generated '' file is needed under the build folder. Downloaded the same from the OpenICE website ( and then I started getting the following 404 error trace


I don't have NodeJs server running on my machine as I presently don't have any insights on how to use it for OpenICE locally.

Any help is highly appreciated.



What are RTI-dds & OpenSplice for?

Hyungi Kim 3 years ago in DDS • updated by Jeff Peterson 3 years ago 3
Hi, guys!

What are RTI-dds & OpenSplice for? on OpenICE.
I think RTI using the transform of idl to java.
that's right?

I want to know the exact usage.


Jeff Peterson 3 years ago
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.



Jeff Plourde 3 years ago in DDS • updated 3 years ago 0
The OpenICE systems need to track the presence and availability of various devices in the system. There are a lot of possible ways to maintain the known "liveliness" of remote participants. Here are some of the ways we have tried in the past and the solution which we have converged upon during OpenICE development.

  • Participant Liveliness
    • Our first mechanism was to use DDS metadata to track the liveliness of remote participants. In principle this worked but it had several drawbacks and unmet requirements...
      • It may not always be desirable to maintain a 1:1 correspondence between participant and device. For instance a participant accepting connections from bluetooth devices might actually communicate data for a number of such devices through one DDS Participant.
      • Participant meta-data does not usually get relayed between DDS networks. Further, when data is relayed to a remote network (perhaps at the central monitoring or data center scope) it is presented to that network through a new participant local to that network.
      • Configuration of discovery-related parameters is vendor-specific so establishing compatible settings can be difficult.
  • DeviceIdentity instance Liveliness
    • Our next attempt was at using the Liveliness of DeviceIdentity instances to track remote device liveliness.
      • This successfully breaks the undesirable 1:1 correspondence participant and device.
      • The problem here is that DeviceIdentity is not frequently republished. Meaning that once a reader has received a DeviceIdentity instance sample it *will* properly mark that instance "NOT ALIVE" when it fails to communicate a heartbeat; but later when the connection is re-established there is no new sample to communicate and the state of the instance will not become ALIVE until a new sample is produced.
  • A distinct HeartBeat topic
    • To meet our requirements we created a Topic in the system expressly for the purpose of discerning liveliness.
    • By contract devices all must publish a new sample of Heartbeat every two seconds. The sample size is deliberately kept very small; including only UDI and a device type.
    • Because this is "user" level data (and not metadata) from the DDS perspective it will "properly" traverse routes and links between DDS systems.
    • This topic is described in our IDL. Our QoS settings are in a profile called "heartbeat" within ice_library.xml.
    • You can view realtime Heartbeats from devices in our lab on our diagnostics page.
DDS OpenICE demo-apps

​I want to know about the data format received from device.​

Hyungi Kim 3 years ago in OpenICE • updated 3 years ago 3
I want to know about the data format received from device.
Although, i saw the Open Source and Standard Document(ISO/IEEE 11073-10101).
But, i didn't found about that.
What should i reference to?

please help me

Hyungi Kim

OpenICE device-adapter

Philips MX800 Device Adapter Numerics

Thomas Drake-Brockman 3 years ago in OpenICE • updated by Jeff Peterson 3 years ago 11

Since getting our Philips MX800 to connunicate correct with OpenICE, I've noticed that some numerics are not being transmitted.

In particular Respiratory Rate, and Exhaled Carbon Dioxide. Neither of these display when viewing the device through the demo apps, although the EtCO2 waveform does come across:

I did notice that the RR values does seem to be present in the messaged produced when I run hello-openice, such as follows:

unique_device_identifier: OC2rcpaYQdOQnLgTvRH0ZCYya91i71pPsxjK
vendor_metric_id: NOM_VENT_RESP_RATE
instance_id: 34628
value: 22.0
device_time :
    sec: 1432600653
    nanosec: 643000000
presentation_time :
    sec: 1432600562
    nanosec: 0
It's currious that these values don't display in the device adapter view. Also, I definately can't find any references to a EtCO2 numeric in the output. Is this cponsistent with your experience with the MX800?

I noticed that appears to define the numerics and waves that are collected from the monitor. Is it simply a case of modifying this file to include the numerics I require? Or do I have to 'teach' OpenICE or the device adapter about these parameters elsewhere also?

In particular, I'm looking to access NOM_AWAY_CO2_ET (from the Philips Data Export Manual) I'd be most appreciative if you could provide some guidance on how to do so.
demo-apps device-adapter

Controlling Device parameter(s) as Supervisor

Kai N 3 years ago in OpenICE • updated by Jeff Peterson 3 years ago 4

I was looking into your system and already managed to compile the code and run the demo-apps. Now I am wondering, if there is a way to control parameters as a supervisor?
For example: I am running the supervisor app, connect to a (simulated) infusion pump and I want to change a parameter, e.g. the drug (name) or the drug mass.

Are such actions possible within your system?

Best regards,
OpenICE demo-apps

Google Glass on OpenICE

Thomas Drake-Brockman 3 years ago in OpenICE • updated by Jeff Peterson 3 years ago 1

Thanks for all your help setting up device adapters and connecting to OpenICE programmatically. Here's a little video of what we've managed to build!