Spotware
27 Mar 2017, 11:51

Hi richardblackhall,

By saying free movement do you mean free chart moving i.e up and down as well as left and right?

Spotware
27 Mar 2017, 11:49

Hi ycomp,

cAlgo is limited at one account at a time. If you want to trade on multiple accounts at the same time, you might consider using Spotware's Connect API.

Best Regards,

Spotware
27 Mar 2017, 11:46

Hi lec0456,

It is is a known issue and will be fixed soon. It has been addressed a few times in the forum already.

Spotware
27 Mar 2017, 09:35

Hi taskman9,

We would advice you to have a look at the FIX API sample here https://github.com/spotware/FIX-API-Sample

Spotware
27 Mar 2017, 09:26

Hi ycomp,

If you want to use the sandbox environment, you will need to use the account credentials provided here https://connect.spotware.com/docs/available-resources/test-environment

Else you can use a demo account on the live environment,

Spotware
24 Mar 2017, 16:22

RE:

Hi Ghashamm,

Please contact your broker to unlink your trading account from this cTID and link it with the correct cTID.

Spotware
22 Mar 2017, 14:35

Hi dm.skpd

Yes this will be updated soon.

Spotware
22 Mar 2017, 14:18 ( Updated at: 21 Dec 2023, 09:20 )

Hi EOL,

Your FIX API credentials page should look like this

Do you run the latest version of Spotware cTrader?

Spotware
22 Mar 2017, 11:04

Hi,

You are advised to use the host name rather than the IP since the IP might change from time to time.

Spotware
22 Mar 2017, 10:46

Hi Taharxeg,

There should be something wrong with your code which is not obvious from the code sample you sent. We advise you to cross check your implementation with our code samples which are working properly https://github.com/spotware

Spotware
21 Mar 2017, 16:07

Hi dm.skpd,

Can you verify that you are sending Trade messages to 5202 and not 5201? 

Spotware
21 Mar 2017, 12:12

Hi ianj,

No this is not possible using FIX API neither we have plans to implement it soon. You will need to implement this functionality on your side.

Spotware
21 Mar 2017, 12:11

Hi ianj,

Currently it is not possible to do so. In an upcoming update we will include the option to cancel an order, therefore you will be able to cancel and place a new one.

Spotware
21 Mar 2017, 10:14

Hi ianj,

Yes hedging in now supported for live accounts

Spotware
21 Mar 2017, 10:11

Hi lec0456,

There is no simple answer to this. In general, you will need to be familiar with parallel programming and use it while programming your cBot. Note that not all algorithms are parallelizable. There are a lot of good articles on the web regarding parallel programming using C# like the following

https://blogs.msdn.microsoft.com/csharpfaq/2010/06/01/parallel-programming-in-net-framework-4-getting-started/

Have a look at it if you are interested in getting deeper into the subject.

Spotware
20 Mar 2017, 14:51

When backtesting cAlgo just runs your cBot. If you want to utilize CPU 100% during backtesting you will need to paralellize your cBot's algorithm.

Spotware
20 Mar 2017, 12:42

Hi j.tarno.

Do you mean the FIX Symbol ID? Go to your cTrader, right click on a Symbol inside the Symbols tab, select information and scroll down to the Symbol Info section. There you can locate the FIX Symbol ID.

Spotware
20 Mar 2017, 10:56

Hi j.tarno

This is an example of a login message for a pepperstone demo account

8=FIX.4.4|9=120|35=A|49=pepperstone.3185604|56=CSERVER|57=QUOTE|50=3185604|34=1|52=20170320-08:50:58|98=0|108=30|553=3185604|554=password|10=090|

and this is the reply

8=FIX.4.4|9=101|35=A|34=1|49=CSERVER|50=QUOTE|52=20170320-08:50:58.122|56=pepperstone.3185604|57=3185604|98=0|108=30|10=212|

You can use our FIX API code sample to see how the messages are constructed. You can find it here. You can use your credentials in the example and test it.

Spotware
20 Mar 2017, 10:28

Hi lec0456,

Can you please elaborate when does cAlgo underutilize the processor so we can investigate? 

Spotware
20 Mar 2017, 10:24

Hi lec0456,

In a recent update we removed the option to show/hide columns in the history tab. Therefore your history tabs contain the columns configured to be visible at the point of the update. It seems you had different columns visible on each machine at the time of the update. This is going to be fixed in the next release.