Getting Started - Community RTI Connext Users
Contents
1. c Close the Status panel Show the content filter expression a In the Physical View tree select the DataReader then select the Description Panel button from the toolbar File Domain Actions Window Help 25 03KH ETOJ TFE Create a new Description panel b Select the Builtin Topic Data tab in the Description Panel Showing Deadlines c See the content filter expression under builtin topic data content_filter_property filter_expression and builtin topic data content_filter_property expression_parameters Description Panel DAR amp builtin topic data is content_filter_property L content filter topic name ContentFilter_1 ie expression_parameters Ll expression_parameters 0 expression_parameters 1 lil expression_parameters z acl expression_parameters 3 i filter_class_name DOSSOL Lal filter_expression X 0 andx 1 and y gt 2 andy 3 L related topic name Square is deadline i period infinite is destination order Li Kind BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS Ll source_timestamp_tolerance 30 0 seconds i disable_positive_acks false v ie durability 4 direct communication true VOLATILE_DURABILITY_Q05 5 Prepare for the next demo a Close the Description panel b In the two instances of Shapes Demo select Controls Delete All 33 Showing Deadlines The steps in this section assume you are using the same profile used in Section 32. 6 j Scroll down to see Discovery Statistics Click the link next to Last DataReader GUID This will select the matching DataReader in the Physical View tree and the panel will switch to show DataReader status instead Status Panel 3 System gt Host BOCAGRANDEsiicom gt Process 9700 gt DP 0 RTI Momtonng Demo gt Publisher gt DW _ Square i Filter by match All Matches Display Mode Basic Advanced Total Count Last Instance Handle Reliable Writer Cache Empty Cache Full Cache Low Watermark High Watermark Unack ed Samples Unacked Samples Peak Publications Matched Total Count Current Count Current Count Peak Last DataReader GUID 0 AQ 950 AZ 0 AQ 950 A2 951 A2 4 1 Y First Unacked Sample DataReader GUID 0a80183 2220 2 80000007 First Unelapsed Keep Duration 1 Reliable Reader Activity Active Count 1 A0 Inactive Count 0 AQ Last DataReader GUID 0a80183 2220 2 80000007 Offered Incompatible QoS Total Count 0 AQ Last Policy Id Invalid Policies DataWriter Cache Sample Count 1 Sample Count Peak 1 Discovery Statistics 1 AQ 1 AQ Click here to select the matching reader 4 e0a80183 2220 2 80000007 7 BHB The top of the Status panel and some of the other entity specific panels that you will see later in this demo shows a list of parent entities to which the selected entity belongs For example Status Panel System gt
3. 1 4 max_remote_vittual_writers_per_instance 1 E max_remote_writers 1 5 max_remote_writers_per_instance 1 8 max_remote_writers_per_sample 3 max sampes per reag IKEI max_samples_per_remote_writer max_total_instances L gt ig reliability Y F resource_limits initial_instances 1 8 initial Samples 1 4 instance_hash_buckets 1 E may instance 2 al max_samples_per_instance 2 it subscription_name 6 Fix the problem by creating a DataReader with a larger queue size a In the Subscriber Shapes Demo instance select Controls Delete All b Create a new reliable square subscriber that uses take and the MonitorDemoLi brary FixedSamplesRejectedScenario profile which will fix the problem by increas ing the queue size c Select Subscribe Square d Choose the profile MonitorDemoLibrary FixedSamplesRejectedScenario This profile uses a larger queue size e Check the Reliability box f For Read method to use select Take g Select OK 3 18 Showing a Samples Rejected Scenario Verify the new reader queue size in Monitor a Select the Expand All button under the Physical View tab b In the Physical View tree select the DataReader c In the Status panel that is already open notice that the Total Count values for Sam ples Lost and Samples Rejected are now zero In the DataReader Cache section notice the values for Sample Count and Sample Count Peak In the Description
4. Connext DDS application If your monitored Connext DDS application is required to use a large maximum serialized type code size or transport settings that support large data you will need to change the correspond ing settings in the QoS profile used by Monitor The maximum type code serialized size is con figured under resource_limits for the participant_qos transport settings are configured under property for the participant_qos The QoS profile used by Monitor is in lt NDDSHOME gt resource xml RTIMONITOR_QOS_PROFILES xml See Section 3 8 in the Monitor User s Manual for more information on editing this file A sample large data QoS profile is provided with Connext DDS for your reference it has large data support turned on for both the UDPv4 and shared memory transports and uses large max imum type code serialized size support If you need to use large data or large type code in your Connext DDS application you can use this provided large data QoS profile in the monitored application and also uncomment the corresponding transport and maximum type code serial ized size settings in the Monitor QoS profile this will enable consistent large maximum type code serialized size and large data transport settings See the section on Monitoring Library in the RTI Connext DDS Core Libraries User s Manual for an explanation of this large data QoS profile No Type Code for Some Entities in Description Panel If the type code for your user dat
5. Count Peak 2 d In the Physical View tree select the DataReader then select the Description Panel button from the toolbar File Domain Actions Window Help lie G or80KE Create a new Description panel 3 17 Showing a Samples Rejected Scenario In the QoS tab scroll down and notice that the values for qos resource_limits max_samples and qos reader_resource_limits max_samples_per_remote_writer are both 2 which is the same as the Sample Count and Sample Count Peak values we saw in the Status panel This shows that the reader s queue for receiving samples is full QoS Builtin Topic Data ais Field Value T reader data lifecycle Li autopurge_disposed_samples_delay infinite Li autopurge_nowriter_samples_delay infinite T F reader_resource_limits Li disable_fragmentation_support false Li dynamically_allocate_fragmented_samples false Li initial fragmented_samples 4 initial infos 32 8 initial_outstanding_reads 2 4 initial remote_virtual_writers_per_instance 2 Li initial remote_writers 2 Li initial remote_writers_per_instance 2 4 intial_ remote_virtual_ writers 2 Li max app ack amp response length 0 E max_fragmented_samples 1 024 baa max_fragmented_samples_per_remote_writer 256 E max_fragments_per_sample 512 4 max_infos 1 L5 max_outstanding_reads 1 bul max_query_condition_filters 4 4 max_remote_vittual_writers
6. This will sort the table by the values in this column Clicking it again will sort in the opposite order This is useful to watch in real time to see which processes are using a lot of CPU You can sort based on any of the columns d Click the B button just above the vertical scrollbar This allows you to choose which columns appear in the table For instance to remove the ID column uncheck it Note to enable the Pack Selected Column option select a cell in the top row Kernel CPU Phy Total Memory MB 0 26 7 pm Ooo ooaj v ID Click here to v Total CPU er hea V User CPU ee To resize columns such as this one to fit v Kernel CPU their contents select this option vV Physical Memory MB v Total Memory MB Horizontal Scroll Pack All Columns Pack Selected Column You can also change the order of the columns by simply dragging them to a new place in the table e Close the Processes Table Showing System Topology Sample Counts and Rates 7 Review all the data types in the system by selecting the System Types Table button from the toolbar File Domain Actions Window Help gt ocos Anga Sasu Create a new System Types Table This will display a panel that shows all the known data types in the selected domain In this case there is only one data type called ShapeType System Types Table BHE Fina Domain 0 I Type Name Type ID Keyed Min
7. 048 464 Y Topics Duplicates Count 0 A0 sis k 7 i Square Square ShapeType Duplicates Bytes 0 40 7 m ie Y Publisher Filtered Count 0 40 Ack Count 188 42 P i i Ack Bytes 5 264 A56 gt DataWriter Square ShapeType PER Bytes 0 40 Nack Count 1 40 DataWriter Statistics Sample Statistics Heartbeat Statistics Pushed Count 9 035 480 Heartbeat Count 190 42 Pushed Bytes 758 940 46 720 Heartbeat Bytes 6 080 464 Pulled Count 0 A0 Gap Count 1 40 ulled Count 40 Gap Bytes 32 A0 Pulled Bytes 0 40 Ack Count 188 A2 Filtered Count 0 A0 Ack Bytes 5 264 A56 Filtered Bytes 0 40 Nack Count 1 40 Nack Bytes 28 A0 Rejected Count 0 40 Sen guin nene T eee hart Time Range minutes AOU Oa E A Oe ey A EE E SE il 2 t 6 2 128 System Metrics Domains 1 Hosts 1 Processes 2 Participants 2 Topics 1 Publishers 1 DataWriters 1 Subscribers 1 DataReaders 1 Summary of the current number of entities being monitored b Close the Status Panel on the right select the red at the top right corner of that panel c Select the System Overview button in the toolbar to see a summary of the monitored domain File Domain Actions Window Help t gt 24c4ov RK MEESTE Create a new System Overview panel 3 3 Showing System Topology Sample Counts and Rates cy System Overview Panel Highlight Mode Notifica
8. 1 Configure the existing instance of Shapes Demo to use the profile MonitorDemoLibrary SamplesRejectedScenario a Select Controls Configuration Stop b Choose the profile MonitorDemoLibrary SamplesRejectedScenario c Select Start 2 Create a reliable square publisher with the MonitorDemoLibrary SamplesRejected Scenario profile a Select Publish Square b Choose the profile MonitorDemoLibrary SamplesRejectedScenario c Make sure the Reliability box is checked d Select OK 3 Create a new Shapes Demo instance with a reliable subscribing rate of 1 000 ms For example on a Windows system open a command prompt and enter the following replacing the installation directory to match your system gt cd lt NDDSHOME gt bin gt rtishapesdemo bat subInterval 1000 Or on a Linux system enter the following replacing the installation directory to match your system gt cd lt NDDSHOME gt bin gt rtishapesdemo subInterval 1000 4 Inthe new Shapes Demo instance create a reliable square subscriber that uses take and the MonitorDemoLibrary SamplesRejectedScenario profile a Select Subscribe Square b Choose the profile MonitorDemoLibrary SamplesRejectedScenario c Check the Reliability box d For the Read method to use select Take Q e Select OK Showing a Samples Rejected Scenario 5 Notice that the subscriber is not receiving all the samples Let s see why a Select the Expand All bu
9. 1 for the two instances of Shapes Demo 1 In one instance of Shapes Demo create a reliable square publisher with a 100ms deadline a Select Publish Square b Make sure the Reliability box is checked c Set Deadline to 100 d Select OK 2 In the other instance of Shapes Demo create a reliable square subscriber with a 250ms deadline a Select Subscribe Square b Check the Reliability box c Set Deadline to 250 d Select OK 3 13 Showing Deadlines 3 Inthe publisher Shapes Demo instance select Controls Pause Publishing 4 Observe the results in Monitor a Select the Expand All button for the Physical View tree in Monitor Notice that all the entities in the Physical View tree are marked with yellow triangles to show there is a potential problem The root cause of the problem is in bold the DataWriter and DataReader in this case The parent entities are also marked with yellow triangles but not in bold Physical View DDS Logical View Qe Entity Description Type EN system v F BOCAGRANDE uti com T 5 Process ID 8736 T a DomainParticipant 0 7 oF Topics P Square Square ShapeType Y Publisher bo DataWriter Square shapelype Y FAl Process ID 9700 T Ea DomainParticipant 0 RT Monitoring Demo v Topics P Square Square ShapeType Y SA Subscriber gt DataReader Square ShapeType b In the Physical View tree select the DataWriter then select the Status Panel but
10. DDSHOME gt bin gt rtishapesdemo pubInterval 250 e On UNIX based systems Enter the following replacing the installation directory to match your system gt cd lt NDDSHOME gt bin gt rtishapesdemo pubInterval 250 3 9 Showing System Topology Sample Counts and Rates 11 12 T3 Just like the other Shapes Demo instances choose the profile MonitorDemoLi brary MonitorDefault In the new Shapes Demo window create a reliable square publisher of a different color a Select Publish Square b Choose the profile MonitorDemoLibrary MonitorDefault c Select YELLOW d Make sure the Reliability box is checked e Select OK Examine the data in chart a In Monitor notice the number of md p System gt Host t gt Process 8736 gt S06 RTI Monitonns Demo gt Subscnber gt DR Square ilt All Matches Chart Data Samples Received Counts x received samples increases in the chart The new DataWriter increases the number of received samples b Right click in the a0 white space in one of the charts to see how you p Properties can change the chart na Save as 30 Print D 40 E Zoom In Both Axes 30 ZoomQut es Domain Axis 20 Auto Range Range Axis c Close the two Chart panels in Se Let s see how to determine which DataWriter is contributing more received samples a In the Physical View tree select the Expand All butt
11. Host BOCAGRANDE meom gt Process 8736 gt DE 0 RTI Momtonng Demo gt Subsenber gt DE Square k Click on DP 0 RTI Monitoring Demo in the list of parent entities This will select the DomainParticipant in the Physical View tree and the Status panel will change to show the DomainParticipant s status Notice that the Status panel now shows an aggregation of the statuses of all the DataWriters and DataReaders that belong to the selected DomainParticipant 1 Close the Status panel Review all the processes in the system a Select the Processes Table button from the toolbar File Domain Actions Window Help ator i Z l agag FFO Create a new Processes Table Showing System Topology Sample Counts and Rates b This will display a panel that shows the processor and memory usage of all moni tored processes ral Processes Table STAR select in Physical Vier Host D TotalCPU UsercPU KemelCPU Physical Memory MB Total Memory MB BOCAGRANDE ti com BOCAGRANDE rti com Select one of the processes in the table and click on the Select in Physical View but ton this will select the same process in the Physical View tree The Find button is useful for searching a large table for a specific process This is a simple string search so you must use the same format displayed in the table for example notice that the process ID includes a comma c Click on the Total CPU column heading
12. RTI Monitor Getting Started Guide Version 5 2 0 a i Your systems Working as one 2011 2015 Real Time Innovations Inc All rights reserved Printed in U S A First printing June 2015 Trademarks Real Time Innovations RTI NDDS RTI Data Distribution Service DataBus Connext Micro DDS the RTI logo 1RTI and the phrase Your Systems Working as one are registered trademarks trademarks or service marks of Real Time Innovations Inc All other trademarks belong to their respective owners Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website https support rti com Contents 1 WOIC OMG ssri annae a AEAEE NaN 1 1 LE Paths Mentioned in Documenta HON bs cosceisasdis sues sudoowiasceraessunes audeptracnebdoronnieesdvosiasssttorausdvesdiodeunpagtaapacent 1 2 2 Starting RTI Monitor aise tneiniencttna vee tne decateartseneneua cane secassin satesenensticaveesiee 2 1 Bede Command l
13. Serialized Max Serialized Max Key Serialized Type Code Serialized E ShapeT pe 4328188006887ba3 ves a woj a 378 a Like the Processes Table we saw earlier this table also has a E button above the verti cal scrollbar to control the columns that appear in the table You can also sort the table based on any of the columns by clicking on the column heading Close the System Types Table 8 Show details of each data type a Select the Physical View tab on the left b Select DataReader in the tree then select the Description Panel button from the tool bar File Domain Actions Window Help YET E TOEO Create a new Description panel c In the Description panel Description Panel select the DataType tab to System gt Host BOCAGRANDE r com gt Process 6364 gt DP 0 i ETI Momnmtonng Demo gt Fabhsher gt OW Tnangle see the data type for the re data reader in IDL You Maximum Serialized Size Maximum Key Serialized Size can also see other proper a ShapeFillKind ties related to the data igre rhe TRANSPARENT_FILL 1 type HORIZONTAL HATCH FILL 2 VERTICAL_HATCH_FILL 3 Sad ie d Close the Description Extensibility EXTENSIBLE_EXTENSIBILITY Panel struct ShapeTypef string 128 gt color er key N amp D 0 9 To show panels for two or long BID 1 arr amp a long y miDb 2 more entities side by side long Shape
14. a type is larger than the default maximum type code serialized size the IDL for that data type may not show up in the DataType tab in Monitor s Description Panel However it should not affect the rest of the monitoring data To see the IDL representation of large type code in Monitor you can increase the maximum type code serialized size both in the monitored Connext DDS application and in Monitor However if you do that you will also need to increase the values in the transport settings to support large data in Connext DDS discovery traffic both in the monitored Connext DDS application and in Monitor A sample large data QoS profile is provides with Connext DDS it has large data support turned on for both the UDPv4 and shared memory transports and a larger maximum type code serial Running out of Memory 49 4 10 ized size See the section on Monitoring Library in the RTI Connext DDS Core Libraries User s Man ual for an explanation of the large data QoS profile If you use the provided large data QoS profile you can uncomment the corresponding settings in the Monitor QoS profile to enable sup port for large type code and large data Both the monitored Connext DDS application and Moni tor must have a consistent maximum type code serialized size and consistent transport settings The QoS profile used by Monitor is in lt NDDSHOME gt resource xml RTI_LMONITOR_QOS_PROFILES xml Running out of Memory If Monitor is runn
15. are b Choose the profile MonitorDemoLibrary MonitorDefault c Make sure the Reliability box is checked d Select OK In the other instance of Shapes Demo create a reliable square subscriber as follows a Select Subscribe Square b Choose the profile MonitorDemoLibrary MonitorDefault c Check the Reliability box d Select OK Start Monitor There are two ways to start Monitor e From RTI Launcher s Tools tab click on the Monitor icon e From a command prompt On UNIX based systems cd lt NDDSHOME gt bin rtimonitor On Windows systems cd lt NDDSHOME gt bin rtismonitor Showing System Topology Sample Counts and Rates 5 Review the system topology a Expand the Physical View tree by clicking the button below the Physical View tab File Domain Actions Window Help 49 S240 VOSG KE Eaz eama Physical View DDS Logical View Description Type Expa nd v BOCAGRANDE tti com Common Information th e E ntit v E Process ID 8736 ion NA Monitoring Data available through aggregation y Y DomainParticipant 0 RTI Monitoring Demo Wed Sep 04 16 58 04 EDT 2013 tree Y Topics j 5 0 seconds Square Square ShapeType T v yp Subscriber DataReader Statistics SW DataReader Square ShapeType Srinagar Thai anes y F3 Process ID 9700 Received Count 9 041 A 81 Heartbeat East 4189 A 2 Y DomainParticipant 0 RTI Monitoring Demo Received Bytes 759 444 46 804 Heartbeat Bytes 6
16. cations in the entire system not just for the selected entity By default it shows both warnings and errors You can choose to see either just the warnings or just the errors by checking unchecking the options A All Notifications Table MET Select in Vie Show Problem Types Warning W Error Entity State Status System gt Host BOCAGRANDE rti com Pro WARNI System gt Host BOCAGRANDE ti com Pro WARNI i If a row is selected in the All Notifications Table clicking the Select In Views button will select the corresponding entity in the tree views d Close the All Notifications Table panel e Select the System Overview Panel button S from the toolbar Select the Notifica tions option All the entities in the system that have caused a notification are high lighted in the system map f Close the System Overview Panel Clear the notifications a In the publisher shapes demo instance select Controls Resume Publishing 3 15 Showing a Samples Rejected Scenario b From Monitor s menu select the Clear All Notifications button from the toolbar This will clear all the yellow markers in the tree File Domain Actions Window Help aac sath SuliaB2e aga Clear All Notifications 7 Prepare for the next demo a In one instance of Shapes Demo select Controls Delete All b Close the other Shapes Demo instance 3 4 Showing a Samples Rejected Scenario
17. cipantMonitoring _ initializeMonitoringLibrary ERROR Failed to get load monitoring library CREATE Participant DDS DomainParticipantMonitoring initializel create monitoring library instance CREATE Participant DDS DomainParticipant createI create builtin monitor ing support CREATE Participant DDS DomainParticipantFactory create participant _ disabledI create participant Not Receiving Monitoring Data due to Inconsistent QoS 4 6 These messages most likely mean that your Connext DDS application is configured to load the monitoring library dynamically but you don t have the monitoring library in your path The environment variable that needs to include the monitoring library depends on your plat form J Linux LD_LIBRARY_PATH J OS X DYLD_LIBRARY_PATH I Windows PATH If you see error messages similar to the following CREATE Participant DDS DomainParticipantFactory set default participant gqos ERROR Inconsistent QoS more information at WARN verbos ity level CREATE Participant DDS DomainParticipantFactory load profilesI ERROR loading profiles CREATE Participant DDS DomainParticipantFactory create participant dis abledI ERROR loading profiles These messages most likely mean that you are using a lot of properties in the ParticipantQos to configure monitoring and Participant property string max length Or Participant property list max length in the DomainParticipant s ResourceLimitsQosPolicy is not large
18. conds lt seconds gt to calculate aggregated statistics and states This value con trols that minimum period specified in seconds Default 5 seconds Monitor saves some statistics history so it can be displayed in the charts This option controls how much historical data historyDepth lt value gt number of samples is saved per monitoring topic Default 12 samples 2 1 Command line Options Table 2 1 Command line Options Instructs Monitor to ignore any type conflicts In Monitor type conflicts are based on type code equality rather than type compatibility This command line option can be useful if you have types that have different type code but are com patible ignoreTypeConflicts Default Not specified do not ignore type conflicts Specifies which domains Monitor will join when it starts up lt domain_id_list gt is a list of domain IDs each separated by a comma To specify multiple domain IDs on a Windows system enclose the comma separated IDs in quotation marks For example initialDomainIds 31 32 initialDomainIds lt domain_id_list gt Default If not specified you will be prompted to enter a domain ID when Monitor starts Specifies the period at which to refresh the system overview matchRefreshPeriodSeconds lt seconds gt panel s matches Default 5 seconds ms A Specifies the number of notifications to keep per entity notificationHistoryDepth lt value gt ER Defaul
19. counts are about the same ll Chart Panel Jox ail P System gt Host BOCAGRANDE ticom gt Process 9700 gt DP 0 RTI Momtonny Demo gt Fublsher gt DW Square Filt All Matches Chart Panel 2 System gt Hoest BOCAGRANDE tLcom gt Fro RTI Momtonng Demo gt Subsenber gt DR f Fit All Matches Chart Data Samples Written Counts Chart Data Samples Received Counts 20 Notes e The default settings set the publish rate of the monitoring topics to 5 seconds Therefore you may need to wait 5 seconds for the Monitor data to be updated e The charts for Samples Written Counts and Samples Received Counts show the number of samples sent received in the last sample period In this case the sam ple period is 5 seconds Since Shapes Demo publishes 16 samples per second you will see approximately 80 100 samples per sample period depending on your platform e The Chart Time Range slider at the bottom of Monitor changes the time scale of the graphs e To unpin the panels press their pin buttons again Notice that now both chart pan els are showing DR as the current entity at the top since that entity is selected in the Physical View tree 10 Start a third instance of Shapes Demo with a specific publishing interval e On Windows systems Open a command prompt and enter the following replacing the installation directory to match your system gt cd lt N
20. enough to accommodate all the properties Try increasing those values in your Con next DDS application to fix the problem Not Receiving Monitoring Data due fo Inconsistent QoS If you see an error message similar to the following WARN com rti dds monitor util DebugDataReaderLis tener on requested incompatible qos Unknown Source topic rti dds mon itoring domainParticipantDescription RequestedIncompatibleQosStatus total count 1 total count change 1 last policy id Durability policies QosPolicyCount policy id Durability counts1 This message most likely means that the internal DataWriters created by Monitoring Library for publishing monitoring topics have QoS that are incompatible with the QoS of the internal DataReaders created by Monitor for subscribing to monitoring topics If you see this error message try specifying the rtiimonitor config qos_library and rti moni tor config qos_profile properties in the Connext DDS application that has monitoring turned on to ensure that the internally created DataWriters are using the correct QoS values The default QoS values used for the internally created DataReaders are listed in RTIMonitoringQosLibrary and RTIMonitoringPublishingQosProfile in the file lt NDDSHOME gt resource xml MONITORING_QOS_PROFILES xml See the section on Monitoring Library in the RTI Connext DDS Core Libraries User s Manual for an explanation of the QoS settings that are required to spec ify the Q
21. evi ously selected entity in the Physical View tree and the System Overview panel Try the Forward button d gt too In the System Overview panel select the Measurement option and Samples Received Count in the drop down menu You will see a color map that indicates the number of samples received by various entities in the system b3 System Overniew Panel BEEJ Highlight Mode O Notifications Matches Measurement Measurement Samples Received Count cale No Scaling LJ Key Selected 0 Display Name Controls All To pic Name i DomainPanticipant To pic Name Publisher To pic Name Host Topic Name Topic Topic Name DataReader Topic Name i i Subscriber Topic Name i DataWriter Topic Name Notes e To change the scaling of the numbers indicated in the color map use the Scale drop down menu e Move the mouse over the entities in the map to see a tooltip of the actual value e You can select different Display Name Controls for each kind of entity or all enti ties to control how much detail will appear in the map in the System Overview panel g Close the System Overview panel h In the Physical View tree select the DataWriter then select the Status Panel button in the toolbar File Domain Actions Window Help gt 24eo78 SKN Suliase ea Create a new Status panel i Select the Advanced display mode Showing System Topology Sample Counts and Rates
22. iddsgen L path to examples gt Examples are copied into your home directory the first time you run RTI Launcher or any script in lt NDDSHOME gt bin This document refers to the location of these examples as lt path to examples gt Wherever you see lt path to examples gt replace it with the appropriate path By default the examples are copied here e Mac OS X systems Users your user name rti_workspace version examples e UNIX based systems home your user name rti_workspace version examples e Windows systems lt your home directory gt rti_workspace version examples 1 2 Paths Mentioned in Documentation You can specify a different location for the rti_workspace directory You can also specify that you do not want the examples copied to the workspace See the RIT Connext DDS Core Libraries Getting Started Guide 1 3 Chapter 2 Starting RTI Monitor There are two ways to start Monitor LI From RTI Launcher s Tools tab click on the Monitor icon L From a command prompt e On UNIX based systems cd lt NDDSHOME gt bin f rtimonitor e On Windows systems cd lt NDDSHOME gt bin rtimonitor Command line options are described in Section 2 1 2 1 Command line Options Monitor accepts the command line options in Table 2 1 Table 2 1 Command line Options Monitor periodically goes through all the monitored entities in the system this information is saved in its own database ageregationPeriodSe
23. ine Op MOMs sgiot mE T 2 1 3 A Demo using RTI Shapes Demou iiieeereeeeseeeeseeessees seen seans ne ee 3 1 3 1 Showing System Topology Sample Counts and RatesS ieeeeeeeeeeeeeeseeseenseeeesscesssessssesssssse 3 1 32 Showing Content Filtered SampleSssiseriiaini eni a n ai a ns saciuasigseredemeenys 3 12 33 SOO WAS DeadIN ES inana g A EE A T 3 13 24 Showing a amples Rejected Senar sire e AA 3 16 A io blesho oiin oen eanga bheadh EEan 4 1 41 Debugging Problems with Monitor on Windows System sesessssssssessesessssesesnesesnesesesnenesnenesess 4 42 Running Monitor on a System with Limited MeMory cccceccesssseeseseeessesesseesseseeseeseessesseeees 4 1 43 Running Monitor with a Large Sy Sten sciseeaaea oineach neas e aE oaasa sh haigh A ah aga aghain 4 1 44 Error Regarding Incompatible Shared Memory Segment c ccc eeeeeseseeseceeeeseeessesseeeenees 4 2 4 5 Unable to Create Participant in Connext DDS Application cece eee cseeseseeeseeeeeseeeeeees 4 2 4 6 Not Receiving Monitoring Data due to Inconsistent QoS eee ec cec eee eeseseseeeseeseeseeeeeseneenes 4 3 47 N t Receiving Monitoring Data tor Entities siacaaccissscac dust ieusaniunssin wad nana a SE 4 4 4 8 No Type Code for Some Entities in Description Panel ccc ceeeeeeeececeeeseeseeeseseesseesseaeeees 4 4 AO Rannin outo MeMO iens anas diana GG ar to anetuascvandg stars duce auras ature esnasaer nama use 4 5 4 10 Running without an Active Ne
24. ing out of memory you can use a smaller value for the historyDepth com mand line option or run Monitor on a 64 bit machine Running without an Active Network Interface If you run Monitor on a computer that does not have an active network interface you may see an error message stating No interface found enabled for multicast Modify the QoS profile used by Monitor to turn off UDPv4 and only use the shared memory transport lt participant qos gt lt transport builtins lt mask gt SHMEM lt mask gt lt transport builtins lt participant qos gt The QoS profile used by Monitor is in lt NDDSHOME gt resource xml RTI_MONITOR_QOS_PROFILES xml See Section 3 8 in the Monitor User s Manual for more information on editing this file
25. is value is 12 If you are running on a system with limited memory you can decrease this value with the command line option historyDepth lt value gt see page 2 1 Running Monitor with a Large System Monitor runs with Java and a default maximum Java heap size of 500m If you are monitoring a very large system you may need to modify lt NDDSHOME gt bin rtimonitor bat on Windows systems or lt NDDSHOME gt S bin rtimonitor on UNIX based systems to increase the maxi mum Java heap size usage For example in the script change Xmx500m to Xmx1536m 4 1 Error Regarding Incompatible Shared Memory Segment 4 4 4 5 Error Regarding Incompatible Shared Memory Segmenf If you see the following error messages D0000 ENABLE NDDS Transport Shmem attach writer incompatible shared mem ory segment found Found segment with max message size 9216 Needed 65530 These messages likely mean either a Another application is currently running on the same host in the same domain with different shared memory transport settings or b If you are on a Linux system there was an old application running on that domain ID before with different shared memory transport settings that was not terminated gracefully To correct problem a if you do not intend to monitor the application that has different shared memory settings on the same host you can use another domain ID for the monitoring topics both in Monitor a
26. nd in the Connext DDS applications that you want to monitor If you intend to monitor all the Connext DDS applications in that domain on the same host make sure that all the applications running on the same host with the same domain ID have consistent shared mem ory transport settings The QoS profile used by Monitor is in lt NDDSHOME gt resource xml RTI_MONITOR_QOS_PROFILES xml The transport settings in this profile need to be consis tent with the transport settings in all the Connext DDS applications that are running on the same host with the same domain ID All shared memory transport settings are specified under the participant_qos and have property names that begin with dds transport shmem builtin See the section on Monitoring Library in the RTI Connext DDS Core Libraries User s Manual for an explanation of the transport settings To correct problem b use the ipcrm command to clean up the shared memory and shared semaphore resources See the RTI Connext DDS Core Libraries Platform Notes for details You can also run Monitor and the Connext DDS application that you want to monitor with another domain ID that doesn t have any shared memory or shared semaphore resources left over from previous runs Unable to Create Participant in Connext DDS Application If you see error messages similar to the following CREATE Participant RTIOsapiLibrary open error opening library rtimonitoringnothing dll CREATE Participant DDS DomainParti
27. nnext DDS notifies Monitoring Library every time an entity is created deleted or a QoS is changed Monitoring Library also periodically queries the status of all entities Monitoring Library sends all the data to Monitor once it gets the data from the Connext DDS application 1 1 Paths Mentioned in Documentation 1 1 Paths Mentioned in Documentation The documentation refers to L lt NDDSHOME gt This refers to the installation directory for Connext DDS The default installation paths are e Mac OS X systems Applications rti_connext_dds version e UNIX based systems non root user home your user name rti_connext_dds version e UNIX based systems root user opt rti_connext_dds version e Windows systems user without Administrator privileges lt your home directory gt rti_connext_dds version e Windows systems user with Administrator privileges C Program Files rti_connext_dds version You may also see NDDSHOME or NDDSHOME which refers to an environment variable set to the installation path Wherever you see lt NDDSHOME used in a path replace it with your installation path Note for Windows Users When using a command prompt to enter a command that includes the path C Program Files or any directory name that has a space enclose the path in quotation marks For example C Program Files rti_connext_dds version bin rtiddsgen or if you have defined the NDDSHOME environment variable SNDDSHOMES bin rt
28. o icon e From a command prompt On UNIX based systems cd lt NDDSHOME gt bin rtishapesdemo On Windows systems cd lt NDDSHOME gt bin rtishapesdemo 3 1 Showing System Topology Sample Counts and Rates a When the Shapes Demo window appears open the Configura SS tion dialog under Controls If E the Stop button is enabled press S it incle Tria gi b Uncheck the Enable distributed logger checkbox Shape Extended c From the drop down list of pro files choose MonitorDemoLi brary MonitorDefault Triangl Choose the domain 9 Dalag Choose the profila Hide 1 Default Default T ch IRTI Shapes _Lib Shapes_ Default Profis gongi Bisita RTT_Shapes_Lib Batching TI Shapes LID History KeepLast 20 able distributed RTI Shapas Lib Ownership Sharad RTI Shapas Libs Ownership _Excusive m1 Shapes _Lib Durabiity_Volatile Manage QoS ATI Shapes _Lib Durabiity Transient Shapes Demo will use domain ID 0 by default If you choose to use a different domain ID make sure to use the same value in both instances of Shapes Demo d Press Start Name ect Ee ee Se ll A i Li HR MonitorDemoLibrary MonitorDe fault MonitorDemoLibrary FixedSamplesRejec User RTI Shapes Lib User Shapes Dei e Repeat so you are running two instances of Shapes Demo In one instance of Shapes Demo create a reliable square publisher as follows a Select Publish Squ
29. oS library and profile 4 3 Not Receiving Monitoring Data for Entities 4 7 4 8 Not Receiving Monitoring Data for Entities Some of the monitoring topics the description monitoring topics can have data that is larger than what is supported by the default transport settings especially for cases in which a lot of propagated properties are added to the PropertyQosPolicy or a large UserDataQosPolicy Topic DataQosPolicy or GroupDataQosPolicy is involved By default asynchronous publishing is used for the writers in Monitoring Library for these monitoring topics to resolve the large data issue transport settings and the maximum type code serialized size are left at the default val ues The maximum type code serialized size and transport settings must be consistent between Moni tor and the Connext DDS application in which monitoring is enabled By keeping the maximum type code serialized size and all the transport settings at default values in the QoS profile used by Monitor all monitored Connext DDS applications that use default settings will work with Monitor out of the box If you are not receiving monitoring data it is most likely because you do have inconsistent transport settings or inconsistent maximum type code serialized size settings between Monitor and the Connext DDS application in which monitoring is enabled maybe you are not using the default maximum type code serialized size or transport settings in the monitored
30. on b Select the DataReader in the tree then select the Status Panel button from the toolbar For Filter by match select the first matching endpoint in the drop down menu c Select the Status Panel button again to open a second status panel for the reader For Filter by match select the second matching endpoint in the drop down menu 3 10 Showing System Topology Sample Counts and Rates Now you have status for both of the reader s matching writers side by side The Received Count values will point out which one is contributing more samples Status Panel J mj xJ of Status Panel 2 System gt Host BOCAGRANDEstcom gt Fa RTI Momtonny Demo gt Subsenber gt DR Host BOCAGRANDE tti com gt Process 9700 System gt Ht BOCAGRANDEsh com gt Process 8736 gt DP i RTI Momtonny Demo gt Subsenber gt DE Square Host BOCAGRANDE ti com gt Process 11324 gt DP 0 RTI Monitoring D ilt Display Mode Basic Advanced Display Mode Basic Advanced Common Information Common Info Version 5 0 0 20 Monitoring Data Version 5 0 0 20 N Last Update Wed Sep 04 17 57 16 EDT 2013 Last Update Wed Sep 04 17 57 16 EDT 2013 Update Feriod 5 0 seconds Update Feriod 5 0 seconds DataReader Statistics DataReader St sample Statistics Heartbeat Statistics sample Statistics i Heartbeat Count E Rec d Count 1 439 A20 Rec d Count 66 008 A871 EE 1 439 a20 Hear
31. panel that is already open notice in the QoS tab that the values for qos resource_limits max_samples and qos reader_resource_limits max_samples_per_remote_writer are now 100 This is larger than the SampleCount and Sample Count Peak values seen in the Status panel This shows that now the reader queue still has a lot of room before it becomes full and starts dropping sam ples This concludes the demo Chapter 4 Troubleshooting 4 1 4 2 4 3 Debugoing Problems with Monifor on Windows System If you run Monitor on a Windows system and it is not showing any error messages but the Mon itor window is not showing up or you are not seeing any data in the Monitor window you can modify lt NDDSHOME gt bin rtimonitor bat to change javaw exe to java exe so that error messages will be displayed in a command prompt to help you debug the issue Running Monitor on a System with Limited Memory Monitor runs with Java and a default maximum Java heap size of 500m If you are monitoring on a system with very little memory and you are only monitoring a very small system you may be able to reduce memory usage by modifying lt NDDSHOME gt bin rtimonitor bat on Windows systems or lt NDDSHOME gt bin rtimonitor on UNIX based systems to decrease the maxi mum Java heap size usage For example in the script change Xmx500m to Xmx300m Monitor will save some history of statistics to be displayed in the charts By default th
32. size MED 3 a IE for comparison you can nepExtensibility EXTENSIBLE_EXTENSIBILITY struct ShapeTypeExtended ShapeType press the pin button at public ShapeFilikind filikind ID 4 the top left corner of all the ae ce eae 1 ite i eExtensibilitvy EXTENSIBLE EXTENSIBILITY entity specific panels The panel is then pinned to the entity and the panel will periodically receive updated data for the pinned entity even when another entity is selected in the tree a Select the Physical View tab on the left b From the menu make sure Window Auto Checkerboard Tile is checked Showing System Topology Sample Counts and Rates c In the Physical View tree select the DataWriter then press the Chart button in the toolbar File Domain Actions Window Help ass Gack Sul B F LO Create a new Chart panel S56 eite d In the Chart panel press the pin button amp on the top left corner Notice that the but ton has changed to pinned to indicate that the panel is pinned to a specific entity For Chart Data select Samples Written Counts e In the Physical View tree select the DataReader then press the Chart button in the toolbar to create the second Chart panel and press its pin button amp For Chart Data select Samples Received Counts f Now you can compare the DataWriter s Samples Written Counts and the DataReader s Samples Received Counts side by side Notice that the send and receive sample
33. storical data instead of live data Click OK to close the dialog box 15 Prepare for the next demo a Select the Join Domain button from the toolbar You will see a prompt asking if you want to lose the currently loaded data Click OK to continue Rejoin your original domain by entering the domain ID then click OK Notice that the title of Monitor is no longer showing Historical data mode Monitor is showing live data again b Close all the panels 3 2 Showing Content Filtered Samples The steps in this section assume you are using the same profile used in Section 3 1 for the two instances of Shapes Demo ie In one instance of Shapes Demo create a reliable sguare publisher a Select Publish Sguare b Make sure the Reliability box is checked c Select OK In the other instance of Shapes Demo create a content filtered reliable square subscriber a Select Subscribe Sguare b Check the Reliability box c Check the Use Filter box under Content Filter Topic d Select OK Notice that the subscriber only receives samples that are within the filtering square Observe the filtered samples in Monitor a Select the Expand All button for the Physical View tree in Monitor b In the Physical View tree select the DataReader The Status panel is showing values for the DataReader Notice that the Sample Statis tics Filtered Count is zero This shows that content filtering is only happening on the writer side in this case
34. t 12 notifications Sets the period at which Monitor should clean up user inter face objects such as the Host and Process nodes in the tree views that are no longer current have no more children nodes in the tree view This value should be increased when dealing with very large systems where the time to complete discovery is longer than the default value of 3 seconds pruneDeadObjectsPeriodSeconds lt seconds gt Default 3 seconds Instructs Monitor to use multiple threads according to the number of cores on the host to retrieve data from its DataReaders which contain monitoring data This is typi spawnReadThreads cally only needed for very large systems Default Not specified use a single read thread to retrieve data at a period of 1 second Sets the verbosity for Monitor and Connext DDS silent both Connext DDS and Monitor errors both Connext DDS and Monitor warnings Monitor only verbosity lt value gt warnings both Connext DDS and Monitor information Monitor only tracing Monitor only tracing both Connext DDS and Monitor Default 1 Chapter 3 A Demo using RTI Shapes Demo Before going through the steps in this chapter make sure that both RTI Monitor and RTI Shapes Demo are installed 3 1 Showing System Topology Sample Counts and Rates 1 Start two instances of Shapes Demo There are two ways to start Shapes Demo e From RIT Launcher s Tools tab click on the Shapes Dem
35. tbeat Bytes ioii t Received Bytes 120 876 A 414880 GaP Count Received Bytes Gan Avtes Delta value shows the change for the update period 14 Let s see how to save the current data to be used for future analysis a Select the Save Data button in the toolbar ill EEH amp 4 ra Save Data b Select a location and enter a filename in the file dialog c Close the third instance of Shapes Demo the one started with pubInterval 250 that is publishing yellow squares d In the remaining two instances of RTI Shapes Demo select Controls Delete All No shapes publications or subscriptions should be running in the system now e Select the Load Data button from the toolbar Lodd Data f You will see a prompt asking if you want to lose the current data and leave the domain Select OK to continue In the file dialog select the file in which you previ ously saved the data Notice that the title of the Monitor window has changed to Historical data mode and shows the name of the loaded data file Now you are seeing a snapshot of the system g Select the Expand All button for the Physical View tree You can see all the previ ously created entities even though no publications or subscriptions are currently run ning 3 11 Showing Content Filtered Samples h Select Domain Show Current Domain from the menu Notice that you are not joined to any domain now because Monitor is showing hi
36. tions O Matches Measurement Measurement Samples Received Count Scale No Scaling Display Name Controls All Topic Name DomainPanrticipant Topic Name T Publisher Topic Name Host Topic Name Topic Topic Name DataReader Topic Name Process Topic Name Subscriber Topic Name DataWriter Topic Name i T Topic Visual map of the system DR DataReader Outer most box represents the host DW DataWriter Sub Subscriber Pub Publisher DP DomainParticipant P process ID d Select the Matches option in the System Overview panel Select DW or DR in the sys tem map to see what entities are matched in the system Lil system Overview Panel BAB Highlight Mode Notifications Matches O Measurement Measurement Samples Received Count Scale No Scaling Key Display Name Controls All Topic Name T DomainPanrticipant Topic Name v Publisher Topic Mame Host Topic Name Y Topic Topic Mame a DataReader Topic Name Process Topic Name Subscriber Topic Name DataWriter Topic Name T z eae III DF 0 RTI Monitoring Demo DFP 0 RTI Monitoring Demo Process 8736 Process 9700 Host BOCAGRANDE ni com Showing System Topology Sample Counts and Rates Notice that when you select an entity in the system map that entity also becomes selected in the Physical View tree Click the Back button aa on the toolbar it will change the selection back to the pr
37. ton in the toolbar In the Status panel select the Offered Deadlines Mlissed Advanced display mode Under Offered Deadlines Missed notice the t Count non zero Total Count highlighted in yellow In the Physical View tree select the DataReader Now the Status Panel is showing values for the DataReader Under Requested Deadlines Missed you will see a non zero Total Count highlighted in yellow Requested Deadlines Missed Total Count You may notice that the DataWriter s Offered Deadlines Missed Total Count is dif ferent than the DataReader s Requested Deadlines Missed Total Count That s because these entities were created with different deadline values 100ms for the writer 250ms for the reader e Close the Status panel 5 Look at the notifications a In the Physical View tree select the DataWriter then select the Notifications Panel button in the toolbar File Domain Actions Window Help ETITI EFORIE Create a new Notifications panel Showing Deadlines The Notifications panel displays the selected entity s current status and a historical list of all alarm statuses related to the selected entity Notifications Panel c0a80183 2220 2 s0008002 a Wed Sep 04 19 30 36 EDT 2013 N b Close the Notifications panel c Select the All Notifications Table button from the toolbar Create a new All Notifications Table The All Notifications Table displays all the notifi
38. tton for the Physical View tree in Monitor b In the Physical View tree select the DataReader then select the Status Panel button from the toolbar c Select the Advanced display mode Notice that the Total Count values for Samples Lost and Samples Rejected are non zero This indicates that not all samples are being received Samples Lost and Sam ples Rejected are both yellow to indicate that this may or may not be a problem depending on your use case Also notice further down under DataReader Cache that both Sample Count and Sample Count Peak are 2 you will see why this is significant later DataReader Statistics Sample Statistics Heartbeat Statistics Received Count 2 365 A82 Heartbeat Count 82 A4 Received Bytes 198 660 A 6 888 Heartbeat Bytes 2 624 4128 Duplicates Count 0 40 Gap Count 1 A0 Duplicates Bytes 0 40 Gap Bytes 32 A0 Filtered Count o 40 Ack Count 25 41 Filtered Bytes o 40 Ack Bytes 700 428 Rejected Count 2411 ABD Cong 57 43 Nack Bytes 1 820 A96 Sass mh Samples Rejected Total Count 2 260 495 Total Count Last Reason LOST BY WRITER Last Reason Liveliness Changed Last Instance Handle cac217c3 18363f8e f1160eee def9e886 Alive Count 14 A0 Requested Incompatible QoS Not Alive Count OT aoe aces 0 40 Last DataWriter GUID c0a80183 2220 4 80000002 ang id Invalid Requested Deadlines Missed Taliesin Caida Total Count 0 40 Sample Count 2 Last Instance Handle Sample
39. twork Interface cee eee cccscesceeeeseceeeseeseescseeseessessessesseeeeeeenes 4 5 iii Chapter 1 Welcome RTI Monitor is a graphical tool that displays monitoring data from RTI Con Comnext Application Connext Application next DDS applications Monitor will help you i N Lo i I Understand your system with RTI RTI i Monitoring mm Monitoring an easy to use graphical view Library A Hay into your entire Connext DDS application I Verify your design by making a Bo sure the entities in your Connext Beer e DDS applications are communi e ES SES mm cating as expected BE e I Tune performance by providing deep statistics on every aspect of the middleware s operation I Optimize integration with gt detailed information on every ennetacon entity in your system RTI Monitor I Monitor real time operation with a dashboard of tools to see traffic patterns errors lost samples and more You can run Monitor on the same host as the Connext DDS application or on a different host To enable a Connext DDS application to provide monitoring data to Monitor the application needs to use the RTI Monitoring Library plug in included with Connext DDS Monitoring is enabled in the application by setting values in the DomainParticipant s Property OosPolicy programmatically or through an XML QoS profile See the Monitoring Library sec tion of the RTI Connext DDS Core Libraries User s Manual Co
Download Pdf Manuals
Related Search