I am looking for an EXPERIENCED professional programmer to redo (or finish) my EA. The current EA is working fine ……. until the connection to the server is lost or timed out, etc. etc. (One time I lost 50% of my capital overnight (luckily in demo) due to a bug creating an excessive number of 'open orders' 'owned' by the EA, both active and pending.)
So the main job is not to create the logic, although you may decide that you need to redo it for one reason or another, the main job is to create a RELIABLE code under real life execution, in other words, code with proper ERROR HANDLING for anything that can come up during unattended live trading.
The code is a Martingale type logic with a simple random entry (for the purpose of this test), so it is fairly straight forward therefore I don’t expect it to be a problem for you. The challenge starts when we get to the testing phase.
Here is my test plan:
First we test the core logic, just to make sure, the program doesn’t have basic logic errors.
Then we test the program for 120 unattended trades (about 2 weeks). The program has to handle the various trade disruptions successfully before I declare success. I.e., it can’t loose the place in the logic, it has to recover gracefully from timeout, weekend re-restart, etc. etc.
We will test it together, and each time there is an error (like in the examples below), I will give you a similar feedback:
2009.08.07 07:12:31 YYYYExit EURUSD,H1: Pending sell failed
2009.08.07 07:12:31 YYYYExit EURUSD,H1: last error: 128:trade timeout
2009.08.07 07:12:31 YYYYExit EURUSD,H1: failed trade: OP_SELLSTOP [email protected] [email protected] [email protected]
2009.08.07 07:12:31 YYYYExit EURUSD,H1: failed to execute stop or limit order after 1 retries
2009.08.07 07:12:31 YYYYExit EURUSD,H1: non-retryable error: 128:trade timeout
2009.08.07 07:09:44 YYYYExit EURUSD,H1: retryable error (1/10): 6:no connection with trade server
2009.08.07 07:09:44 stdlib EURUSD,H1: loaded successfully
2009.08.07 07:07:36 YYYYExit EURUSD,H1: attempted OP_SELLSTOP 2.70000000 lots @1.42570000 sl:1.42670000 tp:1.42070000
Or like this:
2009.08.07 10:04:44 YYYYExit EURUSD,H1: Pending sell failed
2009.08.07 10:04:44 YYYYExit EURUSD,H1: last error: 130:invalid stops
2009.08.07 10:04:44 YYYYExit EURUSD,H1: failed trade: OP_SELLSTOP [email protected] [email protected] [email protected]
2009.08.07 10:04:44 YYYYExit EURUSD,H1: failed to execute stop or limit order after 0 retries
2009.08.07 10:04:44 YYYYExit EURUSD,H1: non-retryable error: 130:invalid stops
2009.08.07 10:04:44 stdlib EURUSD,H1: loaded successfully
2009.08.07 10:03:38 XXXXEntry EURUSD,H1: open #14911354 buy 0.10 EURUSD at 1.4187
So once you understand the program, we need to go through the MQL4 trade execution errors and tell me my options then decide how to handle them before you code it.
I hope, you are already familiar how to manage existing orders by keeping track of the *ticket number* from the server, you are already familiar with LibOrderReliable_V1_1_4.mq4 and OrdersSuite.mq4 and similar attempts to handle errors in a systematic way.
As far as payment, I hope we can agree on something mutually acceptable.
One more thing: you will only program a nontradable code used for the SPECIFIC purpose of proving the error handling.
If you interested, please contact me.
Thanks, explorer
So the main job is not to create the logic, although you may decide that you need to redo it for one reason or another, the main job is to create a RELIABLE code under real life execution, in other words, code with proper ERROR HANDLING for anything that can come up during unattended live trading.
The code is a Martingale type logic with a simple random entry (for the purpose of this test), so it is fairly straight forward therefore I don’t expect it to be a problem for you. The challenge starts when we get to the testing phase.
Here is my test plan:
First we test the core logic, just to make sure, the program doesn’t have basic logic errors.
Then we test the program for 120 unattended trades (about 2 weeks). The program has to handle the various trade disruptions successfully before I declare success. I.e., it can’t loose the place in the logic, it has to recover gracefully from timeout, weekend re-restart, etc. etc.
We will test it together, and each time there is an error (like in the examples below), I will give you a similar feedback:
2009.08.07 07:12:31 YYYYExit EURUSD,H1: Pending sell failed
2009.08.07 07:12:31 YYYYExit EURUSD,H1: last error: 128:trade timeout
2009.08.07 07:12:31 YYYYExit EURUSD,H1: failed trade: OP_SELLSTOP [email protected] [email protected] [email protected]
2009.08.07 07:12:31 YYYYExit EURUSD,H1: failed to execute stop or limit order after 1 retries
2009.08.07 07:12:31 YYYYExit EURUSD,H1: non-retryable error: 128:trade timeout
2009.08.07 07:09:44 YYYYExit EURUSD,H1: retryable error (1/10): 6:no connection with trade server
2009.08.07 07:09:44 stdlib EURUSD,H1: loaded successfully
2009.08.07 07:07:36 YYYYExit EURUSD,H1: attempted OP_SELLSTOP 2.70000000 lots @1.42570000 sl:1.42670000 tp:1.42070000
Or like this:
2009.08.07 10:04:44 YYYYExit EURUSD,H1: Pending sell failed
2009.08.07 10:04:44 YYYYExit EURUSD,H1: last error: 130:invalid stops
2009.08.07 10:04:44 YYYYExit EURUSD,H1: failed trade: OP_SELLSTOP [email protected] [email protected] [email protected]
2009.08.07 10:04:44 YYYYExit EURUSD,H1: failed to execute stop or limit order after 0 retries
2009.08.07 10:04:44 YYYYExit EURUSD,H1: non-retryable error: 130:invalid stops
2009.08.07 10:04:44 stdlib EURUSD,H1: loaded successfully
2009.08.07 10:03:38 XXXXEntry EURUSD,H1: open #14911354 buy 0.10 EURUSD at 1.4187
So once you understand the program, we need to go through the MQL4 trade execution errors and tell me my options then decide how to handle them before you code it.
I hope, you are already familiar how to manage existing orders by keeping track of the *ticket number* from the server, you are already familiar with LibOrderReliable_V1_1_4.mq4 and OrdersSuite.mq4 and similar attempts to handle errors in a systematic way.
As far as payment, I hope we can agree on something mutually acceptable.
One more thing: you will only program a nontradable code used for the SPECIFIC purpose of proving the error handling.
If you interested, please contact me.
Thanks, explorer