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.
No similar topics found.
0
Answered
Controlling Device parameter(s) as Supervisor
Hi,
I was looking into your system and already managed to compile the code and run the demo-apps. Now I am wondering, if there is a way to control parameters as a supervisor?
For example: I am running the supervisor app, connect to a (simulated) infusion pump and I want to change a parameter, e.g. the drug (name) or the drug mass.
Are such actions possible within your system?
Best regards,
Kai
I was looking into your system and already managed to compile the code and run the demo-apps. Now I am wondering, if there is a way to control parameters as a supervisor?
For example: I am running the supervisor app, connect to a (simulated) infusion pump and I want to change a parameter, e.g. the drug (name) or the drug mass.
Are such actions possible within your system?
Best regards,
Kai
0
Answered
Where is the IDL and how do I use it to generate code?
A common question:
Where is OpenICE's IDL and how do you run the tool to generate the C interfaces for the IDLs?
Where is OpenICE's IDL and how do you run the tool to generate the C interfaces for the IDLs?
Answer
Jeff Peterson
10 years ago
The IDL is found in our git repo - the IDL is found under /master/data-types/x73-idl/src/main/idl/ice/ice.idl.
To generate code for the IDL, we use rtiddsgen. The code generator is documented here.
At the command line, enter:
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
0
Answered
microSD card formatted as FAT32
Hi,
Linux image doesnt appear to boot from microSD card (formatted as FAT32).
Has anyone faced the issue before ?
Regards
Linux image doesnt appear to boot from microSD card (formatted as FAT32).
Has anyone faced the issue before ?
Regards
Answer
Jeff Plourde
10 years ago
Vasanth,
Thank you very much for answering your own question! Did it take any unusual steps to succeed? afaik the newer beagles with stock debian will automatically boot from the microsd (without depressing the "option" button)... has that been your experience as well? Also when you get a moment could you add a link to the windows disk imager tool you used? or it is built into newer windows versions?
For anyone else reading it the disk image Vasanth is referring to is posted here:
https://www.openice.info/device-adapter-setup.html#required-software
Thank you
Jeff Plourde
Thank you very much for answering your own question! Did it take any unusual steps to succeed? afaik the newer beagles with stock debian will automatically boot from the microsd (without depressing the "option" button)... has that been your experience as well? Also when you get a moment could you add a link to the windows disk imager tool you used? or it is built into newer windows versions?
For anyone else reading it the disk image Vasanth is referring to is posted here:
https://www.openice.info/device-adapter-setup.html#required-software
Thank you
Jeff Plourde
0
Under review
Hello-openice execution
Hi
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 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.
0
Answered
What are RTI-dds & OpenSplice for?
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
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
Answer
Jeff Peterson
10 years ago
Hi Hyungi,
DDS is a distributed system abstraction layer that passes messages between the OpenICE nodes. DDS is technically a standard with commercial implementations distributed by RTI and PrismTech (OpenSplice). OpenICE is distributed with a community edition of RTI DDS.
More information about how we use DDS in OpenICE can be found in the working-draft of OpenICE App Architecture Description.
Thanks,
Jeff
DDS is a distributed system abstraction layer that passes messages between the OpenICE nodes. DDS is technically a standard with commercial implementations distributed by RTI and PrismTech (OpenSplice). OpenICE is distributed with a community edition of RTI DDS.
More information about how we use DDS in OpenICE can be found in the working-draft of OpenICE App Architecture Description.
Thanks,
Jeff
0
Started
OpenICE not working offline on Ubuntu
Hi again,
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!
Thanks,
Rado
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!
Thanks,
Rado
0
Openice device simulation is not happening with device adapter and supervisor
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
0
Under review
mdpnp on beaglebone black debian jessie
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,
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,
Answer
Jeff Plourde
10 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
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
Under review
Phillips MP5 intellivue RS232 to serial cape to bbb
Hello,
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.
Thank you!
Tyler
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.
Thank you!
Tyler
0
Answered
Custom Data Consumer
Hi,
I'm involved in the development of a trial that involves streaming data from our Philips IntilliVue monitors to a head-mounted device.
I noticed that you'd already gone to the effort of implimented Phillips' Data Export Protocol, which is a huge relief!
Would you suggest:
a) Running an OpenICE network with the adapter for the IntelliVue and then developing a OpenICE 'consumer' for our device, or,
b) Directly interfacing with your implimentation of the Phillips' Data Export Protocol.
I'd ultimately prefer option A, as it would be more flexible, although I'm currious to know if there's any documentation or Java interface available for doing so.
Cheers,
Thomas
I'm involved in the development of a trial that involves streaming data from our Philips IntilliVue monitors to a head-mounted device.
I noticed that you'd already gone to the effort of implimented Phillips' Data Export Protocol, which is a huge relief!
Would you suggest:
a) Running an OpenICE network with the adapter for the IntelliVue and then developing a OpenICE 'consumer' for our device, or,
b) Directly interfacing with your implimentation of the Phillips' Data Export Protocol.
I'd ultimately prefer option A, as it would be more flexible, although I'm currious to know if there's any documentation or Java interface available for doing so.
Cheers,
Thomas
Customer support service by UserEcho
