Pipsgrowth EX16083 Trend

The Pipsgrowth EX16083 is a news-event straddle Expert Advisor. Instead of predicting where price will go when a scheduled data release hits the wire, it brackets the moment with two pending orders — a Buy Stop set above the current ask and a Sell Stop mirrored an equal distance below the current bid. Whichever side the news spike activates first becomes the live position; the other side auto-cancels when its expiry elapses, or is left to expire on its own.

The bracket fires at three server hours — 8, 13, and 15 — which the source code explicitly labels as proxies for actual news times. The header comment in the .mq5 file notes that production deployment should connect to an economic calendar feed; in the open-source version, those three fixed hours stand in. The check is wrapped in two early-out guards: if the current minute is anything other than the top of the hour (if(dt.min != 0) return;) the EA does nothing, and a one-hour cooldown (TimeCurrent() - lastTrade < 3600) blocks the straddle from being re-armed within the same hour even if the EA re-ticks. Together they guarantee at most one straddle per scheduled hour, per day.

Distance and risk parameters are all expressed in pips and entered as integer inputs. InpStopDistance = 20 sets how far the Buy Stop sits above the current ask and how far the Sell Stop sits below the current bid. InpStopLoss = 30 and InpTakeProfit = 50 give a fixed 30-pip protective stop and a 50-pip profit target per triggered position — a 1:1.67 reward-to-risk ratio that the EA does not adjust for volatility, time of day, or news event class. InpLotSize = 0.10 is the size submitted on both pending orders. The position-sizing layer of the EA, like its 12-layer marketing claim in the header, is essentially a single input.

InpCancelAfterMins = 10 is the expiry on the pending orders. Both the Buy Stop and the Sell Stop are submitted with ORDER_TIME_SPECIFIED and an expiry timestamp set to TimeCurrent() + InpCancelAfterMins * 60. If neither order has been triggered by the time the candle pushes past that expiry, the terminal drops the pending order automatically — there is no explicit cleanup loop in OnTick. The trade object here is a single CTrade instance, with trade.SetExpertMagicNumber(22216083) set in OnInit and trade.SetDeviationInPoints(20) allowing up to 20 points of slippage on fill.

What the EA does not do is as relevant as what it does. There is no indicator handle — no iMA, no iATR, no iRSI. The decision to fire the straddle is purely clock-driven. There is no trailing stop, no breakeven function, no partial close, no news filter beyond the hour check, and no daily circuit breaker on either a profit target or a loss limit. The three retry helpers at the bottom of the file — TryClose_EX16083, TryClosePartial_EX16083, and TryModify_EX16083 — are correctly written to handle requote, timeout, price-changed, and price-off returns with a 100-200ms Sleep between attempts, but none of them is wired into the OnTick logic. They are template code from the EA family's scaffolding, not runtime paths.

The implication for live use is that the straddle relies entirely on broker execution. The 20-point deviation allowance is generous for FX majors and tight for gold, and the 50-pip take-profit will be reached or missed based on the post-news spike magnitude. On a thin-liquidity broker, the Sell Stop below a 30-pip stop may fill well below the requested price during a flash gap, because pending-order slippage on stops is not symmetric with market-order slippage on the same event.

The magic number 22216083 and the comment string Psgrowth.com Expert_16083 let the EA coexist on the same account with other PipsGrowth EAs without their orders colliding. There is no global SL cap and no equity floor — the EA does not look at account balance at all once OnInit returns, beyond the initial lot size. The min deposit of $100 that the product page records is therefore a function of surviving the spread and one losing straddle at 0.10 lots, not of any internal risk guard.

If you run this EA, the practical workflow is: attach it to a single chart per symbol you want bracketed, set the magic uniquely if you run multiple instances, and pre-warm the symbol on a calendar so you know whether hour 8, 13, or 15 is the one that matters for your session. Backtests will look poor on M1 historical data because M5/H1 candle compression hides the news spikes that activate the straddle — this is an EA designed to be evaluated on tick-data news windows, not on bar-by-bar signals. The .mq5 compiles under #property strict and uses only the standard Trade.mqh include; no third-party libraries are required.

A subtle gotcha worth flagging: the straddle fires only on the first tick of the matching minute-zero hour. If the terminal is closed, the chart is hidden, or the broker's tick feed is silent at the exact second the bar rolls over, the bracket is skipped entirely until the next scheduled hour. The 3600-second cooldown also means a manual Buy or Sell placed earlier in the hour does not block the straddle from arming at the top of the hour — the only thing the cooldown guards against is the straddle re-arming itself within the same window. Plan for missed events by running a calendar check before each session, not by relying on the EA to catch up.