工作已完成
执行时间9 天
客户反馈
Victor did a great job with the EA. He has good communication skills and is a skilled programmer. Would buy again from him!
指定
**Objective**: Develop a trend-following Expert Advisor (EA) that opens trades based on a trend detected across multiple timeframes using the *AllAverages_v4.9_MT5* indicator. The EA should use a Martingale strategy, only adding trades in the same direction when the price moves against the initial position, and include several risk management settings.
### Strategy Overview
1. **Trend Detection**:
- The EA should detect a trend by analyzing the *AllAverages_v4.9_MT5* indicator across multiple timeframes.
- Execution timeframe will be set to M1, but the trend should be confirmed on multiple selected timeframes.
- **Condition for Entry**: The EA will open a trade only when all selected timeframes show a trend in the same direction, as indicated by the *AllAverages_v4.9_MT5* indicator.
- **Trend Identification**: The EA should use the uptrend/downtrend buffers of the indicator to determine the trend direction.
2. **Martingale Strategy**:
- If the price moves in the opposite direction of the open trade, the EA should open an additional trade in the same direction as the initial trade but with a larger lot size.
- The lot size for each subsequent trade should increase based on a configurable Martingale multiplier.
- The step size (in pips) for opening the next position when the price moves against the trade direction should also be configurable.
- There should be a configurable maximum number of trades in the Martingale sequence to prevent excessive risk.
- The EA should keep opening new trade sequences whenever the last sequence hits TP and the trend is still confirmend on all selected timeframes.
### Configurable Settings
1. **Trend Confirmation**:
- The EA should allow setting the number of timeframes that must show the same trend direction before opening a trade.
- Users should be able to select a specific type of moving average (e.g., HMA, EMA, DEMA, etc.) for each timeframe individually (e.g., H4 could use EMA while M1 uses DEMA).
2. **Trade Settings**:
- **Starting Lot Size**: Configurable starting lot size for the initial trade.
- **Martingale Multiplier**: Factor by which the lot size should increase with each subsequent trade in the Martingale sequence.
- **Step Size**: Number of pips the price must move against the last opened trade of the sequence before the EA opens the next trade in the Martingale sequence.
3. **Take Profit (TP) Settings**:
- TP should be configurable in terms of profit per trade (e.g., $20).
- When a new trade is added to a sequence, the TP should be adjusted to the same for all open trades so that if the TP is hit, the total profit is equal to the target profit specified for the first trade (e.g., if the first trade's target was $20, the cumulative profit for all trades in the sequence should still be $20 when the TP is hit).
- The TP should increase, if necessary, but should never result in a lower total profit than initially targeted.
- The TP should be updated only when a new trade is added to the sequence.
- Spread should be factored in the TP level.
- The TP should be updated only when a new trade is added to the sequence.
- Spread should be factored in the TP level.
4. **Stop Loss (SL) Settings**:
- Configurable SL as a percentage of total account equity.
- This SL should apply to the entire trade sequence, not individual trades. For example, if the SL is set to 5% of equity and there are 4 trades in the Martingale sequence, the SL should adjust to the same for all open trades such that the combined loss would equal 5% of equity if hit.
- The SL should be updated only when a new trade is added to the sequence.
5. **Time Filter**:
- The EA should have a configurable time filter to limit when new Martingale sequences can begin.
- Users should be able to set specific time windows for trading (e.g., 00:00-08:00 and 14:00-23:59).
- If a sequence is still open outside of the trading window, the EA should continue to manage the sequence (e.g., adding trades if necessary and changing TP/SL) until it closes via TP or SL.
- The time filter should use server time.
6. **Capital Loss Limit**:
- An option to set a maximum allowable loss in dollar terms. If this loss limit is reached (including floating losses), the EA should:
- Close all open trades immediately.
- Disable itself to prevent further trading.
- This feature ensures compliance with prop firm drawdown limits. The EA should continuously monitor floating losses on each tick to prevent violating drawdown rules.
7. **Magic Number**:
- The EA should have a configurable magic number to help distinguish trades it opens from other trades on the account.
### Additional Features
1. **Logging**:
- The EA should log all key actions, such as when a new trade sequence starts, trades are added to a sequence, TP or SL levels are modified, and sequences are closed.
2. **Alerts**:
- The EA should send an alert whenever a new sequence is opened and when a sequence closes.
- These alerts should be configurable for desktop notifications and push notifications to a mobile device.
### File Requirements
- The EA should be able to access the *AllAverages_v4.9_MT5* indicator directly to read trend up/downtrend buffers.
### Summary
This EA will serve as a trend-following system using multiple timeframes to confirm a trend direction, with a Martingale approach to manage trades when price moves against the position. Configurable settings will allow for precise control of trade entries, lot sizing, risk management, and time filters. Key logging and alerts will enhance monitoring, and robust risk management features ensure compliance with prop firm trading rules.
反馈
1
等级
项目
25
52%
仲裁
3
0%
/
100%
逾期
2
8%
空闲
2
等级
项目
165
24%
仲裁
23
9%
/
78%
逾期
16
10%
工作中
3
等级
项目
10
10%
仲裁
9
0%
/
89%
逾期
1
10%
空闲
4
等级
项目
8
13%
仲裁
3
0%
/
33%
逾期
2
25%
空闲
发布者: 1 代码
5
等级
项目
19
16%
仲裁
3
67%
/
0%
逾期
0
空闲
6
等级
项目
29
21%
仲裁
20
10%
/
50%
逾期
8
28%
工作中
7
等级
项目
91
52%
仲裁
1
0%
/
0%
逾期
1
1%
工作中
8
等级
项目
0
0%
仲裁
0
逾期
0
空闲
发布者: 1 代码
相似订单
Subject: Major Upgrade Request: Auto Confluence of Signal/Trend/Momentum Scores with Multi-Timeframe SMC Hello, Your bot is excellent analytically, but I'm facing daily manual intervention due to the multiple indicators and timeframes. --- 📊 Current Situation: The bot uses: · Signal Score · Trend Score · Momentum Score · SMC Analysis · 3 Timeframes (Fast 5M, Medium 15M, Main 1H) · 4 Additional Indicators Currently
SMC Trading Bot
30 - 60 USD
1. The Core Idea: The "Liquidity-to-Liquidity" Engine Instead of just looking for a "Supply Zone," the bot must ask: "Whose money was just taken, and whose money are we targeting next?" The "Valid Move" Checklist A structure break or a zone is only "Real" if it meets the SMC Trinity: Inducement/Sweep: Price must take out a previous minor high/low (Retail Stop Loss) before the move. Displacement: The move must be
Multi-Slave Inverse Hedging EA with Martingale Grid — MT5 Category: Experts Description: I am looking for an experienced MQL5 developer to build a professional-grade Expert Advisor system called Hedging EA Trader . This is a well-documented project — I have a full 30+ page Software Requirements Specification (SRS) ready to share with the selected developer. System Overview: The EA uses a Master/Slave architecture: 1
I'm looking for an experienced programmer that can build a good EA/Robot for Price Action and Ichimoku strategy.The strategy Involved only two indicators; Ichimoku Kinko Hyo and Price Action. Buy when Price Action crossess above Kumo Cloud (either Up or Down Kumo Cloud)with 1Pips and Sell when Price Action crosses below Kumo cloud (either Up or Down Kumo Cloud) with 1Pips and exit Buy and Sell Order when its crossed
my tick based EA works on demo account but it fails on real account, issues i can see / guess is order execution in demo account is less choppy and relaxed. is there anyone who can help me to fix it
Fix the errors of this bot
30+ USD
Hello, I need some expert who can hlep me fix the errors of this bot that will work normally ba check the bot file, error messages, and any specific issues you are currently facing so you can get started
1. Project Overview I am looking for an experienced MQL5 developer to design a robust, clean, and well-structured Expert Advisor (EA) for MetaTrader 5. The goal is to transform a clearly defined trading logic into a stable, efficient, and fully configurable EA , suitable for backtesting and optimization. 2. Platform & Language Platform: MetaTrader 5 Programming language: MQL5 Code must follow best practices (modular
Stratégie name this robot
30+ USD
Please, I need an expert and professional to watch the uploaded video and tell me the name of the strategy. Thank you very much.Please name the strategy accurately, professionally, and clearly
I want a modification on my ea . A spread filter or slipage filter such that when the market price is less than 50 point away from the pend order , then ea check the spread if less than the set filter spread. If spread is more than the set spread, the ea will delete the pend order . Secondly , if the broker price is moved or sliped the pending order from the original price it was set by the tolerable slipage distance
Hi, I’m currently looking to purchase a profitable Expert Advisor (EA) for XAUUSD on MT4 and different Symbols . If you have an EA that has consistently been profitable, I’d be interested in purchasing the source code. I would like to backtest the strategy and evaluate it before making any purchases. What I’m ideally looking for: Designed specifically for XAUUSD (MT4) Consistent profitability with solid risk
项目信息
预算
50+ USD