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 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)?
I've come across the class EventLoop, that I assume has something to do with managing Topic events. The code suggests it has to do with managing the running of multiple snippets of DDS-related code.
What is EventLoop's purpose? Would its purpose likely become clear if I learned more about DDS?
I have been reading the node.js code on Github. Could you please explain to us how to use the publishing structure for plotting data on the web browser by implementing node.js? It will really help us a lot.
#1) I'm using the Beaglebone Element14 Black revision C - following the flashing directions for disk image C, it installs version 0.6.2. I noticed that the serial RS232 port is ttyO2 instead of ttyO1, but before I even get to that point, I try to start the software and get this message: (note, the adaptor setup directions say to type OpenICE-0.6.3/bin/OpenICE but the only directory is OpenICE 0.6.2). Here's the copied error message - is there something I'm missing? Sorry, I'm not a developer.
Graphics Device initialization failed for : es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
... 1 more
Exception in thread "main" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)
I've followed the tutorial on OpenICE.info to image a bealgebone with the provided disk image. I started to set it up but found DHCP is enabled by default. I need to set a static IP. Can you give us a quick "how to".
The official documentation for Debian networking configuration is here: https://wiki.debian.org/NetworkConfiguration#Configuring_the_interface_manually
The network setup interfaces configuration file is located at "/etc/network/interfaces”.
With your preferred text editor, change the block in the file /etc/network/interfaces from:
iface eth0 inet dhcp
auto eth0Obviously use your preferred IP addresses. After you’ve saved your changes to the config file, restart the beaglebone with `sudo reboot`.
iface eth0 inet static
Where is OpenICE's IDL and how do you run the tool to generate the C interfaces for the IDLs?
To generate code for the IDL, we use rtiddsgen. The code generator is documented here.
At the command line, enter:
rtiddsgen -language C -inputIdl /path/to/repo/data-types/x73-idl/src/main/idl/ice/ice.idl
Customer support service by UserEcho