RGM diskuse

Hi. Any rationale to Additional_Channels being set to 1 in the range of 0-8? Do you have slippage at default for 1.2.0 which is 0.5 (developer told me that corresponds to 5 under 1.1.6)? I have my AC set to 8 and running demo on EES FX and I got fewer trades than you did today. Thanks.

Also curious what your trade execution speeds are like.

Hi gwrigh,

I'm honestly not sure how the different AC settings affect MDP's trades. I've been told that increasing additional channels causes MDP to enter trades a little earlier than AC=1, which can produce more trades overall. But a few of the trades often get in too early and end up as losers, so I'm not suree if that's something I wanted.

Anyway, I decided to play it conservatively and stick with the default settings for the most part. I have been using NO=0, AC=1, SO=4 (reduced from 8), FIFO=false, Use_Stop_Orders=true, Use_Trailing_Stops=true, Risk=1.5%. However, I lowered SO to 2 the other day, just to see if MDP ran smoother without as many simultaneous orders. But then we had the server disconnect debacle for the past two days, and most of my sl and tp modification orders couldn't get filled, and the original sl was passed over during the disconnect. So my losses were larger than usual. EES FX/ILQ have stated that I will be reimbursed for the losses though, so we'll see. In the end, however, I'll probably increase SO back to 4 and keep it there.

My trade execution and modify times have been very good for the most part -- 300ms - 500ms -- and usually always under 1 second or just slighty over during certain spikes. The only time they have been terrible was during the server freeze over the past two days. By the way, an ILQ rep told me that they found the source of the problem and it has been fixed. So we shouldn't have the same problem going forward. We'll soon see if that is correct or not. Good luck with your trading and take care...

Cheers,
Roger

hi rgmann,

how do you find EES FX/ILQ reliability so far it is ok. I found the support a little bit poor, i also cannot login to their forum. How long yours take the wire deposit to be available in platform?

Hi, did you try AC=0 or have you decided what the ideal values for NO, AC, and Slippage are? Thanks.

Hi rgmann, do you mind giving a complete settings update? Thanks.

Sorry for the delay, I don't check this message area very much. Here's my current settings:

NO=0
AC=1
SO=1
FIFO=false
AutoECN=false
GroupOrders=false
StopOrders=true
Hard Trailing Stops=false
fixed lots= .1

I think everything else is default. I hope that helps out...

Hi Abdul,

The support at EESFX is overloaded. I'm pretty sure it's just a few persons operation, and they got a lot of new clients over the past month. So they are very slow to respond. If you need help, try to contact ILQ directly, as they are the actual broker (EESFX is more like an IB).

My wire deposit was available within the same day that I wired it. But I wired it from within the US, so it may take a little longer if you are overseas. I hope that helps... 😎

Cheers,
Roger

Thanks for the settings. Are you keeping Slippage at 0.5 with EES - is that working? Did you ever try AC of 0? I thought I saw you on Donnaforex saying you were going to try that. Thanks again.

Yes, I've kept the slippage setting at 0.5 for the time being, and I got 3 positive trades today. I also kept the AC at 1 for now because I finally upgraded to v.120 and I wanted to compare how it trades with the same settings I was using with v.116. I may experiment with AC=0 later though. It just depends on how things go over the next week or two. Take care and best of luck to you!

Cheers,
Roger

Hi rgmann,

Have you seen anything like this in your MT4 journal? I'm using the same broker and VPS, I believe...

11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81:5,1: WARN Unable to create BUYSTOP price:1.32495 SL:1.32341 TP:1.32634
11:03:29 stdlib EURUSD,M1: loaded successfully
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops
11:03:29 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 81: Number of subsequently repeated orders reached limit (5)

I believe this resulted in the subsequent trade getting in too late and being a loser. It reached that limit two more times before executing this trade, which was a loser:

11:03:30 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: open #170305 buy stop 5.00 EURUSD at 1.32512 sl: 1.32342 tp: 1.32665 ok
11:03:30 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 86:8,1: BUYSTOP price:1.32512 SL:1.32342 TP:1.32665
11:03:33 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: 87:8,1: Modify Order #170305 BUY tp:1.32665->1.32665 sl:1.32342->1.32428
11:03:33 MillionDollarPipsEURUSD_1.2.0 EURUSD,M1: modify #170305 buy 5.00 EURUSD at 1.32503 sl: 1.32428 tp: 1.32665 ok

