Hello.
I have an ea that places 2 pending orders - 1 buy stop and 1 sell stop at a certain time.
There are a few things i want changed and fixed:
- The breakeven doesnt sometimes work :
04:29:58.331 '168456': order was opened : #32326447 buy stop 4.00 AUDUSD-Pro at 0.93961 sl: 0.93841 tp: 0.94611
04:29:58.331 '168456': pending order sell stop 4.00 AUDUSD-Pro at 0.93763 sl: 0.93883 tp: 0.93113
04:29:58.487 '168456': order was opened : #32326448 sell stop 4.00 AUDUSD-Pro at 0.93763 sl: 0.93883 tp: 0.93113
04:30:04.243 '168456': modify order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 sl: 0.93883 tp: 0.93113 -> sl: 0.93874 tp: 0.93104
04:30:04.415 '168456': order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 was modified -> sl: 0.93874 tp: 0.93104
04:30:05.211 '168456': modify order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 sl: 0.93874 tp: 0.93104 -> sl: 0.93714 tp: 0.93104
04:30:05.398 '168456': order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 was modified -> sl: 0.93714 tp: 0.93104
04:30:05.398 '168456': modify order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 sl: 0.93714 tp: 0.93104 -> sl: 0.93874 tp: 0.93104
04:30:05.554 '168456': order #32326448 sell 4.00 AUDUSD-Pro at 0.93754 was modified -> sl: 0.93874 tp: 0.93104
04:30:15.210 '168456': delete pending order #32326447 buy stop 4.00 AUDUSD-Pro at 0.93961 sl: 0.93841 tp: 0.94611
04:30:15.351 '168456': pending order #32326447 was deleted
and
11:30:24.138 '168456': modify order #32738475 buy 2.30 GBPUSD-Pro at 1.71124 sl: 1.71004 tp: 1.71674 -> sl: 1.71164 tp: 1.71674
11:30:24.304 '168456': order #32738475 buy 2.30 GBPUSD-Pro at 1.71124 was modified -> sl: 1.71164 tp: 1.71674
11:30:24.304 '168456': modify order #32738475 buy 2.30 GBPUSD-Pro at 1.71124 sl: 1.71164 tp: 1.71674 -> sl: 1.71004 tp: 1.71674
11:30:24.478 '168456': order #32738475 buy 2.30 GBPUSD-Pro at 1.71124 was modified -> sl: 1.71004 tp: 1.71674
As you can see the sl is set back to the original one, BUT, sometimes it does work properly so I have no idea how this can be explained.
- I want the other opened pending order to be closed immediately when the other is triggered. For example - the buy stop gets hit - the sell stop is deleted.
- I want the EA to open the opposite trade when the initial stop loss is hit, with the lot size 80% of the order that got stopped, with SL at the stopped out orders open price. For example - EURUSD buy stop gets hit at 1.3000, 10 lots. SL at 1.2990 gets hit, then immediately a sell order is opened, 0.80 lots, SL at 1.3000. This function should have an on/off switch.
- In the time somewhere between 00:00 - 03:00 the ea's timing and dating gets kinda messed up, I'm adding a screenshot, you'll understand what I mean if you take a closer look at the date and time.
Nothing else of the EA should be changed, there a quite a few modications to it, so I hope that nothing else gets messed up.
I will provide EA when everything is setlled.
Benzer siparişler
Description: Looking for an experienced MQL5 developer to build an EA that: Reads MT5 trade history (DEALS format) Reconstructs trades using Position ID Replays trades in Strategy Tester (tick-based) Simulates trades internally Applies additional logic on top of trades Runs dual mode (original vs enhanced) Calculates MAE/MFE Shows trades visually on chart Outputs performance comparison Delivery required: same day
I need a professional developer to help me create an EA using RSI and Moving averages.The strategies are well organised and everything is in order. I will send all the details in the inbox
Build an MT5 EA focused on low-latency M1 scalping , where performance depends on execution quality (spread, slippage, commissions), not complex indicators. Core Idea M1 timeframe scalping only Short-term momentum + volatility-based entries Trade only in high liquidity sessions (London + NY) Avoid low volatility / Asian session conditions Execution Rules (Critical) Max spread filter (configurable) Max slippage filter
Build an MT5 EA focused on low-latency M1 scalping , where performance depends on execution quality (spread, slippage, commissions), not complex indicators. Core Idea M1 timeframe scalping only Short-term momentum + volatility-based entries Trade only in high liquidity sessions (London + NY) Avoid low volatility / Asian session conditions Execution Rules (Critical) Max spread filter (configurable) Max slippage filter
Project Overview I need assistance coding a hedging Expert Advisor (EA) that operates in "closed cycles" with a strict limit of five simultaneous open positions . EA Logic & Mechanism Initial Entry: Open a Buy position of 0.01 lots (Position A) with a Take Profit (TP) target of $1.00. Scenario 1: Price Drops (Hedging Step 1): If the price moves against the first trade, open two positions simultaneously: a Sell 0.02
I really want a powerful developed EA that can generate a minimum of 10% every month without martingale, greed or any dangerous strategy for sale. Developer must provide the mql5 file or the raw file for modification etc
Specification 1. EA opens a buy stop and sell stop on the last candle 2. stop loss is determined by percentage of the distance between the buy stop and sell stop 3. take profit is also determined by percentage of the distance between the buy stop and sell stop 4. lot size is calculated by fixed amount. example risk $40 per trade 5. a small gap between candle and buy/sell limits determined by percentage of distance
build a trading robot for mql5 from a pdf build within a week discuss more about the trading robot demo runs as the bot purchased write a comsulation for the trading robot
i want to add a specific trading time to an already existing wa that places pending orders above and below opening price bar also change stop loss from percentage to a specific amount
I already have a fully developed MT5 Expert Advisor with all required prop firm features, including: Risk management Daily loss & max drawdown limits Spread & slippage filters News filter Trade management system The EA structure is complete. 👉 What I need is a professional developer to replace ONLY the entry logic with a high-quality, rule-based trading strategy. 🚨 STRICT REQUIREMENT (READ CAREFULLY): I am NOT