06ESIW016

1
AUTOMOTIVE
INFOCOM
TRANSPORT ENVIRONMENT
AERONAUTICS
SPACE
DEFENCE SECURITY
A DIS Socket for PSI-SA Merging DIS and
HLA06E-SIW-016 Herbert Tietje, Hartmut
Ufer, Franz SchubertStockholm, June 21, 2006
2
Contents page

• 1. Introduction 3
• 2. DIS Socket 13
• Tests and Results 18
• Conclusion 25

3
Contents page

• 1. Introduction 3
• 2. DIS Socket 13
• Tests and Results 18
• Conclusion 25

4
Naval Simulation Networking via DIS

• TVT Taktischer Verfahrenstrainer (Tactical
  Procedures Trainer), Bremerhaven
• EZ/AZ F122/F123 Frigate Training Centre,
  Wilhelmshaven

5
The Architecture of PSI-SA

• PSI-SA Proposed Standard Interface for
  Simulation Applications

6
Contents of the DIS Socket

• The user sees the HLA objects and interactions of
  RPR FOM 2.0 Draft 17
• 32 PDUs were implemented, all 27 PDUs of IEEE
  1278.1-1995 and 5 PDUs of IEEE 1278.1a-1998
• Underwater Acoustic PDU
• IFF/ATC/NAVAIDS PDU
• Minefield State PDU
• Environmental Process PDU
• Gridded Data PDU

7
Object Classes of RPR FOM 2.0 (1)
8
Object Classes of RPR FOM 2.0 (2)
9
Interaction Classes of RPR FOM 2.0 (1)
10
Interaction Classes of RPR FOM 2.0 (2)
11
Relations between PDU and HLA object classes
12
The Configuration for Testing of the DIS Socket
13
Contents page

• 1. Introduction 3
• 2. DIS Socket 13
• Tests and Results 18
• Conclusion 25

14
The overall Software Architecture of the DIS
Socket

• UDP/IP in broadcast or unicast mode
• Seperate receive thread for incoming datagrams

15
Details

• DIS Entities are identified by the Entity ID
• HLA Objects are identified by the HLA
  ObjectInstanceName
• Mapping between Entity ID and ObjectInstanceName
  needed
• Entity ID not known at DiscoverObjectInstance
• Entity State PDUs are send out, if Entity ID,
  Entity Type, and Spatial are updated other
  Object PDUs, if Entity ID is updated

16
Heartbeat Mechanism for PDU

• The DIS socket sends PDUs according to the
  heartbeat mechanism
• Only changes in received PDUs are communicated to
  PSI-SA

17
Mapping RPR FOM - DIS

• Domains for DIS
• 0 Other
• 1 Land
• 2 Air
• 3 Surface
• 4 Subsurface
• Space
• Object Class AmphibiousVehicle has no
  corresponding Domain in DIS
• Differentation with Category of SurfaceVessel
• Landing Craft
• Hydrofoil
• Air Cusion/Surface Effect
• Amphibious Assault Ship
• Amphibious Cargo Ship
• Amphibious Transport Dock

18
Contents page

• 1. Introduction 3
• 2. DIS Socket 13
• Tests and Results 18
• Conclusion 25

