Hi Srikanth. There is a copy uploaded here. http://www.docfoc.com/philips-interface-programming-guide. However, generally this document is not required to use OpenICE as it already has a Java implementation of this protocol.

Hi Nathan

Thanks for your assistance. I was able to connect via serial to the MP70s today, and also found that both numerics and waveforms were accessible, which is fantastic! Thanks again for your advice and support.

Cheers

Luke

Hi Nathan

Interesting. To quote the Interface Programming Guide:

"IntelliVue Rev. G.0 or higher allows the combination of a LAN interface and one MIB/RS232 port for Data Export. Only one connection is able to request wave data at a time, the other connection responds with a notification that wave polling is not possible.The first connection to request a successful wave poll receives the wave data."

Therefore, I am of the understanding that while numerics can be sent simultaneously via LAN and serial, waveform data cannot. I haven't tested the setup via serial as I am awaiting the delivery of the relevant cables/adapters, but will be sure to check it out as soon as possible.

Just to confirm, your MP70s are connected to a Philips Central Station over LAN, the Central Station is obtaining waveform data from the MP70s, and you are also obtaining waveform data via serial, simultaneously?

Ahhh thanks Nathan. That's both very helpful, and very disappointing. I require both numeric and waveform data from my MP70s, and unfortunately, you can only get the waveform data via either LAN or serial, but not both. Thus, while the monitors are connected to the Information Centre / Central Station, its not possible to get waveform data :\

Yeah my node.js app saves incoming data from OpenICE to a MongoDB database. But you could wire it up to an SQL database, or whatever data storage option works for you.

That's right. SocketIO is a node.js module. It's used primarily by servers to push information to clients (like web browsers, iOS/Android platforms, etc) in real time. It's (likely) used to power the OpenICE demo on the website. SocketIO has a lot of clients available in a variety of languages. If you don't want to use SocketIO and want to build your entire app platform in Java, you can ditch the "SocketController" class and call the relevant methods in "DSSController" directly. However, in my case, I wanted to use node.js (written in Javascript) as my web server and have it talk to OpenICE, which is obviously written in Java. To facilitate communication between the two, I used SocketIO. Hope that helps

I haven't really done anything special compared with what the OpenICE/MD PnP team has achieved. And most of the code is taken directly out of the OpenICE anyway, so I hardly claim ownership of it. The code is all yours :) https://github.com/lukefletcher/CirculateICE

Hi Peter and Gregory. One of the main issues about running OpenICE in headless mode is that there is, as far as I know, no capacity to connect to monitors over LAN or serial without the GUI. Of course, once connected you also need a means of obtaining the data from OpenICE. To this end, I modified the OpenICE source and Hello OpenICE to build an app that responds to SocketIO calls to connect to a monitor, and then once connected, transmits data back via SocketIO. It is then possible to build an app, in your programming language of choice, that can display/save this data in whatever means you deem fit. It's an elegant solution, and once you eliminate all of the JavaFX components, it runs just fine on a BeagleBone Black. Let me know if this is something that might be of help. Cheers!