Quote:
|
Originally Posted by JB_007
I have attached a text file showing the journal log for phoenix 6 simple beta 4 journal. I am aware that settings haven't been finalized yet so the trades did not go that well.
The reason I am attaching this file is because I noticed a few of errors (Invalid S/L or T/P) in the log that may be bugs/errors.
Please ignore this file if the errors are caused by something outside Phoenix.
I will upgrade to beta 5 now and update everyone.
|
I checked through the log and found that after several minutes of delay, the order was resent with the same settings and succeeded. I'm guessing this means we have a tight stop that is chasing at the minimum distance. In between receiving the new price and the order submission, the price changed and the new price caused the trade to be inside the minimum settings allowed. This is completely normal, and higher latency with the broker will cause it to happen more often.
I checked 4 live account journals and did not see a single instance of this happening. If you see that error and then the trade closes on stop loss, your latency just cost you at least 1 pip. That's why I'm running the hosting service, I had high latency at home with DSL. A dialup user did a test and found that his orders were often 90 seconds later than mine on the server.
4 currencies loaded, 1 account = $20/month for basic service. I won't accept new clients if the machine slows down at all. 4 files and a paypal payment to get started.