Questions
0
Answered
IntelliiVue Device Adapter
Hi Jeff,
I have a Philips Intellivue MP5 monitor and want to connect to openICE using IntelliVue Serial Adapter.
Since the protocols are same for all Intellivue series monitor, I am assuming this should work
Please confirm...
My setup details:
Running demo apps software on my windows machine.
Started local device adapter of device type Intellivue Serial RS232/MIB
Connected MP5 monitor through a USB to Com Port Adapter which in turn is connected to my RJ45 to DB9 female connector (setup according to the pin diagram).
Does this setup work? I am hoping to see waveform data from MP5 monitor but I see the device in negotiating state and not proceeding further...Am i missing something ?
Please advise.
Regards
Vasanth
I have a Philips Intellivue MP5 monitor and want to connect to openICE using IntelliVue Serial Adapter.
Since the protocols are same for all Intellivue series monitor, I am assuming this should work
Please confirm...
My setup details:
Running demo apps software on my windows machine.
Started local device adapter of device type Intellivue Serial RS232/MIB
Connected MP5 monitor through a USB to Com Port Adapter which in turn is connected to my RJ45 to DB9 female connector (setup according to the pin diagram).
Does this setup work? I am hoping to see waveform data from MP5 monitor but I see the device in negotiating state and not proceeding further...Am i missing something ?
Please advise.
Regards
Vasanth
Answer
Hi Jeff,
I tried the above setup with MP70 monitor and the demo app works great.
May be there is something missing incase of MP5 even though both of them belong to IntelliVue series and share the same protocol.
Regards
Vasanth
I tried the above setup with MP70 monitor and the demo app works great.
May be there is something missing incase of MP5 even though both of them belong to IntelliVue series and share the same protocol.
Regards
Vasanth
PINNED
Hi Vasanth,
I'm not sure if this helps, but according to the Philips Data Export Interface Program Guide, the pinout for the serial cable needs to be slightly different for the MP5 monitors.
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
In other words, you would need to swap pins 2 and 3 on the DB9 connector.
Hope this helps!
Regards,
Nathan
I'm not sure if this helps, but according to the Philips Data Export Interface Program Guide, the pinout for the serial cable needs to be slightly different for the MP5 monitors.
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
In other words, you would need to swap pins 2 and 3 on the DB9 connector.
Hope this helps!
Regards,
Nathan
Hi Nathan,
Thanks for your response.
I will try the pin out specified above and post my results.
Vasanth
Thanks for your response.
I will try the pin out specified above and post my results.
Vasanth
Hi,
I get the following error when I connect MP5 or any MP series monitor.
2015-03-02 05:35:47,100 | INFO | Loading System configuration from jar:file:/home/debian/OpenICE-0.6.1/lib/demo-apps-0.6.1.jar!/ice.system.properties | org.mdpnp.apps.testapp.Main | main
2015-03-02 05:35:47,705 | WARN | Attempt to load org.mdpnp.data.serial.PureJavaCommSerialProvider | org.mdpnp.devices.serial.SerialProviderFactory | main
2015-03-02 05:35:47,747 | WARN | org.mdpnp.data.serial.PureJavaCommSerialProvider | org.mdpnp.devices.serial.SerialProviderFactory | main
2015-03-02 05:35:49,709 | INFO | Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@1dc03ce: startup date [Mon Mar 02 05:35:49 IST 2015]; root of context hierarchy | org.springframework.context.support.ClassPathXmlApplicationContext | main
2015-03-02 05:35:50,156 | INFO | Loading XML bean definitions from class path resource [DeviceAdapterContext.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:51,542 | INFO | Loading XML bean definitions from class path resource [RtConfig.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:52,822 | INFO | Loading properties file from class path resource [ice.properties] | org.springframework.beans.factory.config.PropertyPlaceholderConfigurer | main
2015-03-02 05:35:54,888 | INFO | Loading ice_library.xml from jar:file:/home/debian/OpenICE-0.6.1/lib/demo-devices-0.6.1.jar!/META-INF/ice_library.xml | org.mdpnp.devices.IceQos | main
2015-03-02 05:35:57,046 | INFO | Refreshing Philips Intellivue (MIB/RS232): startup date [Mon Mar 02 05:35:57 IST 2015]; parent: org.springframework.context.support.ClassPathXmlApplicationContext@1dc03ce | org.springframework.context.support.ClassPathXmlApplicationContext | main
2015-03-02 05:35:57,066 | INFO | Loading XML bean definitions from URL [jar:file:/home/debian/OpenICE-0.6.1/lib/demo-devices-0.6.1.jar!/DriverContext.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:58,831 | INFO | Initializing ExecutorService 'taskExecutor' | org.springframework.scheduling.concurrent.ScheduledExecutorFactoryBean | main
2015-03-02 05:36:02,664 | WARN | 177177567ns to service org.mdpnp.rtiapi.data.EventLoop$2@c7f00c | org.mdpnp.rtiapi.data.EventLoop | EventLoopHandler
2015-03-02 05:36:02,764 | INFO | Initializing ExecutorService 'timerFactory' | org.springframework.scheduling.concurrent.ScheduledExecutorFactoryBean | main
2015-03-02 05:36:03,677 | WARN | 191079763ns to service org.mdpnp.devices.TimeManager$1@11392ad | org.mdpnp.rtiapi.data.EventLoop | EventLoopHandler
2015-03-02 05:36:03,859 | INFO | Registering beans for JMX exposure on startup | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,986 | INFO | Bean with name 'driver' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,992 | INFO | Bean with name 'partition' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,997 | INFO | Bean with name 'timeManager' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,017 | INFO | Located managed bean 'partition': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=partition] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,216 | INFO | Located managed bean 'driver': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=driver] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,449 | INFO | Located managed bean 'timeManager': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=timeManager] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,464 | WARN | Bean with key 'timeManager' has been registered as an MBean but has no exposed attributes or operations | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,482 | INFO | Connecting to >ttyS0< | org.mdpnp.devices.DeviceDriverProvider$SpringLoadedDriver | main
2015-03-02 05:36:04,735 | ERROR | PRESWriterHistoryDriver_initializeSample:!serialize | com.rti.dds | main
2015-03-02 05:36:04,735 | ERROR | WriterHistoryMemoryPlugin_addEntryToSessions:!initialize sample | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | WriterHistoryMemoryPlugin_getEntry:!add virtual sample to sessions | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | WriterHistoryMemoryPlugin_addSample:!get entry | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | PRESWriterHistoryDriver_addWrite:!add_sample | com.rti.dds | main
2015-03-02 05:36:04,737 | ERROR | PRESPsWriter_writeInternal:!collator addWrite | com.rti.dds | main
Please advise.
I get the following error when I connect MP5 or any MP series monitor.
2015-03-02 05:35:47,100 | INFO | Loading System configuration from jar:file:/home/debian/OpenICE-0.6.1/lib/demo-apps-0.6.1.jar!/ice.system.properties | org.mdpnp.apps.testapp.Main | main
2015-03-02 05:35:47,705 | WARN | Attempt to load org.mdpnp.data.serial.PureJavaCommSerialProvider | org.mdpnp.devices.serial.SerialProviderFactory | main
2015-03-02 05:35:47,747 | WARN | org.mdpnp.data.serial.PureJavaCommSerialProvider | org.mdpnp.devices.serial.SerialProviderFactory | main
2015-03-02 05:35:49,709 | INFO | Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@1dc03ce: startup date [Mon Mar 02 05:35:49 IST 2015]; root of context hierarchy | org.springframework.context.support.ClassPathXmlApplicationContext | main
2015-03-02 05:35:50,156 | INFO | Loading XML bean definitions from class path resource [DeviceAdapterContext.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:51,542 | INFO | Loading XML bean definitions from class path resource [RtConfig.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:52,822 | INFO | Loading properties file from class path resource [ice.properties] | org.springframework.beans.factory.config.PropertyPlaceholderConfigurer | main
2015-03-02 05:35:54,888 | INFO | Loading ice_library.xml from jar:file:/home/debian/OpenICE-0.6.1/lib/demo-devices-0.6.1.jar!/META-INF/ice_library.xml | org.mdpnp.devices.IceQos | main
2015-03-02 05:35:57,046 | INFO | Refreshing Philips Intellivue (MIB/RS232): startup date [Mon Mar 02 05:35:57 IST 2015]; parent: org.springframework.context.support.ClassPathXmlApplicationContext@1dc03ce | org.springframework.context.support.ClassPathXmlApplicationContext | main
2015-03-02 05:35:57,066 | INFO | Loading XML bean definitions from URL [jar:file:/home/debian/OpenICE-0.6.1/lib/demo-devices-0.6.1.jar!/DriverContext.xml] | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | main
2015-03-02 05:35:58,831 | INFO | Initializing ExecutorService 'taskExecutor' | org.springframework.scheduling.concurrent.ScheduledExecutorFactoryBean | main
2015-03-02 05:36:02,664 | WARN | 177177567ns to service org.mdpnp.rtiapi.data.EventLoop$2@c7f00c | org.mdpnp.rtiapi.data.EventLoop | EventLoopHandler
2015-03-02 05:36:02,764 | INFO | Initializing ExecutorService 'timerFactory' | org.springframework.scheduling.concurrent.ScheduledExecutorFactoryBean | main
2015-03-02 05:36:03,677 | WARN | 191079763ns to service org.mdpnp.devices.TimeManager$1@11392ad | org.mdpnp.rtiapi.data.EventLoop | EventLoopHandler
2015-03-02 05:36:03,859 | INFO | Registering beans for JMX exposure on startup | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,986 | INFO | Bean with name 'driver' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,992 | INFO | Bean with name 'partition' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:03,997 | INFO | Bean with name 'timeManager' has been autodetected for JMX exposure | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,017 | INFO | Located managed bean 'partition': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=partition] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,216 | INFO | Located managed bean 'driver': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=driver] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,449 | INFO | Located managed bean 'timeManager': registering with JMX server as MBean [mdpnp.driver.IntellivueSerial22815297:service=timeManager] | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,464 | WARN | Bean with key 'timeManager' has been registered as an MBean but has no exposed attributes or operations | org.springframework.jmx.export.MBeanExporter | main
2015-03-02 05:36:04,482 | INFO | Connecting to >ttyS0< | org.mdpnp.devices.DeviceDriverProvider$SpringLoadedDriver | main
2015-03-02 05:36:04,735 | ERROR | PRESWriterHistoryDriver_initializeSample:!serialize | com.rti.dds | main
2015-03-02 05:36:04,735 | ERROR | WriterHistoryMemoryPlugin_addEntryToSessions:!initialize sample | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | WriterHistoryMemoryPlugin_getEntry:!add virtual sample to sessions | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | WriterHistoryMemoryPlugin_addSample:!get entry | com.rti.dds | main
2015-03-02 05:36:04,736 | ERROR | PRESWriterHistoryDriver_addWrite:!add_sample | com.rti.dds | main
2015-03-02 05:36:04,737 | ERROR | PRESPsWriter_writeInternal:!collator addWrite | com.rti.dds | main
Please advise.
That is great news Vasanth I'm glad the MP70 is working for you! In our lab we use an MP70 and an MX800 running revision J of the Philips software. We've had only limited opportunities to test the software on other models and software revisions. You are right that since they share the same data export protocol there is no explicit reason the MP5 shouldn't work. The protocol does allow for a lot of variation and it's possible our software is not handling particular protocol options used by the MP5. If you are using the default log4j settings the OpenICE 'demo-apps' package should be creating a 'demo-apps.log' in your working directory. If you'd like to send along that log after making an attempt to use the MP5 I could try to see if anything is obviously going wrong. If it is of value to you we can pursue the MP5 further.
Thank you
Jeff Plourde
Thank you
Jeff Plourde
Hello Jeff-
Does the MP70 driver also work for the MX800 or does it require a different driver? Our MP70's have software version E, so we're resorting to an MP30 with software version J. But we just got 3 MX800s so could use those if the driver is the same.
thanks,
Alistair
Does the MP70 driver also work for the MX800 or does it require a different driver? Our MP70's have software version E, so we're resorting to an MP30 with software version J. But we just got 3 MX800s so could use those if the driver is the same.
thanks,
Alistair
Hi Alistair,
Our (unofficial) support is limited to devices we have in the lab. We have an MP70 rev J and MX800 rev J that both work with our Intellivue Serial device adapter. We try to help support devices we don't own, but there's really no way for us to definitively know without being able to regression test hands-on in the lab.
Thanks,
Jeff
Our (unofficial) support is limited to devices we have in the lab. We have an MP70 rev J and MX800 rev J that both work with our Intellivue Serial device adapter. We try to help support devices we don't own, but there's really no way for us to definitively know without being able to regression test hands-on in the lab.
Thanks,
Jeff
Customer support service by UserEcho
I'm not sure if this helps, but according to the Philips Data Export Interface Program Guide, the pinout for the serial cable needs to be slightly different for the MP5 monitors.
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
In other words, you would need to swap pins 2 and 3 on the DB9 connector.
Hope this helps!
Regards,
Nathan