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.
+3
Ashish Saini 1 year ago 0

E:\hello-openice-master>gradlew eclipse

:eclipseClasspath
:eclipseJdt
:eclipseProject
:eclipse

BUILD SUCCESSFUL

Total time: 3.217 secs
E:\hello-openice-master>gradlew build
:compileJava
:processResources
:classes
:jar
:startScripts
:distTar
:distZip
:assemble
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check UP-TO-DATE
:build

BUILD SUCCESSFUL

Total time: 4.333 secs
E:\hello-openice-master>gradlew run
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:run
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
strategy: OnMiddlewareThread
> Building 75% > :run
0
Ashish Saini 1 year ago 0

C:\Users\Ashish\Desktop\hello-openice>gradlew run
:compileJava
:processResources
:classes
:run

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

strategy: OnMiddlewareThread

> Building 75% > :run


it stuck at 75% ......


Regards

Ashish

0
Tarun 1 year ago in OpenICE 0

C:\Users\ICU\Desktop\hello-openice-master>gradlew run
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:run
WARN | Unable to load native library nddscore
java.lang.UnsatisfiedLinkError: C:\Users\ICU\Desktop\hello-openice-master\.nddsh
ome\lib\x64Win64jdk\nddscore.dll: The application has failed to start because it
s side-by-side configuration is incorrect. Please see the application event log
or use the command-line sxstrace.exe tool for more detail
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824)
at java.lang.Runtime.load0(Runtime.java:809)
at java.lang.System.load(System.java:1086)
at com.rti.dds.util.NativeInterface.extractAndLoad(NativeInterface.java:
482)
at com.rti.dds.util.NativeInterface.loadNativeLibrary(NativeInterface.ja
va:172)
at com.rti.dds.util.NativeInterface.loadNativeLibraries(NativeInterface.
java:139)
at com.rti.dds.domain.DomainParticipantFactory.<clinit>(Unknown Source)
at org.mdpnp.rtiapi.qos.IceQos.loadAndSetIceQos(IceQos.java:44)
at org.mdpnp.helloice.HelloICE.main(HelloICE.java:372)
The library nddscore.dll could not be loaded by Windows.
Make sure that the library is in your Path environment variable.
java.lang.UnsatisfiedLinkError: no nddscore.dll in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.rti.dds.util.NativeInterface.loadNativeLibrary(NativeInterface.ja
va:168)
at com.rti.dds.util.NativeInterface.loadNativeLibraries(NativeInterface.
java:139)
at com.rti.dds.domain.DomainParticipantFactory.<clinit>(Unknown Source)
at org.mdpnp.rtiapi.qos.IceQos.loadAndSetIceQos(IceQos.java:44)
at org.mdpnp.helloice.HelloICE.main(HelloICE.java:372)
Exception in thread "main" java.lang.UnsatisfiedLinkError: no nddscore.dll in ja
va.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.rti.dds.util.NativeInterface.loadNativeLibrary(NativeInterface.ja
va:168)
at com.rti.dds.util.NativeInterface.loadNativeLibraries(NativeInterface.
java:139)
at com.rti.dds.domain.DomainParticipantFactory.<clinit>(Unknown Source)
at org.mdpnp.rtiapi.qos.IceQos.loadAndSetIceQos(IceQos.java:44)
at org.mdpnp.helloice.HelloICE.main(HelloICE.java:372)
:run FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':run'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_92\bin\java.exe'' finished wi
th non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

BUILD FAILED

Total time: 3.515 secs

0
Neil Young 1 year ago in OpenICE 0

Hello everybody,

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?

0
Under review
Alejandro Figar 2 years ago in OpenICE • updated by Priya Vaity 1 year 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
Answer
Jeff Plourde 2 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

0
Behnood Gholami 1 year ago in OpenICE 0

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?


Thanks.

OpenICE
0
Under review
Pau Soler 2 years ago in OpenICE • updated by NathanS 1 year ago 4
Hi,
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.

Thanks
mirumed.com
0
K. Ebeling 1 year ago in DDS 0

I have installed an evaluation-version of VortexOpenSplice (6.6.2p1) from PrismTech. If I try execute task "osplIdlppJava" - following errors are thrown:


