Topic: Error reading from pipe - detailed logs

Hi Mr Popov.
I`m sending full logs from FST & MT4 (Oanda - test).
The issue as in topic, resulting in losing the open transactions.

Steps to reproduce:
- I`m testing 10 systems on single machine, each on 2 curr: EURUSD & GBPUSD.
- each system has separate connection ID (running from batch file)

Losing transaction tracking was visible on 30.07.
Hope it helps to track the issue.

Re: Error reading from pipe - detailed logs

I`m testing 10 systems on single machine, each on 2 curr: EURUSD & GBPUSD.

Does it means that you have 5 strategies running on EURUSD and 5 strategies running on GBPUSD?

I think it may fail regarding FIFO even if you use different ConnectionID or MagicNumbers.

Re: Error reading from pipe - detailed logs

I want to confirm that trading one symbol on different charts may leads to:
Error in FST Request OrderSend: Opening of an opposite position (hedging) is disabled

FST separates the positions according to their Symbol and MagicNumber. This behaviour allows you to run different strategies on one symbol. It may happen one strategy to open short position and other to wants opening long at the same time. This operation is legal for FST but brokers that doesn't allow hedging will rise an error.

...

Reading from Pipe errors in the log files must be caused by lack of resources of the executing machine.

4 (edited by acerguest 2012-08-01 08:21:04)

Re: Error reading from pipe - detailed logs

Sorry I may not been clear.
It looks like that: 20 FST connected to 10 MT4, each MT4 has 2 chars opened EUR & GBP.
Each FST is using different ConnectionID, additionally I`m always setting unique MagicNumber on each expert.

Machine:
Core 2 Duo (2.8 GHz) ,  4GB Ram, Windows 7
(and it`s used only for trading)

--
Reading from Pipe errors in the log files must be caused by lack of resources of the executing machine.
--
I disagree here, but can`t prove it. I was seeing pipe errors before, even when not running that many systems, but than I was thinking it`s harmless.
But I will cut the running systems by half, and check than.

Would 'pipe errors' can explain situation that FST is loosing track of opened position?

Re: Error reading from pipe - detailed logs

Would 'pipe errors' can explain situation that FST is loosing track of opened position?

Completely.
FST receives positions and account status with the ticks coming from MT4.

We see ticks (TI) info transfer errors in the log file:

18.07.2012 01:04:25 Exception: Error reading from pipe! ErrorCode: 233 Command: 'TI GBPUSD 1 1342551883 1.56492 1.56512 20 0.81389 1342551840 1.56489 1.56492 1.56489 1.56492 2 1342550760 2802.82 2786.39 -16.43 2735.53 39386226 1 0.02 1.55503 1342179299 1.57224 1.54824 -16.43 fxTrade_Practice_#1775752747 cl=0;aSL=0.00000000;aTP=0.00000000;al=0.00000000'

I'm not sure what affects the performance of Named Pipes. I'm running up to 6 strategies normally and never have such problems.

Re: Error reading from pipe - detailed logs

I see something very strange in log files:

First in FST logs we see that FST closes last position:

2012.07.29 22:40:11, EURUSD M1 Position closed at 1.23014, Closed Lots 0.16
2012.07.29 22:40:11, EURUSD M1 Square

After that FST tries to enter short, but receives Hedging error!

http://i.imgur.com/CsBEY.png

FST doesn't open short position. Who did open it?

This info is confirmed form Expert logs:

http://i.imgur.com/cYxhL.png

Are you sure you use unique ID numbers? (Probably yes, because I don't see conflicts in logs. )

Can you send me also Expert logs. See here in the bottom of the page: http://forexsb.com/wiki/fst/manual/expert_options

Re: Error reading from pipe - detailed logs

Sorry Mr Popov, I was pretty sure that I attached every possible logs that I could.
And as I reduced the number of running systems yesterday, I decided to remove everything and start fresh. Have started only 5 systems, and already spotted pipes errors in logs :[

As soon as I will notice a issue, I will send you logs.

8 (edited by acerguest 2012-08-02 22:48:44)

Re: Error reading from pipe - detailed logs

Ok, found it on second PC.
Position was opened on 18, and lost on 22 (over the weekend issue?)

Hope now this are complete logs.