SwingBot Manual
The complete manual for SwingBot — install, every setting, licensing, and support. Back to the product page.
A Foundation Trading Systems product
⚠ Risk disclaimer — read this first
Futures trading carries substantial risk of loss and is not suitable for every investor. You can lose some or all of your capital, and in adverse conditions more than your initial deposit. Only trade with money you can afford to lose.
SwingBot is software — a tool — sold as-is, with no warranty of any kind. It implements published trading systems mechanically; it does not predict markets, and nothing in this manual, on our website, or in any Foundation Trading Systems material is financial advice, a recommendation, or a promise or suggestion of any result. No performance claims are made for this product, and none should be inferred.
You are responsible for your own settings, your own testing, and your own trading decisions. Before enabling SwingBot on any account, test it in simulation until you understand exactly how it behaves on your charts, your data feed, and your settings. The suggested starting settings in the appendix are exactly that — starting points for your own evaluation, drawn from the product's development symbols. They are not recommendations, and using them does not imply any expected outcome.
Foundation Trading Systems and T&E Portfolio LLC accept no liability for any trading loss, missed fill, data-feed failure, platform failure, or other damage arising from the use of this software. If you do not accept these terms, do not use the software.
⚠ Separate accounts — FusionBot and SwingBot
FusionBot and SwingBot can be owned and run at the same time, but run them on SEPARATE accounts.
This is not a preference; it is how the platforms work. NinjaTrader and brokers net positions per account + symbol. If both bots trade the same symbol in one account, their trades merge into a single position: opposite signals cancel each other out, one bot's exit can flatten the other bot's trade, and neither bot can correctly track or manage a position it only partly owns.
SwingBot holds positions for days at a time, so it will routinely be holding a position during the hours an intraday bot is active. Same symbol + same account + two bots is a real collision risk, not a theoretical one.
The same rule applies to running SwingBot alongside any other automated strategy: one account per bot, per symbol. Different symbols on one account do not collide with each other.
⚠ Keep NinjaTrader running — and one platform setting
The bot runs on your PC, inside NinjaTrader. There is no server somewhere running it for you. That means:
- If NinjaTrader is closed, nothing happens. No entries, no exits, no disaster stops. SwingBot's exits — including the Overnight Hold module's 9:30 AM exit — are generated by the strategy at the moment they trigger; they are not orders resting at your broker waiting to fire.
- When you reopen NinjaTrader, the bot is designed to pick an open trade back up and manage it from that moment on — but anything that would have triggered while it was closed did not happen and cannot be replayed. An exit that should have fired at 9:30 fires late at best (Overnight Hold logs it as EXIT LATE — see §8); a disaster-stop level crossed while the machine was down was never acted on. Treat the reopen-and-resume behavior as something to prove in your own simulation testing before you depend on it.
- So while any position is open: leave NinjaTrader open and connected, and your PC awake — overnight included. Swing positions can be held for days, so this applies every night a position is on, not just the entry night.
- If NinjaTrader was down and you restart it with a position open, check the account position yourself before re-enabling anything.
Recommended platform setting — disconnect delay (60 seconds). Brief connection drops are common, and NinjaTrader's default is to treat the connection as lost after about 10 seconds, which can stop strategy instances mid-trade. In NinjaTrader: Tools → Options → Strategies → NinjaScript → set Disconnect delay seconds to 60. Blips shorter than a minute then pass without disturbing the bot. This is a NinjaTrader platform setting, not a SwingBot setting — set it once and it applies to every strategy.
1. What SwingBot is
SwingBot is a NinjaTrader 8 strategy that runs on daily charts and holds positions for days at a time — including over weekends. It checks in mainly once a day, at the daily close. It is a swing tool, not an intraday tool.
Inside the one strategy are four modules, each implementing a published trading system, credited to its authors:
- RSI(2) — Larry Connors' published RSI(2) system. In an uptrend (close above the 200-day average), buy a hard short-term dip (RSI(2) below the entry threshold); exit at the first close back above the 5-day average. Shorts are the mirror image and are the secondary side.
- Double Seven — the published system by Connors & Alvarez. In an uptrend, buy when today closes at the lowest close of the last 7 days; exit at the first close that is the highest close of the last 7 days. Long only.
- VIX Stretches — Connors' published VIX Stretches system. After the VIX has closed stretched above its own average for several days running while price is in an uptrend, buy; exit at the first close with RSI(2) above the exit threshold. Long only, and it only ever fires on one symbol (see §7).
- Overnight Hold — a tradable translation of the overnight-hold research by Lou, Polk & Skouras (Journal of Financial Economics, 2019). Buy at the regular-session close, sell at the next session's open, every night except Fridays. Long only.
Every parameter of every module is a user-adjustable setting. Nothing about any system is hard-coded. You can switch modules on or off per chart, change thresholds, re-rank priorities, and set optional disaster stops — the settings are yours to tune and test.
SwingBot ships with a safety guard on: EnforceSimOnly defaults to ON (see §9). It will refuse entries on any account that is not a simulation/demo account until you deliberately turn the guard off.
2. How the modules interact — one position, priority order
SwingBot holds at most one position per symbol at a time, no matter how many modules are switched on for that chart. When more than one module wants a trade, a priority setting decides.
Each module has its own Priority setting — the lower number wins. The shipped defaults are:
| Priority (default) |
Module |
| 1 |
Overnight Hold |
| 2 |
RSI(2) |
| 3 |
Double Seven |
| 4 |
VIX Stretches |
The rules:
- Flat, and several modules signal at the same decision point → the highest-priority (lowest-number) module takes the trade. The other signals are skipped, never queued. A skipped module needs a fresh signal after the bot is flat again; it does not "get its turn" later.
- A position is open → only the module that opened it (its owner) manages and exits it. A higher-priority signal does not kick an open trade out, and no other module can enter until the position is closed.
- Overnight Hold timing is special. The swing modules decide at the daily close (5:00 PM ET); Overnight Hold enters earlier, at 4:00 PM ET. Before entering, the overnight module checks whether a higher-priority swing module is already signalling on today's forming bar. If one is, the overnight module stands down for that night. If a swing position is already open at 4:00 PM, the overnight module cannot enter either — one position, ever.
- Priorities are settings: you can re-rank the modules per chart. Ties are broken in a fixed internal order (Double Seven → VIX Stretches → RSI(2)).
Ownership and restarts. NinjaTrader cannot tell, after a restart, which module opened an adopted account position. So on every entry fill SwingBot writes a small owner file — SwingBotState_<account>_<symbol>.txt, stored next to its logs — recording which module owns the open trade, and reads it back when it re-attaches to a position. Do not delete the SwingBotState_*.txt files while a trade is open. If the file is ever missing, the bot manages the position as an RSI(2) trade (the fallback default) and states that loudly in the log ("OWNER ASSUMED").
Start behavior is pre-set in the code to Adopt account position, and the bot keeps no in-memory state it depends on: indicators are recomputed from the bars, the position is read from the account, and ownership comes from the owner file. After any NinjaTrader restart, simply re-enable the strategy and check the chart panel shows the correct position and owning module.
Do not enable "exit on session close" for this strategy. It is deliberately set off in the code (IsExitOnSessionCloseStrategy = false): the swing systems are designed to hold overnight and over weekends.
3. Install
- Save the supplied
SwingBot-retail-v1.cs file somewhere you can find it (Downloads is fine).
- In NinjaTrader: Control Center → New → NinjaScript Editor.
- In the editor, use File → Open and select
SwingBot-retail-v1.cs.
- Click the Compile button in the editor toolbar. Compilation should finish with no errors listed at the bottom of the editor. (Use the Compile button — do not rely on a function-key shortcut, which may be remapped on your machine.)
- Close the editor. The strategy now appears in NinjaTrader under the name SwingBot.
Updating to a newer retail version works the same way: open the new file, compile, and your existing charts pick it up. Note that the retail build keeps its own owner/log files (SwingBotState_* / SwingBotLog_*) and does not read files written by any other build.
4. Quick start
4.1 Make a daily chart (repeat per symbol)
- Control Center → New → Chart.
- Instrument: the current front-month contract you want to run, e.g. MES 12-26.
- Interval: Day (daily bars).
- Days to load: 400. Do not skip this. The systems are built on a 200-day average; with the usual handful of days loaded, the bot simply sits in warmup showing NOT ENOUGH BARS.
- Click OK. You should see roughly 400 daily candles.
- Save the workspace once your charts exist.
Notes on daily bars and data:
- On futures, NinjaTrader's daily bar is the exchange (Globex) day, closing at 5:00 PM ET. The swing modules evaluate at that daily close, and their market orders fill at the next tradable moment — live fills will differ somewhat from signal prices. That is normal for daily systems.
- VIX data requirement: the VIX Stretches module needs a daily VIX index series inside NinjaTrader. Whether your data feed serves the VIX index varies by provider. SwingBot handles both cases safely — see §7 for the check and the fix.
- Overnight Hold data cost: on a chart where the Overnight Hold module is on, the bot also loads 400 days of 1-minute bars (it needs them to act at 4:00 PM and 9:30 AM sharp). That chart will load, and reload after every restart, noticeably slower. That is normal. Charts without Overnight Hold on do not pay this cost. Modules that are switched off do not load their extra data series at all.
4.2 Enable the strategy (per chart)
- On the daily chart: right-click → Strategies…
- Find SwingBot, select it, and click Add (or double-click it).
- Set the account — remember the separate-accounts rule at the top of this manual: use an account no other automated strategy trades the same symbol on.
- Set the settings for this chart. A good first pass is the suggested starting settings appendix (§12) for your symbol, or simply the shipped defaults. Changing any module on/off requires a disable → set → enable cycle — NinjaTrader loads the extra data series (VIX, 1-minute) when the strategy starts, so the strategy must be restarted for a module switch to take effect.
- Start behavior: nothing to set — it is pre-set in the code to Adopt account position. If your NinjaTrader shows a Start behavior field anyway, it should already read "Adopt account position"; leave it.
- Check Enabled last, then click OK.
4.3 What you should see
At the top-left of the chart, a status panel:
- ● SwingBot – RUNNING – watching — flat, no signal today.
- IN LONG – D7 / IN LONG – VIX / IN LONG – ON / IN LONG – RSI2 — holding a position, and which module owns it; the panel shows the average price and what would exit the trade.
- WARMUP – NOT ENOUGH BARS — Days to load is too small. Reload with 400.
- BLOCKED – SIM GUARD — the selected account is not a sim/demo account and EnforceSimOnly is on. Entries are refused (see §9).
- BOT FLAT – ACCOUNT HOLDS n (not bot-managed) — the account holds this symbol but the bot does not own the position (for example a manual trade). See Troubleshooting (§14).
- Below that: the account and mode line; the current RSI(2) value, today's close, and the 200-day and 5-day averages; a module board line (each module on/off, its priority, the live VIX streak count, and the current owner); and a "Why:" line giving the reason for the last action or exactly what the bot is waiting for.
- The chart also draws the two moving averages and an RSI panel.
Daily log file: Documents → NinjaTrader 8 → SwingBotLog_<SYMBOL>_<date>.txt. Every entry, exit, and fill is recorded there, tagged by module (RSI2 Long, D7 Long, VIX Long, ON Long — the same names appear as the order names in your executions grid). A CONFIG line at each live start lists which modules are on and whether the extra data series loaded. If you ever contact support, this log file is the single most useful thing you can send.
5. Module: RSI(2)
Larry Connors' published RSI(2) system.
- Long: the daily close is above the trend SMA (default 200 days) and RSI(2) closes below the long entry threshold (published value 10) → buy at the close. Exit: the first daily close back above the exit SMA (published value 5 days).
- Short: the mirror — close below the trend SMA and RSI(2) above the short entry threshold (published value 90) → sell at the close. Exit at the first close back below the exit SMA.
- Shorts are the secondary side of the system. Which sides to run is a per-chart choice; the appendix (§12) shows the starting configuration used on the development symbols.
- Exit at Friday close (default OFF) is not part of the published system. Forcing Friday exits changes the system materially. It exists only as an option for owners who insist on being flat over weekends; leave it off unless you have tested the change yourself and accept that you are no longer running the published system. It applies only to RSI(2)-owned trades.
Settings — 02 RSI(2) Module
| Setting |
Default |
Meaning |
| Use longs |
ON |
Enable the long side |
| Use shorts |
OFF |
Enable the short side (secondary side — per-chart choice) |
| RSI period |
2 |
It is called RSI(2) for a reason |
| Long entry: buy when RSI is BELOW this |
10 |
Published value; a stricter variant of 5 exists for one symbol — see the appendix |
| Short entry: sell when RSI is ABOVE this |
90 |
Published value |
| Exit SMA period |
5 |
Exit at the first close back across this average |
| Priority |
2 |
Lower number wins when flat (see §2) |
| Disaster stop % |
0 (OFF) |
See §10 |
| Exit at Friday close |
OFF |
Not part of the published system — see above |
6. Module: Double Seven
The published system by Connors & Alvarez. Long only.
- Entry: the daily close is above the trend SMA and today's close is the lowest close of the last 7 days (the window is a setting) → buy at the close.
- Exit: the first close that is the highest close of the last 7 days.
- The published system has no stop. An optional disaster-stop setting is provided (§10); its shipped default is OFF.
Settings — 03 Double Seven Module
| Setting |
Default |
Meaning |
| Use Double Seven |
ON |
Module on/off (per-chart choice — see the appendix) |
| Window days |
7 |
Buy at the lowest close of this many days; exit at the highest |
| Priority |
3 |
Lower number wins when flat |
| Disaster stop % |
0 (OFF) |
Per chart, like every other setting; suggested starting values are in the appendix |
7. Module: VIX Stretches — and its data setup
Connors' published VIX Stretches system. Long only.
- Entry: the price close is above its trend SMA and the VIX has closed at least 5% above its own 10-day average for 3 consecutive days → buy at the close on the day the streak first reaches 3.
- Exit: the first close with RSI(2) above 65.
- One symbol only: the module only ever fires on the chart whose symbol matches its Applies to symbol setting (default MES), even if you switch the module on elsewhere.
- It ships OFF in the file. The appendix configuration turns it on for one chart only.
The VIX data chore (do this once)
The module needs daily VIX index bars inside NinjaTrader, and whether your feed serves the VIX index is the one thing that cannot be assumed:
- When you enable a chart with VIX Stretches on, the bot tries to load a daily series for the instrument in the VIX instrument name setting (default ^VIX).
- The
CONFIG line in the daily log will say "VIX series loaded" or "not loaded". If it loaded, the panel's module board shows the live streak (for example VIX[streak 2/3]).
- If the name doesn't resolve or no bars arrive, the bot logs "VIX MODULE INERT" with the reason — and everything else trades normally. The module simply never fires until the data exists. The streak also only counts on fresh data: if the VIX feed goes stale for more than a week, the module treats itself as inert rather than firing on old data, and logs that too.
To check / fix it yourself:
- Control Center → New → Chart → pick the VIX index instrument (type VIX in the instrument search; you are looking for the index, usually shown as ^VIX) → Interval Day → OK.
- If bars appear — your feed serves it, and the bot will get the same data. Done.
- If it doesn't appear or loads nothing — open Tools → Instruments, find what your feed actually calls the VIX index, set the bot's VIX instrument name setting to that exact name, disable/re-enable the strategy, and check the log again.
Settings — 04 VIX Stretches Module
| Setting |
Default |
Meaning |
| Use VIX Stretches |
OFF |
Module on/off (appendix turns it on for the MES chart only) |
| VIX instrument name |
^VIX |
Exact name in Tools → Instruments for your feed; the module stays inert if it cannot be loaded |
| Applies to symbol |
MES |
The module only fires on this chart symbol |
| VIX average period |
10 days |
The VIX is compared to its own average over this many days |
| VIX stretch % |
5 |
VIX close must be at least this % above its average |
| VIX streak days |
3 |
Consecutive stretched closes needed; entry on the day the streak first reaches this |
| Exit: RSI(2) ABOVE this |
65 |
Exit at the first close with RSI(2) above this value |
| Priority |
4 |
Lower number wins when flat |
| Disaster stop % |
5 |
Ships set — see §10 (Disaster stops). 0 = OFF |
8. Module: Overnight Hold
A tradable translation of the overnight-hold research by Lou, Polk & Skouras (Journal of Financial Economics, 2019). Long only.
- Entry: buy at the regular-session close — the bar ending at the Entry time (default 16:00).
- Exit: sell at the next session's open — the first bar at/after the Exit time (default 09:30).
- Fridays: no entry (Skip Friday entries, default ON). This module never holds a position over a weekend. A Thursday-night position still exits Friday at 9:30 as normal.
- Timing comes from a 1-minute data series the bot adds when the module is on, and the times are read off your computer's clock. If you run NinjaTrader on a machine outside the Eastern time zone, adjust the entry/exit settings so they correspond to 16:00 / 09:30 Eastern.
- If NinjaTrader is down at the 9:30 exit, the bot exits at the first later chance — the next 1-minute bar it sees, or that day's daily close at the latest — and logs EXIT LATE, so you can see the fill was late.
- If NinjaTrader is down at the 4:00 PM entry, that night is simply skipped. The module never enters late; a later entry is a different trade from the one the system describes.
- Fill quality matters more for this module than for the swing modules, because the holding period is short and the entry/exit are single bars. Watch your simulation fills before drawing any conclusion about it.
- It ships OFF in the file. The appendix configuration turns it on for one chart only.
Settings — 05 Overnight Hold Module
| Setting |
Default |
Meaning |
| Use Overnight Hold |
OFF |
Module on/off (per-chart choice — see the appendix) |
| Entry time |
16:00 |
Buy at this bar — the regular-session close; read off your computer clock |
| Exit time |
09:30 |
Sell at this bar the next session — the regular-session open |
| Skip Friday entries |
ON |
No weekend holds — see the weekend rule (§11) |
| Priority |
1 |
Lower number wins; higher-priority swing signals stand this module down (see §2) |
| Give-back exit |
OFF |
Optional early exit, this module only — see the give-back note below |
| Give-back ARM ($ per contract) |
100 |
Unrealized profit per contract that arms the lock |
| Give-back LOCK ($ per contract) |
50 |
Once armed, exit when unrealized profit falls back to this level |
Give-back exit (optional, ships OFF). With the give-back exit on, the bot watches the hold's unrealized profit per contract on its 1-minute series. Once that profit first reaches the ARM level, the exit is armed: if the profit later falls back to the LOCK level, the bot exits at market immediately instead of waiting for the Exit time. If the lock never triggers, the normal exit applies unchanged. While armed, the chart panel's top line shows GIVE-BACK ARMED, and the armed state is stored on disk, so restarting NinjaTrader mid-hold does not disarm it. The check runs on 1-minute bar closes. This exit is not part of the published Overnight Hold system — it is an optional owner control, off by default, and it exists only on this module. Whether to use it, and at what levels, is part of your own testing.
9. Safety setting: EnforceSimOnly (ships ON)
Enforce SIM account only (in 01 General) ships ON, and it is the most important safety setting in the product.
- With the guard ON, SwingBot refuses all entries on any account whose name does not contain "sim" or "demo". The chart panel shows BLOCKED – SIM GUARD and the log records the refusal.
- The guard blocks entries only. Exits and position management are never blocked, so a position is never trapped by the guard.
- Turning it off is a deliberate act with a real consequence: with the guard off, the bot will place real orders on a live account. Only turn it off when you have finished your own simulation testing, understand every module you have enabled, and consciously choose to trade live. There is no confirmation prompt beyond the setting itself.
- Our recommendation is simple: leave it on until your simulation testing is complete — however long that takes. "Never off lightly" is in the setting's name for a reason.
General settings — 01 General
| Setting |
Default |
Meaning |
| Contracts |
1 |
Position size for every module |
| Enforce SIM account only (never off lightly) |
ON |
See above |
| Trend SMA period |
200 days |
The uptrend/downtrend line shared by RSI(2), Double Seven, and VIX Stretches (published value 200) |
10. Disaster stops
Each module has its own Disaster stop % setting. A disaster stop is a percent-from-entry stop-market order: when a position is open, a stop is maintained that many percent away from the position's average entry price. The stop is re-anchored to the position's average price at each daily close and is monitored by NinjaTrader around the clock while the strategy is running.
Key facts:
- 0 = OFF. With 0 set, that module trades with no stop at all.
- The published systems ship without stops. These settings are optional risk controls added for owners who want a hard floor under a single trade. The RSI(2) and Double Seven disaster stops ship OFF (0); the VIX Stretches disaster stop ships set at 5%. Suggested starting values per symbol are in the appendix (§12).
- A stop is not a guarantee of the exit price. It is a stop-market order: once triggered it fills at the next available price, which in a fast move can be well past the stop level.
- A round-the-clock stop sees more than a daily chart shows. It is monitored against overnight Globex trading, so it can trigger on an overnight low that never appears on your daily bars.
- No stop protects against a gap. Futures close Friday at 5:00 PM ET and reopen Sunday at 6:00 PM ET (and close/reopen around holidays). If the market reopens beyond your stop, the stop fills at the reopen price — wherever that is. See the weekend rule (§11).
- One stop setting per module, per chart — like every other setting in SwingBot, each chart carries its own values.
11. The weekend rule
The swing modules (RSI(2), Double Seven, VIX Stretches) hold positions over weekends on purpose — that is part of their published design, and SwingBot is built for it (exit-on-session-close is deliberately off). A position opened on a Wednesday may still be open the following Monday. Holding over a weekend means accepting gap risk: the market is closed from Friday's close to Sunday's reopen, prices can reopen far from Friday's close in either direction, and no stop can protect you from the gap itself (§10).
Two deliberate exceptions exist, and both default to the conservative published behavior:
- Overnight Hold never holds over a weekend. Friday entries are skipped (default ON), so its last trade of the week exits Friday morning.
- RSI(2)'s "Exit at Friday close" option (default OFF) would force RSI(2)-owned trades flat before the weekend — but it is not part of the published system and changes the system materially. Leave it off unless you have tested the change yourself.
12. Appendix — suggested starting settings (MES / MNQ / MGC / M2K)
The four symbols below are the symbols SwingBot was developed on. The table is a starting configuration for your own simulation testing — nothing more.
These are starting points only. They are not recommendations, not advice, and not a statement that any configuration performs in any particular way. No performance claim of any kind is made or implied by this table. It is your responsibility to test any configuration in simulation, on your own data feed, and decide for yourself whether and how to use it.
Shared defaults (all charts): Contracts 1 · EnforceSimOnly ON · Trend SMA 200 · RSI period 2 · Long RSI entry 10 · Short RSI entry 90 · Exit SMA 5 · Exit at Friday close OFF · RSI(2) disaster stop 0% (OFF) · Priorities: Overnight 1, RSI(2) 2, Double Seven 3, VIX 4 · Double Seven window 7 days · VIX instrument ^VIX, applies-to MES, VIX average 10 days, stretch 5%, streak 3 days, VIX RSI exit 65 · Overnight entry 16:00, exit 09:30, skip Friday ON, give-back exit OFF (optional candidate to evaluate in your own testing: ON with ARM 100 / LOCK 50 — see §8) · Days to load 400.
| Chart |
RSI(2) longs |
RSI(2) shorts |
Double Seven |
D7 stop |
VIX Stretches |
VIX stop |
Overnight Hold |
| MES |
ON |
ON |
ON |
3% |
ON |
5% |
OFF |
| MNQ |
ON |
OFF |
ON |
0% (OFF) |
OFF |
— |
ON |
| MGC |
ON |
OFF |
OFF |
— |
OFF |
— |
OFF |
| M2K |
ON |
ON |
OFF |
— |
OFF |
— |
OFF |
Notes:
- The file itself ships Double Seven ON, VIX Stretches OFF, Overnight Hold OFF, and RSI(2) shorts OFF. The per-chart changes in this table are your setup steps: for each chart, disable the strategy → set the values from its row → re-enable.
- M2K variant: a stricter Long RSI entry of 5 is a documented alternative for the M2K chart only. 10 remains the everywhere default.
- VIX Stretches only ever fires on the symbol in its "Applies to symbol" setting (MES), even if switched on elsewhere.
- Gold (MGC) shorts are OFF in this configuration — leave them off unless your own testing tells you otherwise.
13. Known limitations
- One position per symbol, ever. Signals that arrive while a position is open, or that lose the priority contest, are skipped and never queued. This is by design, and it means some published-system signals will not be taken.
- One-bar deviation: the bot exits a trade at a decision close and takes the next entry at the next decision point, so in rare cases an entry comes one bar later than a same-close exit-and-enter would.
- Fills differ from signal prices. Swing modules evaluate at the NinjaTrader daily close (the Globex day, 5:00 PM ET) and fill at the next tradable moment; published descriptions of these systems were generally framed on regular-session data. Expect small differences between your fills and any published description.
- VIX Stretches depends entirely on your data feed serving a VIX index series. If it doesn't, that module stays inert (the rest of the bot is unaffected).
- Overnight Hold depends on your machine's clock and uptime. Its entry/exit times are read off your computer's clock, and if NinjaTrader is down at 4:00 PM the night is skipped; if it is down at 9:30 AM the exit is late (and logged as such).
- Restart gaps at the daily close: if NinjaTrader is down at a daily close, that day's swing entry or exit happens at the next close instead. On trades that last days, being late once in a while is a cost of running on a desktop platform.
- Stops cannot close a gap (see §10–§11), and a stop-market order does not guarantee its price in a fast market.
- Restart recovery depends on the owner file. If
SwingBotState_*.txt is deleted or missing while a position is open, the position is managed as an RSI(2) trade until it closes, which may mean different exit/stop behavior than the module that opened it intended.
- Charts with Overnight Hold on load slowly (400 days of 1-minute bars). This is expected behavior, not a fault.
- Quiet stretches are normal. Between them, these are slow, part-time daily systems; long stretches with no trade on a given chart are expected, and the panel's "Why:" line tells you what each module is waiting for.
14. Troubleshooting
- Panel says NOT ENOUGH BARS → Days to load is too low. Right-click the chart → Data Series → set Days to load = 400 → OK.
- Panel says BLOCKED – SIM GUARD → the strategy is pointed at an account whose name doesn't contain "sim" or "demo", and EnforceSimOnly is on. Point it at a simulation/demo account — or, only if you deliberately intend to trade live, turn the guard off (§9).
- Panel says BOT FLAT – ACCOUNT HOLDS… → a position exists in that symbol on that account that the bot does not own — usually a manual trade, or a position from another strategy (see the separate-accounts warning). If it is a position you want the bot to adopt: disable the strategy and re-enable it (adoption is automatic). If it is a manual position you want to keep manual, leave it — the bot will simply refuse to trade that symbol until the account is flat in it.
- Log says VIX MODULE INERT → the VIX index data isn't loading. Follow the VIX setup in §7 (check a ^VIX daily chart; fix the instrument-name setting). Everything else keeps trading.
- Log says OWNER ASSUMED → the owner file was missing when the bot re-attached to a position (a first run counts). The bot is managing the trade as RSI(2). If the trade actually belongs to Double Seven or VIX Stretches, its exit/stop rules will differ until it closes — factor that in before deciding what to do.
- A chart loads very slowly after enabling → that is the Overnight Hold chart (400 days of 1-minute bars). Normal. If you stop using the overnight module, switch it off and re-enable — the minute series stops loading.
- Nothing happened today → normal. These are slow daily systems. Check the panel's module board and "Why:" line — they show exactly what each module is waiting for (for example a VIX streak count, or the current RSI(2) value versus its entry threshold).
- A trade is open and you restarted NinjaTrader mid-trade → re-enable the strategy and check the panel shows IN LONG with the right owning module and average price. The bot manages the trade from there.
- The strategy won't compile → make sure you opened the file in the NinjaScript Editor and clicked the Compile button, and that you are running NinjaTrader 8. If errors remain, send support the exact error text from the bottom of the editor plus your NinjaTrader version.
- A module switch didn't take effect → module on/off changes require a disable → set → enable cycle, because NinjaTrader loads the extra data series (VIX, 1-minute) at strategy start.
15. Ideas and support
Idea submissions. Foundation Trading Systems takes product ideas from its users — a strategy or module idea for the bots, or an idea for an indicator. Submit yours through the ideas page on our website. Ideas are tracked publicly through review stages (submitted → in review → in development → shipped), and the first submission of an idea is the one that counts if duplicates arrive. Ideas that get built are credited under the program rules published on the ideas page.
Support. Email foundationtradingsystems@gmail.com. To get a fast, useful answer, include:
- Your NinjaTrader version
- The chart symbol and the module involved
- The day's log file (
Documents → NinjaTrader 8 → SwingBotLog_<SYMBOL>_<date>.txt)
- A screenshot of the chart panel, if the question is about what the bot is showing
Support covers installation, setup, and how the software behaves. It does not include trading advice, setting recommendations for your account, or any assessment of how a configuration will perform — those decisions are yours.
SwingBot is a Foundation Trading Systems product. The published systems implemented in SwingBot remain the intellectual work of their authors: RSI(2) and VIX Stretches — Larry Connors; Double Seven — Connors & Alvarez; Overnight Hold — based on the research of Lou, Polk & Skouras (Journal of Financial Economics, 2019). This manual describes the software only; it makes no performance claims and offers no financial advice.