Phillips MP5 intellivue RS232 to serial cape to bbb

Hey Tyler,

This is fixable - first question: what type of RJ45 port are you connected to? The serial port or the Ethernet port? I think you're in the Ethernet port and not the serial port.

If you are using a serial cape on the BBB then you should be connecting to the serial port on the MP5. The serial cape will not function with an ethernet connection on the MP5.

The connection status of "Connecting (initializing RS-232 to UDP adapter)" is an IntellivueEthernet specific state meaning OpenICE device-adapter on the Beaglebone is configured as "IntellivueEthernet" and cannot reach an Ethernet port.
The monitor's "Unsupported LAN" message means the MP5 monitor cannot obtain a IP (in your case from the serial cape - which makes sense).

Sounds like you need to do two things: first, move the RJ45 cable on the MP5 to a serial port. (If you don't have a serial port I can help you with Ethernet). Second, change the device-adapter config file on the BBB called device.this to contain: "-device IntellivueSerial". This is explained here: https://www.openice.info/docs/5_device-adapter-config.html#configure

If you want to troubleshoot easier, plug the monitor directly into the computer and run the device-adapter from your computer as shown here: https://www.openice.info/docs/6_example-setups.html#simple

Thanks,
Jeff

Great response! Unfortunately, the MP5 only has the LAN ethernet jack and an RJ45 ethernet jack, but not RS-232 serial port.
Eventually, we will have to pull from the RJ45/RS-232, but just to check everything is working we tried just the LAN.

With the MP5 LAN jack connected to the computers ethernet jack we ran
OpenICE - ICE_Device_Interface, Device
Category: Network,
Device Type: Philips Intellivue (LAN),
Domain_ID: 0.
For the ip address we ran cmd ipconfig and tried the ip addresses listed for the associated ethernet jack.

OpenICE shows "Negotiating (Requesting Association)" monitor still shows "Unsupported LAN", which I am worried has to do with the software revision on the monitor, which is a few editions behind.

We tried this setup with the monitor plugged directly into the computer and with the monitor plugged into a router along with the computer and got the same results. Should we be using a cross-over ethernet cable for plugging the monitor into the computer?

Please let us know if any of this sounds off, this "Unsupported LAN" issue could be on the monitor side and is what is preventing OpenICE from getting past the negotiation.

Thank you,
Tyler

Hi Tyler,

As you know, there are two ways of connecting an MP5 to OpenICE: serial and Ethernet. The MP5 may or may not have a serial connector but will definitely have an Ethernet connector. The serial connector will be an RJ45 form-factor port labeled RS-232, MIB, or with a symbol of an arrow pointing out of a circle as seen here: https://www.openice.info/docs/5_device-adapter-config.html#connect-devices. The Ethernet port will be labelled LAN and is typically used to connect the MP5 to a central station.

The error message "Unsupported LAN" indicates that the MP5 cannot obtain an IP address from the BOOTP server on the network. This message tells me that you are connected to the LAN port on the MP5. If you wish to connect to the MP5 via the LAN connector, you will need to set up a BOOTP server, as described by the MP5 manual, to allow the MP5 to obtain an IP address. You will also need to run the OpenICE device-adapter with the IP that the MP5 is assigned.

To connect to the MP5 via serial, plug into the port described above. Searching Google for MP5 serial port delivered the following picture (that may be useless to you). If available, you can use this port to connect via serial communication. The pinout of the RJ45 to DB9 cable is found here: http://www.frankshospitalworkshop.com/equipment/documents/ecg/service_manuals/Philips_IntelliVue_MP5_Patient_Monitor_-_Service_manual.pdf#page=228. Please note the software revision of your device and consult your manual to ensure the pinout is accurate. Similar instructions for an MP70 connected to a Beaglebone can be found here: https://www.openice.info/docs/5_device-adapter-config.html#required-hardware-mp70.


I hope this helps,
Jeff

Hey Jeff,

Pardon the delay! After some time we were able to get the LAN interface figured out, but it looks like our application requires RS232. I believe I have the beaglebone set up properly with the device.this mentioned in the device adapter configuration example. And we were even able to set the eth0 static IP on the beaglebone, which openICE picks up:


We still seem to be stuck in the Negotiating phase, which happens with or without the monitor. I think we have the pin out set up properly (this is the rj45 to db9 connector)


this post http://community.openice.info/topic/637293-intelliivue-device-adapter/ mentions that the MP5 and MP70 are the same except switching the blue and green cable.

"For the MP70, you need (DB9 -> RJ45):
2 ->5
3 ->7
5-> 4

For the MP5, you need (DB9 -> RJ45):
2 ->7
3 ->5
5-> 4"

I think we have this set up properly, but am I missing something obvious? Just wanted to get a second opinion. We have swapped out a few of the cables and seem to be getting the same results.

Thank you!

Hello, it looks like we are only getting this Request phase when the USB is plugged in. We are troubleshooting to see why the eth0 is not getting picked up, but please let me know if you have any tips or ideas.

Thank you!

Hey, quick update: We switched the pin configuration around and plugged eth0 of the bbb into a specific port in one location and then plugged a laptop running OpenICE into a similar port in another room (same subnet) and the Supervisor application started up automatically, wave forms look great! If we plug the board directly into the laptop via USB it works too!

Now the 2 big issues:
- getting the ICE_Device_Interface to work without a supervisor, shouldn't it just use the same ip as what appears in the supervisor?
- using a crossover cable just between the computers and the board. We can ping and use ssh over the crossover, but the ICE_Supervisor does not pick up the monitor session. This page (https://www.openice.info/docs/5_device-adapter-config.htm) mentions the bbb needs a method of establishing time, is this what is preventing the session from starting over crossover cable?

Thank you!

Hi Tyler,

I'm a little confused about your setup so if my advice is off-base, I apologize.

It sounds like you have a Beaglebone (BBB) formatted with the OpenICE disk image, running the device-adapter service configured correctly, and the BBB is equipped with an RS232 cape plugged into the serial connection of an MP5. Also plugged into the BBB is an Ethernet network cable to eth0. eth0 is plugged into a network that also has a router with DHCP, NTP clock info, and another computer running the Supervisor which is successfully subscribing to the BBB and displaying the data. Your objective is to use a crossover cable instead of the network to connect a computer directly to the BBB? "Without a supervisor" is confusing me as well. Do you wish to write your own subscriber? (If so check out HelloOpenICE on github)

Here's a little tidbit that may help: BBBs do not have a real-time clock. They negotiate time from the network after boot. The GUI on the supervisor will not display waveforms from an out-of-sync device, even if the data is present on the wire. For this reason it is necessary to provide an NTP time server for the BBB to use to sync on boot. This is out of the scope of OpenICE, but if you run either DHCP with option 43 enabled on the network interface you are plugging the crossover cable into, or alternatively run an NTP server on the network interface, you should be able to fix any time sync issues. I would recommend always using the "System Explorer" app to check for data and connectivity as it is less finicky than the device view.

Connect directly to the BBB and Supervisor computer(s) to ensure your networking and time sync are working.

Thanks and feel free followup with additional questions/clarification. Good luck!
Jeff

Jeff! I was just typing a quick update:

We were able to get the ICE Supervisor working with the crossover cable. It worked like a charm once we got the both the board and computer host on the same subnet mask with linked IPs (similar to the set up mentioned on this site http://www.networking.windowsreinstall.com/directconnectionnetwork/). At first it was just the numerics only, but once we set the time on the board to the same time as the host waveforms came through. We set the time on the BBB manually, but I will check out the DHCP option 43 and NTP on the network interface because setting manually is not ideal.

The issue of running "without a supervisor" has to do with running the ICE Device Interface on the host computer connected to the BBB. When we tried the LAN interface it displayed data with the ICE Supervisor and the ICE Device Interface, but now that we are working with the RS-232 we can only get the Supervisor to display data. I assume this is because the when we use the BBB with RS-232 the ICE Device Interface is already running on the BBB and we need a supervisor to capture that data? Where as the LAN interface runs the Device Interface on the connected machine, which is why we could see data with both the Supervisor and Device Interface.

Don't know how I missed OpenICE! It looks like this is an example for collecting data from the BBB running the OpenICE device adapter (similar to how the supervisor works)?

I think we have resolved the major issues mentioned in this thread (I might start up a new one if/when we have questions about Hello OpenICE and capturing OpenICE transmitions from the BBB).

Thank you so much for your response(s)!

"Without a supervisor" sounds like the "simple setup" here: https://www.openice.info/docs/6_example-setups.html#simple This setup has no BBB, but instead runs both the ICE_Device_Interface (aka Device Adapter) and the OpenICE Supervisor on the same machine. In this setup you would plug the RS232 directly into the computer, no LAN required. Take a look at the sample setups for some inspiration. Essentially you need one instance of ICE_Device_Interface (Device Adapter) connected to the serial port of each device and a Supervisor (or custom app) to subscribe to the devices. The adapters and supervisors are connected by a network, even if it's just the local loopback adapter.

HelloOpenICE https://github.com/mdpnp/hello-openice is sample code for subscribing to the data structures that the Device Adapters (ICE_Device_Interfaces) are publishing the same way the Supervisor functions. The sample code should allow you to quickly write application level software without the immense struggle of writing code for the underlying middleware (DDS).

Feel free to startup a new thread as issue arise. I'm happy to help.
Thanks,
Jeff

Hi Tyler (and Jeff)- Reading through your post, I've also gotten stuck at the negotiating phase. (negotiating - requesting association). Can you tell me how you rewired the custom RJ45-DB9 adaptor? Assuming we're both using the SF cable adaptor, I found this chart online:
Pin1 -- Blue
Pin2 -- Orange
Pin3 -- Black
Pin4 -- Red
Pin5 -- Green
Pin6 -- Yellow
Pin7 -- Brown
Pin8 -- White
So I've used the red, green and brown wires (4,5,7) but noticed you had blue, black and green. I've tried red->5, green->2, brown->3, and red->5, green->3, brown->2, but still only get the 'negotiating -requesting association' (how long does this step usually take? more than a minute?).
Any help you might have I'd greatly appreciate.
Thanks,Alistair.