모든 주문
규칙
트레이딩 로봇 주문 방법을 보십시오
주문을 실행하거나 포스트하기 전에 규칙을 읽으십시오
MQL5 및 MQL 4의 트레이딩 로봇을 주문하는 방법
로봇을 주문하기 위해샘플 요구 사항을 보십시오
카테고리의 새로운 주문:
30 - 50 USD
80+ USD
30+ USD
30 - 100 USD
30+ USD
30 - 50 USD
30+ USD
작업 종료됨
실행 시간 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%
중재
2
0%
/
0%
기한 초과
1
1%
작업중
8
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
게재됨: 1 코드
비슷한 주문
I am looking for a highly skilled and experienced MQL5 developer to build a professional-grade, fully automated Expert Advisor for MetaTrader 5. This is not a simple project — the EA must combine multiple trading strategies, a dynamic risk management system, a real-time news filter, and a sophisticated trade management engine into one cohesive, well-coded solution. Strategy Overview: The EA should operate on multiple
Copy trading bot
80+ USD
Here is what I’m looking for: • Signal source: On-chain wallet address monitoring. I want to copy trade high win-rate meme coin wallets (smart money / profitable traders), not Telegram signals. • Market: Crypto (primarily meme coins). • Execution speed: Very important — I want as close to sub-second execution as possible. Low latency is a top priority. • Infrastructure: I’m open to self-hosted VPS or cloud setup if
Advanced Prop-Firm Compliant MT5 Expert Advisor (Capital Protection Focus) Project Overview I am looking for a high-quality Expert Advisor (EA) for MetaTrader 5 designed for prop firm challenges and funded accounts. The system must prioritize capital protection, strict rule compliance, consistency, and long-term stability. The EA must work on Gold (XAUUSD) and major Forex pairs. 🔐 Risk Management Requirements
Olá, Sou um comprador sério interessado em adquirir um Expert Advisor (EA) já existente, estável e rentável, projetado especificamente para: 👉 principalmente (XAUUSD) ou qualquer outro câmbio Trata-se de um pedido de compra integral. ⚠️ Não estou interessado em criar um novo EA do zero. Somente sistemas prontos para uso e comprovados, com histórico real de desempenho. ✅ Requisitos da EA (Rigorosos) 📌 Símbolo e
Money Manger/monitor changes
30 - 100 USD
My EA (Expert Advisor) is a powerhouse! 💪 With rock-solid 100% risk management, it lets you trade stress-free while maximizing gains. Free to manage manually, it's designed to boost profitability. 🚀
Grid bot for pionex bitmart, gateio
100 - 350 USD
Hello, Primary goal: convert the existing MQL5 strategy logic to Python as soon as possible and make it work for API trading (order management, exchange connection, basic bot structure). I want to keep the core logic unchanged . I haven’t chosen the exchange yet (must be usable in the EU ). Binance, OKX, Kraken, and Bybit are not options. Bitmart, pionex, gateio are options. Secondary goal (code reduction): the
This post is subject to developers response . Edit the post as you like . May be with me you can make a come back . So , , , Shift calculations . More to the calculation then you can comprehend is known . What else comes to your mind
This first robot I'm needing to order a robot that will help me with my trading and make it most efficient Help me with my margins my signals or anything I need to do associated to my trading or classroom
1- In the Universal EA that I currently have, in MA mode under the Take Profit options, when using the “Kill positions + clean one buy one” option, the counter resets itself before the accumulated loss is fully recovered while the loss stored in memory is being cleared. If fixing this is not possible, then I would like to modify the method as follows: Instead of clearing the accumulated losses in the Losses Pool one
1. Shift the Time Gate (Critical) Current start time: 08:30 New required start time: 08:35:01 The EA is currently triggering trades too early (between 08:25 – 08:30 ), which is causing incorrect entries. Please ensure the EA cannot enter any trade before 08:35:01 . 2. Change Order Execution Logic The current code is using Pending Orders . Please remove pending order logic completely . Replace it with Direct Market
프로젝트 정보
예산
50+ USD