Download and Change Log
Important Note: It is recommended you update to latest available PrimeXM MT5 Gateway Version to take advantage of significantly faster loading and reloading of the gateway configuration Parameters as well as faster loading times solving loading-related issues.
| Version | Release Date | Criticality | From XCore Version | From MT5 Version | Download | Changes |
|---|---|---|---|---|---|---|
| v2.3.2.2 | - | Medium | 6.05.52 | 5830 | Download | - Added CmdSymbol messages for symbol data exchange.- Removed contractsize from order request messages.- Added optional DuplicateOrderWindow parameter (1–5000 ms) to reject duplicate market orders submitted by an EA while the original request is still being processed. If absent, the protection is disabled.- Increased the Manager connection timeout to 30 seconds. Added MgrConnectTimeout to adjust it (1000–60000 ms).- Removed user not found warning on balance operations. |
| v2.3.0.1 | 2026/08/24 | Medium | 6.05.22 | 5830 | Download | - Added logging when MT5 Gateway parameter items have no match. |
| v2.3.0.0 | 2026/07/04 | High | 6.05.22 | 5830 | Download | - Fixed memory issues during the reuse of order execution operations. - Added SendBufferSize and RecvBufferSize configuration parameters (in KB), default value = 256 |
| v2.2.0.7 | 2026/05/17 | Medium | 6.05.22 | 5830 | Download | - Rebuilt with the new MT5 libraries (version 5830). - Manager DLLs are now embedded in the gateway executable (no separate MT5APIManager64.dll download required). |
| v2.2.0.5 | 2026/04/25 | Medium | 6.05.00 | 5770 | Download MT5APIManager64.dll(Build 5770) |
- Added PartyID to SubID3 in the format "mt5_login-mt5_partyId". - Added module_id to executions. |
| v2.2.0.4 | 2026/04/25 | Medium | 6.03.04 | 5120 | Download MT5APIManager64.dll |
- Tweaks around memory usage. - Added coverage retry if result = MT_RET_REQUEST_PRICE_OFF (10021). - Fixed issue where error.dat was cleared if new errors arrived after restart. |
| v2.2.0.1 | 2026/03/12 | Medium | 6.01.83 | 5120 | Download MT5APIManager64.dll |
- Added MT5 Coverage Sync. - Real-time synchronization of deposits, withdrawals, credits, and end-of-day (EOD) reconciliation via Manager API. - Improve nio/ByteBuffer handling |
| v2.0.6.3 | 2025/11/21 | Medium | 6.01.56 | 5120 | - Fixed a condition where a close followed by a stop-loss in MT5 resulted in duplicate XCore executions and MT5 booking failures. | |
| v2.0.6.2 | 2025/11/06 | Medium | 6.01.56 | 5120 | - Added account color to order requests for routing alongside other parameters in ConnectorRoute | |
| v2.0.6.1 | 2025/07/10 | High | 6.01.28 | 5120 | - Rebuilt with the new MT5 libraries (version 5120). - Fixed synchronization issue for symbols and groups after startup. - Added a 5-second verification delay to ensure groups and symbols are loaded properly. |
|
| v2.0.5.4 | 2025/04/20 | Medium | 6.01.28 | 4410 | - Fixed an issue where replayed orders displayed incorrect timestamps due to timezone differences between the local machine and the MT5 server. Only compatible with XCore versions >= 6.01.28 | |
| v2.0.5.3 | 2025/02/19 | Medium | 5.77.23 | 4410 | - Fixed issue with MT5 position id not being sent to XCore | |
| v2.0.5.2 | 2025/02/05 | Medium | 5.77.23 | 4410 | - Fixed an issue where an order request was incorrectly rejected during partial close execution. | |
| v2.0.5.1 | 2025/01/22 | High | 5.77.23 | 4410 | - And yet another fix for closeby. | |
| v2.0.5.0 | 2025/01/14 | High | 5.77.23 | 4410 | - Fixed further issues with closeby. | |
| v2.0.4.9 | 2024/12/18 | High | 5.77.23 | 4410 | - Fixes an issue where in hedging mode a client could close positions which are already under execution by executing a closeby. | |
| v2.0.4.8 | 2024/10/30 | High | 5.77.23 | 4410 | - Fixes an issue where Volume on Coverage orders, could potentially be rounded down to 0. | |
| v2.0.4.7 | 2024/10/24 | Low | 5.77.23 | 4410 | - Maintenance release which includes DealerLock logs and enhanced logging helping to trouble shoot any performance issues. | |
| v2.0.4.6 | 2024/10/06 | High | 5.77.23 | 4410 | - Fixes an issue where “route not found” rejection messages might appear right after an MT5 Server Restart. | |
| v2.0.4.5 | 2024/09/04 | High | 5.77.23 | 4410 | - IMPORTANT: - The Gateway prevents any cases where the fill size exceeds the requested order size on MT5. While this scenario should not occur, it is safeguarded to avoid booking failures. - Order sizes are rounded to the configured MT5 step_size. Users can disable the rounding behavior by defining the following special MT5 Gateway parameter settings- DISABLE_ORDER_ROUNDING - DISABLE_COVERAGE_ROUNDING - Orders are no longer rounded up to the MT5 minimum size if they fall below the configured min_size.- Coverage orders are no longer restricted by the MT5 max_size limit. |
|
| V2.0.4.4 | 2024/08/20 | Medium | 5.77.04 | 4410 | Added delay of 5 seconds for coverage after the gateway is enabled | |
| V2.0.4.3 | 2024/07/21 | Medium | 5.75.98 | 4410 | Fixed issue with market orders passing reference price including MT5 group markups | |
| V2.0.4.2 | 2024/04/20 | High | 5.75.98 | 4260 | - Fixed issue where order.fillVolume could exceed order.volume for specific configurations. - Fixed the problem with order.init creating message objects that surpass the maximum string length. |
|
| v2.0.4.1 | 2024/04/16 | High | 5.75.98 | 4260 | - Fixed issue with regex patterns for symbol settings at the group level. | |
| v2.0.4.0 | 2024/04/02 | High | 5.75.98 | 4260 | - Added ExecErrorTimeout parameter. - Added replay feature. - Added support for symbol settings at the group level. - Fixed issue with ByteBuffer overflow. |
|
| v2.0.3.2 | 2024/02/26 | Medium | 5.75.94 | - Added support for leg based giveup. - Fixed coverage price rounding issue |
||
| v2.0.3.1 | 2024/02/16 | Medium | 5.75.80 | - Fixed issue with symbol routes based on full symbol path | ||
| v2.0.3.0 | 2024/01/31 | High | 5.75.80 | - Resolved Rounding Overfill Issue: Addressed a critical issue where rounding errors could lead to overfill and consequently prevent trade bookings. - Enhanced ROUNDING DISCREPANCY Warning: Updated the warning message for rounding discrepancies to include ‘size’ and ‘contract_size’ information. |
||
| v2.0.2.9 | 2024/01/10 | Medium | 5.75.80 | - Enhanced the ‘ROUNDING DISCREPANCY’ warning message to include both orderID and symbol. | ||
| v2.0.2.8 | 2023/12/27 | Medium | 5.75.80 | - Fixed an issue where Stop Losses (SLs) were not selecting the correct execution rule. - Added log alerts to flag rounding issues when MT5 symbol step sizes are incompatible with executed XCore fill sizes. - Enhanced logging capabilities for changes in symbol configurations. |
||
| v2.0.2.7 | 2023/12/15 | Low | - Added lock parameter. | |||
| v2.0.2.6 | 2023/11/26 | High | - Fixed issue with route not found when adding groups and symbols dynamically without gateway refresh | |||
| v.2.0.2.5 | 2023/10/15 | Medium | Added rounding for sizes and prices reported into MT5 | |||
| v.2.0.2.4 | 2023/09/13 | Low | Improvements in coverage logic | |||
| v2.0.2.3 | 2023/07/27 | Low | - Fixed issue with Gateway Start. | |||
| v2.0.2.2 | 2023/07/25 | Low | - Minor Bug Fixes. | |||
| v2.0.2.1 | 2023/06/15 | Medium | - Fixed a rare issue that under conditions of poor network connectivity, the Gateway might have been unable to re-establish connection to the XCore for several minutes. | |||
| v2.0.1.0 | 2022/08/14 | Low | - Fixed issues with error trigger on MT5 Symbol level. | |||
| v2.0.0.9 | 2022/08/05 | Low | - Improved compatibility with external plugin | |||
| v2.0.0.7 | 2022/06/22 | Low | - Minor cosmetics log improvements | |||
| v2.0.0.6 | 2022/05/27 | High | - 1. The Scaling Factor functionality is removed. - 2. There are important syntax changes to the MT5 Gateway Parameter configuration. - Specifically in the MT5 Gateway v.2.x Parameters: - sec: Supports comma-separated “,” list of symbol paths. Masks allowed are “*” or masks that end with “\*” - sym: Supports comma-separated “,” list of symbols. Masks allowed cannot be “*” and cannot end with “\*” - login: Supports comma-separated “,” list of logins. - group: Supports comma-separated “,” list of groups - Very Important Note: In MT5 Gateway v.1.x the above Parameter syntax conditions did not exist - PrimeXM Gateway routing rules are used to route trade requests from MT5 to XCore following the below logic: - 1. Find and use the last matching routing rule by client login and symbol. If no such rule exists: - 2. Find and use the last matching routing rule by client login and security. If no such rule exists: - 3. Find and use the last matching routing rule by group and symbol. If no such rule exists: - 4. Find and use the last matching routing rule by group and security, If no such rule exists then there is no match. |