UTM: Troubleshooting Guide – Other – 31 August 2023

That is a part of the bigger  UTM Manager Guide – Other – 30 January 2023 – Traders’ Blogs (mql5.com)

In case you are experiencing any bugs or issues with the UTM Supervisor, please comply with the steps under to help the developer in troubleshooting the problem:

1. Allow Debugging Logs:

• Launch the the UTM Supervisor.
• Go to the “Settings”
• Within the Settings, allow “Debugging Logs” checkbox.

Be aware: Understand that debugging logs are disabled on every begin of the UTM, so you may have to repeat this step each time you launch UTM.

2. Clear Logs (Non-compulsory, for shorter logs):

   • Within the MT5, click on on the “Specialists” tab situated on the backside of the GUI.
   • Proper-click on the specialists tab and choose “Clear” to take away any present log entries.

3. Reproduce the Difficulty you had:

   • Carry out the actions within the UTM Supervisor that led to the issue or bug you’re experiencing.

4. Retrieve Log Information:

• After reproducing the problem, return to the “Specialists” tab.
• Proper-click on the specialists tab and choose “Open” to entry the file folder situated at “MQL5Logs”.
• A file explorer window will open, displaying the logs folder.
• Find the newest log information on this folder.

1. Contact the developer via the MQL5 market chat (from the vendor profile) for the product.
2. Ship a personal message to the developer.
3. Within the message, present an in depth description of the issue, together with the model of the supervisor you’re utilizing.
4. Connect the newest log information from the “MQL5Logs” folder to the message.

By following these steps, you’ll allow debugging logs, carry out actions to generate related logs, and ship the newest log information to the developer. This can assist them higher perceive and resolve the problem you’re dealing with.

To succeed in out to the developer:

1. Go to the product web page of the UTM Supervisor on the MQL5 market.
2. Click on on the vendor’s title. This can lead you to the vendor’s profile.
3. Right here, click on on the ‘Ship Message’ button to provoke a dialog with the developer.

When reporting a problem, guarantee to supply the next particulars:

• The model of the UTM Supervisor you are at the moment utilizing.
• The sequence of actions you undertook that led to the issue.
• Connect the newest log information, which may be discovered within the ‘MQL5Logs’ location. (Directions for accessing these information are offered above.)

This data will help the developer in understanding the problem higher and facilitating a swift decision.

Reset All Supervisor Settings

The Supervisor features a characteristic to “Reset all Supervisor settings” which may be helpful if the Supervisor is behaving unexpectedly or if the person needs to begin with a clear slate. To entry this characteristic, test the “Reset All Supervisor Settings on Shutdown” checkbox within the Supervisor settings. Be aware that each one different Supervisor cases should be closed earlier than this reset can take impact.

Why Does the Supervisor Seem to Danger Too A lot?

Downside Assertion

Newbie merchants usually are available in with the grievance: “My Lot measurement is simply too large, why did the supervisor calculate it incorrect?” At first look, it might look like the supervisor’s calculations are off, however the situation usually lies elsewhere. Particularly, the issue can come up as a consequence of small Cease Loss (SL) sizes being affected by slippage and unfold modifications, which the supervisor can’t predict.

Understanding the Difficulty

Cease Loss and Slippage

1. Cease Loss (SL): That is the value stage at which your commerce will mechanically shut to forestall additional losses.

2. Slippage: That is the distinction between the anticipated worth of a commerce and the value at which the commerce is executed. Slippage can happen throughout excessive volatility or low liquidity.

The Math Behind It

For instance the supervisor initially calculated a Cease Lack of 1.4 pips and accounted for a variety of 0.1 pips, making the whole SL measurement 1.5 pips. If slippage of 0.3 pips happens, the efficient SL turns into 1.8 pips.

The slippage of 0.3 pips on a 1.5 pip SL is a 20% improve. In case your preliminary threat was $50, the slippage would improve the danger to $60, which can be a 20% improve.

Why This Is Not the Supervisor’s Fault

1. Unpredictable Slippage: The supervisor has no option to predict slippage, which may occur as a consequence of market circumstances.

2. Unfold Fluctuations: Brokers can change the unfold at execution time, and the supervisor can’t account for this in real-time.

Options and Finest Practices

1. Use Bigger Cease Loss: For those who use a Cease Lack of 4 pips or extra, the impression of slippage will probably be much less vital.

2. Danger Administration: For those who insist on utilizing small SL sizes, then threat much less capital to account for potential slippage.

How one can learn ‘Commerce Closed’ from specialists tab.

• Preliminary Cease Loss (SL): The commerce was initially set with a Cease Lack of 1.4 pips.

• Unfold and Slippage: On the time of commerce execution, the unfold was 0.1 pips and slippage was 0.3 pips. These added to the unique SL, making the efficient SL 1.8 pips.

• Impression on Cease Loss: As a result of added unfold and slippage, the Cease Loss elevated by 20% (from the supervisor’s calculated 1.5 pips to the precise 1.8 pips).

• Monetary Impression: Initially, you have been risking $50 on this commerce. Nonetheless, the 20% improve in SL additionally led to a 20% improve in your monetary threat, bringing it to $60.

Why Does “Unfold Ignore” Mode Generally End in Sudden Danger Ranges in Pending Orders?

Downside Assertion

Within the context of the “Unfold Ignore” mode, merchants might discover that the danger on purchase orders can generally seem both too excessive or too low in comparison with the supposed threat stage. This discrepancy is just not a miscalculation by the supervisor however a results of how “Unfold Ignore” mode interacts with EMA Smoothed Spreads.

Understanding the Difficulty

EMA Smoothed Spreads in “Unfold Ignore” Mode

When utilizing “Unfold Ignore” mode for purchase positions, the supervisor employs EMA Smoothed Spreads to approximate the unfold prices on the time the commerce will probably be activated. This can be a forecast system designed to anticipate future unfold ranges.

Fluctuating Spreads

The EMA Smoothed Spreads are typically a great approximation however can generally be off, particularly throughout occasions of excessive market volatility or low liquidity. This will trigger the precise executed threat to deviate from the supposed threat stage.

Why This Is Not the Supervisor’s Fault

1. Unpredictable Spreads: Identical to slippage, spreads may be risky and unpredictable. The supervisor makes use of EMA Smoothed Spreads as a greatest guess however can’t assure accuracy.

2. Excessive Volatility: Throughout excessive volatility, spreads can widen considerably, inflicting the EMA Smoothed Spreads to be much less correct.

Options and Finest Practices

1. Modify EMA Smoothed Spreads: For those who discover constant discrepancies in threat ranges, think about adjusting the EMA Smoothed Spreads to raised align with precise market circumstances.

2. Danger Administration: Be ready for some stage of threat deviation when utilizing “Unfold Ignore” mode and modify your buying and selling technique accordingly.

Conclusion

Whereas “Unfold Ignore” mode affords a number of benefits, together with extra exact entry and exit factors, it is important to grasp that it will probably additionally introduce some stage of threat variability. Being conscious of this and adjusting your methods accordingly is vital to efficient threat administration.