Pipsgrowth EX16043 Trend

Pipsgrowth EX16043 Lock Profit is a position-management utility, not a strategy EA. It never opens trades. Its job is narrower and more focused than the other files in the EX16 family: every tick it walks the open positions on the account, filters for the ones tagged with magic number 22216043, and progressively ratchets the stop-loss on each one to lock in realized profit. The header file claims a '12-layer stack' spanning REGIME, SIGNAL, ENTRY, CONFIRM, NO-TRADE, CAPITAL CAP, RISK, SIZING, MANAGE, EXIT, SCALING, and OnTester, but in practice the only layer that does any work is MANAGE — the trailing-stop engine — and the closest thing to a NO-TRADE gate is the magic-number filter that decides which positions this EA is willing to touch. There are zero indicator handles, no OnInit-time IndicatorCreate calls, no arrays of MQL5 indicator buffers, and no OnTester. This file is a tool you attach to a chart, not a system that decides when to enter.

The trailing engine is built around four numeric inputs. InitialTriggerValue=20 is the profit threshold that has to be crossed before the EA does anything at all. InitialSLValue=9 is the first amount of profit it locks in once the trigger fires. StepTriggerValue=20 is how much additional profit is needed for the next ratchet, and StepSLIncrement=9 is how much additional profit gets locked at that ratchet. So with the defaults, on a long trade the EA waits for 20 units of profit, then moves the stop to entry+9; when profit hits 40 units, the stop moves to entry+18; at 60 units, entry+27; and so on, climbing by 9 units every 20 units of additional profit. The level number outProfitLevel = 1 + floor((profit - 20) / 20) is what the panel displays, and the EA also records the last level per position in a long array (lastTrailLevels) so it only fires a PositionModify when the level has actually increased.

The units in those four numbers depend on TrailMode, an enum with three values. TRAIL_BY_POINTS treats one unit as one SymbolInfoDouble(SYMBOL_POINT), so on a 5-digit gold broker 20 points equals 2.0 pips. TRAIL_BY_PIPS multiplies by point*10 to get the conventional 1-pip = 10-points relationship, so 20 pips means 200 points. TRAIL_BY_PROFIT_USD, which is the default, treats the numbers as dollars of floating P&L, and the EA converts dollar amounts into a price offset through the broker's tickValue, contractSize, and tickSize fields — the same math the broker uses to mark positions to market. That last mode is the only one that genuinely works across symbols with different contract specs, since the EA reads tickValue at modify-time and re-computes the price offset from scratch every call.

CalculateNewSL is the function that does the math. It pulls the position's entry price, current price, lots, and floating P&L out of PositionGetDouble, calls ConvertPriceToValue to normalize the profit into the mode's unit, compares it against InitialTriggerValue, and returns 0 if the trigger hasn't been crossed yet. If it has, it computes the level, multiplies the locked-profit value by the level ramp, and calls ConvertToPriceOffset to turn that into a price delta from the entry. The check at line 412 honors SYMBOL_TRADE_STOPS_LEVEL — the broker's minimum stop distance — but only logs a warning if the calculated SL is too close, it does not actually reject the trade; that responsibility falls through to the broker's own order-validation and either succeeds or returns an error code through TryModify_EX16043. The function also has commented-out MathMin/MathMax clamps (lines 402, 408) that would have enforced the stop-level strictly, but they're disabled in the current build.

The trailing direction is one-way. For a buy, the new stop must be higher than the entry price AND higher than the current stop (or the current stop must be zero, which is treated as 'no stop yet'). For a sell, the stop must be lower than the entry AND lower than the current stop. There is no path in the source that loosens a stop — the only PositionModify calls that fire are moves that lock in more profit. That property is what makes the EA genuinely a 'lock profit' tool and not a generic stop-chaser.

The chart panel is built by BuildPanelText but, at least in this build, it isn't actually shown. OnTick has the line string currentPanelText = "HELLO LIVE CHART"; instead of the real BuildPanelText() call, and a 1-second OnTimer prints "HELLO LIVE CHART - Timer". The full panel logic exists in the source — it lists every matching position with its ticket, direction, lots, profit, current SL, locked level, and distance to the next ratchet — but the wiring is incomplete. If you want to see the panel, uncomment those two lines. The logging is real, though: LogAction writes to a 20-entry ring buffer actionLog that the panel would display, and prints to the terminal journal if EnableDebugPrints is true (the default).

At the bottom of the file are three retry helpers — TryClose_EX16043, TryClosePartial_EX16043, and TryModify_EX16043 — that wrap trade.PositionClose, trade.PositionClosePartial, and trade.PositionModify in a 3-attempt loop that retries on REQUOTE, TIMEOUT, PRICE_OFF, and PRICE_CHANGED. Only TryModify_EX16043 is actually wired in: ProcessTrailingSL calls it on line 224 to push the new SL. The two close helpers are unused dead code. ErrorDescription is a 35-entry switch that maps MQL5 trade error codes to human-readable strings, also currently unused by the live path.

The header lists the EA as 'portable' across FX Majors, Gold/Metals, with a suggested timeframe of M5 (also works on H1). That's accurate given the design — there is nothing symbol-specific or timeframe-specific in the logic — but because the EA doesn't gate by session or by weekday, you should run it on the same chart where the original entry was placed, or on a chart that has visibility into the same account's positions. The minimum recommended balance in the database is $100, which is realistic for a utility: this EA doesn't allocate margin, it only modifies SLs, so its capital footprint is whatever the opening EA decided on.

What to expect in backtest: the Strategy Tester will load this file, the OnInit will succeed, but the OnTester and no trade-execution paths will produce almost no tester activity — there are no entries, no exits by this EA, and the trailing logic only fires on positions that exist on the account. In live or demo use, the value is real: drop this EA on a chart that already has open trades with magic 22216043 (or change InpMagicNumber to match your strategy's magic), set the four knobs to your preferred scale, and the SL on each trade will march into profit according to the ladder.