Hi Vinzze, 

Thanks for the question and .set file so I can check into things. 

It seems the source of the confusion is that you have set the following input: 
Active in profit only = Trail in profit; 

When you have done so, it will not activate the 20 pip fixed trail unless it is already protecting profit. 

For instance, if your GBPUSD travels 5 pips in profit (your specified threshold), then the 20 pip fixed trail would be set 15 pips below your entry; however,  because you also indicated Trail in Profit mode, then that 20 pip fixed trail will not get activated because your trail SL is not protecting profit. With a 20 pip fixed trail, the trail SL will not get activated till it exceeds 20 pips in profit, which is the phenomena you were noticing. 

Now, if you want to have UTS activate a 20 pip fixed trail after reaching its 5 pip threshold, regardless if the trail level is protecting profit or not, then you would simply indicate
Active in profit only = inactive; 

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: Tck:40655193, lxTA:true, vesSymbPerm:

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: symb permitido 40655193

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: Tck:40643276, lxTA:true, vesSymbPerm:

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: symb permitido 40643276

...........

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: Tck:40643276, lxTA:true, vesSymbPerm:

0 00:00:11.367 Ultimate Trailing Stop EA GBPUSD,H1: symb permitido 40643276

Please check what error this is. It shows up continuously, my log file is more than 20mb.

Thank you.

V2.59 work fine with me now.

I'm glad the newer versions are working fine for you now :)

Hi Pham, just to follow up, those were prints that were added to debug a problem and do not affect the EA. I removed the prints and version 2.64 now does not have them. 

Hi Blake,

So I just purchased the EA, and have been playing around with it for a bit to optimize the settings.  Although the EA did something funny at one point:  For example, I placed a long signal for EURUSD at 1.05050 with the trailing SL at 1.05000, and a threshold of 1.05025.  The SL did indeed start trailing the signal properly once it surpassed the threshold.  HOWEVER, when the signal started to move short (against my signal), the SL actually moved back along with it as well, defeating the whole purpose of what a 'Trailing' stop should do (ie. only move in ONE direction).  Is there something within the setting that's making it do this?  Let me know when you see this, thank you!

Thanks for your question and compliment, and I apologize for not seeing your comment earlier. 

If you don't set a threshold, the fixed trail will move immediately behind your current price. For instance, if Threshold in pips or atr multiplier or ratio=0 and Fixed Trail=20, then the stop loss will trail 20 pips below your closing price, limiting your loss to 20 pips at the onset. 

However, if you indicate Threshold in pips or atr multiplier or ratio=30 and Fixed Trail=20, then the program will wait till you have achieved 30 pips in profit and then trail 20 pips below the closing price, protecting 10 pips at the onset. 

Can you please share with me your .set file so I can check your settings out and see why this issue happened. 

I trade the SP500, which is close enough to the NAS100. 

What I have found is that you probably need a threshold (in order to allow your trade to mature in profit before trailing it) and a trailing stop that is not too tight or too loose. 

As for threshold, I would go with something like: 

Choose Pips or ATR or Threshold = ATR; 

ATR Time frame for calc=1 hour; 

ATR Period for Calc=25; 

Threshold in pips or ATR multiplier or ratio=1; 

As for the trailing stop, I would go with something like a trail at 30 Percent: 

=== Global Inputs

Trailing Stop Method = Percent;

=== Percent Inputs

Percent = 30; 

50% trail will find you being trailed out too fast, but 30% trail will allow the trade to breath enough so that you can pick up higher profits when the trade moves more in your direction. 

I have also had good success with moving average trails: 50 EMA on H1. 

HI Blake,

Appreciate the prompt reply.  Attached is a screenshot of the current settings.  You can also e-mail me at yasumuranao0205@gmail.com as well if you'd like.  Thank you!

With version 2.70, there is now this feature: 

- now when the UTS has a problem setting an SL, it will retry 5 seconds later. The SL Value on the Panel will be shown in red and if you put the mouse cursor over it, it will show the error message. 

Hi Blake,

Your backtest option looks very promising.

I’ve tried to configure it following your recommendations and taking a mql5 signal’s history csv file, but there’s absolutely no results appearing after I run the test.

Besides, I see the following messages at the end of the report’s journal :

-          84 bytes of leaked memory

-          1 object of type rrLstHstTrd left

-          1 undeleted objects left

Maybe I’m missing something in the settings ? Do you have a more detailed tutorial to see how it should work ?

Many thanks,

Andrei

The fixed trail doesn't need a threshold. It trails x pips below the price if no threshold is indicated. 

Example: If you indicate threshold=0 and fixed trail=10, then it will trail 10 pips below its current price. 

Optionally ,fixed trail can work with a threshold. 

Example: if you indicate threshold=20 and fixed trail=10, then it will first wait to reach 20 pips and then trail 10 pips below current price. 

Ok, since you will not work with the trailing mechanism, you need to de-activate that by putting threshold=1000 (or auto-active trail on open=false AND auto-activate trail on new=false). 

Your next input values will go into the the Virtual TPs: 

Size Type=Percent; 
TP1 Size=30; 
TP1 Close Percent=50; 
TP2 Size=50; 
TP1 Threshold for trail=false;
TP2 Size=50
TP2 Close Percent=50; // because it works on remaining, and you want it to work on initial, 50% of remaining in this case would be 25% of initial, like you want it
Use TP as TP1 = true; 

Hi Andrei, 

When backtesting, make sure that the signal history's csv file is saved in the correct format. By default, the signal history gets saved in CSV UTF-B (Comma delimited) format when it should be in CSV (Comma delimited) format to read correctly. 

I end up having to open the signal history in Microsoft Excel, and then save as CSV without the UTF-B: 



I then copy and paste that newly saved file into my tester > files folder



When I have UTS loaded up in the strategy tester on the signal symbol I am tested with, I put in the following settings: 



I can then run the strategy tester as is, and see if it matches the signal performance, more or less: 




I then experiment with optimization with various trailing stops of UTS to see if I can get bettter results: