Library Model


Application Templates Based on Libraries:

The Pre-Built models provide a convenient mechanism to learn quickly all the features of VisualSim.  Every operation of each block is explained using examples.  There are  examples that can be used as a starting point for many design exploration studies.  All examples are documented.

VisualSim Modeling Libraries

Table of Content






Basic Graphical Operation Model Setup Traffic Results

How-to-Tasks
Repeat
Dynamic Instantiation
Applet
Parameter
Altering the BDE View
Unit
Static Unit
Non-Static Unit
Type
Sketched Source
RegEx Expression Language Eg.
Draw Tools
Parameter
Simulator
Variables
Hierarchical_Blocks
FSM
Utility
Clock
Event
Interactive
Traffic
Delay
PlotManager
3D Interactive Creator
Plotter
Statistics_Generator
Text






File IO Behavior Mapper Resources

File Import
Database
ExpressionList
Script
Fork
Join
IN
OUT
Execution Control
Switching
Processing
Mux
Mapping
Smart_Resource/Queues
Channel and Pipeline
Event Queue
Quantity-based
Timed-Queue
Scheduler/System Resource






Power Modeling Hardware Setup Processor Generator Memory

Power_Manager
Battery
Architecture_Setup
Utility
Core_Architecture
Vendor_Specific Processor
Cache
Memory






Hardware Devices Interfaces and Buses FPGA's System Language

Bus_Switch_Ctrl
Standard_Bus
Emerging_Bus_Standard
Xilinx_FPGA C_and_CPP
MatLab
Python
Satellite Toolkit






Hardware Language Data Access Math Operations Application

SystemC
Verilog
Database
Corba
SQL Database
File_Access
Socket
Serial io
Excel
XML Parsing
Array
Boolean
Counter
Distributions
Logic
Math and Trig
Parser
Transform
String Operations
Auto
Aerospace
Networking
Wireless_Sensor






Algorithms



Analog
Control_Systems
Image_Processing
Petri_net
Signal_Processing









Demonstration Models and Example Systems


Basic Graphical Operations







How-to-Tasks

Demonstrates the basic usage of the hierarchical blocks, ports and block-to-block connection

Repeat

This feature provides the facility to pause and save simulation data to continue simulation even after closing the tool
Demo Model is available in VS_AR\doc\Training_Material\How_to_tasks\Repeat directory

Dynamic Instantiation

Using the Dynamic Instantiation to make the multiple instantiation of a single without cluttering the model diagram

Applet

Basic understanding of including Applets in the documentation

Parameter

Shows the use of the int-range/ slider parameter

Altering the BDE View

Shows the use of special XML parsing functions for altering the screen view

Unit

Explains the rationale and the usage of the Unit System in VisualSim

Static Unit

Provides the means to constrain a model in terms of the allowable units of measure

Non-Applet Static Unit Description

Provides the means to constrain a model in terms of the allowable units of measure

Type

This explains the polymorphic nature of the Type System and how the block port adapts their data type based on the port that it is connected too.

Sketched Source

Use the graph to create new interactive sources





RegEx Function







Built-in RegEx Function






Model Setup






Draw Tools

Parameter

Simulator

Variables

Hierarchical Blocks

FSM

Utility






Traffic






Clock

Event

File Import

Interactive

Traffic

Delay






Results






PlotManager

3D Interactive Creator

Plotter

Statistics Generator

Text






Behavior






Database

Processing

Expression List or Decision

IN

OUT

Basic Processing

Virtual Connection


Script (Virtual_Machine)

Virtual_Machine_Untimed






Delay and Utilities







SingleEvent

Fork or Isolate Input

Join or Isolate Output

Execution Control

Switching






Resources






Smart Resource/Queue/Server Resource

Channel and Pipeline

Event Queue

Quantity-based

Timed_Queue

SystemResource/SystemResource_Extend/Scheduler






Mapper






Mapping







Power Modeling







