Yasunao Koyama / Profil
- Information
2 Jahre
Erfahrung
|
4
Produkte
|
0
Demoversionen
|
0
Jobs
|
0
Signale
|
0
Abonnenten
|
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.25→1.26
new: As a configurable item for all versions, "Interval with S/L value at maximum ordering" (allowable loss width after maximum ordering) (point specification) was added to the upper limit of the number of duplicate creation stages. Even if there is enough surplus margin, duplicates with insufficient loss allowance will not be created from the beginning. The actual loss cut is performed at the lowest margin maintenance rate (Stop Loss Target) as before.
update: Supported overwriting of S/L value by "Trailing stop" function on the terminal side. The S/L value is not overwritten from the EA only when the S/L value is on the profit side from the profit and loss demarcation point.
update: The minimum waiting time until the start of the cancellation process of the copy destination order that has not started the transaction, which is performed after the copy source is settled / canceled, has been increased (3 sec → 15 sec). As a result, the problem that the generation of a new copy source, the accompanying generation of the copy destination, and the synchronization of the T/P value, etc. did not precede the deletion process was corrected.
update: If you change the "duplicate creation interval" or "lot size increase rate" in the paid version setting items while the duplicate has been created, the lot size will be changed only for the stage where the transaction has not started. The automatic deletion / regeneration of the stage is made to be performed, and the profit / loss demarcation point, T/P value, etc. are made to be consistent with the existing duplication that has already started trading.
bugfix: Fixed the problem that the T/P value may deviate from the copy source in rare cases depending on the price fluctuation situation. (Due to price fluctuations in the settlement currency and account currency pair). "All copy destinations for which transactions have started" do not allow deviations in the T/P value and S/L value from the copy source)
update: For duplicates that have already been created, as a result of changing the setting values, "reservations that exceed the upper limit of the number of duplicate creation stages and have not started transactions" are now deleted.
update: Added the process for the server that "S/L value / T/P value cannot be set when ordering". This ensures that once an error is detected, the S/L and T/P values will no longer be set at the time of ordering. In line with this, the timing was adjusted so that the set values would be updated as soon as possible after the order was placed.
bugfix: Fixed the problem that EA may terminate abnormally if the server is changed while EA is running.
bugfix: Fixed a small deviation in the calculation formula of the profit and loss demarcation point.
ver1.24→1.25
bugfix:Corrected the point that there was another error in the judgment condition for placing a market order for the "0th stage" that was re-corrected in ver1.24. (This should be okay, but we will continue to conduct operation tests.)
ver1.23→1.24
new: Added one setting item for all versions. This makes it possible to choose whether to maintain / delete / settle the existing duplicate or to create a new duplicate.
bugfix: The point that there was an error in the judgment condition for placing a market order for the "0th stage" corrected in ver1.23 was corrected again.
bugfix: Fixed an issue where the T/P value change as the stage progressed might not be done immediately after the stage progressed.
bugfix: Regarding the problem that the message "It is not an error, but the value has not been changed" (Error code: 1) may be returned when confirming the update of S / L value, T / P value, limit order amount. Corrected again.
update: In the setting item of the paid version, "Magnification when increasing lot size" used for each step of the duplication destination, it is now possible to handle other than integer multiples.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
Currently, we are checking whether it works stably and whether unnecessary error messages etc. appear.
We are also checking and fixing new features that will be enabled in the paid version.
The new features aren't a big deal, but I was wondering if it would make things a little easier. Use this feature only if you are not using another "Automatic Ordering EA". Therefore, make it possible to turn on / off.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.21→1.22
new: As a settable value in the paid version, "lot size of 0th stage" can be specified separately from "lot size of 1st stage and subsequent stages" (setting value of "multiplier of lot size" (LotSizeMultiplier) is "greater than 1", the 0th row is also affected)
update: In the display contents output to the terminal log, "estimated margin reserve ratio at the start of all stages" is now divided by "quantity of existing duplication sources".
bugfix: Normalized the number of digits displayed for "valid margin" in the display contents output to the terminal log.
update: "Predicted value of profit / loss demarcation point" (point display of currency pair of ticket) was added to the display contents output to the terminal log when the S/L value and T/P value is updated.
update: If the S/L value or T/P value is set in the "duplicate source created by another tool, etc.", the S/L value and T/P value of the "function to overwrite the set value of the copy destination" Changed to reflect separately.(Until now, when one of the values was set, even if the other was "no setting", it was overwritten with that "no setting")
bugfix: Fixed the problem that the variable for fee calculation was not initialized correctly in "Transfer of the copy source fee in deriving the profit and loss demarcation point" which is valid in the paid version. (Before the correction, there was a symptom that the T/P value became farther by the amount of the fee each time it was recalculated.)
bugfix: Corrected a sign error in "Transfer of copy source fee in deriving profit / loss demarcation point" which is effective in the paid version. Also, when the account currency is "JPY" and the fee is "directly proportional to the lot size", the point that the cumulative calculation was overestimated was corrected.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.20→1.21
Bugfix: Fixed the problem that "Problem of margin shortage in" Coexistence of multiple duplication sources "possible in paid version" implemented in ver1.20 was not applied to S/L value calculation.
bugfix: With the function of "Delete the copy destination with insufficient margin maintenance rate", the reserve requirement to be applied was separated as the one on the S/L set value side. In the previous version, before reaching the set S/L value, forced settlement will be applied with the reserve requirement ratio at the time of generation below the lower limit. As a result, the "lower limit at the time of ordering in all stages" is applied to the complementary generation of the copy destination, and the "lower limit of the S/L set value" is applied to the automatic deletion.
bugfix: Fixed the point that another fix was in the way and did not work with the function of "automatically delete the copy destination with insufficient margin maintenance rate" (simple test shortage. Due to the trigger of the copy source, This is because we have confirmed the operation in the actual market, not in the environment for demonstration, but it worked when the function was implemented. Sorry)
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
At the time of ver.1.00, it should have been a little as 2000 lines (it can be said that the making was rough at the beginning).
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.19→1.20
bugfix: Fixed the problem that "Orders that have not started trading" that remained after automatic settlement were not deleted depending on the timing, and a new copy was not created in some cases.
bugfix: Fixed an incorrect fee setting in "Free English Edition".
(If there is no fee for the copy source, there is no problem. "Is there a fee for the copy source?" Is prioritized over the set value. If the copy source ticket has a fee, The fee amount of the copy destination was calculated incorrectly. In the free version, it is originally fixed at 0)
update: As a provisional response, a fix was made to the "problem of margin shortage in'coexistence of multiple duplication sources', which is possible with the paid version".
As a response, "the set" lower limit of the margin reserve ratio "is multiplied by the number of duplication sources." At the moment, if the starting lot size of the duplication destination is the same, it seems that there will be no problem even if it becomes "start of all-stage transaction" (the number of stages to create a duplication is shared).
new: For some reason, if there is a "duplicate destination that has not started trading" with insufficient margin reserve ratio, it will be automatically deleted (this is a fundamental response to the case dealt with in 1.19). The "uncreated copy destination stage" where the margin is no longer insufficient has been dealt with by "complementary processing for missing copy destinations").
update: Enhanced the judgment regarding the detection of alternative tickets when "orders created by other tools, etc., which are the copy source" are settled or deleted.
bugfix: Fixed the problem that the request to the server for making a copy may be issued again to determine the copy source and make a request before the terminal recognizes the new ticket.
(Even if the request is accepted, there is a time lag until the terminal recognizes it. If the "cheaper copy source" is recognized before the terminal recognizes the requested copy destination, a new copy source is recognized. The duplication destination was sometimes created)
ver1.18→1.19
bugfix: Fixed the problem that new duplication by manual order was not sometimes done depending on the pricing.
update: When updating the contents of the copy destination, added "Limit price" to the contents that write the values before and after the update to the log (displayed only when there is a change). At the same time, the case where there was a description omission when using it in a language other than Japanese was also corrected.
bugfix: In "Complementary processing for missing duplicate destinations", a judgment process was added just in case a ticket was issued that was not restricted by the margin reserve ratio (not reproducible so far. Accidental phenomenon)
update: Added the currency unit to "Profit and Loss from Automatically Settled Duplication".
bugfix: Fixed the phenomenon that the setting of "Lower limit of margin reserve ratio at the start of all stages" is exceeded.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.17→1.18
update: Enabled to allow decimals in "Lot size increase rate after the number of fixed size stages" in "Paid version setting items".
bugfix: Since it was confirmed that there was a range of balance that interrupted the setting of "lower limit of margin reserve ratio at the start of all stages", the detection process was reviewed.
bugfix: Since it was confirmed that the judgment result may become unstable due to the change in the order status during the judgment process, the target matching for new creation, settlement, and deletion of duplicates was strengthened.
bugfix: When setting the S/T value and T/P value for the "order that is the copy source created by another tool, etc.", there was an omission in the judgment to reflect to the copy destination. Fixed.
bugdix: Fixed the problem that "after the order was accepted, the copy was sometimes generated again before it was reflected in the order list on the terminal side" when creating a new copy ("with other tools, etc." In rare cases, multiple duplication sources were allowed in the confirmation of the number of created "orders that are the duplication sources").
update: As a measure against delays when "automatic payment" and "new order" are mixed, the implementation timing of "deletion of duplicates that have not started transactions" has been changed. As a result, the execution of the confirmed "replication to be deleted" is always after the execution of "automatic settlement" and "new order and order reservation".
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
update:
update:Revised the output timing to the terminal log in "Complementary processing for missing replication destination".
bugfix: Fixed the problem that the output judgment of "Profit and loss due to automatically settled duplication" sometimes failed.
Bugfix: Fixed the problem that the description output to the terminal log was incorrect in the file output executed when the EA was terminated or the timeframe was changed (there is no problem with the file output itself).
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
new: When "automatic settlement of duplicate ticket" is performed other than "settlement by automatic setting of T/P value", "profit and loss due to automatic settlement of duplication" is output to the terminal log.
update: Changed to include the ticket number and comment description as much as possible in the output contents to the terminal log.
bugfix: Corrected the problem that the displayed message was incorrect when a retry loop occurred in the update process of the copy destination (the process itself works normally because of the problem only with the output contents to the terminal log).
update: In rare cases, the comment description of the copy destination was partially missing, so the check when generating the character string was strengthened.
bugfix: When the value of "2 or more" is set in "0th stage generation" in the setting item of the paid version only, the point that it was erroneously judged by the collation of the number of successful orders was corrected . The process itself works normally, only the to the terminal log output content is a problem. Adjusted the loop processing for new orders accordingly.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.12 → 1.14
new: Enable the function to complement the copy destination for "0th stage" (In addition to the market price, the order price is affected by the setting value of'AutoEntrySlippingMax'and the T/P value is affected by the setting value of'LimitEntryDisableWidth'. increase)
update: Even when the copy destination is complemented, the same "expected margin reserve ratio, etc." as when creating a new one is displayed.
bugfix: Fixed the problem that the required margin was overcalculated.
bugfix: Fixed the problem that the price difference detection in the market order sometimes failed.
update: Minor corrections to the description in the terminal log.
bugfix: Fixed the problem that the allowable width judgment of the automatic duplication creation "0th stage" was incorrect.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver1.10→1.12:
bugfix: Corrected the mistaken judgment that "the number of cases is abnormal" when there was an automatic closing target (there was a problem only in the log output. The process is performed normally)
bugfix: Fixed the problem that "duplicate source by other tools" was mistakenly excluded when the limit on the number of duplicate sources was enabled.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver 1.09→1.10 (for all edition)
update:The judgment readjustment of the copy destination complement function was carried out.
![Yasunao Koyama](https://c.mql5.com/avatar/avatar_na2.png)
ver 1.08→1.09 (for all edition)
update: Strict judgment of replication destination completion function.
bugfix: Fixed the problem that the "0th stage" quantity addition to the cumulative number of ordered lots was omitted.
bugfix: Fixed the point that the value was different between the accumulated number of ordered lots and the accumulated fee in the recalculation of the duplicated target value.
Update:ver1.53 (2023/08/16) ・ Overview and required environment Generate a duplicate limit order reservation for manual orders or orders from other tools, etc. This is specialized to "simplify the ordering operation". For the analysis to decide ordering, please do your best by yourself, such as fishing for materials, deriving a rule of thumb, using other analysis tools and EA together, etc. Since version 1.28, the function of "automatically re-order after settlement" has been implemented. (This
Update:ver1.53 (2023/08/16) ・ Overview and required environment Generate a duplicate limit order reservation for manual orders or orders from other tools, etc. This is specialized to "simplify the ordering operation". For the analysis to decide ordering, please do your best by yourself, such as fishing for materials, deriving a rule of thumb, using other analysis tools and EA together, etc. Since version 1.28, the function of "automatically re-order after settlement" has been implemented. (This
Update:ver1.53 (2023/08/16) ・ Overview and required environment Generate a duplicate limit order reservation for manual orders or orders from other tools, etc. This is specialized to "simplify the ordering operation". For the analysis to decide ordering, please do your best by yourself, such as fishing for materials, deriving a rule of thumb, using other analysis tools and EA together, etc. Since version 1.28, the function of "automatically re-order after settlement" has been implemented. (This
Update:ver1.53 (2023/08/16) ・概要と必要環境 手動発注もしくは他ツール等からの発注に対し、指値発注予約の複製を生成します。こちらは「発注操作の簡易化」に特化したものになります。発注判断となる分析は、資料を漁る、経験則を導く、他の分析ツールやEAを併用する等、利用者ご自身で頑張ってください。なお、ver1.28より、「決済後、自動で再発注する」機能が実装されました。(有償版でのみ有効化できます) ・導入と導入後の操作 導入そのものは簡単です。「自動売買可能なEA」として、適当なチャートにて動作させるだけです。(チャートの対象相場は問いません。このEAは、チャートを見ていません)。あとは、「このEAでのローカルコピー以外の発注」があれば、それに応じて「損失が出た場合に備えての追加取引の予約」という形で、指値発注が自動生成されます。
・ Overview and required environment Generates a duplicate of the limit order reservation for only one order, either a manual order or an order placed from another tool or service. For analysis that makes an order decision, please do your best by yourself, such as collecting materials, guiding rules of thumb, and using other analysis tools and EA together. ・ Installation and operation after installation Easy to deploy. As an "EA that can be bought and sold automatically", just operate it on an