Spécifications

# Project Requirements – Sierra Chart to MT5 Integrated Alerts

*Scope:*  
The project must be a *fully integrated system* including both:  
1. *Sierra Chart ACSIL sender* – writes alerts to JSON.  
2. *MT5 EA (Listener)* – reads JSON alerts and executes trades in MT5.  

The system must handle alerts *from Sierra Chart to MT5 execution* completely, not just file sending.

*Duplicate Alert Detection:*  
- Use *timestamp* for each alert.  
- Only *one trade per alert at a different time*.  

*JSON Fields Required:*  
{
  "symbol": "...",
  "timeframe": "...",
  "direction": "...",
  "valid": true
}

*Trade Execution Settings (MT5 EA):*  
- *Loss:* in currency, manually set in inputs.  
  - Example: if the difference between entry and stop is 20 points → loss = $100.  
- *Take Profit (TP):* from 1 to 5 (or 1 to 3), manually configurable.  
- *Entry:* at the close of the alert candle.  
- *Stop Placement:*  
  - Buy → below the alert candle  
  - Sell → above the alert candle  
- *News Filter:*  
  - Close all trades 5 minutes before news  
  - Accept new orders 5 minutes after news  
- *MT5 Symbol Suffix/Prefix:* Depends on broker. Currently, no suffix/prefix.  

*Sierra Chart Performance:*  
- Ensure *Sierra Chart performance is not affected* during alerts sending.  

*MT5 EA Behavior:*  
- Receive JSON payload.  
- Execute trade *immediately if valid=true*.  
- Ignore alert if valid=false.  

*Development Deliverables:*  
1. *ACSIL source code (.cpp)*  
2. *MT5 EA source code (.mq5)*  
3. *MT5 executable (.ex5)*  

*Testing & Support:*  
- Testing and bug fixing are *free*.  
- Support must be provided *even after project completion*.  
- The developer *must provide a video demonstration* showing complete setup, installation, and running of the system.  
- If installation issues arise, the developer must *connect via AnyDesk* to fix problems directly.  

*Additional Requirements:*  
- The system must *read Alert Manager file periodically*.  
- Only detect *new alerts*.  
- The system should be *extendable* to allow additional JSON fields for MT5 trade execution in the future.








Hi
Trade Execution Settings (MT5 EA):**  
- *Loss:* in currency, manually set in inputs.  
  - Example: if the difference between entry and stop is 20 points → loss = $100.  
- *Take Profit (TP):* from 1 to 5 (or 1 to 3), manually configurable.  
- *Entry:* at the close of the alert candle.  
- *Stop Placement:*  
  - Buy → below the alert candle  
  - Sell → above the alert candle  
- *News Filter:*  
  - Close all trades 5 minutes before news  
  - Accept new orders 5 minutes after news  
JPG
IMG_20260608_170353_163.jpg
640.2 Kb
Such as Risking money is another example. 

 risk 100 $ 


manually configurable.  
- *Entry:* at the close of the alert candle.  
- *Stop Placement:*  
  - Buy → below the alert candle  
  - Sell → above the alert candle  

Loss:** in currency, manually set in inputs.  
  - Example: if the difference between entry and stop is 20 points → loss = $100.  

 Use TP3 only      true or false   
Use TP5  only       true or false 
Use TP7 only        true or false 
Use TP10 only      true or false  


Is this clear? 
Hi,
I need to implement a dynamic lot size calculation module in this MetaTrader 5 Expert Advisor (MQL5). The position size must not be fixed; instead, it should be calculated automatically for every trade based on a manually set dollar risk and the point distance between the entry price and the stop loss.
Here are the technical requirements and input parameters:


Risk_Amount_USD (input double): Default = 100.0 (The maximum amount in account currency I am willing to lose per trade).
Use_TP3_Only (input bool): Default = false
Use_TP5_Only (input bool): Default = false
Use_TP7_Only (input bool): Default = false
Use_TP10_Only (input bool): Default = false
(Note for Developer: Please ensure these TP inputs act as an exclusive radio-button logic in the OnTick() or OnInit() to avoid conflicts).
2. Entry and Stop Loss Logic
When an alert/signal is received for the Alert Candle:
Execution Time: Execute the market order immediately at the Close of the alert candle (EntryPrice = Candle\ Close).
Stop Loss Placement (SL_{price}):
For BUY: SL_{price} = Alert\ Candle\ Low
For SELL: SL_{price} = Alert\ Candle\ High
3. Dynamic Lot Size Calculation (MQL5)
Before sending the trade request via CInTrade or MqlTradeRequest, the EA must calculate the exact lot size based on the candle size.


ample Scenario:
Risk_Amount_USD = $100
Alert Candle closes, triggering a BUY.
EntryPrice (Close) = 1.1020, SL_{price} (Low) = 1.1000 \rightarrow Risk = 200 Points.
The EA must calculate the exact lot size so that if the trade hits the SL, the realized loss is exactly $100.

Final Trade Management Specification for the Developer
Hi,
Please implement the final Take Profit (TP) and Breakeven (BE) logic based on the user selection. Only one TP setting can be true at a time.
Here is how the EA must manage the trade for each specific input:

Important Rules for the Code:
Exclusive Inputs: If Use_TP3_Only is true, the EA should ignore or automatically set the other TP inputs to false to avoid conflicts.
Execution Flow: * For TP3: Open Trade \rightarrow Hits 3R Target \rightarrow Close Trade.
For TP5 / TP7 / TP10: Open Trade \rightarrow Hits 3R Level (Move SL to Entry) \rightarrow Hits Final Target (Close Trade).


Add this requirement for Alert Time Filtering:
"Please implement a strict Alert Time Filtering module for incoming signals from Sierra Chart. The EA should only process alerts and execute trades if the signal is received within a user-defined time window.
Please add these input parameters:
START_Time (input string): Default = "03:00" (HH:MM format, manually configured by the user).
END_Time (input string): Default = "04:00" (HH:MM format, manually configured by the user).
Execution Logic:
When an alert message is received from Sierra Chart, the EA must check the current time against the START_Time and END_Time window.
IF the alert arrives strictly between START_Time and END_Time \rightarrow The EA is allowed to calculate the lot size and execute the trade.
IF the alert arrives outside this designated window \rightarrow The EA must completely ignore the alert and take no action.
This is critical to ensure the EA only operates during the specific high-probability market hours I select."

 

Hi,
I need to implement a dynamic lot size calculation module in this MetaTrader 5 Expert Advisor (MQL5). The position size must not be fixed; instead, it should be calculated automatically for every trade based on a manually set dollar risk and the point distance between the entry price and the stop loss.
Here are the technical requirements and input parameters:


Risk_Amount_USD (input double): Default = 100.0 (The maximum amount in account currency I am willing to lose per trade).
Use_TP3_Only (input bool): Default = false
Use_TP5_Only (input bool): Default = false
Use_TP7_Only (input bool): Default = false
Use_TP10_Only (input bool): Default = false
(Note for Developer: Please ensure these TP inputs act as an exclusive radio-button logic in the OnTick() or OnInit() to avoid conflicts).
2. Entry and Stop Loss Logic
When an alert/signal is received for the Alert Candle:
Execution Time: Execute the market order immediately at the Close of the alert candle (EntryPrice = Candle\ Close).
Stop Loss Placement (SL_{price}):
For BUY: SL_{price} = Alert\ Candle\ Low
For SELL: SL_{price} = Alert\ Candle\ High
3. Dynamic Lot Size Calculation (MQL5)
Before sending the trade request via CInTrade or MqlTradeRequest, the EA must calculate the exact lot size based on the candle size.


ample Scenario:
Risk_Amount_USD = $100
Alert Candle closes, triggering a BUY.
EntryPrice (Close) = 1.1020, SL_{price} (Low) = 1.1000 \rightarrow Risk = 200 Points.
The EA must calculate the exact lot size so that if the trade hits the SL, the realized loss is exactly $100.

Final Trade Management Specification for the Developer
Hi,
Please implement the final Take Profit (TP) and Breakeven (BE) logic based on the user selection. Only one TP setting can be true at a time.
Here is how the EA must manage the trade for each specific input:

Important Rules for the Code:
Exclusive Inputs: If Use_TP3_Only is true, the EA should ignore or automatically set the other TP inputs to false to avoid conflicts.
Execution Flow: * For TP3: Open Trade \rightarrow Hits 3R Target \rightarrow Close Trade.
For TP5 / TP7 / TP10: Open Trade \rightarrow Hits 3R Level (Move SL to Entry) \rightarrow Hits Final Target (Close Trade).
Feature Requirement: Trade Notification System (WhatsApp & Telegram)
Condition:
The Expert Advisor (EA) must include a built-in notification system capable of sending real-time trade results and details (Opening, Closing, and Modifications) automatically via Webhooks/API to both WhatsApp and Telegram

