The system suddenly stopped, and I'm not sure what the reason is. I've tried reopening the software, but that didn't work either.
- #2,843
- Jan 31, 2026 8:46am Jan 31, 2026 8:46am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
{quote} After switching accounts, it was confirmed that the problem was with the platform. However, I didn't complete many orders today.
it worj fast with 5541, for settin, order entry , closing, ertc . . just do not change chart frame to acvoid noisy halt!i think mt5 will solve thier problem soon . .
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,845
- Jan 31, 2026 8:52am Jan 31, 2026 8:52am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
gday Macd-rsiDiscovery of 2 Obstacles when using the lrweinan_Key; 1) After the bot starts, USER is unable to align the RSI_TARGET value with another bot on the same symbol, preventing the ability to simultaneous close out all positions & removal of RSI at the symbol level at the same time - defeating the Keys primary objective.
if it is off .. it is ok for that symbol--2 bots serve the same target
or just use strategic % or account profit since it is independent of IRWININ0
i will read the other part of your post ..
if possible could you draw logic diagram for what you need?
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,846
- Jan 31, 2026 9:00am Jan 31, 2026 9:00am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
but through timers you can overcome this problem as if there is only one expert.
assume time now is 12:00:00
and you have 4 bots:
be clever and do the folliwing:
for each expert make R timer R/12
but let bot 1 strat at 12:00:00
and bot 2 at 12:00:03
bot 3 at 12:00:06
bot 4 at 12:00:09
so you make it very ligh
time-threading! on system-safe timers
assume time now is 12:00:00
and you have 4 bots:
be clever and do the folliwing:
for each expert make R timer R/12
but let bot 1 strat at 12:00:00
and bot 2 at 12:00:03
bot 3 at 12:00:06
bot 4 at 12:00:09
so you make it very ligh
time-threading! on system-safe timers
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,847
- Jan 31, 2026 9:01am Jan 31, 2026 9:01am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
hi Mac-rsi
i onlu have 15 and 16
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,848
- Jan 31, 2026 9:02am Jan 31, 2026 9:02am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
it is ok with me now . .
a,b,c,d for 4 bots
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,850
- Edited 3:53pm Jan 31, 2026 9:42am | Edited 3:53pm
Mad-rsi (hope I explain better)
(I did not think this would be a problem - only became apparent in my testing under simulated real conditions).
SYMBOL > bot A, bot B
Once the SYMBOL’s (combined A&B) TP% target is reached, both A & B close positions & remove rsi.
AS IS they are independent & they will close & remove rsi independently once each of their respective TP% targets are reached (GREAT-FANTASTIC)
BUT IF the reason for having 2 bots on 1 symbol is to behave differently (complementary) to each other, with the objective of reaching the selected TP% target as one…THEY THEN MUST ACT TOGETHER & close positions & remove rsi AS ONE (at the same time). Otherwise one side closes & stops trading leaving the other side exposed & unbalanced with NO certainty of ever reaching its target EVEN IF it is just $1 difference between bot A & bot B's TP% number used to close positions.
All we need is way of inputing the same TP% into BOTH bot A & bot B for the instruction of closing open positions AFTER the bots start. If the TP% is inputed before hand then the numbers will match up. But this is NO good in real live situations. We need to be able to input the TP% while the bots are trading.
Objective; ability to input on the fly the SAME TP% for the instruction of removing rsi = done, achieved via the STRATEGIC_TARGET & remove rsi button (red)
Objective; ability to input on the fly the SAME TP% for closing positions = unable currently to input the same TP% on both bots A & B
How this is achieved I have previously given 2 possible methods that I suggested (without understanding the underlying mechanics). I think (hope) we r close & there just needs to be small addition/adjustment of what is already available.
(hope I explain better)(I did not think this would be a problem - only became apparent in my testing under simulated real conditions).
SYMBOL > bot A, bot B
Once the SYMBOL’s (combined A&B) TP% target is reached, both A & B close positions & remove rsi.
AS IS they are independent & they will close & remove rsi independently once each of their respective TP% targets are reached (GREAT-FANTASTIC)
BUT IF the reason for having 2 bots on 1 symbol is to behave differently (complementary) to each other, with the objective of reaching the selected TP% target as one…THEY THEN MUST ACT TOGETHER & close positions & remove rsi AS ONE (at the same time). Otherwise one side closes & stops trading leaving the other side exposed & unbalanced with NO certainty of ever reaching its target EVEN IF it is just $1 difference between bot A & bot B's TP% number used to close positions.
All we need is way of inputing the same TP% into BOTH bot A & bot B for the instruction of closing open positions AFTER the bots start. If the TP% is inputed before hand then the numbers will match up. But this is NO good in real live situations. We need to be able to input the TP% while the bots are trading.
Objective; ability to input on the fly the SAME TP% for the instruction of removing rsi = done, achieved via the STRATEGIC_TARGET & remove rsi button (red)
Objective; ability to input on the fly the SAME TP% for closing positions = unable currently to input the same TP% on both bots A & B
How this is achieved I have previously given 2 possible methods that I suggested (without understanding the underlying mechanics). I think (hope) we r close & there just needs to be small addition/adjustment of what is already available.
- #2,853
- Jan 31, 2026 10:16am Jan 31, 2026 10:16am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,854
- Jan 31, 2026 10:21am Jan 31, 2026 10:21am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,855
- Jan 31, 2026 10:22am Jan 31, 2026 10:22am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
{image}
if yes, it is very strange
there is a solution go to thier website, within 1 min esta[lish a user name . .
Exness Personal Area
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,856
- Jan 31, 2026 10:23am Jan 31, 2026 10:23am
- Joined Oct 2019 | Status: Forexian Fighter = FF | 16,341 Posts
each day 10%,,,, https://www.forexfactory.com/thread/1371538
- #2,857
- Jan 31, 2026 10:26am Jan 31, 2026 10:26am
https://youtu.be/6pMY0hUsm54 This could be a mistake.
ACCOUNT_PROFT_TARGET reached & open positions closed...what am I missing here m8?
- #2,859
- Jan 31, 2026 11:47am Jan 31, 2026 11:47am
{quote} Starting from 18 seconds, take a close look. Without setting a stop-loss, it closed my order. My account balance went from 995 to 896.
> Uncheck the red pads next to the TP's u don't want active or set TP% that are equity level with a higher number than whatever your current account balance level is -
make sense?
- #2,860
- Edited Feb 1, 2026 6:39am Jan 31, 2026 12:38pm | Edited Feb 1, 2026 6:39am
but through timers you can overcome this problem as if there is only one expert. {image} assume time now is 12:00:00 and you have 4 bots: be clever and do the folliwing: for each expert make R timer R/12 but let bot 1 strat at 12:00: and bot 2 at 12:00:03 bot 3 at 12:00:06 bot 4 at 12:00:09 so you make it very ligh time-threading! on system-safe timers
Yes I am aware of the timer to start the bots off at small intervals & YES this is a great concept for a lot of scenarios. But in this case it will then have a negative effect on the bots behaviour - they will be out of sync. They need to all be making decisions from the same source (time & data). ONLY their collective sending of orders at the same time will potentially cause problems - hence my suggestion of a TIME_DELAY option where users can (or not) set up a delay in milliseconds for a staggered approach for each bot executing their respective orders. Thus decreasing the chances of bottlenecks of data as instructions are sent to the broker's servers.
UPDATED AGAIN (time to think some more)