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
What does an EventLoop do?
As I've been reading DeviceListModelImp.java and related classes, in an attempt to duplicate the OpenICE Supervisor's behavior around detecting devices going on and off.
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?
Thanks,
Brad
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?
Thanks,
Brad
0
Answered
How to change the Device-Adapter to use a static IP address...
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".
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".
Answer
Jeff Peterson
10 years ago
The beaglebone is a standard linux computer running Debian. The default user is “debian”; the default password is “debian”. You can access the terminal in a variety of ways; the easiest is plugging in a USB keyboard and a monitor (there’s a mini-HDMI port on the beaglebone). Alternatively if you feel comfortable with SSH, you can access the terminal at debian@192.168.13.2 through the Micro-USB port on the beaglebone. USB networking is enabled by default and separate from Ethernet networking so you can use one to change the other.
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:
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:
auto eth0to:
allow-hotplug eth0
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
address 192.0.2.7
netmask 255.255.255.0
gateway 192.0.2.254
0
Under review
DeviceConnectivity for late joiners?
I'm (still) writing an ICE app that detects when devices turn on and off.
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)?
Thanks,
Brad
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)?
Thanks,
Brad
0
Under review
mindray monitors
Hello, can we expect support for Mindray Beneview series of Patient monitors anytime soon?
0
Answered
Philips RJ45 Port Wiring
Hi,
I've been working with a Philips IntelliVue MX800, and the associated RJ45 to RS232 adapter required.
I've been left a little confused after seeing the below diagram on your website. It appears to me that the white numbers on the left-most diagram of the RJ45 connector appear to be inconsistent with the two other diagram of the RJ45 connector.
This is based on the assumption that the left-most diagram is displaying and end-on view of the RJ45 connector.
I've been working with a Philips IntelliVue MX800, and the associated RJ45 to RS232 adapter required.
I've been left a little confused after seeing the below diagram on your website. It appears to me that the white numbers on the left-most diagram of the RJ45 connector appear to be inconsistent with the two other diagram of the RJ45 connector.
This is based on the assumption that the left-most diagram is displaying and end-on view of the RJ45 connector.
Answer
Jeff Peterson
10 years ago
Hey Thomas,
The left-most diagram is a cross section of a male connector plugged into a female connector. Use the pin connection numbering described by the drawing with the pin layout of the smaller drawings. The pinouts on the two smaller individual illustrations are the correct layout for each gender connector. The pin numbering is standardized so feel free to Google around for better pictures.
Thanks,
Jeff
The left-most diagram is a cross section of a male connector plugged into a female connector. Use the pin connection numbering described by the drawing with the pin layout of the smaller drawings. The pinouts on the two smaller individual illustrations are the correct layout for each gender connector. The pin numbering is standardized so feel free to Google around for better pictures.
Thanks,
Jeff
0
Under review
Issues logging in from corporate network
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.
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.
0
Answered
OpenICE code in 3rd party app
Hello,
First off, thank you for providing such a good (open source!) solution for connecting to medical devices.
My company's primary product is an application that is a reporting solution for doctors/nurses. We're attempting to integrate the Philips Intellivue MP90 so we can automatically capture data, track live data, and add it to our reports.
OpenICE can get the Serial # + connect, but it stops there - I think it's because our MP90 currently doesn't have a measurement module, which should be coming in soon. I'll be able to test it more thoroughly in a few days.
If you don't mind answering, my two questions are these
Thank you!
Jeremy
First off, thank you for providing such a good (open source!) solution for connecting to medical devices.
My company's primary product is an application that is a reporting solution for doctors/nurses. We're attempting to integrate the Philips Intellivue MP90 so we can automatically capture data, track live data, and add it to our reports.
OpenICE can get the Serial # + connect, but it stops there - I think it's because our MP90 currently doesn't have a measurement module, which should be coming in soon. I'll be able to test it more thoroughly in a few days.
If you don't mind answering, my two questions are these
- Have you attempted to connect to a MP90?
- I've noticed that there is the function TestIntellivue() under TestIntellivue.Java, but it contains commented out functions that don't exist. Assuming I've read the documentation on exporting data from Philips devices, could you explain how OpenIce calls on devices/philips/Intellivue to connect to the MPxx device?
Thank you!
Jeremy
-1
How to change default configration of Openice ?
Hello Mdpnp team
I want to say change default configration . I am just asking if i have run the mdpnp program
Default Application Select is ICE_Device_interface , Device Category is Serial, Device Type is Drager Evita4 and Serial port is xyz is selected.
Thanks
Customer support service by UserEcho
