Skip to main content

HX100 Platform Orientation

HX100 is a simulation-first tour of the desktop. The goal is to open the right tools, verify where data comes from, verify where orders go, and save a reusable layout before writing code. Check the documentation version map for the installed release and any newer workflow notes.

Start with the release boundary

Read Feature And Provider Status before configuring a provider. A visible connection or tool name does not prove that it is supported for live use.

Lesson 1: Map The Desktop​

Use the Desktop And Main Menu as the detailed map. The main areas are:

  • New: charts, MegaDOM, Level II, Time and Sales, Strategy, Validator, Optimizer, Performance, and Output.
  • Tools: instruments, instrument lists, Code Lab, Trade Copier, Agent Builder, Research Lab, reports, and Options.
  • Connections: saved provider definitions and connection state.
  • Workspaces: open, save, save as, and manage layouts.
  • Project: compile the complete custom-source project.
  • Help: support, knowledge base, update check, log exports, and version information.

The lower panel shows Logs, Strategies, Accounts, Positions, Orders, and Executions. A green market-data state is not proof that a particular account route is safe or live-ready.

Lesson 2: Separate Data From Order Routing​

A provider connection can supply market data, accounts, order routing, or only a subset of those capabilities. Treat these as two separate choices:

  1. Data source: provider live data, stored history, or Playback.
  2. Order route: LocalPaper, Server Paper, or Broker.

Playback changes the data clock; it does not force trading tools onto LocalPaper. You must select LocalPaper explicitly rather than relying on a build-specific external-account guard. Review Accounts And Trading Environments, then complete this check:

  1. Connect a supported provider.
  2. Verify history and live updates on a chart.
  3. Open Chart Trader and select LocalPaper explicitly.
  4. Read the account name again immediately before submitting a test order.

Lesson 3: Open And Inspect A Chart​

Create a chart from New > Chart, then choose the connection, instrument, data series, interval, and history range.

On the chart:

  • Confirm the symbol, provider, timeframe, and most recent timestamp.
  • Add one indicator and change one parameter.
  • Open Data Box and inspect OHLC and plot values under the cursor.
  • Add and remove a manual drawing.
  • Toggle Chart Trader.
  • In multi-chart mode, click the intended chart before using shared controls or AI context.

Do not assume that a loaded chart has current data merely because candles are visible. Stored history can remain visible after a connection stops.

Lesson 4: Use Chart Trader Only In Simulation​

Chart Trader sends directly to its selected account after local validation. It does not show a general manual-order confirmation dialog and it does not provide a universal maximum-order or daily-loss guard.

For the first exercise:

  1. Select LocalPaper.
  2. Confirm symbol, quantity, order type, and time in force.
  3. Submit a small simulated order.
  4. Find it in Orders and verify any fill in Executions and Positions.
  5. Cancel working orders and flatten the simulated position.

Hyperion Sim is a simplified full-fill model. It does not reproduce queue position, partial fills, configurable slippage, buying-power rejection, liquidation, or provider latency. See Chart Trader And Manual Trading.

Lesson 5: Know The Market-Data Tool Boundaries​

  • MegaDOM: Current order-entry ladder; it routes directly to its selected account.
  • Level II: Preview because the window can show generated fallback rows when real provider depth is unavailable.
  • Chart-linked Time and Sales: Current for prints delivered by the active chart stream.
  • Standalone or restored Time and Sales: Preview because it can open with seeded sample rows.

Before using any of these views, verify provider, symbol, timestamp, and whether the rows came from provider data, chart context, or a fallback. Follow Market-Data Tools.

Lesson 6: Manage Historical Data Through The App​

Use the Historical Data area in Options for market-data import. Tools > Import is for C# source, not market data.

The signed 1.1.12 baseline retains two important local tick-importer boundaries:

  • The visible time-zone selector is not forwarded to the parser. Naive timestamps can be interpreted through the Windows local zone before UTC normalization.
  • The overwrite path merges existing and imported rows by timestamp; it is not a guaranteed delete-and-replace operation.

Import a small range, inspect warnings, and compare timestamps with a trusted reference before research. See Historical Data And Import.

Lesson 7: Save And Restore A Workspace​

A workspace saves supported window layout and configuration. It does not checkpoint provider sessions, live orders, positions, running strategies, in-memory strategy fields, or active Validator/Optimizer jobs.

  1. Arrange the chart and one diagnostic window.
  2. Select Workspaces > Save As and give the layout a clear name.
  3. Reopen it.
  4. Verify every provider, symbol, timeframe, indicator, and account.

A restored Chart Trader account must be checked again before an order. Use Save And Restore Workspaces for the exact saved-state list.

Lesson 8: Enter Code Lab Safely​

Code Lab compiles the complete custom-source project into one runtime assembly.

  1. Open Tools > Code Lab.
  2. Create an indicator from a HyperionX template.
  3. Build the complete project and fix the first compiler error first.
  4. Add a fresh indicator instance to a chart.
  5. Before the next build, remove affected instances or disable affected strategies.

A successful build does not replace an existing indicator or strategy object in place. See Build, Test, And Debug.

Completion Check​

  • You can identify the data source and order route independently.
  • You can place, cancel, and flatten only a LocalPaper test order.
  • You can distinguish real depth/prints from Preview fallback or sample data.
  • You can import a small historical sample and verify its time alignment.
  • You can restore a workspace and re-verify its trading context.
  • You can compile Code Lab and create a fresh runtime instance.