OpenICE Community Support Forum

Hi,

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.

Regards,

Tarun

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?

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.

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?

Hi

Firstly, thanks to the OpenICE community for supporting this amazing project.

I'm trying to use OpenICE (v0.6.3) to connect to Philips IntelliVue monitors over LAN. My computer (OSX 10.11.3) is connected to the same internal ICU LAN network the monitors are connected to. I have an IP address, and I can ping the monitors. However, when I connect to the monitor IP address, the connection status in OpenICE is stuck on "Negotiating (Requesting association)". This is true of any monitor I attempt to connect to in the unit. Just to be explicitly clear, I am not using serial/RJ45/RS232. Just LAN.

I am able to connect to the monitor just fine when the monitor is connected to an isolated network. I believe the issue may be that the monitors are already connected with the central Philips server. Can IntelliVue monitors connect to both the Philips server and OpenICE simultaneously? Is there any other reason that could explain this behaviour?

Kind regards

Luke Fletcher

I'm starting a project using the Raspberry Pi with OpenICE. I downloaded the zip file, but when I try to run the OpenICE script within the bin directory, nothing happens. I am pretty new to RPi so any help would be great. Thank you

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 )?

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

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?

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