Your comments
Hey Jeff,
Thanks for updating hello-openice for me. I will look into this further, and let you know how I get on.
Thomas
Thanks for updating hello-openice for me. I will look into this further, and let you know how I get on.
Thomas
Hey Jeff,
Thanks, executing the program with USER_QOS_PROFILES.xml in the working directory seems to have improved things.
Now when I execute the program I get the following output:
I assume that this means that I need to tell the ICE supervisor to listed on 7410 or 7412, but I'm unsure how to do this. It's not a firewall issue as these are both running on the same host, and I also trialled disabling the firewall just in case.
Cheers,
Thomas
Thanks, executing the program with USER_QOS_PROFILES.xml in the working directory seems to have improved things.
Now when I execute the program I get the following output:
WARN | DDS_XMLParser_parse_from_file:Loading : USER_QOS_PROFILES.xml
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF2 in use
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_SocketFactory_create_receive_socket:invalid port 7410
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_create_recvresource_rrEA:!create socket
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF4 in use
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_SocketFactory_create_receive_socket:invalid port 7412
WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_create_recvresource_rrEA:!create socket
WARN | RTICdrTypeObjectStructureType_is_extensible_assignable:types are not assignable: types have different number of key members
WARN | RTICdrTypeObjectStructureType_is_assignable:types are not assignable: structures are not assignable: ice::Numeric, ice::Numeric
WARN | RTICdrTypeObjectStructureType_is_extensible_assignable:types are not assignable: types have different number of key members
WARN | RTICdrTypeObjectStructureType_is_assignable:types are not assignable: structures are not assignable: ice::SampleArray, ice::SampleArray
I assume that this means that I need to tell the ICE supervisor to listed on 7410 or 7412, but I'm unsure how to do this. It's not a firewall issue as these are both running on the same host, and I also trialled disabling the firewall just in case.
Cheers,
Thomas
So, I can get the demo-apps running fine, with an ICE Supervisor and a simulated Pulse Oximeter. That all works fine, really easily out of the box.
Then I've gone and cloned the hello-openice repo, compiled that, and trying to get that to run. However, I'm getting this set of errors:
This is running on a 64-bit Fedora (RHEL) Linux host, if that makes any difference.
Cheers, Thomas
Then I've gone and cloned the hello-openice repo, compiled that, and trying to get that to run. However, I'm getting this set of errors:
# ./hello-openice WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF2 in use WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_SocketFactory_create_receive_socket:invalid port 7410 WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_create_recvresource_rrEA:!create socket WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_Socket_bindWithIp:0X1CF4 in use WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_SocketFactory_create_receive_socket:invalid port 7412 WARN | [D0000|ENABLE]NDDS_Transport_UDPv4_create_recvresource_rrEA:!create socket WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name 'Device') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0 WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name '(null)') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0 WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name '(null)') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0 WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name 'Device') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0 ERROR | DDS_QosProvider_get_profile_xml_objectI:ERROR: Profile 'ice_library::waveform_data' not found ERROR | DDS_QosProvider_get_datareader_qos_from_profile:ERROR: Profile 'ice_library::waveform_data' not found Exception in thread "main" com.rti.dds.infrastructure.RETCODE_ERROR at com.rti.dds.util.Utilities.rethrow(Unknown Source) at com.rti.dds.infrastructure.RETCODE_ERROR.check_return_codeI(Unknown Source) at com.rti.dds.domain.DomainParticipantFactoryImpl.get_datareader_qos_from_profile_w_topic_name(Unknown Source) at com.rti.dds.subscription.SubscriberImpl.create_datareader_with_profile(Unknown Source) at com.rti.dds.domain.DomainParticipantImpl.create_datareader_with_profile(Unknown Source) at org.mdpnp.helloice.HelloICE.main(HelloICE.java:49) ABRT problem creation: 'success' WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name 'Device') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0 WARN | PRESParticipant_assertRemoteParticipant:Warning: remote participant on same host (with name '(null)') has disabled shared memory and this participant ignores UDP loopback. To allow communication, set ignore_loopback_interface to 0
This is running on a 64-bit Fedora (RHEL) Linux host, if that makes any difference.
Cheers, Thomas
Hey Jeff,
"Hello OpenICE" looks to be just what I was looking for, thanks very much!
Given that I'll be going option A and building the app to hook up to an OpenICE network.
All very exciting... I'm already having ideas for the studies we could run if we deployed a dozen or so Beaglebones into the OT suite.
And sure, feel free to post to the support page.
Cheers,
Thomas
"Hello OpenICE" looks to be just what I was looking for, thanks very much!
Given that I'll be going option A and building the app to hook up to an OpenICE network.
All very exciting... I'm already having ideas for the studies we could run if we deployed a dozen or so Beaglebones into the OT suite.
And sure, feel free to post to the support page.
Cheers,
Thomas
Customer support service by UserEcho
Using the updated hello-openice I successfully connected to my OpenICE supervisor.
Thanks for all your assistance.
Thomas