Note, it's a $20K real account and I was experimenting with larger trade sizes.

Hi gwrigh,

I stopped getting REQUOTING + REPEATING warnings for the most part when I set Hard_Stop_Trailing=false and set Max_Simultaneous_Orders=1. I'll still get the occasional warning, but it seems to place the orders much smoother with these settings. However, I still keep Use_Stop_Orders=true, as I think it's too dangerous to have MDP place the initial order without the sl and tp already set.

My trade execution and modification times were mostly between 1 to 2 seconds today for some reason. They're usually below 1 second though, so I'm not sure what happened today. I also experimented with NumOrders_Levels=1 today, so that may have been a factor in my 2 trades being losers: -10.7 and -0.4 pips. But I had NumOrders_Levels=0 on my other ILQ account and I got 1 positive trade for +7.1 pips.

Cheers,
Roger

I had Max_Simultaneous_Order=1 when I got this error. I'm going to try AutoApply_ECN=false with Use_Stop_Orders=false and Hard_Stop_Trailing=false (with smaller trade sizes) to see if it helps. I'm also going to try Additional_Channels=0 with this. Let you know how it goes.

Hi Roger,

I saw that you just add EA Shark 6.0 into your live account. Are you running EA Shark and MDP in the same platform? is EA Shark the good EA?

Best Regards,
Thanat

Hi Thanat,

Yes, I just added EA Shark 6.0 to my account yesterday, and I'm running both the Shark and MDP on the same platform. Since the Shark usually only trades during the Asian session when the market is relatively quiet, I don't think it will ever try to place trades at the same time as MDP. So I don't forsee any problems running them on the same platform.

I feel that both MDP and the Shark are good EAs, but so far the 36% gain I have on my account has come solely from MDP. Now that I'm running both EAs at the same time, I'm hoping to see my account grow even faster! But only time will tell... 😎

Cheers,
Roger

Hi Roger,

I set AC=0 and did not get any trades on the last spike. So I'm moving back to AC=1. Do you think those warnings I was getting:

WARN Unable to create BUYSTOP
WARN following error blocked our last trading command (REQUOTING + REPEATING) : invalid stops

Do you think it is because it tries to set a S/L but the prices is changing too quickly that by the time it executes, it is no longer valid? So it keeps trying, but it's behind the ball and too slow?

How would Use_Stop_Order=false and Hard_Stop_Trailing=true work? Would it open the initial order without S/L but then modify the order with trailing Stops? I'm a little confused there. It worries me a little to have it opening orders without S/L given the connection issues that have happened to some, including you.

Thanks for your insights,
Geoff

Hi Geoff,

Yes, that's most likely why you're getting those warning messages. I was getting them when I had SO=4 or higher. But since I dropped it to SO=1 I haven't gotten any. But I did get the following on the second price spike yesterday, along with several trades that took more than 2 seconds to execute and modify...

16:32:20 '1344': pending order buy stop 0.08 EURUSD at 1.33324 sl: 1.33018 tp: 1.33600
16:32:20 '1344': order buy stop 0.08 EURUSD opening at 1.33324 sl: 1.33018 tp: 1.33600 failed [Invalid S/L or T/P]
16:32:20 Expert stdlib EURUSD,M1: loaded successfully
16:32:21 '1344': pending order buy stop 0.08 EURUSD at 1.33344 sl: 1.33032 tp: 1.33580
16:32:21 '1344': request was accepted by server
16:32:21 '1344': request in process
16:32:22 '1344': order was opened : #178629 buy stop 0.08 EURUSD at 1.33344 sl: 1.33032 tp: 1.33580

I'm not sure what caused that. I'm assuming that the price moved too quickly and passed the sl and tp that MDP was trying to set. Any ideas?

Using StopOrders=false and HardStopTrailing=true will open the order without a sl or tp already set. It will then try to modify the order with a sl and tp. Once that is done it will modify the order with a hard trailing stop as the price moves into positive territory.

Personally I use StopOrders=true so that it opens the trades with a sl and tp already set. That's much safer in my opinion. But I don't really see the need to have HardStopTrailing=true, because MDP will still continually modify the sl and tp during the trade, even with HardStopTrailing=false. Plus, it just seems to work smoother with HardStopTrailing=false from what I've seen so far. But I could be wrong. This bot has so many different combination of settings, it's almost impossible to come up with the perfect set up! 😲

Cheers,
Roger