Spotware
12 Jul 2017, 17:43

Resolved

Hello williamtokyo88,

Thank you for posting this in our forum. We have already resolved this question with you via email, for the benefit of the rest of the users in the forum we will explain the situation. 

cTrader uses a Smart Stop Out algorithm for closing positions when Margin Level falls below the Smart Stop Out level which is set by the broker. This is why you saw multiple closing orders in your trade history, but in fact they all belong to the same 6 positions, but they were partially closed in the smallest possible increment in order to restore margin level just above Smart Stop Out level. This is beneficial because it prevents the whole position from being closed.

To read more about Smart Stop Out, please use the following link http://help.spotware.com/trading/smart-stop-out

Regards,

cTrader Team

Spotware
12 Jul 2017, 16:12

Dear 3161529,

Thanks for your question. It is possible to reference cAlgo.API in your application but it would not be of much practical usage, since the API uses data provided by cAlgo, like market data which is necessary to plot an indicator. The cAlgo.API does not offer functionality to fetch this data from the server. If you want to develop your own application then we recommend you to use Connect API instead to get all the necessary data and use cAlgo.API as a complementary API in case you need to use any of the classes and functions it offers.

If you still want to reference cAlgo.API in your application you can do it as follows

1. Open your Visual Studio project
2. Go to References
3. Right Click > Add Reference
4. Click Browse
5. Navigate to C:\Users\yourusername\Documents\cAlgo\API
6. Select cAlgo.API.dll and press add
7. Click OK

Best Regards,

cTrader Team

Spotware
12 Jul 2017, 13:00

Dear Jared and taharxeg,

An update has taken place recently and this issue has been resolved now. You can receive trendbars through Connect API now. 

Best Regards,

cTrader Team

Spotware
12 Jul 2017, 11:56

Dear Lukedeland,

Thanks for your suggestion. We will consider it. You can also post your suggestion at http://vote.spotware.com/

Spotware
12 Jul 2017, 11:51

Hi Futuresmo,

No this is not currently possible. You can post your suggestion at http://vote.spotware.com/

Spotware
12 Jul 2017, 11:47

Hi ctid320188,

This information is not currently available in cAlgo API but you can use Connect API to read this information. Have a look here https://connect.spotware.com/docs/api-reference/accounts-api

Spotware
12 Jul 2017, 11:42

Hi xmforex9,

Can you please elaborate on what are the problems you are facing so that we can investigate further?

Spotware
11 Jul 2017, 18:42

Hello tmfd,

Thank you for your post. You're right that most of the features we have been releasing have been for cTrader, although these are actionable on the UI they still require a lot of development on the server-side, especially since cTrader is an STP platform and has to comply with many different execution destinations. 

cAlgo now has a new manager and a dedicated team that is expanding, their second priority is to deliver multi instrument & timeframe backtesting. 

Budgets have not been cut and we have been continuously optimizing the cTrader internals for years to help the entire product scale with the growth of new users and brokers. A lot of new features can be implemented without first being developed on the server-side. A lot of projects that we have been working on are not visible because they are still in development, when they are released it will be clear what we have been working on.

Our CEO recently responded to an open letter and it will give you some insight into the company and our plans going forward. Here is the post: /forum/suggestions/11655#3  

Regards,

cTrader Team

Spotware
06 Jul 2017, 15:34

Dear GoldnOil750,

Thanks for reporting your problem. We have tested cTrader thoroughly on all brokers and on several computers but what you describe is not a behavior that was observed in any case (e.g. 45 seconds to load a chart). Could you please investigate further if this is a local problem of your computer? Could you please check if this issue is reproducible on other computers as well?

Spotware
03 Jul 2017, 12:49

Dear Derek,

Can you please elaborate on the problem you are facing? Why do you say that the "Reverse Signals" mirroring mode is not working? Are the signals not mirrored at all? Are they mirrored to the wrong direction? Do you get a message? Please give us some more information on the issue so that we can investigate.

Spotware
21 Jun 2017, 14:42

Dear suraditrading,

In order to investigate properly the issue, we will need some troubleshooting information to be sent to our technical team. Next time this happens, please restart cAlgo, press Ctrl + Alt + Shift + T and a troubleshooting pop up form will appear. Please describe the issue you face in the relevant text box and submit the information.

Spotware
21 Jun 2017, 12:45

Dear Uche,

