Support / OpenICE Community

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.

Or leave us a private message

No similar topics found.

0 similar topics found. Vote for them.

Unmarked topics

60

Active topics

24

Closed topics

41

Answered

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

10 years ago in OpenICE • updated 10 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

Thanks
Hyungi Kim

OpenICE device-adapter

Vote

Answered

Philips MX800 Device Adapter Numerics

10 years ago in OpenICE • updated by 10 years ago • 11

Hey,

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
metric_id: MDC_VENT_RESP_RATE
vendor_metric_id: NOM_VENT_RESP_RATE
instance_id: 34628
unit_id: MDC_DIM_RESP_PER_MIN
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 intellivue.map 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

Vote

Answered

Controlling Device parameter(s) as Supervisor

10 years ago in OpenICE • updated by 10 years ago • 4

Hi,

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,
Kai

OpenICE demo-apps

Vote

Answered

Google Glass on OpenICE

10 years ago in OpenICE • updated by 10 years ago • 1

Hey,

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!

Cheers,
Thomas

Vote

Answered

How to start working with OPENICE. Basics to start

10 years ago in OpenICE • updated 10 years ago • 5

Hi,

I am new to this community. I am not able to follow to work with OpenICE. I installed OPENICE. I can able to see the applications .
And how to work with these applications.

very confusing...
please help

OpenICE

Vote

Answer

10 years ago

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

Answered

Interfacing with OpenICE from Java

10 years ago in OpenICE • updated by 10 years ago • 3

Hey,

Having now managed to get my Philips MX800 to talk to OpenICE (thanks for the help!) I've moved on to interfacing with OpenICE, following the example in hello-openice.

Currently, with OpenICE 0.6.2 and the latest hello-openice (in which I have ugraded OpenICE to version 0.6.2), I'm running into the following error:

WARN | PRESPsService_isRemoteWriterLocalReaderCompatible:incompatible destination order kind: writer 0 reader 1

I've started porting some of the code from hello-openice into my application, and I'm getting the same error - so it's probably best to get hello-openice working before I go much further.

Cheers,
Thomas

Vote

Answered

OpenICE Execution Ubuntu - Beginner

10 years ago in OpenICE • updated by 10 years ago • 3

Hi!
I am glad to have opportunity to communicate with you all.
I am planning to implement testbed as a network of OpenICE devices that all of them are Ubuntu/Debian VMs. I installed JDK 1.7.0-79 as you can see below:

~/Downloads/OpenICE-0.6.2/bin$ java -version
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

When I try to execute OpenICE, I face following error, I highly appreciate your help and attention in advance.

~/Downloads/OpenICE-0.6.2/bin$ ./OpenICE
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/mdpnp/apps/testapp/Main : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)

OpenICE

Vote

Answered

IntellivueSerial driver throws an error in OpenICE 0.6.1

10 years ago in OpenICE • updated by 10 years ago • 3

device-adapter

Vote

Answer

10 years ago

Hi Vasanth,

Please try version 0.6.2. We've corrected a minor bug with a major impact that we think caused this error. Sorry for the inconvenience and time delays. Let me know if the new version works.

Jeff

Answered

Not able to run OpenICE as a service in BBB rev C (new Debian Image)

10 years ago • updated by 10 years ago • 4

Hi,

After loading new Debian image (Open ICE version 0.6.1), OpenICE.exe doesnt run if started as service.

Please advise.

Regards

Vote

Answered

Order BeagleBone Black

10 years ago • updated by 10 years ago • 5

Hi Jeff,

I would like to place an order for BeagleBone Black to connect Philips MP70 monitor.
Can BB box be shipped to India ?

Regards
Vasanth

Vote

Answered

Availability of new disk image

10 years ago in OpenICE • updated 10 years ago • 3

Hi Jeff,

Can you please provide us the link to download new disk image.

Thanks
Vasanth

Vote

Answer

10 years ago

Thanks for watching out for it!

For the record the new images are linked from:
https://www.openice.info/device-adapter-setup.html#required-software

I see that you've got other questions that hopefully we can answer all together. So you know in addition to beagles connected to med devices we've got about 14 RevC beagles (pictured) and 7 RevBs currently running simulators in a 'testbed' in our lab and one of my colleagues is working on manageability and devops strategies for those beagles once they get into "the field". Also another colleague has installed different types of real-time clocks into two of the beaglebones (marked with white labels in the picture). As you know a beaglebone with a realtime clock would ameliorate a lot of issues with our 100% NTP-dependence.

We are still doing our own testing but I'm curious your opinion about the switch to Debian. I made it because Debian is now the "stock" install on the beagles. In addition the USB networking "gadget" is terribly useful for debugging (i.e. being able to ssh into the beagle over the USB connection) since we've disabled the console on the RS-232 port in favor of its use for med device connectivity. We were even thinking we could make modifications to the default "start" webpage that the beagle hosts for its PC peer to help make the process of getting started with beagles and OpenICE easier.

