PanagiotisCharalampous
04 Feb 2019, 10:26

Hi cysecsbin.01,

Can you share the cBot with us so that we can reproduce? Also please let us know the cBot parameters you are optimizing.

Best Regards,

Panagiotis

PanagiotisCharalampous
04 Feb 2019, 10:22

Hi shrumr,

At the moment this is not possible.

Best Regards,

Panagiotis

PanagiotisCharalampous
04 Feb 2019, 10:20

Hi Vitore,

You can suggest this in our UserVoice forum.

Best Regards,

Panagiotis

PanagiotisCharalampous
04 Feb 2019, 10:18

Hi tgjobscv,

There are no plans for this at the moment. You can easily develop a cBot so send you alerts for specific indicators.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 18:00

Hi netread2004,

First of all you should not use the sample application as a design pattern to build your own. The example application only serves the purpose of demonstrating how to construct, send and receive FIX messages. It is not a FIX engine. Essentially, you should have a listener function that should always listen to messages arriving from the server e.g. read data from the connection every 100 ms. This way your listener will be intependent of your message sending functions. Maybe you would like to have a look at the Open API sample application that follows such a design. 

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 17:24

Hi netread2004,

If you are sending a message with a ClOrdID (1517158681)  but you receive a response with another ClOrdID (1746432918) then probably the server is still responding to messages sent before (1746432918 must have been sent before 1517158681). So you need to wait until 35=8 arrives for 1517158681 instead of sending additional messages which will cause more displacement and confusion. It seems that you assume that each message that arrives is a response to the previous message sent which is not the case. This is why tag 11 exists, to distinguish for which message the response corresponds to. If the ClOrdID of a response does not match to the ClOrdID of a request then it is not a response to that request. I believe you need to tidy up a bit the way you send and receive messages instead of sending additional messages until you get what you want. You must not assume that you will receive a response before you send the next message and some responses might come after you have sent several messages. Therefore you will need to match responses to previous requests. However, whatever I say is hypothetical since I do not know what the code is actually doing.

Best Regards,

Panagiotis 

PanagiotisCharalampous
31 Jan 2019, 15:38

Hi netread2004,

After sending 35=D, you should wait for 35=8 (Execution Report). After the execution report, you should send the message for the positions (35=AN) and receive 35=AP. 

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 15:02

Hi netread2004,

No it doesn't make sense. You should send 35=AN once and wait for the response. The way you do it, you are probably spamming the server hence the delay. The server will need to respond to all your requests.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 14:36

Hi netread2004,

There is no other way to get open positions than 35=N. Is there a reason to send the message every 100 ms if you have not sent an order?

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 12:56

Hi netread2004.

Presonally there are not much things I can advise you regarding this since I do not know how your system works. I tested the specific message with our sample application but there is no delay. Can you try the sample application as well and let me know if you can reproduce such a delay?

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 12:26

Hi bienve.pf,

We managed to reproduce the probem. We will fix it in an upcoming update.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 10:00

Hi Alex,

Are you referring to the UI or through cTrader Automate? Through the UI, you can do this using Advanced Protection.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 Jan 2019, 09:47

Hi Alex,

Stochastc and Stochastic RSI are different indicators, Here is the Stochastic RSI for cTrader. Is takes a hardcoded MarketSeries.Close as input but you can easily tweak it to take it as a parameter and use OHLC/4 instead.

Best Regards,

Panagiotis 

PanagiotisCharalampous
30 Jan 2019, 16:36

Hi Vito,

Since v3.3 all accounts need to be linked with a cTrader ID, in contrast with previous versions where you had the choice not to use cTrader ID but only your trading account. This happens because many of the features we develop are cloud based and require cTrader ID. Therefore we cannot support signing in with a trading account.

Regarding

"Why is it so important to prevent traders from re-assigning their accounts among their cTrader IDs easily on their own?". 

We do not intentionally prevent it but it is a complicated feature to be developed due to the security implications. Also it is not a very common scenario therefore there is not much requests for it. At the moment it is easier for the broker to validate your request, make sure that you own the other cTrader ID as well and change the ownership of the account.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 15:17

Hi bienve.pf,

Ok now I understood. It should be working, we will check this.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 14:40 ( Updated at: 21 Dec 2023, 09:21 )

Hi bienve.pf,

Seems to be working fine for me. See below

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 12:33

Hi bienve.pf,

Can you share the indicator with us? If programmed properly, it should work fine.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 12:14

Hi lw3010996,

if you remove this piece of code

             thread.Join();
             while (thread.IsAlive)
               System.Windows.Forms.Application.DoEvents();

It should work fine.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 11:51

Hi Nasser,

The feature is in our backlog but we do not expect to have this soon, at least in the following couple of updates. We will keep you posted regarding any progress.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 Jan 2019, 11:38

Hi Alex,

You cannot add it to Stochastic since Stochastic does not use such type of sources to be calculated. The calculation of Stochastic requires candlestick information. You can find the formula here. 

Best Regards,

Panagiotis