Midas VWAP - EA

MQL5 Experten

Spezifikation


********** The $30 price is for illustrative purposes only. If you are interested in the project I will create an order of $400 specifically for your user***********

Requirement:

->There must be a function to calculate the price VWAP from a certain point.

There is already an indicator that does this. He calls it VWAP Midas.

 

* When the indicator is plotted on a top it calculates the VWAP taking into account the High:



void CalculateVWAP()

  {

   double sumPrice=0,sumVol=0;

   for(int i=startVWAP; i<iRatesTotal; i++)

     {

      sumPrice    += Price(iHigh ,i)*iVolume[i];

      sumVol      += iVolume[i];

      vwapBuffer[i]= sumPrice/sumVol;

     }

  }

* When the indicator is plotted on a bottom it calculates the VWAP taking into account the Low:


void CalculateVWAP()

  {

   double sumPrice=0,sumVol=0;

   for(int i=startVWAP; i<iRatesTotal; i++)

     {

      sumPrice    += Price(iLow ,i)*iVolume[i];

      sumVol      += iVolume[i];

      vwapBuffer[i]= sumPrice/sumVol;

     }

  }

->There must be a function to calculate the standard deviation of the VWAP(σ).

->There must be a function to calculate the lower and upper band of the VWAP.

 

BottomBandBuffer = VWAP -K1*σ

 

Where K1 is a “double” input and σ is the standard deviation of the VWAP.

 

BufferBandSuperior= VWAP + K2*σ

 

Where K2 is a “double” input and σ is the standard deviation of the VWAP.

 

->There must be a function to validate the VWAP.

(Long exemple)

* When a candle closes below the VWAP it is no longer a valid VWAP and the robot can no longer use that VWAP.


(short exemple)

* When a candle closes above the VWAP it is no longer a valid VWAP and the robot can no longer use that VWAP.

* In the red arrow the VWAP was valid. In the blue arrow after the closing of the candle above the VWAP it is no longer valid.



* VWAP is only valid for N First Rings. If the price touches the VWAP N+1 times it is no longer valid. Where N is an input with default = 3.


In the example above, the VWAP is still valid on the blue arrow, but on the orange arrow it is already invalid, as it is the fourth touch.

In this other example the first vwap is no longer valid on the yellow line. The second vwap is no longer valid on the green line and the third vwap is no longer valid on the purple line (because of the 3-touch rule). However, if the 3-touch rule did not exist, the third vwap would only cease to be valid on the brown line.


->EA Entry pattern:

 

-> The robot will enter the operation based on the VWAP which was plotted by the user.

The robot will only enter the trade if:

 

(short example)

Rules:

* There must be 1 valid VWAP

* Price must touch vwap and close below it

* The price must make a high higher than the highest high between the last N candlesticks (Input: default N=3) And close below. (See example in the graph in blue). The highest high among the last 3 candlesticks was the middle candlestick.

* Entry is made on the next candlestick (0.5 pips before touching vwap)


In this example the entry was made on the red line (0.5 pips before touching vwap).


In this example: The maximum of the last 3 candles is the rightmost candle. The candle touched the VWAP and closed below it. The candlestick made a high higher than the high of the candlestick further to the right and closed below that high. The sell occurs (0.5 pips before touching the vwap) on the red bar.

*Note: The VWAP test must be on the next candlestick.

 

->Take Profit

(short example)

Take will be

BottomBandBuffer = VWAP -K1*σ. K1 defaults to 1

 

->Stop Loss

(short example)

The stop will be

BufferBandSuperior= VWAP + K2*σ. K2 default will be 0.5

 

By default the stop will be 0.5 standard deviation from the VWAP and the take will be 1 standard deviation from the VWAP. But the user can change this input if he wants.

 

Note: Stop and target will be fixed and will be in the position of the respective bands when the robot enters the trade. Stop and target will not be dynamic following the bands!

 

-> Early Stop Loss

(short example)

If the robot is in the middle of a trade and the price closes above the VWAP, it can close the trade (Leave an input(true,false) option to activate this functionality)


In this example the robot must close the operation on the yellow bar at the closing of the candle.

 

->There must be a time filter that the robot can open operations (Input)

 

-> Trading lot control:

*Fixed lot options

*Options to cross out % of the account. With default risk 1% per trade.

->Trade protection

(Purchase example)

*There must be an input (true, false) to allow trade protection (0.5 pips above the entry) if it has gone N% of target. The default of N = 70%

 

 *** must contain the executable and the source code! ***



Bewerbungen