Add this requirement for Alert Time Filtering:
"Please implement a strict Alert Time Filtering module for incoming signals from Sierra Chart. The EA should only process alerts and execute trades if the signal is received within a user-defined time window.
Please add these input parameters:
START_Time (input string): Default = "03:00" (HH:MM format, manually configured by the user).
END_Time (input string): Default = "04:00" (HH:MM format, manually configured by the user).
Execution Logic:
When an alert message is received from Sierra Chart, the EA must check the current time against the START_Time and END_Time window.
IF the alert arrives strictly between START_Time and END_Time \rightarrow The EA is allowed to calculate the lot size and execute the trade.
IF the alert arrives outside this designated window \rightarrow The EA must completely ignore the alert and take no action.
This is critical to ensure the EA only operates during the specific high-probability market hours I

Répondu

1
Développeur 1
Évaluation
(279)
Projets
377
72%
Arbitrage
19
32% / 47%
En retard
15
4%
Gratuit
Publié : 15 codes
2
Développeur 2
Évaluation
(258)
Projets
323
30%
Arbitrage
34
26% / 65%
En retard
10
3%
Travail
3
Développeur 3
Évaluation
(8)
Projets
9
11%
Arbitrage
0
En retard
0
Gratuit
4
Développeur 4
Évaluation
(545)
Projets
827
62%
Arbitrage
33
27% / 45%
En retard
23
3%
Gratuit
Publié : 1 code
5
Développeur 5
Évaluation
(8)
Projets
8
0%
Arbitrage
2
50% / 0%
En retard
1
13%
Travail
6
Développeur 6
Évaluation
(28)
Projets
39
23%
Arbitrage
14
0% / 93%
En retard
4
10%
Gratuit
7
Développeur 7
Évaluation
(163)
Projets
172
44%
Arbitrage
3
33% / 33%
En retard
1
1%
Travail
8
Développeur 8
Évaluation
(24)
Projets
31
19%
Arbitrage
4
50% / 25%
En retard
4
13%
Gratuit
9
Développeur 9
Évaluation
(593)
Projets
685
33%
Arbitrage
42
45% / 45%
En retard
12
2%
Occupé
10
Développeur 10
Évaluation
(7)
Projets
10
10%
Arbitrage
4
50% / 0%
En retard
0
Travail
Publié : 4 articles, 33 codes
11
Développeur 11
Évaluation
(1)
Projets
1
0%
Arbitrage
1
0% / 0%
En retard
0
Gratuit
12
Développeur 12
Évaluation
(258)
Projets
265
29%
Arbitrage
0
En retard
3
1%
Gratuit
Publié : 2 codes
13
Développeur 13
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
14
Développeur 14
Évaluation
(48)
Projets
56
34%
Arbitrage
15
27% / 60%
En retard
1
2%
Travail
15
Développeur 15
Évaluation
(58)
Projets
90
43%
Arbitrage
4
0% / 100%
En retard
3
3%
Travail
16
Développeur 16
Évaluation
(42)
Projets
50
60%
Arbitrage
4
50% / 25%
En retard
0
Travail
17
Développeur 17
Évaluation
(25)
Projets
31
13%
Arbitrage
13
0% / 77%
En retard
9
29%
Gratuit
Commandes similaires
I need an Ai trading bot for Binance and BTC on MT5 that also uses order flow data. It should also make use of TSI- Temporal indicator sampling and also it should make use of fundamental analysis in the process of signal generation
Title: MT5 Forex Trading Robot Development I need a MetaTrader 5 (MT5) Expert Advisor (EA) for automated Forex trading. Requirements: 1. The robot must be fully automated and capable of opening and closing trades without manual intervention. 2. Compatible with MetaTrader 5 (MT5). 3. Adjustable lot size, Stop Loss, and Take Profit settings. 4. Built-in risk management based on account balance. 5. Ability to trade
MT5 EA Developer for Structured ICT/SMC Market Logic Requirements Specification: I need an MT5 Expert Advisor only in MQL5. No indicator, no script, no DLL, and no external API. The EA must be built on a rule-based ICT/SMC-style framework with objective, backtestable logic. I am not looking for social-media-style ICT/SMC interpretation. I need a developer who can convert trading concepts into clear coding rules. The
I need an experience programmer on news based EA, the EA will be able to fetch or return both historical and current calendar data and implore them into trading, The rest EA details will be communicated in the chat section
Mambo 30+ USD
I need a bot that can trade weltrade synthetic indices that can be consistently making profits if you have one for deriv its also fine a bot that executes and closes trades automat Will be ideal
I am looking for an experienced MQL4/MQL5 developer to build a custom MT4 indicator from scratch or cracking my ex4 file that i provide to you. I already have an existing indicator (EX4) which produces highly accurate buy/sell signals. I want a similar indicator developed based on its observable behavior and signal structure. my existing indicator is pc id protected so you have to do PC ID security bypass and source

Informations sur le projet

Budget
100+ USD
Délais
de 1 à 5 jour(s)

Client

Commandes passées3
Nombre d'arbitrages0