OpenICE Community Support ForumWelcome 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.
Hello Mdpnp team
I want to say change default configration . I am just asking if i have run the mdpnp program
Default Application Select is ICE_Device_interface , Device Category is Serial, Device Type is Drager Evita4 and Serial port is xyz is selected.
I have add successfully dependencies
compile group: 'mysql', name: 'mysql-connector-java', version: '5.1.6'
and connection s is successfully established
but i dont know where data is stored ? I have to create the table name is mdpnp and create 5 columns .
It was successfully created ,but don't know where is going indata MySQL
First off, thank you for providing such a good (open source!) solution for connecting to medical devices.
My company's primary product is an application that is a reporting solution for doctors/nurses. We're attempting to integrate the Philips Intellivue MP90 so we can automatically capture data, track live data, and add it to our reports.
OpenICE can get the Serial # + connect, but it stops there - I think it's because our MP90 currently doesn't have a measurement module, which should be coming in soon. I'll be able to test it more thoroughly in a few days.
If you don't mind answering, my two questions are these
- Have you attempted to connect to a MP90?
- I've noticed that there is the function TestIntellivue() under TestIntellivue.Java, but it contains commented out functions that don't exist. Assuming I've read the documentation on exporting data from Philips devices, could you explain how OpenIce calls on devices/philips/Intellivue to connect to the MPxx device?
I am creating a new app like all other present in the openice.
I have created a package and also implemented the IceApplicationProvider interface but my app is not displayed on the main screen.
I am new to this can you guide me about how to solve this problem?
I has try install OpenICE and successful installed.
I has create simulated device and link to patient (list in patient ID), it look working fine.
I has run HL7 export and start it, but HL7 message has been capture did not show active patient data , why this thing happened?
hope you can help me. thank you
INFO | Loading ice_library.xml from jar:file:/C:/Users/Ashish/.gradle/caches/modules-2/files-2.1/org.mdpnp/x73-idl-rti-dds/0.6.3/8e5005d356d91f80cfb3b157e610971108aa35e3/x73-idl-rti-dds-0.6.3.jar!/META-INF/ice_library.xml
it stuck at 75% ......
I am currently connecting Evita4 with laptop.
my connection is as follows:
evita->serial to usb connector ->laptop USB. I have crossed pin2 and 3(rx,tx) from evita.
Then i launch openice device configurator and add evita4 via serial. I tried all baudrates and parities. The device connector goes into endless connecting loop. However, I can use realterm to transmit basic commads and get replied.
Can you please provide steps to connect Evita 4.
I'm a newbie.I want to buy a BBB startkit to study openice.But I cant find a kit which can exactly meet the requirement mentioned in the article:a BBB kit with 'RS232 Cape'\'MircroSD Slot'\'Enclosure'.
Who can help me find an url to order the BBB kit which can directly deployed?
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.
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]
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:
Thank you very much
Hi MDPnP Team,
I noticed in your introduction video that you have a GE CareStation Ventilator in the lab. However, I don't see this ventilator as one of the supported devices in OpenICE. Do you have any plans to include GE CareStation as one of the supported devices anytime soon?
I would like to understand if the device drivers you have already developed would be compatible with Philips Intellivue MP50, either through the serial or ethernet connections. I understand you can only confirm and maybe support devices you acctually have at the lab, like MP70, but I wonder if in your opinion it should be compatible - the protocol manual is the same- and if it has been tested by anyone in the community.
Customer support service by UserEcho