C7 Channel Breaks, PAM bots, 2222scalpers (2xRisk)
Lietotājs ir dzēsis šo sistēmu.
Diskusija
Feb 05, 2015 at 21:44
449 Views
5 Replies
Biedrs kopš
33 ieraksti
Feb 06, 2015 at 13:09
This bot uses advanced channel detection capabilities to determine and adapt. It will determine the probability and extent of the breakout and will adapt to it. This bot operates on only stop order entries and is not a scalper so delays won't matter at all. This bot can use strategically trailed stop-losses as many successful traders do. This bot is currently set to trade risking up to about 6% of equity on each position and up to 4 positions on a single pair (quite rare and with diversified stops and tp)
C7 bot is available in the market:
https://www.mql5.com/en/market/product/2733 -mt5
https://www.mql5.com/en/market/product/2753 -mt4
C7 bot is available in the market:
https://www.mql5.com/en/market/product/2733 -mt5
https://www.mql5.com/en/market/product/2753 -mt4
Biedrs kopš
33 ieraksti
Mar 19, 2015 at 11:39
Two pending orders today with 'market closed' errors from broker that would have been triggered. Still haven't heard back from tickmill support. The trades were taken fine in the PAM bot account though (which is also on tickmill and also on the same vps with the same ea...):
https://www.myfxbook.com/members/bendex77/shmendridge-pam-real/1191303
tickets 28671597 and 28671599 on the Shmendridge-Pam-Real account that should've been mirrored on this account....
https://www.myfxbook.com/members/bendex77/shmendridge-pam-real/1191303
tickets 28671597 and 28671599 on the Shmendridge-Pam-Real account that should've been mirrored on this account....
Biedrs kopš
33 ieraksti
Mar 25, 2015 at 00:03
(labots Mar 25, 2015 at 00:05)
According to Tickmill support, this turned out to be my ea placing an order right at the 'moment of swap calculation' so I have added error checking for this now.
Biedrs kopš
33 ieraksti
Mar 25, 2015 at 00:23
I suppose I should also post here, as per the new title of this system. PAM bots have all been added to this account earlier this month as well as the C7. The PAM Carrot is right here and it's free:
https://www.mql5.com/en/market/product/8052
https://www.mql5.com/en/market/product/7942
https://www.mql5.com/en/market/product/8052
https://www.mql5.com/en/market/product/7942
Biedrs kopš
33 ieraksti
Apr 04, 2015 at 19:45
29298736- Massive Slippage during low liquidity period. (C7 trade) The spread widened to 9 pips, but not quite enough to trigger the low liquidity safety off (10 pips). Most C7 owners did not get hit by this trade as the spread of other brokers widened more which triggered their safety off. The setting of this safety measure has been adjusted to 5 pips as well as a secondary measure coded in to the C7 engine which will react swiftly against any spread volatility regardless of whether its a new bar or not.
I will not open a new account for the C7 systems as I feel that would be dishonest.
I will not open a new account for the C7 systems as I feel that would be dishonest.
Biedrs kopš
33 ieraksti
Apr 07, 2015 at 14:05
Well, some of the slippage was refunded by Tickmill. Too bad the correction must appear as a deposit in to the account instead of correcting the equity gains/losses of the account.
'We totally understand your concern regarding USD/JPY slippage. Being an STP broker we just clear our client's trades and re-translate quotes we get from Citi and other liquidity providers. Orders on the real market are always executed by current market prices, that's why slippage may occur during sharp movements.
Friday 03.04.15 was a holiday, the liquidity on that day was on the extremely low level and due to that fact the spreads were extremely wide as same as the volatility. The widest spreads were right before and some time after the news release.
We have investigated your order 29298735, due to the high volatility it was closed with negative slippage at 119,759 at actual market price.
We also have investigated your second order 29427758, it was opened with negative slippage, but was closed with positive slippage for T/P.
For this second order we decided to compensate You the negative slippage during the opening of the trade in amount 90,08 USD You will see that on your balance account with the comment Corr: Refund AM'
'We totally understand your concern regarding USD/JPY slippage. Being an STP broker we just clear our client's trades and re-translate quotes we get from Citi and other liquidity providers. Orders on the real market are always executed by current market prices, that's why slippage may occur during sharp movements.
Friday 03.04.15 was a holiday, the liquidity on that day was on the extremely low level and due to that fact the spreads were extremely wide as same as the volatility. The widest spreads were right before and some time after the news release.
We have investigated your order 29298735, due to the high volatility it was closed with negative slippage at 119,759 at actual market price.
We also have investigated your second order 29427758, it was opened with negative slippage, but was closed with positive slippage for T/P.
For this second order we decided to compensate You the negative slippage during the opening of the trade in amount 90,08 USD You will see that on your balance account with the comment Corr: Refund AM'
*Spams netiks pieļauts, un tā rezultātā var slēgt kontu.
Tip: Posting an image/youtube url will automatically embed it in your post!
Tip: Type the @ sign to auto complete a username participating in this discussion.