There is no evidence that your cBots have been decrypted and decompiled. The most possible reason that your cBot code leaked is that you have accidentally uploaded it with source code. If you have a specific method that can decrypt and decompile a cBot, please share it and we will investigate.

Spotware
20 Jun 2017, 09:06

Hi luke.poortinga,

In order to close a position in a hedging account, you need to create an order with the same volume and in the opposite direction referencing the position id in PosMaintRptID tag.

Spotware
19 Jun 2017, 17:07

Hi jhk63,

Please see below what each arrow represents

Single Arrow Right - Stop Loss will be triggered by Bid for Buy positions and by Ask for Sell positions.

Double Arrow Right - Stop Loss will be triggered after two consecitive Bid ticks below the Stop Loss price for Buy positions or after two consecutive Ask Ticks above the Stop Loss price for Sell Positions.

Single Arrow Left - Stop Loss will be triggered by Ask for Buy positions and by Bid for Sell positions.

Double Arrow Right - Stop Loss will be triggered after two consecitive Ask ticks below the Stop Loss price for Buy positions or after two consecutive Bid Ticks above the Stop Loss pricefor Sell Positions.

Spotware
13 Jun 2017, 15:02

Hi sand,

Thanks for sharing your opinion and for the constructive discussion. Please find below some comments on some of the points mentioned in your post

"The 2nd type of stop order, is like a stop-loss order"​

This is not true. Stop Orders assosiated to positions can be used for much more cases, like to increase volume (opening), to decrease it (fully or partially closing the position) or even reverse the position. So, a Stop Order assosiated to a position can't be interpret as solely as a stop loss.

"As far as I know what you advise is not possible in your platform. Your platform can close only a PosID but cannot close an OID (order id). Your platform can close only positions but it cannot close orders. Please correct me if I am mistaken."

Just for clarity and use of the correct terminology, orders cannot be closed but only cancelled. Order cancellation has been added to our FIX API. Please check the latest rules of engagement here. Therefore it is possible to handle this on the client side.

"The attached stop order (or stop-loss) must not remain in the air by itself; it must be closed automatically by the broker."

This cannot be done currently on our side. The reason is because we have both netting and hedging accounts. If we cancel pending orders, then it will be impossible to put pendings into netting accounts.

"It works for quotes but for trades it is absolutely no use."

Please accept our disagreement with this statement. If FIX API is used properly, it can be useful for both cases.

Implementing a stop loss on our side is not theoretically impossible but raises many other technical implications e.g handling position increase/decrease, that it is architecturally more corrert that the entire logic is implemented on the client side.

In any case, please rest assured that all your feedback has been sent to the product team for consideration. 

Spotware
12 Jun 2017, 11:57

Hi to all,

cAlgo files are encrypted and can be decrypted only by cAlgo. Therefore it is not possible to be reverse engineered. Reverse engineering would be possible only if the files where obfuscated or compiled to native code, somehing which is not the case with cAlgo.

Spotware
12 Jun 2017, 11:28

Hi sand,

Thanks for reporting the issue you face. However this is not a bug of FIX API but rather an expected behavior. A stop order will be executed unless it is explicitely canceled. If you wish your stop order to be canceled when a related position is closed, then this is a functionality that you need to develop on your side. You will need to keep track of your positions and the related orders and cancel those orders when positions are closed.

Spotware
07 Jun 2017, 15:24

Dear andi21,

The cAlgo team has investigated your issue but they did not find a general way to reproduce the problem. Also the stack trace you posted shows that the exception is thrown from somewhere within the cBot, so it could be a programming issue somewhere inside your code. Therefore, in order to proceed with the investigation and advise further, we will need a cBot that reproduces the problem. Please let us know if you could send us such a cBot.

Spotware
01 Jun 2017, 17:32

Hi andi21,

Yes there is a textbox that you can use to sumbit your comments as well. You can include your email in case the support team needs to get in contact with you.

Spotware
01 Jun 2017, 17:07

Hi andi21,

Regarding the following case

"1. Why does cAlgo optimization stop too early sometimes (see also /forum/calgo-support/11573?page=2#12)? THIS should NOT happen, because it is nearly the same effect like if cAlgo crashes!"

Can you please send us troubleshooting information as soon as the optimizations stops? You can do this by pressing Ctrl+Shift+Alt+T in cTrader or cAlgo. This will send us the logs from your PC and we will be able to investigate further.