darashikoh/mql5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Commit graph

  • c7a617709f Resolution of git index lock due to VS Code repo editing darashikoh 2025-08-13 01:34:23 +01:00
  • d6eccab613 Resolution of git index lock from VS Code darashikoh 2025-08-13 01:33:37 +01:00
  • d346ae6a94 darashikoh 2025-08-08 20:32:34 +01:00
  • 39c0d6785c 1. Ultra-Low Latency Processing darashikoh 2025-08-08 11:05:06 +01:00
  • 926b6c195a darashikoh 2025-08-05 13:20:50 +01:00
  • 9f3303dbc2 Major Fixes Implemented: 1. Multi-Symbol Detection Fixed darashikoh 2025-08-04 22:50:57 +01:00
  • 2a617b1dab darashikoh 2025-08-01 11:25:48 +01:00
  • f14cb7649f Rename to v7.0 darashikoh 2025-08-01 11:25:16 +01:00
  • 9b1c52209b BRANCH ERMT v7 Enhanced Dashboard, MultiTrade Reporter, External Trade management M1-4 compile and debug darashikoh 2025-08-01 11:13:35 +01:00
  • 9afaf5efaf Summary I've provided you with a comprehensive solution for managing your commercial EA trades using the Risk Management Overlay EA, despite MT5's one-EA-per-chart limitation: 1. Complete Management Guide darashikoh 2025-08-01 10:56:06 +01:00
  • 56a1014695 Established enhanced dashboard and advanced reporting for external trades darashikoh 2025-07-31 19:52:26 +01:00
  • 82c958b8a4 ERMT_v6.6 darashikoh 2025-07-30 20:50:27 +01:00
  • 56209c4d63 Summary of Fixes The "Stop distance must be greater than 0" error is caused by a chain of issues in the ATR calculation. Here's what you need to do: 1. Replace the GetValidATR function in EntrySystem.mqh The original code had a recursive call bug. Replace the entire EntrySystem.mqh file with the fixed version I provided above. 2. Update the GetATR method in TechnicalAnalysis.mqh Replace the GetATR method with the fixed version that includes fallback calculations. 3. Update the AnalyzeMarket method in TechnicalAnalysis.mqh Replace the AnalyzeMarket method with the enhanced version that ensures volatility is always valid. 4. Update the main EA file (ERMT_6.0.mq5) Replace the CheckEntrySignals() and UpdateMarketConditions() functions with the enhanced versions that include debugging and validation. Key Changes Made: darashikoh 2025-07-30 19:33:01 +01:00
  • 44f028731b Summary The "Stop distance must be greater than 0" error was caused by: darashikoh 2025-07-30 18:55:56 +01:00
  • bd30cf417a The Problem: In MT5's Strategy Tester environment, file operations are restricted for security reasons. The backtest runs in a sandboxed environment where file creation/writing may be blocked or redirected to a different location. darashikoh 2025-07-30 14:26:35 +01:00
  • 3295dab1db Summary of Changes to Fix Zero Stop Distance Error The error "Invalid stop distance: 0.0" was occurring because the entry signals were being generated with invalid (zero) stop distances. This happened when the market volatility (ATR) value was 0 or not properly calculated. Key Changes Made (Version 6.5.1): darashikoh 2025-07-30 13:32:29 +01:00
  • 32998d8c9a What Was Wrong: darashikoh 2025-07-28 18:23:20 +01:00
  • a74c45d240 Summary of Fixes I've identified and fixed the lot size calculation issue. The problem was in the formula used to calculate lot size from risk amount. Here's what was wrong and how it's fixed: The Problem The original calculation was producing lot sizes that were off by a factor of 100,000 (e.g., 1,315,295 lots instead of ~13 lots). This was due to an incorrect formula that wasn't properly using the tick value and tick size. The Solution The corrected formula now: darashikoh 2025-07-23 23:46:39 +01:00
  • 3ae0f49654 The issue is in the lot size calculation in RiskManager.mqh. The calculation is producing an extremely large value (860,373 lots!) when it should be much smaller. darashikoh 2025-07-22 18:24:37 +01:00
  • 53c5b161e5 fix: resolve pointer syntax errors and missing return statements darashikoh 2025-07-22 18:11:53 +01:00
  • ffae6bf4ff Fix: Resolve backtesting trade execution issues Problem: EA was not opening trades during backtesting due to overly restrictive spread validation and position sizing calculation failures. Changes Made: 1. EntrySystem.mqh - Improved Signal Validation darashikoh 2025-07-22 17:33:44 +01:00
  • cd2696ae28 fix: resolve invalid pointer access error in EA initialization darashikoh 2025-07-22 17:07:29 +01:00
  • b801040daf Risk Management Overlay EA v6.0 - Code Review and Fix Guide Critical Issues Found 1. Main EA File (ERMT_6.0.mq5) Missing Definitions: darashikoh 2025-07-22 16:37:29 +01:00
  • 32705c5d61 1 - Backtest for 1.5 years EURUSD M5 - no trades initia; Critical error on exitlised 2- Compile and debug - Critical error on exit - OnDeinit 3- Fix for Entry System - Add to OnTick(): 4 - ENUM_TECHNICAL_LEVEL enum in DataTypes.mqh -> other Enums and structures DataTypes.mqh v3 The Complete DataTypes Module provides the robust foundation needed for your institutional-grade risk management system, offering better trade tracking, risk analysis, and technical integration capabilities essential for professional algorithmic trading. darashikoh 2025-07-20 22:38:24 +01:00
  • 644016f8e2 Moved ERMT_6.0, post first compile and debug to Advisors folder darashikoh 2025-07-20 19:23:58 +01:00
  • fb5ce9481d Added v2.0 in the header to reflect function change from Compile 1 Debug darashikoh 2025-07-20 17:37:34 +01:00
  • ac6089b898 Compile 1 Debug Position Selection in MQL5: Unlike MQL4, MQL5 doesn't have PositionSelectByIndex(). You must use: darashikoh 2025-07-20 17:22:58 +01:00
  • 7aaae3f1a1 ERMT modules v6.0 darashikoh 2025-07-20 17:02:39 +01:00
  • aebe367724 new files added darashikoh 2025-07-20 16:41:20 +01:00
  • 4ab54de5f6 new files added darashikoh 2025-07-08 23:34:12 +01:00
  • 5a3d4c4d30 Initial commit darashikoh 2025-06-09 08:52:01 +00:00