Pipsgrowth EX16064 Trend

Pipsgrowth EX16064 is not a trading strategy. It is a price-streaming utility that pumps live bid, ask, and mid quotes from MetaTrader 5 out to an external PHP endpoint using the WebRequest function. The chart symbol and any user-defined symbol list are polled on a fixed timer; each tick of the timer ships a JSON payload to the URL configured in the inputs, and the receiving PHP script is expected to persist or broadcast those prices to whatever downstream system needs them — a custom web dashboard, a Telegram bot, a mobile app, a remote journal, or an analytics back-end. There are no entries, no exits, no stop loss, no take profit, no indicator stack, and no risk model. Three CTrade retry helpers (TryClose_EX16064, TryClosePartial_EX16064, TryModify_EX16064) are defined in the source but are never called from OnTimer or OnInit; they are vestigial scaffolding from the template the EA was forked from, not part of the operational flow.

The polling rhythm is set by the IntervalSeconds input (default 5 seconds). OnInit calls EventSetTimer with that value, OnDeinit calls EventKillTimer to release the timer cleanly, and OnTimer is the only routine that runs after startup. Each OnTimer invocation calls BuildPayload to assemble the JSON body and then SendJSON to ship it. If the user has populated the SymbolsList input with a comma-separated list, BuildPayload splits that list, trims each token, looks up SymbolInfoDouble for SYMBOL_BID and SYMBOL_ASK, and concatenates a JSON object per symbol — { code, bid, ask, mid } — into a single array. If the list is empty, the EA falls back to chart-symbol mode and emits a single JSON object for whatever symbol the chart is currently showing. In both cases the output is normalized to a JSON array before being sent, so the receiving endpoint never has to branch between single-object and array shapes.

Symbol mapping is handled by the MapToCode function. It strips common broker-suffix decorations (a trailing dot-suffix such as .r or .m, or trailing letters pro/r/m that some brokers append to symbol names) and then applies a hard-coded code map: XAUUSD becomes GOLD, XAGUSD becomes SILVER, WTI/CL/UKOIL/USOIL collapse to OIL, NG/NATGAS to GAS, and DXY to USD. Anything else — EURUSD, GBPUSD, USDJPY, AUDUSD, and so on — passes through unchanged. The map exists so the upstream pricing service can key prices on stable, broker-independent codes rather than on whatever your MT5 broker happens to call a metal or index contract. If you need to add your own mapping, the function is the single place to extend.

The HTTP request itself is constructed in SendJSON. The URL is built by appending ?token= plus the Token input to the Endpoint string; the body is the JSON array returned by BuildPayload; the method is POST; the content type is application/json; and the timeout is 8000 ms. A non-200 response prints the HTTP code and the body so the user can see why the push failed. With LogSuccess set to true, every successful push also prints the response body — useful for debugging the PHP side but noisy in production, where the default is false.

Configuration lives entirely in the two input groups. The Identity group holds InpMagicNumber (long, default 22216064) and InpTradeComment (the comment string Psgrowth.com Expert_16064 that would be written to a trade if the EA ever opened one). The Price Push Settings group holds the Endpoint URL, the shared Token, the SymbolsList string, the IntervalSeconds int, the PushChartSymbolAlso flag, and the LogSuccess flag. There are no other inputs. There is no buffer to be wrong, no indicator period to tune, no risk percentage to debate — the EA is what its inputs say it is.

There are three operational gotchas worth knowing up front. First, WebRequest is restricted by default in MT5: the exact Endpoint URL (or its host) has to be added to Tools → Options → Expert Advisors → Allow WebRequest for the listed URL, otherwise every push will fail with a 4063-style error. Second, the Token is a shared secret — the default CHANGE_ME_TOKEN should be replaced before the EA goes live, and the matching PRICE_PUSH_TOKEN on the PHP side has to be set in the .env of the receiving application. OnInit prints a soft warning if the token is shorter than 8 characters. Third, pushing more often than roughly once per second starts to compete with the terminal's own price updates and can produce duplicate or near-duplicate rows on the receiver; the input comment explicitly advises against sub-2-second intervals, and the default of 5 is a sensible floor for most dashboards.

Typical use cases are dashboard bridges — piping the broker's spot prices into a custom website so customers see the same quotes the broker sees without scraping — price-mirroring for social-trading or signal services that need a stable feed, journaling integrations that record every tick for later analysis, and lightweight alert engines that watch prices in PHP rather than in MQL. The 12-layer architecture label in the header is descriptive boilerplate carried over from the EA template; the actual behavior is just timer-driven HTTP POST.

In backtest this EA will not open or close anything and will produce a flat equity curve — it is not a strategy. Its value is operational, not alpha-generating. Attach it to a chart on any symbol you want to feed, configure the endpoint and token, make sure the WebRequest URL is allowlisted, and you will see a fresh JSON push arrive at the receiving service every IntervalSeconds. A ForcePush() function is exposed as a public no-argument routine so a chart hotkey or another EA can trigger an immediate push outside the timer cadence if a specific event needs to be flushed right away.