Concepts

 

CIGI is a data packaging protocol and thus does not depend upon a specific physical communications medium or transport protocol. Any suitable physical medium may be used, including Ethernet, Token Ring, optical fiber, shared memory, etc. The transport protocol(s) used should depend upon performance and what is appropriate to the communications hardware. This document assumes the use of the User Datagram Protocol (UDP) over Ethernet for ease of discussion.

 

CIGI data exchanges is based on standardized data packets.

A complete documentation can be found here: https://www.sisostds.org/stdsdev/tracking_final/doc_191/siso-std-013-draft_cigi_version4.pdf

 

The way vsTASKER uses CIGI is by code generating all calls to the CIGI libraries from definitions and messages created into the database.

It then produces the CIGI host side which will be included into the simulation engine to produce a unique and deployable executable.

 

 

Simulation runtime will then take this configuration:

 

 

vsTASKER is using CIGI CCL (http://cigi.sourceforge.net) library under GNU license.

Include files are located in /include/CIGI and libraries per compiler in /Lib/vc100/CIGI (for VisualStudio 2010):

 

User can replace these libraries by versions of his own if he extends the messages or add new fields in existing ones.