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.

- Is it?
- Inappropriate
- Spam
- Duplicate

Openice device simulation is not happening with device adapter and supervisor

9 years ago in OpenICE • 0

Hi I also have a similar kind of problem, I have installed latest openice software and running on two windows laptops. When try network simulation from one laptop using device adapter on the other laptop supervisor we can see the simulated devices (Both the laptops are connected to Wi-Fi network).

But when i use one laptop connected to wi-fi and other laptop connected through Ethernet ( Virtual Machine) the device simulation is not happening.

Can any one please suggest me what steps i have to take to make it working.

Thanks,

Phaninder

Vote

Under review

mdpnp on beaglebone black debian jessie

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

I have a Beaglebone Black with debian jessie. I've installed Oracle Java. Then I've cloned mdpnp project from github. Then I've tried to build demo-apps with gradlew and I've got the following error:

Defining custom ?build? task is deprecated when using standard lifecycle plugin has been deprecated and is scheduled to be removed in Gradle 3.0

FAILURE: Build failed with an exception.

* Where:

Script '/home/debian/mdpnp/interop-lab/demo-apps/javafx.plugin' line: 60

* What went wrong:

A problem occurred evaluating script.

> Could not find JavaFX Packager Tools, please set one of [jfxrtDir in Gradle Properties, JFXRT_HOME in System Environment, JAVA_HOME in System Environment, java.home in JVM properties]

Please advice,

Thanks,

demo-apps device-adapter

Vote

Answer

10 years ago

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

Under review

Phillips MP5 intellivue RS232 to serial cape to bbb

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

Hello,

we would like to get OpenICE working for the serial port of a Phillips MP5, but are having some trouble. Currently, the set up is

MP5 RJ45 port > RJ45 to RS-232 adapter > serial cape > bbb > router > computer

The bbb is running Rev C from this page https://www.openice.info/docs/4_device-adapter-setup.html
The computer is running OpenICE 0.6.3.
OpenICE shows "Connecting (initializing RS-232 to UDP adapter)" and the monitor displays "Unsupported LAN" when plugged into the LAN port. We cannot use a LAN to the monitor in our application, but it would be reassuring to know that the monitor can send data out of the LAN port.

The major questions right now are:

- It looks like the sw revision on the monitor itself is E.01.26, is this too old to be compatible with OpenICE?

- The bbb has the bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb-openice-0.6.2.img file loaded and I can see the OpenICE folders from SSH, but is this 0.6.2 img file an older version?

- The Phillips documentation mentions a BOOTP server, but I haven't seen it mentioned in any other documentation, is necessary to get the monitor connected over LAN?

- What are some good troubleshooting techniques to check if the separate components and software are functioning properly? For example communicating with the monitor via the bbb over ssh to show that connection is working.

Thank you!
Tyler

OpenICE device-adapter

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

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

Under review

IVY 450C Device Time of 0?

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

We're using an IVY 450C Multiparameter Monitor, with a Device Adapter running on an Intel Edison. Any ideas why the Device Time reported for, for example, heart rate is 0 (the Epoch)?

The Monitor is connected to a Patient Simulator, and is reporting heart rate and blood pressure that look good, except that Device Time for all its values is reported as 0.

On a likely-related note, the OpenICE Supervisor shows what looks like a time-sync warning for the Multiparameter Monitor (and our other devices). Any idea what's going on here? What is required for a Device Adapter to properly time-sync?

Thanks,
Brad

Vote

Fixed

OpenICE patch

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

>
> Hi Jeff,
>
> I’m a contractor at NIST working on the ICE project. I have been tracking and using your OpenICE code releases here for some time. Your recent addition of reading /etc/issue for operating system information on Linux systems broke the code running here. Locally, /etc/issue is over 800 bytes long and contains a warning about accessing a federal government owned computer.
>
> After a little research, I found the file /etc/os-release has become a standard file in most all the major Linux distributions. The file was originally introduced for systemd, but it has since been picked up even by distributions that have not converted to using systemd. Ubuntu 12.04 LTS has the file, for instance. The file format is defined at http://www.freedesktop.org/software/systemd/man/os-release.html .
>
> I have attached a patch that reads this file instead of /etc/issue. I’m a C++ programmer and not a Java programmer so perhaps the code could be improved. But I have tested it here and it works. I hope you this useful.
>
> Dennis

Attachments:
0001-Use-etc-os-release-instead-of-etc-issue-for-OS-infor.patch

Vote

Answer

10 years ago

Hi Dennis,
I’m sorry that the recent change broke the code for you and I greatly appreciate your reporting it and even including a patch. In our lab we’re still working on a really flexible deployment strategy for our ‘fleet’ of beaglebones. I added the /etc/issue as a quick way to see which had been upgraded to 14.04LTS. I should have done more research on the /etc/issue file in general before including it. I know a lot of folks at NIST who use CentOS, is that the distro you are using?

If I understand correctly what broke down was the lengthy string … probably throwing an exception in the CdrOutputStream? I’m really not thrilled about RTI’s API support for java programmers. On the plus side they have bound their underlying CDR (common data representation) libraries to java which is great. It means I can generate types natively in java (other implementations such as OpenDDS require types be generated in C++ first; then a JNI binding library is built specifically for those types … which is a multi-platform deployment nightmare). But on the other hand they do not support the standard java DDS API (I believe they plan to in the future) So as you can see the one adjustment I made to your patch was to jump some hurdles to avoid hardcoding the length (128). It would be nicer in java if they annotated max lengths in a way that facilitated validation. The commit in SourceForge git viewer:
http://sourceforge.net/p/mdpnp/code/ci/5757b04fabe6c870e748e7922a8573cc45a152b3/

If you wouldn’t mind I’d love to hear more about how you are using the code. Should I expedite a new release for you or are you building from source? If I know your particular areas of interest I can try to involve you in relevant discussions about how OpenICE should evolve. Also if you have issues or comments we’ve set up a website at http://community.openice.info that you can use in the future.

Thanks again,
Jeff

Answered

Simple OpenICE Setup

10 years ago in OpenICE • updated 10 years ago • 2

Hello,

I have a question regarding how to connect using the Simple OpenICE Setup.

In the diagram for the Simple OpenIce setup here (https://www.openice.info/docs/6_example-setups.html), You have a MP70 directly connected to the computer via RJ45 -> DB9 -> USB. This makes sense, but upon opening OpenIce and selecting the Intellivue/Serial option, it prompts me for a network address.

I'm a bit unclear as to what I should be inputting for a network address when connecting via serial, could someone elaborate?

Thanks very much!

Jeremy

Vote

- Is it?
- Inappropriate
- Spam
- Duplicate

OpenICE not working on Windows 10

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

Hi all,

please is the app compatible with Windows 10? I have installed OpenICE on my machine with Windows 10 but it keeps freezing.

Thank you,

Petr

OpenICE

Vote

Answered

Research

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

hello, I'm looking into this community as a noob to the EMR, EHR, MD PnP, Payer, Provider etc. There is a lot to wrap my head around.

My questions are more related to how you are interfacing with EMRs, and what format you're pushing that data? From a more technical perspective, are you exposing the data through an API? Or are you publishing that data directly to a system? Would love to get a quick overview, from a quasi-technical perspective.

Thanks.

JD
jdietrich@croocial.com

Vote

Answer

10 years ago

Hi JD,

Thanks for your question! The short answer is that EMR communication/integration is done through HL7 (http://www.hl7.org/). Our preferred HL7 version is the development version of HL7 FHIR (http://hl7-fhir.github.io/). If you're interested in using HL7 FHIR and java (what OpenICE uses), a fantastic learning resource is the HAPI FHIR project (http://jamesagnew.github.io/hapi-fhir/).

We have only begun to experiment with EMR integrations, but our current state is best illustrated by the OpenICE Supervisor app 'HL7 Exporter'. You can use the app by installing OpenICE: http://mdpnp.sourceforge.net/. And you can check out the code here: https://sourceforge.net/p/mdpnp/code/ci/master/tree/interop-lab/demo-apps/src/main/java/org/mdpnp/apps/testapp/hl7/. The app will take data from the active patient and export it via HL7 at a user defined time interval.

Our HIMSS15 demo app illustrated some mock "auto-validation" of medical device data that was then exported using the HL7 export app to a fake EMR. That system is representative of some of our future development ideas that will be on our roadmap eventually. For now, there is still a lot of work to do in this area...

Feel free to continue the conversation. Thanks,
Jeff

Customer support service by UserEcho

OpenICE Community Support Forum

Openice device simulation is not happening with device adapter and supervisor

mdpnp on beaglebone black debian jessie

Phillips MP5 intellivue RS232 to serial cape to bbb

Custom Data Consumer

IntellivueSerial driver throws an error in OpenICE 0.6.1

IVY 450C Device Time of 0?

OpenICE patch

Simple OpenICE Setup

OpenICE not working on Windows 10

Research

Forums

Knowledge bases

Categories

Community stats

3
Support agents