19
Contents of the Configuration File
DIS_Socket.dcd
DIS-Socket config File DIS_Socket.dcd
LogLevel 0 Site 11 Application 4
Exercise 1 Hostname (Broadcast, Localhost,
lthostgt) Broadcast Port 6994
SelfDeliveryEnabled 0 HRT_BEAT_MPLIER 2.4
HRT_BEAT_TIMER 5.0 UA_STATE_UPDATE_HRT_BEAT
_TIMER 180.0 IFF/ATC/NAVAIDS_DFLT 10.0
MINEFIELD_DFLT 5.0 GD_HRT_BEAT_TIMER 900.0
20
Script for DIS Socket Tester (1)
ltConnect "F1" "RPR FOM20" "FEDTester" "RPR
FOM20.fed"gt ltPublish objectClass"ObjectRoot
.BaseEntity.PhysicalEntity.Platform.Aircraft"gt ltPu
blish ltPublish objectClass"ObjectRoo
t.BaseEntity.PhysicalEntity.Platform.SurfaceVessel
"gt ltPublish interactionClass"InteractionRoo
t.WeaponFire"gt ltPublish interactionClass"In
teractionRoot.MunitionDetonation"gt ltSubscribe
objectClass"ObjectRoot.BaseEntity.PhysicalEntity.
Platform.Aircraft"gt ltSubscribe
objectClass"ObjectRoot.BaseEntity.PhysicalEntity.
Platform.SurfaceVessel"gt ltSubscribe
interactionClass"InteractionRoot.WeaponFire"gt ltSu
bscribe interactionClass"InteractionRoot.Muni
tionDetonation"gt ltCreateObject "objectRoot.BaseEnt
ity.PhysicalEntity.Platform.Aircraft"
"DIS000110000400001"gt ltUpdate "DIS000110000400001"
lt EntityType" 1 2 78 1 2 0 0
", EntityIdentifier" 11 4 1 ",
Spatial" DRM_RVW 39565.2 47955.2
50287.2 false 1.1 0.2 0.3
10.1 11.2 12.3 3.1 3.2 3.3 4.1 4.2 4.3
", AlternateEntityType" 1 2 78 1 2
0 0 ", DamageState"SlightDamage",
FlamesPresent"true",
ForceIdentifier"Friendly", Marking"
ASCII 65 66 67 68 69 70 71 72 73 74 0 ",
PowerPlantOn"true" gt gt
21
Script for DIS Socket Tester (2)
ltSendInteraction "interactionRoot.MunitionDetonati
on" lt DetonationLocation"
39057.2 47950.2 50287.2 ",
DetonationResultCode"EntityProximateDetonation",
EventIdentifier" 7 'DIS000110000400001
' ", FiringObjectIdentifier"
'DIS000110000400001' ",
FinalVelocityVector" 110 120 130 ",
FuseType"Contact", MunitionObjectIdentifi
er" ' ' ", MunitionType" 2 1 1 1 2 2
2 ", QuantityFired"1",
RateOfFire"0", RelativeDetonationLocation
" 0.3 0.5 0.7 ", TargetObjectIdentifier
" 'DIS000110000400022' ",
WarheadType"HighExplosive" gt gt ltDELAY
5.0gt ltDeleteObject "DIS000110000400001"gt ltDELAY
0.01gt ltDeleteObject "DIS000110000400022"gt ltDELAY
0.01gt ltDisConnect "F1"gt Ende Tag
22
Logging of PDU Tester (1)
1 Entity State PDU Version 5
Exercise 1 PDU-Type 1 Protocol-Family
1 Time Stamp 3097541096 Length 144 Byte
Padding 0 Time 4316.329 Entity Site
11 Application 4 Entity 1 Force ID
1 Articulation Parameter 0 Kind 1
Domain 2 Country 78 Cat 1 Sub 2 Spec 0
Extra 0 Kind 1 Domain 2 Country 78 Cat 1 Sub
2 Spec 0 Extra 0 Vx 10.1000 Vy
11.2000 Vz 12.3000 v 19.461 m/s X
39565.200 Y 47955.200 Z
50287.200 psi 1.1 theta 0.2
phi 0.3 Appearance 4227080 0x408008
Slight Damage Flaming Power Plant on Dead
Reckoning-Algorithmus 4 0 0 0 dsx
0 dsy 0 dsz 0 ax
3.1 ay 3.2 az
3.3 omx 4.1 omy 4.2 omz
4.3 Marking 1 65 66 67 68 69 70 71 72 73
74 0 Capabilities 0 v_max 400.00 m/s ,
b_max 40.00 m/s2 , omega_max 20.00 1/s
Status 9
23
Logging of PDU Tester (2)
7 Detonation PDU Version 5 Exercise
1 PDU-Type 3 Protocol-Family 2 Time
Stamp 3098176224 Length 136 Byte Padding
0 Time 4316.861 Firing Site 11
Application 4 Entity 1 Target Site
11 Application 7 Entity
12 Munition Site 0 Application 0
Entity 0 Event Site 11 Application
4 Entity 7 Vx 110.000 Vy
120.000 Vz 130.000 v 208.33 m/s X
39057.200 Y 47950.200 Z
50287.200 Muni Kind 2 Domain 1 Country 1
Cat 1 Sub 2 Spec 2 Extra 2 Head 1000 Fuze
1000 Quantity 1 Rate 0 x
0.3 y 0.5 z
0.7 Detonation Result 2 Entity Proximate
Detonation Status 2061
24
Configuration at the overall Test in October 2005

• BHV Bremerhaven
• WHV Wilhelmshaven

25
Contents page

• 1. Introduction 3
• 2. DIS Socket 13
• Tests and Results 18
• Conclusion 25

26
Conclusion

• In this project, a DIS socket for PSI-SA was
  developed
• The user handles the HLA objects and interactions
  of RPR FOM 2.0 Draft 17
• 32 PDUs are implemented, all 27 PDUs of IEEE
  1278.1-1995, and 5 PDUs of IEEE 1278.1a-1998
• Additions are driven by user needs
• The combination of a DIS socket with an RTI
  socket allows for the creation of a DIS HLA
  gateway

27
Your contact

• IABG mbH
• VG 14
• Dr. Herbert Tietje
• Schiessplatz (Geb. 170)
• 49716 Meppen
• Germany
• Phone [phone]
• Fax [phone]
• tietje_at_iabg.de
• www.iabg.de