What do you think about the choice? There are definitely advantages to ubuntu as well but at this time Debian seemed to me to have more.

Thanks
Jeff Plourde

Answered

microSD card formatted as FAT32

10 years ago in OpenICE • updated 10 years ago • 3

Hi,

Linux image doesnt appear to boot from microSD card (formatted as FAT32).
Has anyone faced the issue before ?

Regards

Vote

Answer

10 years ago

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

Answered

IntelliiVue Device Adapter

10 years ago in OpenICE • updated 10 years ago • 9

Hi Jeff,

I have a Philips Intellivue MP5 monitor and want to connect to openICE using IntelliVue Serial Adapter.
Since the protocols are same for all Intellivue series monitor, I am assuming this should work

Please confirm...

My setup details:
Running demo apps software on my windows machine.
Started local device adapter of device type Intellivue Serial RS232/MIB
Connected MP5 monitor through a USB to Com Port Adapter which in turn is connected to my RJ45 to DB9 female connector (setup according to the pin diagram).

Does this setup work? I am hoping to see waveform data from MP5 monitor but I see the device in negotiating state and not proceeding further...Am i missing something ?

Please advise.

Regards
Vasanth

Vote

Answered

Custom Data Consumer

10 years ago in OpenICE • updated 10 years ago • 9

Hi,

I'm involved in the development of a trial that involves streaming data from our Philips IntilliVue monitors to a head-mounted device.

I noticed that you'd already gone to the effort of implimented Phillips' Data Export Protocol, which is a huge relief!

Would you suggest:
a) Running an OpenICE network with the adapter for the IntelliVue and then developing a OpenICE 'consumer' for our device, or,
b) Directly interfacing with your implimentation of the Phillips' Data Export Protocol.

I'd ultimately prefer option A, as it would be more flexible, although I'm currious to know if there's any documentation or Java interface available for doing so.

Cheers,
Thomas

Vote

Fixed

OpenICE Demo-apps on WinXP (32 bits)

10 years ago in OpenICE • updated by 10 years ago • 4

Hi Jeff,

Using your advice, I've been able to build my own cable to connect with a Philips MP70 monitor, and with a few modifications to AbstractDevice.java, I've been able to build my own version in Windows 7 that can record waveform data to a csv file. (Thank you for your help!)

However, I need to deploy my code on a Windows XP (32 bit) machine. I run into the following error whenever I try to run ICE_Device_Interface on WinXP (for example, one of the simulated waveforms):

2015-03-20 12:38:42,078 | WARN | Unable to load native library nddscore | com.rti.dds | main
java.lang.UnsatisfiedLinkError: mdPNP\demo-apps-0.5.0\demo-apps-0.5.0\bin\.nddshome\lib\i86Win32jdk\nddscore.dll: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source)
at com.rti.dds.util.NativeInterface.extractAndLoad(NativeInterface.java:482)
at com.rti.dds.util.NativeInterface.loadNativeLibrary(NativeInterface.java:172)
at com.rti.dds.util.NativeInterface.loadNativeLibraries(NativeInterface.java:139)
at com.rti.dds.domain.DomainParticipantFactory.<clinit>(Unknown Source)
at org.mdpnp.apps.testapp.RtConfig.loadAndSetIceQos(RtConfig.java:165)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:591)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1111)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1006)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:298)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:762)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
at org.mdpnp.apps.testapp.Configuration.createContext(Configuration.java:147)
at org.mdpnp.apps.testapp.DeviceAdapter$DeviceAdapterCommand.execute(DeviceAdapter.java:65)
at org.mdpnp.apps.testapp.Main.main(Main.java:51)

This occurs both with my version, and when running the 0.5 code downloaded from sourceforge. When I look in .nddshome, the i86Win32jdk directory only contains the nddscore.dll.manifest file, but none of the other ndds* files are present. I do have the Microsoft Visual C++ 2005 ATL Redistributable installed on the target machine. I have tried manually copying the needed files over, but the .nddshome directory is cleared at runtime.

Do you have any ideas what might be causing this error? If I needed to regenerate the nddsjava-5.1-mdpnp.jar file, how could I do so? (I have also tried to install the RTI packages on my development machine, if that helps.)

Thanks!

Regards,
Nathan

Vote

Customer support service by UserEcho

OpenICE Community Support Forum

60

24

41

Recently updated feedback 125

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

Philips MX800 Device Adapter Numerics

Controlling Device parameter(s) as Supervisor

Google Glass on OpenICE

How to start working with OPENICE. Basics to start

Interfacing with OpenICE from Java

OpenICE Execution Ubuntu - Beginner

IntellivueSerial driver throws an error in OpenICE 0.6.1

Not able to run OpenICE as a service in BBB rev C (new Debian Image)

Order BeagleBone Black

Availability of new disk image

microSD card formatted as FAT32

IntelliiVue Device Adapter

Custom Data Consumer

OpenICE Demo-apps on WinXP (32 bits)

Forums

Knowledge bases

Categories

Community stats

3
Support agents