1
Entwickler 1
Bewertung
(851)
Projekte
1464
72%
Schlichtung
122
29% / 48%
Frist nicht eingehalten
358
24%
Arbeitet
Veröffentlicht: 3 Artikel
2
Entwickler 2
Bewertung
(34)
Projekte
60
23%
Schlichtung
11
73% / 9%
Frist nicht eingehalten
3
5%
Frei
3
Entwickler 3
Bewertung
(322)
Projekte
499
67%
Schlichtung
5
40% / 0%
Frist nicht eingehalten
4
1%
Frei
Veröffentlicht: 8 Beispiele
4
Entwickler 4
Bewertung
(3)
Projekte
4
0%
Schlichtung
2
50% / 50%
Frist nicht eingehalten
0
Frei
Ähnliche Aufträge
Freelance Task — EA Recovery Layer Hello. I have a ready-made MQL5 EA. The signals, SL/TP and lot calculation should essentially not be touched. I need a recovery system added. I am not a programmer — below is how the robot should behave. What stays Entry only from an EA signal. Stop-loss is not a new signal. Trailing is already built into my EA — recovery does not implement its own trailing. If trailing is disabled
Watcher position 30 - 100 USD
//+------------------------------------------------------------------+ //| synthetic tick generator based on two assets | //+------------------------------------------------------------------+ class CSyntheticTickGenerator { private : string symbol_a; string symbol_b; string synth_name; double ratio; double last_price_a; double
# SNRZ BOT — SESSION PROGRESS LOG Last updated: 2026-09-16 (local late-evening session) ## SAN BOT (new — cloned from SNRZ) - `MQL5\Experts\AutomatedOrderBot_SAN.mq5` / `.ex5` — v1.0, compiled 0 errors/0 warnings - Signal source: custom indicator "SAN" (InpSANName, buy buf 0 / sell buf 1, target bar 1), same SNRZ-style read, MA fallback if missing - Magic number 234567 (separate from SNRZ 123456 so both bots can run
Multi-Asset EA (XAUUSD / FRA40) with Time Filters, High-Impact News Avoidance, Advanced Risk/Lot Sizing, and H1 Breakout Strategy 1. RISK SETTINGS * Max Daily Loss Limit: (bool) Toggle true/false. If true, input double for max loss in currency (e.g., $500). If hit, close all positions and stop trading until next day. * Lot Sizing Mode: Dropdown menu: 1. Fixed Lots (e.g. 0.10); 2. Percentage Risk (%) based on Account
Should be as it but no alarms, also we need to add a deep search so he can see all the preves candles and a memory function so its not slowing down the indicator. for higher time frames daily 4h 1h around 365 days and for lower time frames we do up to 20k bars but both flexible so i can change it later. the memory is important so the indicator is not always recalculating everything when a new candle shows especially
Creating a bot using the Parabolic indicator with a simple interface.. I want a bot that uses the Parabolic SAR indicator only, with these orders attached to it. Boot name : HEMIN .FX Magic number : 000000 …………………………………………………. Trade behavior : regular OR inverse OR only long "buy" OR only short "sell" Timeframe : ………… Period: ……… ………………………………………………….. Lot size : ……………… Break even in points : …
I am looking for an experienced MQL5 EA developer to develop an MT5 EA by the observable trading behaviour from a supplied live XAUUSD trade history . The EA appears to use a simple grid/recovery/hedging strategy with alternating BUY/SELL positions and progressive lot sizes. I need the developer to Develop the EA for MT5 / XAUUSD . Reproduce the observed entry, grid/add-on, recovery/hedging, lot progression and
Project: Fix & Schedule My Dual Fibo Standard Fibonacci Bot I have an existing MQ4 expert advisor called "Dual Fibo Standard Fibonacci". It needs to process 1,000 clients. Right now it runs blindly with no schedule and takes way too long. I need you to optimize it so it runs like a professional business with a 50-100 batch printed stamp copy progress log. Please reply with your numbers for this simple layout: * Phase
Gold robot 30+ USD
Yes. This screen is asking you to write the Requirements Specification for your Gold/XAUUSD trading robot. Since you want your DEEPTHINK X10 institutional-style MT5 system , use this ready-to-paste specification: DEEPTHINK X10 GOLD ROBOT – MT5 EXPERT ADVISOR REQUIREMENTS Develop an advanced MetaTrader 5 Expert Advisor (EA) for XAUUSD (Gold) scalping based on a multi-factor DEEPTHINK X10 trading framework. 1. MARKET -
Need an MQL5 Expert Advisor for MT5 that automates my manual trading strategy. Entry logic: Enter only when trend direction, support/resistance level, and RSI all align (Triple Confirmation). Extra confluence from Smart Money Concepts (order blocks, Fair Value Gaps, BOS/CHoCH). Risk rules: 1% risk per trade, minimum 1:2 risk-reward, stop-loss at structure levels (not fixed pips). Must-haves: Works on Islamic

Projektdetails

Budget
30+ USD