Odysseus with DDS or RTPS interfaces

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Odysseus with DDS or RTPS interfaces

Post by kauerbach » Mon Nov 17, 2014 9:34 pm

Hello,

Could you tell me if Odysseus would allow me to use a data source from a DDS or RTPS interface?

Thank you.
Regards,
Ken Auerbach.

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Odysseus with DDS or RTPS interfaces

Post by Marco Grawunder » Tue Nov 18, 2014 9:35 am

You mean http://portals.omg.org/dds/ ?

Currently, this is not directly available, but we use the Netty library (netty.io) where it is contained. It should be possible to implement that.

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Wed Nov 19, 2014 6:11 pm

Hello Marco,

Thank you for your quick reply. Could you tell me how I would go about using Odysseus Studio with this Netty library to access my data stream instead of using the TCP/IP socket method that I used before?

Thank you very much.
Ken.

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Wed Nov 19, 2014 7:32 pm

Hello Marco,

I looked at the NETTY documentation and it looks like it should be compatible with our new DDS interface. Is there a certain NETTY-compatible data handler in Odysseus that I can use in my script to interact with the new data stream?

Thank you.
Ken.

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Wed Nov 19, 2014 11:15 pm

Hello Marco,

Here, below, is a sample of our current data stream using our new DDS interface. We would like to use this as our new source for Odysseus Studio.

Thank you.
Kind regards,
Ken.

--------------------------
unique_device_identifier: 36n0LggyTbVEIwvsDA4fARGdGd2HpFi3rCaz
metric_id: MDC_PULS_OXIM_PLETH
instance_id: 0
unit_id: MDC_DIM_DIMLESS
frequency: 50
values :
userData: 31.0, 31.0, 31.0, 31.0, 31.0, 35.0, 41.0, 51.0, 60.0, 67.0, 68.0, 64.0, 61.0, 54.0, 49.0, 44.0, 41.0, 39.0, 38.0, 36.0, 35.0, 34.0, 34.0, 33.0, 33.0, 32.0, 32.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 31.0, 34.0, 38.0, 48.0, 57.0, 65.0, 69.0, 69.0, 63.0
device_time :
sec: 0
nanosec: 0

:
unique_device_identifier: 36n0LggyTbVEIwvsDA4fARGdGd2HpFi3rCaz
metric_id: MDC_PRESS_BLD
instance_id: 0
unit_id: MDC_DIM_DIMLESS
frequency: 50
values :
userData: -3.0, 2.0, 12.0, 21.0, 28.0, 32.0, 34.0, 35.0, 35.0, 33.0, 30.0, 26.0, 22.0, 21.0, 21.0, 24.0, 24.0, 20.0, 16.0, 13.0, 10.0, 7.0, 5.0, 3.0, 2.0, 1.0, 0.0, -1.0, -2.0, -3.0, -3.0, -4.0, -3.0, -4.0, -4.0, -3.0, -3.0, -3.0, -4.0, 8.0, 17.0, 25.0, 30.0, 33.0, 35.0, 35.0, 35.0, 31.0, 28.0, 24.0
device_time :
sec: 0
nanosec: 0

:
unique_device_identifier: 36n0LggyTbVEIwvsDA4fARGdGd2HpFi3rCaz
metric_id: MDC_PRESS_BLD
instance_id: 1
unit_id: MDC_DIM_DIMLESS
frequency: 50
values :
userData: 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
device_time :
sec: 0
nanosec: 0

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: MDC_PRESS_AWAY
instance_id: 0
unit_id: DRAEGER_mbar
frequency: 125
values :
userData: 17.6, 17.6, 17.6, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.6, 17.6, 17.6, 17.6, 17.6, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.7, 17.6
device_time :
sec: 1415567344
nanosec: 881000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: MDC_FLOW_AWAY
instance_id: 0
unit_id: MDC_DIM_L_PER_MIN
frequency: 125
values :
userData: 21.5, 21.7, 21.5, 21.4, 21.3, 21.3, 21.0, 20.9, 20.9, 20.9, 20.8, 20.8, 21.0, 20.8, 20.8, 20.7, 20.4, 20.6, 20.1, 20.1, 20.1, 19.9, 19.8, 19.7, 19.7
device_time :
sec: 1415567344
nanosec: 881000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: MDC_VENT_VOL_TIDAL
instance_id: 0
unit_id: MDC_DIM_MILLI_L
frequency: 125
values :
userData: 272.0, 275.0, 278.0, 281.0, 284.0, 286.0, 289.0, 292.0, 295.0, 298.0, 300.0, 303.0, 306.0, 309.0, 312.0, 314.0, 317.0, 320.0, 322.0, 325.0, 328.0, 331.0, 333.0, 336.0, 338.0
device_time :
sec: 1415567344
nanosec: 881000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_Oxygen
instance_id: 0
unit_id: MDC_DIM_PERCENT
value: 21.0
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_InspTidalVolume
instance_id: 0
unit_id: MDC_DIM_L
value: 0.52
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: MDC_TIME_PD_INSPIRATORY
instance_id: 0
unit_id: MDC_DIM_SEC
value: 1.5
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_IPart
instance_id: 0
unit_id: DRAEGER_None
value: 1.0
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_EPart
instance_id: 0
unit_id: DRAEGER_None
value: 2.3
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_FrequencyIMV
instance_id: 0
unit_id: DRAEGER_OnePerMin
value: 12.0
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: DRAEGER_SETTING_PEEP
instance_id: 0
unit_id: DRAEGER_mbar
value: 5.0
device_time :
sec: 1415567343
nanosec: 17000000

:
unique_device_identifier: unMv6oHm2tdlPHKdBr5aZzDFYtqAWBUkCh5t
metric_id: MDC_TIME_PD_APNEA
instance_id: 0
unit_id: MDC_DIM_SEC
value: 15.0
device_time :
sec: 1415567343
nanosec: 17000000

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Wed Nov 19, 2014 11:25 pm

Hello Marco,

The java script that created that stream is on GitHub here:

https://github.com/mdpnp/hello-openice/ ... loICE.java

Thank you.
Kind regards,
Ken.

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Odysseus with DDS or RTPS interfaces

Post by Marco Grawunder » Thu Nov 20, 2014 9:18 am

Hello Ken,

currently, this feature is not implemented. Give me some days ;-)

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Odysseus with DDS or RTPS interfaces

Post by Marco Grawunder » Fri Nov 21, 2014 1:56 pm

Unfortunenatly, its not that easy... will take a longer time to understand the model behind DDS and RTPS and provide a generic solution.

In the source code you linked me: Is com.rti.dds commercial code (http://www.rti.com/products/dds/)?

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Fri Nov 21, 2014 3:57 pm

Hello Marco,

I think only the "Professional" version of com.rti.dds is commercial software. I will confirm that and let you know for sure.

Thank you.
Kind regards,
Ken.

kauerbach
Posts: 30
Joined: Fri Aug 22, 2014 4:52 pm

Re: Odysseus with DDS or RTPS interfaces

Post by kauerbach » Fri Nov 21, 2014 4:34 pm

Hello Marco,

I just checked. We are only using the "Community" version which is NOT commercial. To get access to this version you just need to apply for the license here --> http://www.rti.com/downloads/IC-license.html . It's very easy and they sent me the license immediately after applying. I think it would be valuable for the Odysseus project to provide a data handler for accessing data streams through this interface since it is becoming the standard interface middle-ware for healthcare and medical software providers.

Thank you.
Kind regards,
Ken.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest