Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

EvenBetterFastSim: The reliable SECS/GEM tool


EvenBetterFastSim is a desktop utility for emulating SEMI SECS/GEM equipment communication. It lets you emulate an equipment or host on your PC, and exchange HSMS/SECS-II messages manually or create your own scripted scenarios.

Features


  • HSMS (TCP/IP) communication with a live, timestamped message log
  • An editable SECS/GEM message library loaded from XML (S1F1, S1F3, S2Fx, S6F11, …)
  • Simulate workflows with multiple responses to a message using the Scenario canvas
  • Simulate a connection loss at a chosen point of a scenario (TCP reset, port closed for a set time)
  • Create and define equipment events, reports and variables, and fire them as S6F11
  • Run multiple instances at once (e.g. a Passive + Active pair) that talk to each other
  • Control-state model (Online/Offline, Local/Remote) and configurable HSMS timers (T3–T8)

Build and Debugging


Use Visual Studio 2026 to open the .sln file.

You may download Visual Studio Community Edition for free to build, run or develop EvenBetterFastSim.

From the command line:

dotnet build EvenBetterFastSim.sln
dotnet run --project EvenBetterFastSim/EvenBetterFastSim.csproj

Usage


0. Download

You can download the application using the following link Releases · Pre-Se/EvenBetterFastSim

Download the .zip file: it contains the exe together with the default message library (Library\DefaultLibrary.msgpack).

1. Pick or create an instance (the Hub)

Launching the app with no arguments opens the Hub. Each row is a named instance (a name plus an IP / port / connection mode/library); every profile launches as its own process so you can run several simulators side by side.

The Hub / launcher window

  • New – add a single profile.
  • New linked pair – create a Passive + Active profile that share one endpoint, so the two instances connect to each other the moment you launch them.
  • Edit / Duplicate / Delete – manage existing profiles.
  • Select a profile and click Launch instance (or double-click it).

Profiles live in %APPDATA%\EvenBetterFastSim\profiles\. Launching with --profile <name> skips the Hub and opens that instance directly.

2. The main window

Main window – Messages view

Area What it does
Left nav Switches the centre panel between Messages, Events, Reports, Variables and Scenarios.
Centre panel The library for the selected section, with a toolbar (Add / Modify / Duplicate / Delete / Send …).
Message Log (right) Every SECS-II and HSMS control message, newest in order, with a ↑/↓ direction icon and millisecond timestamp. Double-click an item to inspect its tree (values shown as hex or Base64).
System Log (bottom) Human-readable status: library loaded, connection changes, send failures, etc.
Status bar The port toggle button, the HSMS state (Not Connected → Not Selected → Selected), comms-established flag, control state, and the Online / Offline / Local / Remote buttons.

The window title shows the profile name and its endpoint so instances are easy to tell apart.

3. Configure the connection

Open Connection ▸ Properties to set the IP address, port, connection mode (Passive = listen, Active = dial out) and the HSMS timers (T3–T8), session id, etc. When you launch from a Hub profile these are already filled in from the profile.

Click the port button in the bottom-left of the status bar to open/close the port. The connection restarts automatically if you change a setting while it is open.

4. Send messages

In Messages, the tree is your SECS/GEM library (loaded from Library\SECSGEM_Library.xml by default). Select a transaction and click Send — the primary message goes out and any reply is paired up and shown in the Message Log. Use Add Transaction / Add Item / Modify to shape the payloads, or Library ▸ Save Library to export your edits back to XML.

5. Events, Reports and Variables

Events view

Define status/data variables under Variables, group them into Reports, then attach reports to a collection event under Events. Send Event builds and sends the corresponding S6F11 event report. (These lists start empty, populate them per your equipment model.)

6. Scenarios

Scenario canvas

The Scenarios section is a visual node graph for multi-step exchanges. Drag a transaction from the DRAG TO CANVAS palette onto the canvas, wire nodes from Start to End, and press Run to execute them in order against the live connection.

Node types: Send and Send & Wait (both send the message and go on at once; neither waits for the reply), Receive (waits for a matching incoming message until the run's Timeout (s) is over; with 0 it waits until the message arrives or you press Cancel) and Wait (a fixed delay). To wait for a reply, put a Receive node after the Send node. Drag WAIT from the NODES palette onto the canvas and double-click the node to set its time in milliseconds; the node shows it as "Wait 1500 ms". Scenarios are saved per instance and can be exported / imported.

Simulating a connection loss

Two more nodes in the NODES palette drop the connection at a chosen point of a scenario and wait for it to come back:

  • Drop connection aborts the connection with a TCP reset (RST). Its value is the downtime in milliseconds: the port stays closed that long and is then opened again. With 0 a new connection is set up right away.
  • Wait for communication waits until data messages can be exchanged again (HSMS Selected and Comms Established in the status bar). Its value is the timeout in milliseconds; with 0 it waits as long as the run may take.

Double-click a node to set its value. Both nodes have two outputs, the upper for success and the lower for failure: Drop connection fails when there is no connection to drop, Wait for communication when its timeout is over. A failure with no wire on the lower output ends the run.

A typical scenario: Start → Receive S6F11 (with a condition on the CEID) → Drop connection 5000 → Wait for communication 20000 → Receive S6F11 → Send S6F12 as the reply → End.

What to expect:

  • How long the outage lasts. The other side sees at least the downtime. The connection comes back with the next attempt of the active side; after a refused attempt that is its T5 later (10 s by default). The outage lasts exactly the downtime only when this instance is the active side. With 0 on the active side the first attempt can still be refused, when the other side needs a moment before it listens again.
  • A reset, not a pulled cable. The other side learns at once that the connection is gone. For a silent loss, put a firewall rule or a TCP proxy between the two.
  • After the connection is back about a second passes before messages can be sent (select, then S1F13/S1F14). A Send node fails during that time (unless Ignore HSMS State is ticked in Connection ▸ Properties), so put Wait for communication in front of it.
  • Replies from the library. While a scenario with a Receive node runs, the library does not answer that node's Stream/Function by itself, whatever the condition of the node. Send the reply in the scenario.
  • Replies from the stack (S1F14, S1F4, S2F34/36/38 and others) are not held back. Whether one that is due right before the drop still goes out is not guaranteed.
  • One connection for all scenarios. A drop in one running scenario hits the others too.
  • Connect button. While a Drop connection node keeps the port closed, the button is disabled. Cancel the run to open the port at once.
  • Older versions of the app do not know these two nodes. They cannot run them, and saving the scenario there drops the wires on their failure outputs.

7. Two instances talking

Create a linked pair in the Hub and launch both. One listens (Passive), the other dials in (Active); once HSMS shows Selected on both, send a message from either side.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages