Disliked{quote} I closed it manually...so not sure if this is useful: {image}Ignored
1
Money management: Capital needed per 0.07 USD per microlot 0 replies
The Volume Detective 411 replies
Disliked{quote} I closed it manually...so not sure if this is useful: {image}Ignored
Disliked{quote} I closed it manually...so not sure if this is useful: {image}Ignored
Disliked{quote} Since you first reported this I've tested both the single-trading EA with Strategy Tester and the AllPairs EA on an M1 chart. To my eyes the CC Exit is working fine. According to the logging: 1. The trade was opened at 2019.09.16 @12:00 2. The 'x' that you circled occurs at 2019.09.16 at @13:00 3. The trade was manually closed at 2019.09.16 @17:15 Since the EA has to wait for a candle to close, then I would have expected CC Exit to close the trade at @14:00 -- which it did not. So -- I agree. The trade should have closed at @14:00. And I...Ignored
Disliked{quote} @northwind -- The setting says "4-digit group ID [1000-9999]". There are a couple of problems with the numbers you chose: 1. They are not 4-digits and do not fall in the range [1000,9999]. 2. The default Group ID for the single-trading EA is '1111'. So, '1111' will be replaced with your 4-digit group ID. 3. You can not assign numbers for each currency -- the EA is responsible for composing that portion of the Magic Number.Ignored
Disliked{quote} Hi, Just made a list of the 8 currencies and gave each one a number 11, 22, 33, 44, 55, 66, 77, 88 to use in EA. In the EA 4 digit group ID field for EURUSD I manually type 2211, for GBPUSD I typed 3311, for EURJPY I typed 2244, etc. The EA shows this 4 digit ID on the chart as the Magic Number. But the trades don't show 4 digit ID in the comments.Ignored
Disliked{quote} Hi, Just made a list of the 8 currencies and gave each one a number 11, 22, 33, 44, 55, 66, 77, 88 to use in EA. In the EA 4 digit group ID field for EURUSD I manually type 2211, for GBPUSD I typed 3311, for EURJPY I typed 2244, etc. The EA shows this 4 digit ID on the chart as the Magic Number. But the trades don't show 4 digit ID in the comments.Ignored
Disliked{quote} @northwind -- I searched back through the thread and found the post where I first described how magic numbers are composed -- post #4982. Here is a link: https://www.forexfactory.com/showthread.php?p=12383893#post12383893 The format remains the same today -- though there might be some minor differences when it comes to the symbol IDs.Ignored
Disliked{quote} R4M, Thank you. I must be misunderstanding Post #4982 where it says, "Magic Numbers: I've been meaning to explain how the EAs use MagicNumbers. For the single-pair trading EAs the default MagicNumber is '0'. If you leave it at '0' then the EA will compose one on its own according to the rules I layout below. If you enter a number other than '0' then it will use that. For single-pair EA on EURUSD I entered magic number 2211. But the single-pair EA comment is showing 1111 for EURUSD and for different pairs. {image} {image} {image}Ignored
Disliked{quote} Since you first reported this I've tested both the single-trading EA with Strategy Tester and the AllPairs EA on an M1 chart. To my eyes the CC Exit is working fine. According to the logging: 1. The trade was opened at 2019.09.16 @12:00 2. The 'x' that you circled occurs at 2019.09.16 at @13:00 3. The trade was manually closed at 2019.09.16 @17:15 Since the EA has to wait for a candle to close, then I would have expected CC Exit to close the trade at @14:00 -- which it did not. So -- I agree. The trade should have closed at @14:00. And I...Ignored
DislikedHi It was discussed i know, but the TMA repaints badly... Stated to watch the LMW crossing withe the midleline and it shows there is no magick in the indi {image} see this pic {image} and see this pick You can clearly see that the rapaints 6 bars, wich is a whole day...thats huge in my opinion... So in other words good entries at firs can later bee seen as bad entries or even no entries... FOR those who will say try it first and you will see I am {image} The only prosit the are my own trades. The time frame is 4h, no intervention.Ignored
QuoteDislikedIt was discussed i know, but the TMA repaints badly...
Stated to watch the LMW crossing withe the midleline and it shows there is no magick in the indi
Disliked{quote} Same again on AUDUSD: {image} {image} {image} EDIT: I just noticed the indi gave a Buy signal but the EA did not add a position to the current position that is still open. {image} {image}Ignored
QuoteDislikedSame again on AUDUSD
QuoteDislikedI just noticed the indi gave a Buy signal but the EA did not add a position to the current position that is still open.
DislikedThanks for the latest update R4. The new exits for the H1 seem to be working fine before a potential waterfall. Better safe than sorry. Rich {image}Ignored
Disliked{quote} {quote} I have the same chart and signals. Check out the screen shot below: 1. AUDUSD-H1 opens a BUY at 2019.09.17@9:00 and that is closed at 2019.09.17@11:00 by CC Exit 2. AUDUSD-H1 opens a BUY at 2019.09.17@13:00 and that is closed at 2019.09.17@15:57 by midline crossing {image} Could you double-check and make sure the indicator and EA are both using the same Entry Type -- i.e. Consecutive Candles. If the indicator is using Consecutive Candles and the EA is using HA Transitions then it will get confusing trying to match things up. Actually...Ignored
Disliked@R4m Testing it on 5 min as suggested with 5%ADR to get some fast examples. I just got my first demo trade to hit mid line, candle closed with a midline notification, next candle opened and closed gave midline notification again and the trade did not close. {image} {image} {image} Shall update more later. EDIT UPDATE: Here is AJ several candles later and there have been multiple candles getting the midline close alert but the trade stayed open. Also other buy signals but no new buys. {image} {image} Very strange.Ignored
Disliked{quote} @simontw -- I still can't explain why you'd be encountering this problem with the latest version and not with previous versions -- but now I'm wondering whether this might have something to do with the logic and code that I had added that prevents repeatedly opening / closing trades on the same bar. That is, the code that is supposed to protect against intrabar trading (by ignoring certain signals) might also be responsible for this behavior. However, that was added a few versions ago. I'll continue to look into this and keep you posted....Ignored