OpenICE Community Support Forum

Hello Jeff,
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.
Cheers
Tim

Hello. I've been trying to follow the directions for the device-adaptor but running into some glitches.
#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.

debian@beaglebone:~$ OpenICE-0.6.2/bin/OpenICE

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.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280)

at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:227)

at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:173)

at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)

at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)

at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695)

at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$152(LauncherImpl.java:182)

at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found

at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:94)

at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:124)

... 1 more

Exception in thread "main" java.lang.RuntimeException: No toolkit found

at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:185)

at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)

at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)

at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695)

at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$152(LauncherImpl.java:182)

at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

debian@beaglebone:~$

Common question:

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".

Do you have a recommended/favorite DDS introduction/tutorial? I'm finding that having a grounding in DDS would help in my understanding of how to use OpenICE.

Thanks,
Brad

A common question:

Where is OpenICE's IDL and how do you run the tool to generate the C interfaces for the IDLs?

I'm writing an OpenICE app designed to report the on/off state of various Devices. So far I've successfully modified Hello OpenICE code to Subscribe to HeartBeat and DeviceIdentity Topics. The HeartBeat data seems to arrive fine, but the DeviceIdentity data has problems.

In the received DeviceIdentity, the model name is blank, rather than being something like "Pulse Ox (simulated)". I've seen some symptoms that suggest that the model string gets filled in later, but I'm not certain of that.

I wanted to double-check with you that I'm using the correct pattern to read the DeviceIdentity data: I substituted class names in Hello OpenICE code based on some guesswork, so something may be incorrect. Based on the symptom I'm wondering whether I'm not properly telling DDS that I want to read the data contents. I haven't found an example of reading DeviceIdentity in the mdpnp git.

Here is the relevant code (adapted from HelloICE.java) - I apologize for the formatting. Note that on reception of a Pulse Ox (simulated) DeviceIdentity, the model field is blank.

Thanks for your help,
Brad
---------------------------------

public void on_data_available(DataReader reader) {

I'm writing an OpenICE application to keep track of what Devices are running, and note (on a UI) when they come and go.

So far, I've successfully written code to Subscribe to and Read HeartBeatTopic data, and filtered out the Supervisor data vs. Devices' data. Now that I have unique device IDs from the HeartBeat, I want to ask the model number (and more if I can) of the Device that sent the HeartBeat.

How do I do that?

Thanks,
Brad

Hi, guys!

I was installed Revision C Disk Image and gradle-2.4 and sync to a NTP clock on BBB.
but, jdk 8u33 in Rev.C disk image is not build OpenICE source on BBB. (./gradlew)
The reason is 8u33 is not supported JavaFx. so I reinstalled jdk 8u6.
but OpenICE source is not build on BBB....
I want to build OpenICE source on BBB.
help me how to build OpenICE source on BBB or build reference.

p.s - Your device adapter(BBB) have a rs-232 serial port. my BBB don't have a serial port. T.T


thanks
Hyungi

When I try to login to community.openice.info from our corporate network, the login doesn't fail, but doesn't seem to authenticate - it's as if I'm not logged in.

Logging in from my phone-as-hotspot (no proxy or firewall) works fine.

So I need to find what about or corporate proxy or firewall is preventing my logging into the community site. More info as I find it.

Hello, can we expect support for Mindray Beneview series of Patient monitors anytime soon?

Hi everyone,

Sorry to keep asking questions, but this one has actually bugged us for a while now. Do you know how to make the Puritan Bennett 840 ventilator output waveform data?

We have tried all ports but all we get is the miscf message with numeric data only. We can't see any options on the ventilator itself either. As far as I understand from the code, the PB demo is also only set up to ask for numeric data.

Any insight you might have will be appreciated.

Thanks!

Rado

Do you guys have any experience with Alaris pumps? We have one in the lab but I can't get it to export data. The manuals are not very helpful either - apparently there is some software (also developed by Alaris) that seems to be the only way to export data.

Thanks,
Rado

Hi,
I have cloned the OpenICU (master) branch on my Win-7 and hosted it on IIS7.5. When I visit the OpenICU Webdemo page of hosted website (http://localhost/openice/demo.html), the 'Connecting..' status never changes.

Upon debugging, figured out that the generated 'openice.info.js' file is needed under the build folder. Downloaded the same from the OpenICE website (https://www.openice.info/demo.html) and then I started getting the following 404 error trace

http://localhost/socket.io/?EIO=3&transport=polling&t=1427954861373-0

I don't have NodeJs server running on my machine as I presently don't have any insights on how to use it for OpenICE locally.

Any help is highly appreciated.

Thanks.

Hi, guys!

What are RTI-dds & OpenSplice for? on OpenICE.
I think RTI using the transform of idl to java.
that's right?

I want to know the exact usage.

Thanks,
Hyungi

The OpenICE systems need to track the presence and availability of various devices in the system. There are a lot of possible ways to maintain the known "liveliness" of remote participants. Here are some of the ways we have tried in the past and the solution which we have converged upon during OpenICE development.

• Participant Liveliness
  • Our first mechanism was to use DDS metadata to track the liveliness of remote participants. In principle this worked but it had several drawbacks and unmet requirements...
    • It may not always be desirable to maintain a 1:1 correspondence between participant and device. For instance a participant accepting connections from bluetooth devices might actually communicate data for a number of such devices through one DDS Participant.
    • Participant meta-data does not usually get relayed between DDS networks. Further, when data is relayed to a remote network (perhaps at the central monitoring or data center scope) it is presented to that network through a new participant local to that network.
    • Configuration of discovery-related parameters is vendor-specific so establishing compatible settings can be difficult.
• DeviceIdentity instance Liveliness
  • Our next attempt was at using the Liveliness of DeviceIdentity instances to track remote device liveliness.
    
    • This successfully breaks the undesirable 1:1 correspondence participant and device.
    • The problem here is that DeviceIdentity is not frequently republished. Meaning that once a reader has received a DeviceIdentity instance sample it *will* properly mark that instance "NOT ALIVE" when it fails to communicate a heartbeat; but later when the connection is re-established there is no new sample to communicate and the state of the instance will not become ALIVE until a new sample is produced.
• A distinct HeartBeat topic
  
  • To meet our requirements we created a Topic in the system expressly for the purpose of discerning liveliness.
  • By contract devices all must publish a new sample of Heartbeat every two seconds. The sample size is deliberately kept very small; including only UDI and a device type.
  • Because this is "user" level data (and not metadata) from the DDS perspective it will "properly" traverse routes and links between DDS systems.
  • This topic is described in our IDL. Our QoS settings are in a profile called "heartbeat" within ice_library.xml.
  • You can view realtime Heartbeats from devices in our lab on our diagnostics page.