PanagiotisCharalampous
04 Jun 2018, 10:27 ( Updated at: 08 Feb 2023, 14:49 )

Hi Paul,

Yes it is seems correct. Pip position is second decimal place. Therefore the calculation goes as follows

773525 - 765025 = 8500

Best Regards,

Panagiotis

PanagiotisCharalampous
04 Jun 2018, 10:20

Hi Nasr,

Thanks for your suggestion. I would recommend you to post it in the Suggestions section of the forum so that it gets considered by the relevant product team.

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 17:13

Hi thongbaogiaodich,

Is it possible to send us the cBot code to check this?

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 16:12

Hi uwe.g.heilmann@gmail.com,

Indeed this is how it works. PositionClosed is raised for any position closed. Therefore you will need to make the relenant checks in order to find what is the symbol of the closed position. You can find the position information in the args argument.

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 15:53

Hi uwe.g.heilmann@gmail.com,

It seems that an exception is thrown from Write_Notification() method. Could you please send us the code of that method as well?

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 14:11

Hi,

It is not necessary to send us the complete cBot. Just a cBot with the relevant parts that reproduce the problem would be enough.

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 11:09

Hi uwe.g.heilmann@gmail.com,

Thanks for the valuable feedback regarding the recent update. We will be taking all of your comments into consideration. Regarding the error messages, is it possible to post a sample cBot that reproduces the error messages so that we can look into this further?

Best Regards,

Panagiotis

PanagiotisCharalampous
01 Jun 2018, 08:55

Hi,

You can contact me at community@spotware.com

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 18:00

Hi, 

I don't need the information in order to put the blame on your side but in order to reproduce this on my computer and then show it to the product manager :). If you can send me a sample cBot that behaves this way, I would be able to run it locally and demonstrate it to cAlgo team so that they can run their performance analysis. 

Looking forward to the cBot code!

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 17:39

Dear Trader,

Even though the tone and content of your first post is not aligned with the rules and guidelines of the community, I have chosen to ignore it and I kindly asked for further information so that I can help you. However, you insist to derail this into a meaningless conversation in the same tone. I don't see a reason participating in such a conversation. If you wish us to help you further, you are welcome to send us additional information to investigate your issue in depth.

Best Regards,

Panagiotis 

PanagiotisCharalampous
31 May 2018, 16:58

Dear Trader, 

Spotware cTrader Beta has been available for three months now so you are definitely not the first to test the product. It would be more constructive if you could provide technical details about your situation, so that we can determine if this is a performance issue of if it is just a natural overload. To make safe conclusions we need a) hardware specifications b) the cBot's code c) the number of cBot instances running d) the state of cTrader at the time this happens e.g. number of charts opened.  

Looking forward to your reply and your help to make this product better,

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 15:24

Hi David,

Thanks for posting this. Our engineers are looking at it.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 11:52

Hi Patrick,

Thanks for the positive feedback. I will pass all your suggestions to the product team.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 11:46

Hi Waxy,

Could you please send some more information about this to feedback@spotware.com so that they can investigate further? Please let them know your broker, account numbers and when do these disconnections happen. Even a short video demonstrating this behavior would be very helpful.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 11:44

Hi Waxy,

All brokers have been upgraded to cTrader 3.0 therefore you should not have this problem anymore. You should just upgrade your cBot to use the latest function and the warning will go away.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 11:34

Hi Jeshayle,

We are aware of this issue and we will resolve it in an upcoming update.

Best Regards,

Panagiotis

PanagiotisCharalampous
31 May 2018, 10:27

Hi dgedenfield,

Can you please post some more information about this so that we can investigate like broker, symbol, cBot and backtesting parameters, screenshots? We will need more information in order to investigate this.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 May 2018, 15:48

Hi fxwisdom1@gmail.com,

You can read more about orders, seals and positions here. However information about Submitted Price is not available in cAlgo.API or in Connect API. I will discuss this with cAlgo team and check if we can add this field in the API.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 May 2018, 15:37

Hi irmscher9,

We are already aware of this issue thanks. We will resolve it.

Best Regards,

Panagiotis

PanagiotisCharalampous
30 May 2018, 15:22

Hi irmscher9,

Thanks, I have reported this to cAlgo team.

Best Regards,

Panagiotis