LRSF - TMS Expert Advisor

Quoting Abhimanyu

Disliked

OrderSend error 138

Ignored

 * 20-08-2017 Version 1.09
 * - After some improvements to version 8 it was decided to re-release version
 *   8 with all the updates as version 9.
 * - Bugfix: TDI value did not use parameter tframe.
 * - Function ntr_chk_pac() is now used to check if the PAC supports a new
 *   trade-entry.
 * - Calculation of PAC-trend hugely simplified and more generic.
 * - Add test to PAC that previous bar broke PAC -and- had right color.
 * - Bugfix: Profitprotection took orders out too soon.

 * 15-09-2017 Version 1.10
 * - Using the class cl_symbol where possible.
 * - Better messages on screen about status.
 * - No new orders after 18:00 on friday.
 * - Close positive orders on friday after 23:50.
 * - Some classes are now suitable for multi-curency and multi-timeframe
 *   operation. This is needed if we want this program to run on a single
 *   instance but still trade multiple currencies.
 * - Exit trade when we are under 3 pips profit and the MA10 on M1 is
 *   against us.
 * - Make use of extra ma_fast and ma_slow optional.
 * - Set BE SL when the price reaches BE trigger. The old algo would wait
 *   for the current bar to finish and then set BE to the LOW of the
 *   previous bar (the one just completed) if that would be above the
 *   open-price.
 * - Made PAC-check a separate function.
 * - Made MA-check a separate function.
 * - Redesigned code to check the conditions from the TDI.
 * - Bugfix: For some brokers the errorcode SendOrder 138 (Requote) occured.

 * 17-12-2017 Version 1.11
 * - Version 1.10 now has the correct entry mechanics for standard PAC
 *   trading. Version 1.11 will add correct exit mechanics for standard
 *   PAC. The rest is optimisation of existing code. No new functionality.
 * - Made STO-check a separate function.
 * - Made TDI-check a separate function.
 * - Made exit-check for changing HA-color a separate function.
 * - Bugfix: The checks of the lower timeframes MA1 and MA5 were actually
 *   checking the current timeframe and always bar[0] which makes testing
 *   difficult. This is now fixed.
 * - Made MA5-check a separate function (not stable yet).
 * - Made HIST check a separate function.

Quoting jansb000

Disliked

MEME-Trade, what is it? I am not going to try to come up with an official definition. For that I refer to the official TMS thread. But this is a small example: {image} Note that this is a screenshot from the H1 timeframe, but the first trade was done in the H4 timeframe. My initial trade went nowhere and under normal circumstances it would have been stopped by a stop-loss. However, because I was convinced that this trade was good and eventually would go in the direction that I initially anticipated... I decided to enter a second, and later a third...

Ignored

Quoting Deichkind

Disliked

...I've done a test with the V1.11 and my problem is that it is very slow.......after ending I see that over 200(!!) TDI-indicators are opened...is that right?...

Ignored

Quoting fung0625

Disliked

Hi there No appropriate TDI indicator is running in EA. {image}

Ignored

Quoting emmanuel7788

Disliked

{quote} Hi Jan, one suggestion for MEME trade management is to use Profit Lock when you have 3 or more positions in MEME. see comments in your chart. {image} the management will be he same even when you have 2 open positions, you 'lock the profits' at the breakeven level of 2 positions and exit both positions when M5 (TDI or MACD) cross up for sell.

Ignored

Quoting jansb000

Disliked

{quote} Hi Deichkind, Thank you for testing. I noticed that the EA is slow and therefore difficult to test and optimise in the stategy tester. However, I never found the reason why (apart from that a custom indicator is slower than the build-in indicators). How do you know that there are >200 TDI indicators? Where would I be able to see that? As far as I am concerned there is no reason for so many TDI Indicators. So it is definitely not part of a strategy that I deliberately build in. Cheers...

Ignored

Quoting Deichkind

Disliked

do you use the TDI green red or the TDI RT_clone indicator? Will that make sence to change? regards

Ignored

Quoting jansb000

Disliked

{quote} I have a TDI from the TMS-thread. There are now so many versions of TDI around that I am not sure which one exactly I have, but it came with source code and there is nothing suspicious as far as I can see. I re-posted this version in this thread: https://www.forexfactory.com/showthr...6#post10631496 If you, or anyone else reading this, has another version of TDI and used it without any problems in other EA-projects, then I wouldn't mind trying them. I am using the red, green and yellow line so just the red-green...

Ignored

Quoting Deichkind

Disliked

{quote} Hi Jansb000, I've now taken the TDI from your link and deleted my old ones. But the problem is still there Works slowly, doesn't open a trade and at the end more then 200 TDIs are opened on the tester-end-screen in visual-mode regards

Ignored

Quoting jansb000

Disliked

{quote} Hi Deichkind, Thank you for your effort to run this EA through the strategy tester. Would it be possible for you to do the same test with some of the older versions? It would be interesting to know when this problem was introduced or if it was there from the start. Cheers...

Ignored