Topics
Replies
maxim_7
18 Oct 2016, 08:22
RE:
Spotware said:
Hi,
Please try again and let us know if you still experience any issue. It seems you wrote this post at the weekend and it could be possible our services were temporarily unavailable when you were trying to connect. We usually reserve the weekend for performing maintenance.
Let us know.
Regards,
cTrader Team
HI cTrader Team,
The same result also during weekdays.
Can you confirm from your side what FIX API is OK, thru proxy?
Thanx
M.
@maxim_7
maxim_7
18 Oct 2016, 00:00
RE:
Spotware said:
Hello,
...4) The position which is most unprofitable will be partially closed.
For the benefit of other people reading this thread; here is the page we are discussing = http://help.spotware.com/trading/smart-stop-out
Hi Support,
I am not comfortable with 4), I do not understand how closing of "most unprofitable" will help to maintain Margin Level above Stop Out.
If I have 2 positions Long and Short with equal volumes, and price goes down. (Let say Long stay unprofitable and Short became profitable) In this case, "most unprofitable" became Long position, isn't it?
According to your explanation server will partially close Long position, BUT this action will do nothing: “Equity” will not be changed. Margin Level = “Equity” /"Margin Used", "Margin Used" will not be affected since Server closes only side of two positions, thus Margin Level remain below Stop Out.
I predict the next step of server: On next tick server will close, some more from Long position, w/o affecting Margin Used - and gradually will close Long position totally.
Therefore, my question is: Could you please explain background of "Smart Stop Out" algorithm. Obviously I am missing something here and cannot understand where "Smart" is?
Thanx
M.
@maxim_7
maxim_7
15 Oct 2016, 02:24
RE: RE: RE: RE:
david-connect-api said:
And adding tag 265=1 to MsgType(35)=V even though the ctrader's rules of engagement says it is not necessary? I am using quickfix/j and it is working for me, i can subscribe for data request (the server responds with MsgType(35)=W, not with MsgType(35)=X but it works). I can't think in anything else...
Today spotware added SSL transport support and I've tried second request with Real account and got response from server.
So believe issue exists only on Demo server.
It is good enough for me, Thanx for help.
M.
@maxim_7
maxim_7
15 Oct 2016, 00:40
RE: RE:
david-connect-api said:
I had the same problem which I resolved adding tag 50=QUOTE to the header of the Logon message that starts the session for which you are requesting market data. Also check the ports you are using, since sessions for quoting and trading have different ports.
Thanx for attempt to help. But I already using tag 50=QUOTE to the header of the Logon message, and also tried both ports. On both ports the same result.
@maxim_7
maxim_7
28 Oct 2015, 16:47
RE: RE:
Do not worry, it is not relevant anymore
maxim_7 said:
Thanx for response.
If so, (plan to add one more property to position) is it possible add one more property Color of position line. - For Robot Label (Comment) for User different color of grouped positions.
M.
hhi sir which type of spy|protect method u want to use?
@maxim_7
maxim_7
22 Dec 2014, 14:46
( Updated at: 21 Dec 2023, 09:20 )
RE:
Spotware said:
Click take profit 1 , select the amount of pips of your take profit and the volume it will close
Click take profit 2 , select the amount of pips of your take profit and the volume it will close etc
You can check out this video for more information
http://youtu.be/v9rUd53B260
Looks like this feature is not working correctly,
Setup:
Long position of 70K
3 TP positions on 3 pips (20K)+6 pips (20K)+8pips(30K)
After hitting first target, Client stops working and removes TP lines from screen. Nothing happens on hitting next target.
----->> 
In this way I can loss money, if marked reverses instead of taking profit.
Please fix
@maxim_7
maxim_7
10 Dec 2014, 18:37
RE:
Minimal robot to reproduce issue
using cAlgo.API;
using cAlgo.Indicators;
namespace cAlgo.Robots
{
[Robot()]
public class R : Robot
{
protected override void OnStart()
{
Indicators.GetIndicator<SampleAlligator>(MarketData.GetSeries(TimeFrame.Minute5), 13, 8, 8, 5, 5, 3);
MarketData.GetMarketDepth(Symbol);
}
}
}
If lunched on TimeFrame != 5 Minutes
Please help.
@maxim_7
maxim_7
09 Dec 2014, 11:42
RE:
Spotware said:
Dear Trader,
Thank you for your suggestion, we will consider it.
Hi Spotware,
This is not only suggestion for algorithm, this also request to fix Client SW.
With previous algorithm I was able to sort my positions by Gross/Net profit and select next victim for server closure in case of Stop-out event.
But with new algorithm there is no exact way to know which position will be closed:
Just an example:
X-K Long position as price P1 + Y-K Short position at price P2 - which position will be closed by server??????
So, I think, it is huge failure of this update - provide change for server and totally ignore Client SW.
Current Client SW shows only total Margin and not per position.
Please provide fix for Client cAlgo/cTrader.
Thanx for understanding.
@maxim_7
maxim_7
05 Dec 2014, 12:35
RE:
Grate intent, but I have one very simple example where new algorithm cause loss of entire account just in few pips price move
One position X-K Long at price P1
Two positions X + X-K Short at price P2.
P1 > P2
Marked goes up and reaches ~30% margin level. According to new algorithm server closes Long position (higher margin requirement) instead of X-K short as in previous - market goes up for few pips and all account lost. In previous algorithm I will loss only one short position.
This is a real example from both real and demo accounts.
Retested it on demo account to understand it better and as I see this algorithm have huge disadvantage comparing to previous one.
Please comment.
Maxim
@maxim_7
maxim_7
05 Dec 2014, 11:23
Since October, new Stop-out position closure algorithm was introduced by my provider.
In new algorithm if Margin Level ~30% server begins close positions starting with position with higher margin requiremnt.
Because I did not succeed to get distinct answer from my provider I am asking it here.
So my question is: what is the background for changing this algorithms from previous where server closes most unprofitable one.
Thanx
Maxim
@maxim_7
maxim_7
04 Dec 2014, 09:11
RE: RE: RE:
AlexanderRC said:
As a workaround, a cBot can balance the Long/Short position count by immediately closing a position of the opposite direction. It should be pretty trivial to write one.
Except one thing: Server side will serve all cases cBot only specific client.
@maxim_7
maxim_7
02 Dec 2014, 18:12
RE:
Spotware said:
The most losing position will be closed in that case.
Exactly, this is the problem. From my point of view, this behavior is wrong. and MUST be changed, to close opposite positoin to preserve account in balanced state (X Volumes Long and X Volumes Short), instead of closure one by one all positions of one direction.
@maxim_7
maxim_7
16 Jul 2013, 17:01
RE:
It is continent way to group positions.
With cAlgo I can run robot what spy/protect open positions.
cAlgo may run robot on one host but I can open and close positions on other host.
Using same label value for position/order I can signal to robot to join/group two positions or position and order in pair and behave correspondently.
M.
@maxim_7
maxim_7
24 Oct 2016, 17:20
Hi Support,
The problem looks more serious. If connection dropped brutally, (modem/router power loss/…) Client cannot reconnect to FIX server for 1-2 min.
Could you provide your comments, please?
Thanx
M.
@maxim_7