Generating from ice.idl
/opt/PrismTech/Vortex_v2/Device/VortexOpenSplice/6.6.2p1/HDE/x86_64.linux/bin/idlpp EVALUATION VERSION
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Type 'wstring' (defined in DeviceIdentity) unsupported near the token #pragma keylist DeviceIdentity unique_device_identifier
(line: 165, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Type 'wstring' (defined in DeviceConnectivity) unsupported near the token #pragma keylist DeviceConnectivity unique_device_identifier
(line: 218, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Type 'wstring' (defined in InfusionObjective) unsupported near the token #pragma keylist InfusionObjective unique_device_identifier
(line: 354, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Type 'wstring' (defined in InfusionStatus) unsupported near the token #pragma keylist InfusionStatus unique_device_identifier
(line: 390, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Undeclared referenced declarator alarm_limit_type near the token #pragma keylist AlarmLimit unique_device_identifier metric_id alarm_limit_type
(line: 424, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Undeclared referenced declarator alarm_limit_threshold near the token #pragma keylist GlobalAlarmLimitObjective metric_id alarm_limit_threshold
(line: 440, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Undeclared referenced declarator alarm_limit_type near the token #pragma keylist LocalAlarmLimitObjective unique_device_identifier metric_id alarm_limit_type
(line: 461, column: 0)
*** DDS error in file /home/kieb/workspace/mdpnp/data-types/x73-idl/src/main/idl/ice/ice.idl: Type 'wstring' (defined in Patient) unsupported near the token #pragma keylist Patient mrn
(line: 531, column: 0)
:data-types:x73-idl-ospl-dds:osplIdlppJava FAILED


It seams that type "wstring" is unkown in VortexOpenSplice and I can't see declarators "alarm_limit_type" and "alarm_limit_thresold" in file "x73-idl/src/main/idl/ice.idl"?


Can you help me please?

0
Gregory Rehm 2 years ago • updated by Luke Fletcher 2 years ago 10

Hi,


I was wondering if the openice supervisor could be run headlessly (without GUI). I've been poking around at it on my own computer and I got as far as


./bin/OpenICE -app ICE_Supervisor -domain 15


To which java gives me an error.


Exception in thread "main" java.lang.IllegalStateException: Failed to create command instance org.mdpnp.apps.testapp.IceAppsContainer

at org.mdpnp.apps.testapp.Configuration.getCommand(Configuration.java:126)
at org.mdpnp.apps.testapp.Main.main(Main.java:59)


It seems java wants some kind of command before we can proceed but there doesn't seem to be any available documentation on commands to use. Was wondering


1. Even if I take this to its terminus can we run the process headlessly?

2. What are the lists of available commands to use?

0
vishnu 2 years ago in OpenICE 0

Hi guys,

I am Happy and excited to find OpenICE, and this forum.

I am planning to connect IntelliVue MX800 with OpenICE. So from Docs, i can understand that, no need of BBB for simple connection. Just connect RS232 port on MX800 to OpenICE (via RJ45 -> DB9 -> USB). I can see 2 RS232 port in the MX800.

Which port i should use for serial communication?

Another question is, can i direct connect MX800 to openICE using LAN cable (By connecting the LAN port in MX800 and Ethernet port in Laptop )?

0
Searching answer
Rado 3 years ago in OpenICE • updated by Alistair MacDonald 2 years ago 22
Hi guys,

Sorry to be such a pain, but we are working on several devices in parallel and are getting stuck on all of them right now. We've been trying to connect to a Philips MP70 for several weeks now but to no avail.

The problem is that for some reason openICE doesn't connect and keeps sending association request messages, so we keep receiving what I believe is an association response. As far as I understand, there are multiple revisions of the communication protocol but I'm not quite sure how to find out which version our monitor uses. I was looking through the old topics and saw a picture posted by Jeff where the monitor had a total of 4 ethernet ports, two output and two input. Ours only has two ports - one input and one output (of course, there is also the LAN port, which we don't want to use).

Do you guys know what the problem is or at least where to start looking for it?

Thanks and sorry again!

Rado

P.S. Just so you don't think I'm only trouble, let me say that we are making good progress with the Drager Apollo and are getting ready to start collecting data from it soon, so thanks for that! :)
OpenICE device-adapter
0
Paul Ourada 2 years ago 0

Hi Jeff -


I'm helping a friend of mine who is doing some research using OpenICE. They want to use a medical monitor which is not yet supported. I haven't yet dived into the code, so I was wondering about the architecture for the device adapter serial driver. Is it straight hard coded parsing the input and producing output, or is there a framework for doing things like

  • identifying common message types for the same device type
  • supplying the message header/trailer framework, and methods to fill in the particulars?
  • Also perhaps identifying common workflows (session, login, security, etc) and creating plugins which implement the workflows, or customize them?

Best Regards,

Paul

device-adapter
0
Tim 3 years ago in DDS • updated by Paul Ourada 2 years ago 13
MDPnP et al,
I wanted to find out where the focus in regards to the DDS would currently and in the future?
  • Will RTI-DDS and Prismtech-DDS be implemented together? 
  • or one or the other DDS technologies used provided by the above stated vendors?
  • Are RTI-DDS, Primstech-DDS and OpenDDS interoperable with each other?
  • Does OpenDDS not satisfy all the requirements compared to RTI and Primstech DDS technologies?
  • According to OMG specification the DDS is embedded on top of UDP or TCP, is that correct?
  • How is DDS different from RTP/RTCP/RTSP and IEC 61850-GOOSE, if we are trying to achieve and implement real-time communication layer?
  • Have you guys had any thoughts of looking into Transport Information Collection Protocol (TICP) http://planete.inria.fr/ticp/ on top of IP?
Thanks
Tim
0
Achilleas 2 years ago in OpenICE • updated by Paul Ourada 2 years ago 3

Hallo,


We are currently trying to export data from a local ICU, some of the medical devices that are available to us are supported by openICE. We are experiencing some problems regarding the Puritan Bennett 840 ventilator. When we directly communicate with the ventilator using the SNDF command we get the expected number of fields responce (171). But when the openICE was used only a fraction of the fields were captured (39). We tested it on 3 different ventilators, all of which yielded the same result.
The ventillators were not connected to anyone at that time, is it possible that that was the problem or we should look for something else? The operating system that runs the application is Windows 10.


One note regarding the PB840.
The PB840 has several versions, some of them have a single serial port while others have three ports. The latest openICE version requires two ports for the PB840, connecting it to a machine with only one port leads to an error message that there is no device found on the second port and thus the connection is terminated. We temporary bypassed this issue by building two different versions for the demo apps, the first using the source code as it is, and the second one with a minor change on the PB840Provider.java file:
return new DeviceType(ice.ConnectionType.Serial, "Puritan Bennett", "840", "PB840", 2);
we changed the number of devices from 2 to 1, so that only one port will be requested. Doing so we limit ourselves in capturing only the PB parameters since the DemoPB840.java uses the first port created for the PB parameters and the second for the waveforms ( if i understand it correctly ), but since we are interested only in the parameters, at least for the time being, we are fine with that.


One bug i noticed, though irrelevant to the openICE application.
On the CSVPersister.java the date used to create a testing file was hard coded using the American eastern time zone ( -05:00 ) , that resulted in an error when trying to built the whole project ( i thought it was nessessary at the time) in a different timezone ( +02:00 ).I made the following alteration, which is nothing fancy since my Java knowledge is pretty basic.On the CSVPersister.java file, i added the following library:
import java.time.ZonedDateTime;
and changed the testCVSLine() function to the following:
public void testCVSLine() throws Exception {
SimpleDateFormat dateFormat = DataCollector.dateFormats.get();
ZonedDateTime timeZone = ZonedDateTime.now();
String timeZoneString=timeZone.getOffset().toString();
timeZoneString=timeZoneString.replace(":", "");

Date d0 = dateFormat.parse("20150203.235809.985"+timeZoneString);
Value v = DataCollector.toValue("DEVICE0", "METRIC0", 0, d0.getTime(), 13.31);

String line = CSVPersister.toCSVLine(v);
Assert.assertEquals("Invalid csv line", "DEVICE0,METRIC0,0,20150203235809"+timeZoneString+",13.31", line);
}
The same issue also appears in the DataCollectorTest.java file.


Thanks,

Achilleas

OpenICE demo-apps
0
Phai Reddy 2 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