The GX7016 software features a simulation mode which allows you to write test code which includes the switching subsystem and observe the effects that you test code would have on the switching cards states using our suite of software tools. Upon system boot-up the simulated domain is reset, behaving as a physical board’s relays would. Calling the DLL functions or using the software tools with simulation enabled will open and close the same relays and read back relay information in the same manner as it would a physical board.
Enabling simulation depends on the tool used:
● ATEasy: Enable simulation by toggling the Simulate option in the Conditions menu
● C++: Set simulate to TRUE when calling the GxxxxxInitialize or GxxxxxInitializeVisa function.
● GXxxxx/SwitchExec Panel: Check the Simulation box prior and then click Initialize (panel only) to enter Simulation mode. Uncheck the box and click Initialize (panel only) to leave Simulation mode.
Enabling simulation depends on the tool used:
· ATEasy: Enable simulation by toggling the Simulate option in the Conditions menu
· C++: Set simulate to TRUE when calling the GxxxxxInitialize or GxxxxxInitializeVisa function.
· GXxxxx/SwitchExec Panel: Check the Simulation box prior and then click Initialize (panel only) to enter Simulation mode. Uncheck the box and click Initialize (panel only) to leave Simulation mode.
To present an accurate simulation, the configuration of your chassis must be modeled in GxSw.ini, which is located at %ProgramData%\Marvin Test Solutions\GxSw. The INI file format configuration file that holds information about the local PCs simulation. The data configured in the file should follow these rules to enable simulation:
● The section count must be defined.
● count should contain a single key called boards with a single integer assigned to it. The number should be between 1 and 20.
● For each board being simulated, a section should be created named boardn where n an integer between 0 and boards-1.
● boardn should contain at least two keys: type and slot. Slot is the simulated slot number. Type is the board type: 6192, 6256, 6864.
● boardn may contain a key named RTM with a value of 1 to simulate the existence of an RTM module at that slot.
● boardn may contain a key named SR with a value of 1 to simulate the existence of a SR module at that slot.
The configuration file can also store logical names associated with inputs from the GX6032 Rear-Transition Module and the GX6192 High Frequency card. These names are updated automatically when using the SwitchEasy driver from ATEasy whenever an input is mapped.
● The section SwitchExec_RtmLogicalName may be defined.
● SwitchExec_RtmLogicalName may contain keys named SlotnRtmChannelx when n is the slot number and x is the channel number that is being mapped to a logical name. The value of the key is the logical name of the input.
● The section SwitchExec_HfLogicalName may be defined.
● SwitchExec_HfLogicalName may contain keys named SlotnRtmChannelx where n is the slot number and x is the channel number that is being mapped to a logical name. The value of the key is the logical name of the input.
The follow information added to the INI file will cause the SwitchExec and GxxxxxPanel to simulate a switching domain of 3 boards: the GX6256 at slot 2 with an RTM and SR, a GX6864 at slot 6, a GX6192 at slot 20 with an SR. The RTM at slot 2, channel 20 has a logical name of “DMM High” and the GX6192 at slot 20, channel 2 has a logical name of “2-Arb 1”
[count]
boards=3
[board0]
type=6256
slot=2
RTM=1
SR=1
[board1]
type=6864
slot=6
[board2]
type=6192
slot=20
SR=1
[SwitchExec_RtmLogicalName]
Slot2RtmChannel20=DMM High
[SwitchExec_HfLogicalName]
Slot20HfChannel2=2-Arb 1