This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.
I do not understand what is the problem. What other case could there be for local execution?
In addition to this, I don't see any explicit reference to the respective account where a cBot is running.
What do you mean by explicit reference?
Hi Panagiotis,
I do not understand what is the problem. What other case could there be for local execution?
Isn't the issue obvious? I've addressed this in the original thread. The account mentioned in the screenshot is not the account in which the cBot is running. Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?
What do you mean by explicit reference?
Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.
Hi ncel01,
I still don't understand
Isn't the issue obvious? I've addressed this in the original thread.
No, that is why I am asking.
The account mentioned in the screenshot is not the account in which the cBot is running.
Please provide screenshots demonstrating this
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?
Cloud execution. If the cBot is executed on the cloud it could run on a different account.
Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.
I don't understand what do you want to check. It should be what you see on your screen.
Best regards,
Panagiotis
Hi Panagiotis,
The account mentioned in the screenshot is not the account in which the cBot is running. Correction: Every time a new account is selected, the cBot execution is stopped on the previous account and applied to the new account instantly, which is also not great, I'd say.
However, I noticed that every time a demo account is involved, the cBot execution is stopped and not applied to the new account. This does not make much sense to me. Shouldn't this work the other way around, for obvious reasons? To make it worse, users are not warned when switching accounts while a cBot is running, which would prevent a cBot from stopping on the current account, as well as any accidental cBot execution on the new account.
Cloud execution. If the cBot is executed on the cloud it could run on a different account.
Why is this not possible locally as well? It would be a great feature. At the moment, every cBot running on a different account requires a dedicated cTrader instance which is very resource-intensive.
Hi there,
Ok it's more clear now. I still don't see the problem. Local execution works the same way since cAlgo 1.0. Running a cBot on an account that is not the one to which cTrader is connected is not as simple as it sounds and not as obvious as it might be for your. Not all users would like such a breaking change to the way cTrader has always worked. That's why you have an option of running your cBot in an external process.
Could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
The Symbol.MinCommissionType property is indeed designed to provide clarity on how the minimum commission (MinCommission) is expressed. Here are the key reasons for its existence:
Clarity and Explicitness:
The property explicitly states whether the MinCommission is denominated in the symbol’s quote asset or a different asset. This helps prevent any ambiguity or misinterpretation, especially when dealing with various symbols and assets.
Ease of Use:
By providing a clear indication of the commission type, it simplifies the logic needed to handle different commission structures. This can be particularly useful in complex algorithms where commission calculations play a significant role.
Comparative Check:
While you could infer the commission type by comparing the MinCommissionAsset with the quote asset, having a dedicated property like MinCommissionType allows for a quicker, more direct check. This can enhance code readability and maintainability.
Example Use Case:
Consider a scenario where you need to implement different handling or calculations based on whether the MinCommission is in the quote asset or another asset. The MinCommissionType property allows you to write straightforward conditional logic without needing additional comparisons or checks.
While the MinCommissionAsset property provides the specific asset in which the commission is denominated, the MinCommissionType property adds an additional layer of clarity and convenience. It allows you to easily understand and handle the commission structure without needing extra logic for comparison.
Arguably the most important settings before deploying a bot are its parameters. Hidden away in the poorly titled “Public Settings”, I assume this is the only place you can change the symbol and period for a bot? Do you really need to create multiple instances of a bot for each set of parameters?
Not sure what do you mean. It's as easy as before
When you add a bot to a chart you've got no option to change its parameters from the chart view, you have to go back to algo, back through the stupid intermediary page, click on the poorly titled "Public settings" button that opens a window that finally provides its parameters. Why not allow for the settings dialog to be opened by double clicking the bot widget on the chart?
This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.
I do not understand what is the problem. What other case could there be for local execution?
In addition to this, I don't see any explicit reference to the respective account where a cBot is running.
What do you mean by explicit reference?
Hi Panagiotis,
I do not understand what is the problem. What other case could there be for local execution?
Isn't the issue obvious? I've addressed this in the original thread. The account mentioned in the screenshot is not the account in which the cBot is running. Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?
What do you mean by explicit reference?
Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.
Hi ncel01,
I still don't understand
Isn't the issue obvious? I've addressed this in the original thread.
No, that is why I am asking.
The account mentioned in the screenshot is not the account in which the cBot is running.
Please provide screenshots demonstrating this
Question #1: What's the purpose/logic behind mentioning an account other than the cBot's respective account?
Cloud execution. If the cBot is executed on the cloud it could run on a different account.
Question #2: How to easily check the account associated to a running cBot? I don't see this information explicitly (at a glance) available.
I don't understand what do you want to check. It should be what you see on your screen.
Please note that the WebSocket server needs to use this port as well. Else no communication is possible.
Here’s a step-by-step guide to set up your WebSocket server to communicate with your cBot:
Set up your WebSocket Server:
Ensure that your WebSocket server is configured to listen and send messages on port 25345.
Here is a simple example using Node.js with the ws library:
const WebSocket = require('ws');
const server = new WebSocket.Server({ port: 25345 });
server.on('connection', socket => {
console.log('Client connected');
socket.on('message', message => {
console.log('Received:', message);
// Process the message and send a response if needed
socket.send('Message received');
});
socket.on('close', () => {
console.log('Client disconnected');
});
});
console.log('WebSocket server is listening on port 25345');
Update Your cBot to Connect to the WebSocket Server:
Ensure your cBot is configured to connect to your WebSocket server. The URI should look like this: wss://example.com:25345/.
Here is an example cBot code snippet:
using System;
using System.Text;
using cAlgo.API;
using cAlgo.API.Internals;
namespace cAlgo.Robots
{
[Robot(TimeZone = TimeZones.UTC, AccessRights = AccessRights.None)]
public class WebSocketBot : Robot
{
private WebSocketClient _webSocketClient;
protected override void OnStart()
{
_webSocketClient = new WebSocketClient();
var uri = new Uri("wss://example.com:25345/");
_webSocketClient.Connect(uri);
Print("WebSocket connection opened");
}
}
}
Testing:
Start your WebSocket server and ensure it is running and accessible on port 25345.
Deploy your cBot to the cTrader Cloud instance.
Monitor the logs to ensure the cBot is connecting to the WebSocket server and receiving messages correctly.
By following these steps, your cBot should be able to communicate with your WebSocket server, even in a cTrader Cloud instance.
If you encounter any issues or have further questions, please feel free to reach out.
The problem you are trying to describe is not clear to me. Can you please rephrase and use some images so that we can understand what you are looking at?
Best regards,
Panagiotis
I started copy trading with my chosen strategy provider, but no trades are being copied, as shown in the image. Thank you.
Hi there,
Why do you hide the strategy name? Does your strategy provider have open positions? Can you share a screenshot showing that the strategy has open positions but your account has not?
This is the case even when a cBot is running (as shown below), suggesting that the respective cBot instance is always running on the active account, which is (obviously) not always the case.
I do not understand what is the problem. What other case could there be for local execution?
In addition to this, I don't see any explicit reference to the respective account where a cBot is running.
Can you rephrase your question? It is not clear what you are asking for.
Best regards,
Panagiotis
Hi there,
This page just provides you with a token and a refresh token. There is nothing else to do than copy the token and use it as per your wish. What are you trying to do? What do you expect to happen? Please provide some more context.
Best regards,
Panagiotis
Hi there,
I just want to use cMAM. I want to see all my ctrader accounts to use cMAM. I don't know how to get there. I want to have a master account and slave accounts. I am just a simple person, running a ctrader live account, which is the best platform. I am not a ctrader Guru. That is why I am kindly and humble asking for help. That is all what it is about.
Thank you.
I am not familiar with cMAM. Did you read the documentation? Did you ask in the product's Telegram group https://t.me/cmam_official ?
This happens because the strategy providers have these positions open in their accounts.
Best regards,
Panagiotis
i already check there is nothing open in his account and it's not just one provider it's all of them opening same positions 2 deferent provider attached in the photos every time i close the copy and open again it will give me the same 2 positions
What exactly did you check? Can you share a screenshot with the strategy's positions?
The history is on the server, let us know if this still happens on v5.0
I have the same problem on 5.0.25. The Object "History" in Calgo is not reachable neither; so my bots whose use it are crashing. I tried to delete the fxpro directories in appadata, but it don't works, it works one time, i retrieve the full history the first start of CTrader, after from the second start same thing: the history is empty, only positions who are closed while ctrader is open will be displayed, but at the next start of ctrader, the history will be empty.
Hi there,
Can you record a video demonstrating this happening on the latest version?
PanagiotisCharalampous
05 Jul 2024, 05:04
RE: RE: RE: RE: How to easily identify the respective account for a running cBot ?
ncel01 said:
Hi there,
Ok it's more clear now. I still don't see the problem. Local execution works the same way since cAlgo 1.0. Running a cBot on an account that is not the one to which cTrader is connected is not as simple as it sounds and not as obvious as it might be for your. Not all users would like such a breaking change to the way cTrader has always worked. That's why you have an option of running your cBot in an external process.
Best regards,
Panagiotis
@PanagiotisCharalampous