When TS starts up, or when it comes time for the daily subscription check, you will currently get this error:

"The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."

Information is sent between TS and my database via an encrypted connection. Unfortunately what has happened is that my SSL certificate expired.

Obviously TS has been out in public now for almost a year. And obviously I didn't write down in my diary the date of expiry, nor did my webhost remind me.

So, we have to wait until the new certificate is issued. I've created the support ticket, it's been assigned to somebody, and all that's left is the waiting.

Sorry for the trouble. If it helps, this is only going to happen once a year, and now it's in my diary I shouldn't forget next time.

Download - Purchase.

Fixed Or Added In v0.9.3

• New Rules:
  • [OHLC] Is More Than X Pips Above Entry
  • [OHLC] Is More Than X Pips Below Entry
• More Long/Short Stop Loss Mgmt Rules and Values. That is, you have more ways to decide when and where to move the stop loss. In total there are 9 ways to move the stop loss, plus the Move To Break Even one makes 10.
• Auto-login.

Support is as normal - within 24 hours of receiving your request.

Download - Purchase.

Fixed Or Added In v0.9.2

• No trades taken during backtesting when using Enter At Market.
• Fixed calculations for all X-Over rules.
• Forget RateTable exceptions given by Oanda API. Create Activity instead.
• Cannot cast DBNull error when backtesting.

Travelling Friday, apartment search Saturday, start new job Monday. Sorry, but I can't guarantee your emails will be answered within 24 hours until things settle.

Support is as normal - within 24 hours of receiving your request.

I'll be travelling about 500km on Sunday, job interview on Monday, drive back Tuesday. I'll check emails on Monday afternoon and Tuesday night (GMT+10). Apologies in advance for any inconvenience.

Download - See what changed - Purchase.

When testing auto-trading, I set it to output files just like it does when backtesting, so I could see what it's doing. But I forgot to turn this off when I released v0.9.0. So whenever auto-trading kicks off, it printed out 2 files for each trading system checked.

It no longer does this.

If you click "Admin" > "Options" from the main menu, you can see the location that the files will be in. The same as the backtesting output directory. Go to that directory using Windows Explorer, delete, and you're done.

When you fill in the details of a trading rule, such as a Long Entry Rule, there is the "I want this to NOT be true" option.

Moreover, generally there are always opposite rules available. E.g.:

• Close Above Simple Moving Average
• Close Below Simple Moving Average

So what's the difference between choosing:

1. "Close Above Simple Moving Average" and using the "I want this to NOT be true" option; and
2. "Close Below Simple Moving Average"

?

Well, there is a slight one.

When the Close is below the SMA, both option #1 and #2 are true.

When the Close is above the SMA, both option #1 and #2 are false.

When the Close is exactly the same as the SMA, option #1 is true, while option #2 is false.

Using "I want this to NOT be true", TS calculates the result of the rule as if you did not want to use this option, then it takes the opposite of that result.

So when the Close equals the SMA, no, it's not above the SMA so the normal result is false, then taking the reverse, the result is true.

In a lot of cases, you can use both methods interchangeably. E.g.:

• One Simple Moving Average Is Above Another
• One Simple Moving Average Is Below Another

In this case there will be no difference between simply choosing the other option, or instead using the "I want this to NOT be true" option.

So you will have to think about your particular situation.

But here's one to consider - the MACD Histogram cross from Oversold into Overbought.

For this one, you choose the following Long Entry Rules:

• "MACD Histogram In Oversold", and set the Bar Offset to 1, meaning you want this rule to have been true 1 bar ago; and
• "MACD Histogram In Overbought"

These two rules combine to allow Long orders to be placed only when the MACD Histogram crossed from Oversold into Overbought.

But what if the value of the MACD Histogram 1 bar ago was exactly zero? In this case the MACD Histogram is neither in Overbought, nor in Oversold. So while the MACD Histogram has legitimately crossed from Oversold into Overbought, TS will disallow the trade because it thinks the MACD Histogram was not in Oversold 1 bar ago.

(Remembering that TS is in fact doing exactly as you told it to do).

This situation is not going to happen very often. If it did, all that happens is you miss a trade. But, if you're worried about it, set the Long Entry Rules to this:

• "MACD Histogram In Overbought", use the "I want this to NOT be true" option, and set the Bar Offset to 1; and
• "MACD Histogram In Overbought"

Doing it this way effectively changes the entry rule from being "enter when the MACD Histogram crosses from Oversold into Overbought" to "enter when the MACD Histogram crosses from not in Overbought into Overbought".