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.
I am new to this community.I was doing some experiment in openice.Recently i found an interesting problem.When i ran the newest version openice on two computers in the same network,especially,i ran "ICE_Supervisor" on computer A,and ran a simulated device through "ICE_Device_Interface" on computer B.What i found is that the simulated device did not show in the supervisor in computer A .But i remember it's not the case like this in the older version openice.Does not a supervisor can recognize a device in the same network not only in the local computer? So i got confused and need help. Thank you very much.
I am new to this community and I want to set up a device simulator on my windows laptop, there is already one virtual machine kept in the network and OpenICE supervisor is also running on that computer.
Can any one please help me how can i simulate the medical device traffic and get it stored on openICE supervisor ?
Any specific hardware is required for setting up a device simulator on Windows laptop ?
Appreciate your help.
OK, one more problem with Ubuntu 14.04. We are trying to run openICE on a beagle board that will run on its own with no internet connection. However, it turns out there is an error when openICE is run on Ubuntu without internet connection (both on the laptop and on the beagle).
It is interesting that I get slightly different errors if I run this from eclipse and from the command line. On eclipse I get:
Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'rtConfig' defined in class path resource [DriverContext.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mdpnp.apps.testapp.RtConfig]: Factory method 'setupDDS' threw exception; nested exception is com.rti.dds.infrastructure.RETCODE_ERROR: error creating entity
From the command line, the error is:
Exception in thread "main" org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 6 in XML document from class path resource [DriverContext.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 6; columnNumber: 95; cvc-elt.1: Cannot find the declaration of element 'beans'.
This doesn't happen under Windows or Mac. As far as I know, I performed the exact same installation steps. Also, the problem goes away if there is connection to the internet, in which case the spring-beans.4.1.xsd schema can be retrieved.
Do you guys know what the problem is? Any help would be greatly appreciated!
At the beginning of integrating a middleware which I would prefer not to write a driver myself per one of the focuses that OpenICE is trying to get rid of. Does anyone have any suggestions or experience integrating/facing with this software? I have not seen the lab end integrated into OpenICE which I hope can come soon... If I can help integrated that aspect it is probably bigger than the medical device conundrum.
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?
We've run into an interesting symptom: normally the OpenICE Supervisor closes normally (after a few seconds). When we're on a slightly different network configuration, the Supervisor hangs - seemingly forever - after we click the close button.
The difference in the network configuration is that the "hang-on-close" configuration is that the laptop is on a subnet hosted by another computer, which is then connected to the main network.
Any ideas why network configuration would cause the OpenICE Supervisor to hang on close?
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!
I am new to this community. I tried running the hello-openice code by downloading it from github using gradle commands and I am stuck at gradlew run command it stops at Bulding 75%. I am not able to understand what is going wrong.
I have cloned the repo of mdpnp with git. The java jdk I use is 1.8.0_40 (Oracle Corporation 25.40-b25) and gradle is version 2.3. I work on Mac OS X 10.10.4 x86_64. If I try to build OpenICE with command "gradle build" from root directory of mdpnp following error is thrown:
FAILURE: Build failed with an exception.
Build file '/Users/kieb/Documents/workspace_openICE/mdpnp/interop-lab/demo-apps/build.gradle' line: 16
* What went wrong:
A problem occurred evaluating project ':interop-lab:demo-apps'.
> Could not resolve all dependencies for configuration 'classpath'.
> Could not resolve org.bitbucket.shemnon.javafxplugin:gradle-javafx-plugin:8.1.2-SNAPSHOT.
> Could not HEAD 'http://repository-javafx-gradle-plugin.forge.cloudbees.com/snapshot/org/bitbucket/shemnon/javafxplugin/gradle-javafx-plugin/8.1.2-SNAPSHOT/gradle-javafx-plugin-8.1.2-20141008.214348-1.pom'.
> org.apache.http.client.ClientProtocolException (no error message)
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
I also have tried to import OpenICE as Gradle-project into Eclipse Luna (4.4.2) with same result. I switched to openICE-tag 0.6.3 - same result. What is wrong?
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.
I've been able to connect with your socket.io server at openice site with my own nodejs primitive code. Could you provide more information about your server? Is there any protocol for receiving data? Which messages should I send to your server or listen to in order to start getting data from openice?
I've been learning about node.js with your demo. So far we've been able to build everything locally with grunt on a Mac OS and windows OS. I've been able to connect with your socket.io server at openice site with our own node.js developed code.
- We would really appreciate if you could please provide us more information about your server?
- Is there any protocol for receiving data?
- Which messages should I send to your server or listen to in order to start getting data from openice platform?
The constructor takes an int seconds, and Java defines the default int to be signed 32 bits. From a quick calculation, that number will overflow in about 68 years from the origin.
Any idea what the origin for DDS Time_t is?
So far, the app Subscribes to HeartBeat and DeviceIdentity.
We've found this doesn't seem to be sufficient to detect whether the device is on or off.
Now I've added a subscription to DeviceConnectivity, and am planning to consider a device "on" only if the app has received a DeviceIdentity (to know about the device), and DeviceConnectivity (to know when the device is in the Connected state).
It seems that DeviceIdentity is emitted by a device adapter only when its connection state changes. Given that, it seems that a late joiner app cannot know the DeviceConnectivity state (without provoking the Device Adapter in a way I don't yet know).
This leads me to ask two questions:
1) is there a simple method that I've missed, for detecting whether a given Medical Device is on or off?
2) (failing that) how should a late joiner app find whether the Devices it receives HeartBeat data from are on or off (connected or not connected)?
Customer support service by UserEcho