Trade Copier on Beta 7

[heispark]

I tried with the latest build of beta 7 and it didn't work as expected. Connected multiple futures prop firms accounts and they failed reacting properly with the lead account. Does anyone have the same issue?

 

[jsgold]

Yes, it is pretty much unuseable in my experience so far with it. Since you mentioned multiple prop firms, I have a suspicion the problem is with rithmic specifically more than the copier itself - verision 7 moved to a new rithmic data source, web api I believe, and the copier functionality is full of errors. I have sent logs and explanations with screenshots to support, with no response for weeks. It doesn't seem to be much of a priority to fix unfortunately.

 

[Vlad]

I use it - 5 connections, all rithmic. I use legacy Rithmic Gateway for primary quotation feed, so one of the five is configured as Rithmic Gateway. It seems more stable. There are occasional errors, of the following types:
1. minor error popup on first order entry - just ignore it, and reenter your orders
2. orders created but not cancelled when hit "flatten" or "cancel" - need to disable connection to secondary rithmic account and reconnect. Often requires restart. I had to split my 5 connections into two workspaces, 3 connections in each, not to deal with this trying to trade the open for example. This doesn't seem to appear in the most recent build from this weekend though. Maybe just luck
3. Account balance/positions do not update for one of the connections - i.e. all orders placed fine, just MW doesn't get updated. Fix is to reconnect the problematic connection
Overall best practices that help me - 1. always test your trade copier by placing and cancelling orders somewhere far from current price. 2. always keep rithmic r trader open with positions and orders clearly visible for each connection. R Trader remembers all settings for each connection, so once you arrange all internal windows and tiles in your windows workspace, you won't need to redo it. 3. When starting MW, I wait a few moments after each password entry for each connection to initialize, but have no idea if this really helps with anything.
All in all, I'm now down to a single workspace with 5 connections, but I'm not copy trading more than 3 connections at a time as part of risk mgmt

 

[jsgold]

I use it - 5 connections, all rithmic. I use legacy Rithmic Gateway for primary quotation feed, so one of the five is configured as Rithmic Gateway. It seems more stable. There are occasional errors, of the following types:
1. minor error popup on first order entry - just ignore it, and reenter your orders
2. orders created but not cancelled when hit "flatten" or "cancel" - need to disable connection to secondary rithmic account and reconnect. Often requires restart. I had to split my 5 connections into two workspaces, 3 connections in each, not to deal with this trying to trade the open for example. This doesn't seem to appear in the most recent build from this weekend though. Maybe just luck
3. Account balance/positions do not update for one of the connections - i.e. all orders placed fine, just MW doesn't get updated. Fix is to reconnect the problematic connection
Overall best practices that help me - 1. always test your trade copier by placing and cancelling orders somewhere far from current price. 2. always keep rithmic r trader open with positions and orders clearly visible for each connection. R Trader remembers all settings for each connection, so once you arrange all internal windows and tiles in your windows workspace, you won't need to redo it. 3. When starting MW, I wait a few moments after each password entry for each connection to initialize, but have no idea if this really helps with anything.
All in all, I'm now down to a single workspace with 5 connections, but I'm not copy trading more than 3 connections at a time as part of risk mgmt

thank you! Nice to hear it's improving, going to give it a shot again.

 

[kally]

I use it - 5 connections, all rithmic. I use legacy Rithmic Gateway for primary quotation feed, so one of the five is configured as Rithmic Gateway. It seems more stable. There are occasional errors, of the following types:
1. minor error popup on first order entry - just ignore it, and reenter your orders
2. orders created but not cancelled when hit "flatten" or "cancel" - need to disable connection to secondary rithmic account and reconnect. Often requires restart. I had to split my 5 connections into two workspaces, 3 connections in each, not to deal with this trying to trade the open for example. This doesn't seem to appear in the most recent build from this weekend though. Maybe just luck
3. Account balance/positions do not update for one of the connections - i.e. all orders placed fine, just MW doesn't get updated. Fix is to reconnect the problematic connection
Overall best practices that help me - 1. always test your trade copier by placing and cancelling orders somewhere far from current price. 2. always keep rithmic r trader open with positions and orders clearly visible for each connection. R Trader remembers all settings for each connection, so once you arrange all internal windows and tiles in your windows workspace, you won't need to redo it. 3. When starting MW, I wait a few moments after each password entry for each connection to initialize, but have no idea if this really helps with anything.
All in all, I'm now down to a single workspace with 5 connections, but I'm not copy trading more than 3 connections at a time as part of risk mgmt

Honestly, that doesn't sound very confidence-inspiring. Quite disappointing, same as the stable version.
The copier was almost the main thing why I bought MW...

 

[AyeconTrading]

The copier needs to be remade - It will blow any kind of funding company accounts in one trade because of phantom orders - java timeouts - unable to flatten - it doesn't have a mechanism that if one account is locked (rejects orders) to still manage the group.

 

[heispark]

I am doubt it would work properly even when stable v7 is released in the near future. For the time being Quantower is the only option.

 

[jzmorgan]

I use it - 5 connections, all rithmic. I use legacy Rithmic Gateway for primary quotation feed, so one of the five is configured as Rithmic Gateway. It seems more stable. There are occasional errors, of the following types:
1. minor error popup on first order entry - just ignore it, and reenter your orders
2. orders created but not cancelled when hit "flatten" or "cancel" - need to disable connection to secondary rithmic account and reconnect. Often requires restart. I had to split my 5 connections into two workspaces, 3 connections in each, not to deal with this trying to trade the open for example. This doesn't seem to appear in the most recent build from this weekend though. Maybe just luck
3. Account balance/positions do not update for one of the connections - i.e. all orders placed fine, just MW doesn't get updated. Fix is to reconnect the problematic connection
Overall best practices that help me - 1. always test your trade copier by placing and cancelling orders somewhere far from current price. 2. always keep rithmic r trader open with positions and orders clearly visible for each connection. R Trader remembers all settings for each connection, so once you arrange all internal windows and tiles in your windows workspace, you won't need to redo it. 3. When starting MW, I wait a few moments after each password entry for each connection to initialize, but have no idea if this really helps with anything.
All in all, I'm now down to a single workspace with 5 connections, but I'm not copy trading more than 3 connections at a time as part of risk mgmt

How do you keep your R trader connections open when all of them are logged into MW 7? R trader pro will kick me out once logged into MW. I am using the copier, but obviously want to double check R trader in case there’s an issue.

 

[heispark]

How do you keep your R trader connections open when all of them are logged into MW 7? R trader pro will kick me out once logged into MW. I am using the copier, but obviously want to double check R trader in case there’s an issue.

Turn off Market Data. Then you won't be kicked out.