PowerTable

  • Schedulers-based system model: This is a Dynamic Voltage Frequency Scaling (DVFS) model.  Look at the power information table, use of the power RegEx functions to change the state and the power levels.
  • System and Environment Model: The power handling is done entirely using the Power RegEx functions in the Processing blocks.  Look at the (1) check for current battery power, (2) charge the battery, and (3) determine scheduler on/off based on available charge.
  • Platform Architecture model: You can evaluate the system power consumption on the software task processing.  The Power table is constructed with information in the ARM datsheet.  This has a complete platform including the ARM9, AHB bus, cache, DRAM and DMA controller.  The power estimate can be used to partition the tasks into software and hardware; configure the devices; allocation of data to memories and optimize the platform topology
  • Exploring Power Management Schemes: In this model, you will see how to setup scenarios, evaluate different sleep modes, modify transition cycles.  If you are going to be studying power management or closed-loop voltage control at the system-level, this would be the model to look at.  This model is focus on low power application.
  • Distributed system power: In this model, we show the complete power flow- generator; consumption by mechanical, electrical and electronics; management; and conservation.
  • Semiconductor Power: This shows how a centralized management system changes the state of all the devices.  The explanation is on this page- Semiconductor Demo.
  • Software Tasks: Shows the use of the Power modules for evaluating the hardware and software architecture for power.
  • Simple Power: Simple model showing the use of all the power blocks.
  • Power Analysis Tutorial: Example showing the use of equations, dynamic changing of states and frequency modification.  This model is implemented at a much lower of abstraction that the other models.  The description is on this Page.
  • Hybrid System Power Design: This model looks at the end-to-end power systems- generation, consumption, management and measurement.  It also utilizes the blocks available in the Power folder.  This model also contains electrical, electronics, mechanical and electro-mechanical components.  The model has multiple sources of power being generated.
  • Using Power Blocks: This is model that explains the use of all the blocks in the Power folder.

Battery

  • BatteryProfile File: text file containing battery parameters and values for each type battery type. Custom battery type can be constructed by filling the resective entries.
  • Server Model: This model contains a single Server Block. Power consumption is captured using the VisualSim power toolkit.
  • SystemResource Model: This model contains a systemResource to which transactions are mapped from three mapper blocks. Power toolkit includes Battery, PowerTable and energy harvester.
  • Sensor Model: This model contains application sensor traffic, architecture platform DMA channel etc. Power consumption is captured using PowerTable, Battery.
  • SystemResource_3_Load: This model contains 3 SystemResource blocks. Each SysteResource has different power levels. This model includes energy harvester, Battery and PowerTable.
  • Processor Model: This model contains the the processor, bus and an SDRAM. the system is powered by by a Li_ion battery which is powered by a constant power supply.





Hardware Setup






Architecture Setup

Utility






Processor Generator






Core Architecture

Vendor Specific Processors

Cache






Memory






Memory






Hardware Devices






Bus Switch Control






Interfaces and Buses






Standard Bus

Emerging Bus Standard

AMBA AXI PCIe RapidIO
Switched Ethernet Spacewire FibreChannel FireWire
TTEthernet
AFDX

Audio Video Bridging

AutosarCAN BusFlexRay





FPGA's






Xilinx FPGA







System Language






C_and_CPP

MatLab

Python

Satellite Toolkit






Hardware Language






SystemC

Verilog






Data Access






Corba

SQL Database

File_Access

Socket

Serial_io

  • Serial_IO Model (Currently not available.  Contact Mirabilis Design)

Excel

XML_Parsing






Math Operations






Array

Boolean

Counter

Distributions

Logic

Math_and_Trig

Parser

Transform

String Operations






Applications






Auto

AVB- Audio-Video Bridging
Aerospace

       TTEthernet
       Spacewire

Networking

Other Network Block
  • Using Ethernet Traffic Generator- Using the Traffic Generator to generate Ethernet streams
  • Retry_Layer1 Demo Model shows the connection between the Layers and to the Node.  It also shows the association of the Layer_Table to the Layer_Protocol.  This models shows the use of multiple Layer_Tables in the model and the setting of the retry.
  • Network_External_Defn Demo Model shows the Configuration Layer setting to External Delay and the conenctivity for this.
  • Network_Basic Demo Model.  This shows a basic connectionless network, the Routing Table reference and the path definition in the Database block.  
  • Retry Network Demo Model.  This shows a Connected Network with the layers of the OSI stack referenced.
  • Gateway_Connected Demo Model.  This shows the use of the Node as a Gateway.
  • Multi_Network_w_Intermediate_Gateway Demo Model.  This model has a intermediate of Gateway nodes.
  • Gateway_w_Diff_Return_Model Demo Model.  In this model, the forward and return directions use a different Gateway Node. 
  • Two_Networks_w_Gateways Demo Model.  This shows two Gateways between two networks.
  • Using Multicast Demo Model.  This models uses the Multicast block to create a multicast and a broadcast.
  • Header Compression: Evaluate different TCP/IP Header Compression algorithms

Wireless_Sensor

  • Antenna Pattern: This example illustrates modeling transmit antenna gain. The Sender has an 8-element beamforming antenna with a steering angle applied. When you run this model, the Receiver will move around the Sender and measure the received power. It then plots the receive power on a polar plot, with the distance from the origin representing the received power, and the angle representing the angle of its position relative to the transmitter. In effect, it measures and displays the antenna gain pattern of the Sender. (See ReceiveAntennaPattern.xml as an example of modeling receiving antenna gain)
  • Circular Range: This model shows a transmitter (at the left) and a receiver (at the right), where the receiver moves in and out of range as the model executes. The channel is a LimitedRangeChannel, which is a simple wireless channel model where the transmitter specifies via a parameter in its output port the distance over which it can transmit. In this model, that distance is shown graphically as the radius of the circular icon for the transmitter. As the model executes, at random times, the range of the transmitter decreases.
  • Collisions: In this model, two transmitters broadcast signals that may collide with one another. The receiver will correctly receive a signal if the signal to interference ratio is 3dB or better, meaning that the received signal has at least twice the power of the interfering signal. When Transmitter1 is far away from the receiver, it cannot interfere with the transmission of Transmitter0. However, when it gets close, it can.
  • Evader/Pursuer: This model shows an "evader" and a "pursuer" moving through a sensor network. The "evader" emits sounds that are detected by the sensor nodes, and the sensor nodes relay information to the pursuer. Running the model shows the evader moving at random and the pursuer seeking to track it based on the information from the sensors.
  • PowerVariability: This model shows a transmitter (at the left) and a receiver (at the right), where the receiver moves as the model executes. The channel is a PowerLossChannel with a limited range. When the receiver is in range, the power depends on the distance to the transmitter, according to an inverse square law.
  • Small World: This demo shows a sensor network where each node rebroadcasts the first message it receives. An "initiator" component broadcasts a message, and the model keeps track of the number of nodes that receive the message after one hop, after two hops, etc., and plots a histogram.
  • Smart Parking: Sensors placed in a parking lot can be used to collect data (including which parking spot is taken, how long a car has parked on a spot). The parking lot can process the collected data and provide some services to clients to guide their parking. This demo illustrates these ideas. The dots are sensors on the parking spots. We use green color to indicate the spot is free and red to indicate the spot is taken. When a sensor detects a car arriving or leaving a spot, it sends an update to the server of the parking lot, which collects and processes sensor updates to provide information to parking clients. The "car model" component models when a car arrives or leaves, and where to park based on the information the server provides. It is a abstraction for all the cars dynamics during a specific time. The components in the upper right corner represent the server function, which receives sensor data and provides information the clients. The "signal light" component indicates whether the parking lot is full (using red) or not (using green).
  • Terrain Model: This simple example illustrates modeling terrain effects. The TerrainProperty models some obstacle which blocks the communication from the Sender to the Receiver if the communication path between them intersects with the terrain shape. When you run this model, the sender will emit a signal every second from time 0.0 to time 36.0. The Receiver will move around the Sender and measure the received power. It then plots the received power on timed plot if it is greater than 0.0. The plot shows that the receiver can only receive the signal (with power value larger than 0) when it is not shadowed by the terrain model.
  • Sound Detection: This example shows a SoundSource (concentric circles icon) moving through a field of sensors (SoundSensor actors, with translucent circle icons) that detect the sound and communicate with a Triangulator actor (overlapping ellipses icon). The Triangulator performs sensor fusion to triangulate the location of the sound source. It generates a plot with estimated locations.





Algorithmic






Analog

Control_Systems

Image_Processing

Note: Requires Java Advanced Imaging and Java Media Framework Libraries

Petri_net

Signal_Processing