Scribd
Upload
15 views2 pages

C2SIM-VRForcesv2.8

The VR-Forces C2SIM interface operates as a command-line application that connects to a C2SIM server and listens for orders without XML schema validation. It distinguishes five object types for ManeuverWarfareTask and allows for simulation initialization per C2SIM standards, including unique UUIDs for orders and tasks. The interface supports commands for moving and attacking objects, as well as specific missions like evacuating noncombatants, while sending periodic position reports for friendly initialized objects.

Uploaded by

sunjas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views2 pages

C2SIM-VRForcesv2.8

The VR-Forces C2SIM interface operates as a command-line application that connects to a C2SIM server and listens for orders without XML schema validation. It distinguishes five object types for ManeuverWarfareTask and allows for simulation initialization per C2SIM standards, including unique UUIDs for orders and tasks. The interface supports commands for moving and attacking objects, as well as specific missions like evacuating noncombatants, while sending periodic position reports for friendly initialized objects.

Uploaded by

sunjas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

VR-FORCES C2SIM INTERFACE

Current interface runs as a separate command-line application in Windows. It makes a VRForces Remote
Control DIS Interface connection to VRForces. It then subscribes to a C2SIM server (default 10.2.10.30,
REST port 8080, STOMP port 61613) and listens for IBML09 and C2SIM standard orders. It does not
validate the order against an XML schema; simply parses out the necessary information elements. It
defaults to C2SIM schema, initialization from the server, and address 127.0.0.1 for VR-Forces.

The prototype distinguishes five types of objects for ManeuverWarfareTask PerformingEntity, as


established in the C2SIMInitialization:

• An aggregate mobile infantry squad, recognized by the 12th character in the 15- character
SIDCString having value “B” and not having initialized HostilityCode “HO”
• An aggregate irregular squad-size mobile team, recognized by the 12th character in the 15-
character SIDCString having value “B” and having initialized HostilityCode “HO”
• An aircraft is recognized by character 3 in that string having value “A”; all aircraft are AH-64
Apache helicopters, except those that have DIS Entity string 1.2.225.23.1.1.0 which are Chinook
• A boat is recognized by character 3 in that string having value “S”
• Everything else is represented as a VR-Forces Abrams Tank (clearly there is a lot more to do in
defining objects)

Units to be simulated are initialized per C2SIM standard. If server is not yet running, the interface waits
on a startup initialization message; if already running. it requests late joiner initialization for which the
server sends the same message but with object positions from latest reports. Hostility and name come
from the initialization process, with Entity UUID as key.

The order can have multiple tasks. Data pulled from the order are UUID, TaskersIntent (IBML09 only),
DateTime, and vector of GDC coordinate points identified as latitude, longitude, and optional
elevationAGL, provided as either a single-point destination or a route.

Order and Task UUIDs must be unique. In addition to their UUIDs, Tasks must have a unique name that
does not contain blanks.

The order can be sent to the server by a command-line client or by the BMLC2GUI (both available open
source on c4i.gmu.edu/OpenBML under C2SIM Client and Servers).

The implemented order directs VR-Forces to MOVE an object with name given by UnitID through the
sequence of locations given by the route, or ATTACK at the same coordinates.

A Chinook can be given a mission EVACTN to evacuate noncombatants. The Chinook will embark them
up at the last Location in Route, debark them at the task’s directed Location, and return to its original
position. The object to be evacuated is selected by proximity to the pickup point; it must be within 100
meters of the pickup point.

After an object is created and the server goes into running state, VR-Forces sends a C2SIM/BML position
report for every friendly initialized object, every 30 seconds. The report uses the syntax of the last order
received (IBML09 or C2SIM). Simulation execution starts when the first order is received. Hostile objects
can have automatic sending of position reports configured (see main.cxx) but the default is for them not
sending. Aircraft and aggregated objects send C2SIM observation reports or IBML09 general status
reports if they detect other than friendly objects.

The variety of objects and actions they can take are based on needs of the MSG-145 C2SIM validation.
We do not plan to expand c2simVRF to the full capabilities of VR- Forces; only to enable those use cases
tried by MSG-145.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy