Pipsgrowth EX16058 Trend

Pipsgrowth EX16058 Trend is a specialized news management utility — not a signal generator. It attaches to an MT5 chart alongside any other EA and acts as a guard: when an economic-calendar event is about to strike, EX16058 closes the open positions on the affected pair, deletes pending orders, optionally stops the EA's auto-trading, and re-enables trading after the news shock has dissipated.

The mechanism is straightforward but layered. On initialization the EA fires a GET request to https://nfs.faireconomy.media/`ff_calendar_thisweek`.xml using MQL5's WebRequest(). The response is an XML feed of the week's economic events. EX16058 walks the block, pulls the , , , , and from every node, converts the date string to a datetime value, and stores the result in a 500-element news_event_struct array. Up to 500 events are kept in memory; the EA's EventSetTimer(news_update_hour*3600) schedules a re-fetch every 2 hours so the calendar stays current without spamming the network.

Before storing, each event runs through three filter functions. CurrencySelected() keeps only events whose currency appears in either the chart symbol (default) or a custom symbol list — default USD,EUR,GBP,JPY,CAD,CHF, set via the symbol_type and news_symbols inputs. TitleSelected() optionally narrows further to a comma-separated keyword list, which defaults to Non-Farm,Unemployment,ISM,PMI,CPI,FOMC,Retail Sales,Final GDP q/q,Core PCE Price Index m/m,Empire State Manufacturing Index,Advance GDP q/q,JOLTS — the dozen or so USD releases that reliably move XAUUSD. ImpactSelected() limits by severity, defaulting to high-impact only with include_medium and include_low both off. Any of these three filters can be widened: a trader running only USD pairs can leave the title list as-is and let the dozen named releases through; a multi-pair portfolio operator can disable the title filter entirely with use_title=false and let high-impact events for any of the six watched currencies trigger the lockdown.

Once the calendar is in memory, the per-tick logic in OnTick() runs two timing checks. BeforeNewsForZeroProfit() returns the affected currency if the current GMT time is between min_before_zero=60 minutes before the event and the event time itself. AtNews() returns the affected currency if the current GMT time is between min_before=5 minutes before the event and min_after=45 minutes after. These two windows are deliberately different in shape: the pre-window is wider (60 minutes) and is used for harvesting profits ahead of volatility, while the at-window is asymmetric (5 before, 45 after) and is used for full defensive lockdown while the market digests the release.

When the pre-window fires (and close_zero=true, default), EX16058 checks if ACCOUNT_PROFIT >= close_profit (default $1). If yes, it runs CloseAll(_pair) which iterates the position pool backwards, calls trade.PositionClose() on each ticket through the TryClose_EX16058() retry helper, and accepts either TRADE_RETCODE_DONE or TRADE_RETCODE_DONE_PARTIAL as success. The retry helper loops up to three times on TRADE_RETCODE_REQUOTE, TRADE_RETCODE_TIMEOUT, TRADE_RETCODE_PRICE_OFF, or TRADE_RETCODE_PRICE_CHANGED, sleeping 200ms between attempts. If close_pending=true, DeleteAllPendings() follows — same loop, but with trade.OrderDelete(). The function OpenTrades(_pair) returns the count of remaining positions; if it is still >0, the EA sleeps 5 seconds (the delay input) and re-runs on the next tick. If close_only_news_pair=false (default), the pair string is "all" and the close sweep runs across the entire account.

When the at-window fires, the same close logic runs unconditionally (if close_open=true). If stop_algo=true (default), AlgoTradingStatus(false) is called. This is the only place EX16058 touches Windows: it pulls the chart's HWND via ChartGetInteger(ChartID(), CHART_WINDOW_HANDLE), walks up the parent chain with GetAncestor(hwnd, GA_ROOT), and posts WM_COMMAND with MT_WMCMD_EXPERTS to flip the Algo Trading button off. The next time AtNews() returns "No News" and the internal allow_trade flag is false, the function is called again with true, restoring the button. The Print(), SendNotification(), and Alert() calls fire one combined message ("[NEWS!] All trades are Closed. All pendings are Deleted. Auto trading is Disabled.") when the lockdown engages. Close_zero logic and the at-window logic are guarded by separate allow_trade flips, so the pre-news profit-take can fire independently of the at-news lockdown.

Visualization is on by default. DrawNews() runs on init and on every timer tick, walking the first 100 stored events and dropping a vertical line at each event time on the chart, color clrRed, style STYLE_DOT, width 1 (all configurable via Line_Color, Line_Style, Line_Width). Each line is hidden from selection (OBJPROP_SELECTABLE=false, OBJPROP_SELECTED=false, OBJPROP_HIDDEN=true) and lives in front of candles (OBJPROP_BACK=false). When the EA is removed, OnDeinit clears the chart comment and ObjectsDeleteAll(0) removes the lines.

A few details round out the build. slippage=5 is hardcoded as a global (no input), and the per-symbol filling mode is set via trade.SetTypeFillingBySymbol() before every close or delete to handle both IOC and FOK exchanges without manual configuration. MarketOpen() checks the symbol's session table via SymbolInfoSessionTrade() and returns false on weekends or outside the trading session, preventing close attempts when the book is frozen. TryClosePartial_EX16058() is wired but never called — dead code kept for symmetry with the other two retry helpers. Every order touched is tagged with the trade comment Psgrowth.com Expert_16058, which makes it trivial to filter post-trade analytics by which closes were news-driven versus manual.

Practical deployment requires two terminal settings. First, Tools → Options → Expert Advisors → Allow DLL imports must be checked, otherwise OnInit() aborts with a MessageBox. Second, the URL https://nfs.faireconomy.media/ must be added to the same tab's Allow WebRequest list — if it is not, the first WebRequest() returns error 4060 and OnInit() prompts the user with a popup naming the URL. Both are one-time setup steps that take under a minute.

The use case is narrow but well-defined: a discretionary or systematic trader who runs any EA on XAUUSD, EURUSD, GBPUSD, USDJPY, USDCAD, or USDCHF and wants a deterministic defense against the dozen-or-so USD data releases per month that routinely produce 20–50 point whipsaws against open positions. Backtest behavior is structural rather than statistical — there is no equity curve, no PnL attribution, no optimization surface to tune. The EA is either correctly fetching the calendar and clamping the windows, or it is not, and the chart's vertical red lines plus the Print() log are the only diagnostics.