Степан Иванов: Olá, mais interessante ainda, abriu automaticamente uma operação no aud/usd, fechou com take profit +50$, o provedor de sinal usa apenas o par eur/usd e tal operação em seu histórico não encontrei de onde veio? Eu realmente quero entender tudo, me ajudem!
Então os sinais funcionaram? Se sim, ótimo. E o arquivo de registro da guia "Journal" ajudará a resolver o problema.
Karputov Vladimir: Então os sinais estão funcionando? Se sim, é bom. O arquivo de registro da guia "Journal" o ajudará a resolver o problema.
106:49:57.901 MQL5.community: authorization failed
106:49:59.548'7773899': connect failed [Нет связи]
006:50:10.404'7773899': login on Alpari-Demo through demo.nl.3006:50:11.052'7773899': login datacenter on Alpari-Demo through demo.nl.3006:50:11.246'7773899': previous successful authorization performed from78.85.179.29006:50:11.904'7773899': Signal - connecting to signal server
006:50:12.473'7773899': Signal - signal provider has balance 44163.13 USD, leverage 1:500006:50:12.473'7773899': Signal - subscriber has balance 10000.00 USD, leverage 1:500006:50:12.475'7773899': Signal - percentage for volume conversion selected according to the ratio of balances and leverages, newvalue10%
106:50:12.476 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
006:50:12.476'7773899': Signal - synchronization finished successfully
006:50:12.572'7773899': Signal - ping to signal server 95.66 ms
006:50:12.575 MQL5.community: activated for'IvanovSt', balance: 0.00006:50:27.740'7773899': auto connecting to a better access point demo.nl.3 a (ping is87.93 ms)
006:50:28.342'7773899': login on Alpari-Demo through demo.nl.3 a
006:50:29.354'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
006:50:29.581'7773899': previous successful authorization performed from78.85.179.29007:17:29.289'7773899': instant order sell 1.00 AUDUSD at 0.69978 sl: 0.00000 tp: 0.69928107:17:29.669 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
007:17:29.669'7773899': order was opened : #297283674 sell 1.00 AUDUSD at 0.69978 sl: 0.00000 tp: 0.69928007:17:35.925 Trades: use hosting service to speed up the execution - 1.74 ms via 'Netherlands (Webzilla Inc.)' instead of 87.93 ms
007:46:17.865 System to be shutdown, request for close Alpari Limited MT4
207:46:18.257 Expert MACD Sample AUDUSD,H1: removed
007:46:19.955 Alpari Limited MT4 build 840 stopped because system shutdown
016:35:16.278 Alpari Limited MT4 build 840 started (Alpari Limited)
016:35:16.278 Data Folder: C:\Program Files (x86)\Alpari Limited MT4
216:35:25.740 Expert MACD Sample AUDUSD,H1: loaded successfully
016:35:28.698'7773899': login on Alpari-Demo through demo.nl.3 a
016:35:30.211'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
016:35:30.459'7773899': previous successful authorization performed from78.85.179.29016:35:31.095'7773899': Signal - 'Alex Week DEMO'for'IvanovSt' subscription found, 2015.10.21 expiration, enabled
016:35:31.095'7773899': Signal - money management: use 50% of deposit, equity limit: 0.00 USD, deviation/slippage: 0.5 spreads, copy SL/TP: enabled
016:35:31.096'7773899': Signal - connecting to signal server
016:35:31.506'7773899': Signal - signal provider has balance 44163.13 USD, leverage 1:500016:35:31.506'7773899': Signal - subscriber has balance 10050.00 USD, leverage 1:500016:35:31.508'7773899': Signal - percentage for volume conversion selected according to the ratio of balances and leverages, newvalue10%
116:35:31.526 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
016:35:31.526'7773899': Signal - synchronization finished successfully
016:35:31.628'7773899': Signal - ping to signal server 102.18 ms
016:35:33.786 MQL5.community: activated for'IvanovSt', balance: 0.00016:35:34.821'7773899': auto connecting to a better access point demo.ru.0 a (ping is108.50 ms)
016:35:35.703'7773899': login on Alpari-Demo through demo.ru.0 a
016:35:36.968'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
016:35:37.209'7773899': previous successful authorization performed from78.85.179.29016:35:41.023 News: news base synchronization
116:51:33.260'7773899': datacenter connecting failed [6]
016:51:33.754'7773899': login on Alpari-Demo through demo.ru.0 a
016:51:34.702'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
016:51:34.979'7773899': previous successful authorization performed from78.85.179.29117:08:40.897'7773899': datacenter connecting failed [6]
117:09:40.924'7773899': connect failed [Нет связи]
117:13:07.476 MQL5.community: authorization failed
117:16:54.246 MQL5.community: authorization failed
107:01:11.710 MQL5.community: authorization failed
107:01:12.426'7773899': connect failed [Нет связи]
007:01:27.987'7773899': login on Alpari-Demo through demo.ru.0 a
007:01:28.916'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
007:01:29.146'7773899': previous successful authorization performed from78.85.179.29007:01:29.465'7773899': Signal - connecting to signal server
007:01:32.380 MQL5.community: activated for'IvanovSt', balance: 0.00007:01:33.491'7773899': auto connecting to a better access point demo.nl.3 a (ping is87.58 ms)
007:01:34.074'7773899': login on Alpari-Demo through demo.nl.3 a
007:01:34.961'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
007:01:35.190'7773899': previous successful authorization performed from78.85.179.29107:01:35.690'7773899': Signal - connect to (null) through proxy failed
007:01:35.692'7773899': Signal - connecting to signal server
107:01:46.526'7773899': Signal - connect to (null) through proxy failed
007:06:05.376'7773899': Signal - connecting to signal server
107:06:16.366'7773899': Signal - connect to (null) through proxy failed
007:11:05.538'7773899': Signal - connecting to signal server
107:11:16.394'7773899': Signal - connect to (null) through proxy failed
007:16:05.898'7773899': Signal - connecting to signal server
107:16:16.546'7773899': Signal - connect to (null) through proxy failed
007:21:06.059'7773899': Signal - connecting to signal server
107:21:16.695'7773899': Signal - connect to (null) through proxy failed
007:26:06.231'7773899': Signal - connecting to signal server
107:26:16.825'7773899': Signal - connect to (null) through proxy failed
007:31:05.322'7773899': Signal - connecting to signal server
107:31:15.904'7773899': Signal - connect to (null) through proxy failed
007:36:05.492'7773899': Signal - connecting to signal server
107:36:16.492'7773899': Signal - connect to (null) through proxy failed
007:41:05.641'7773899': Signal - connecting to signal server
107:41:16.600'7773899': Signal - connect to (null) through proxy failed
007:46:05.761'7773899': Signal - connecting to signal server
107:46:16.307'7773899': Signal - connect to (null) through proxy failed
113:48:55.766'7773899': connect failed [Нет связи]
113:48:58.787 MQL5.community: authorization failed
013:49:06.439'7773899': login on Alpari-Demo through demo.nl.3 a
013:49:07.350'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
013:49:07.694'7773899': previous successful authorization performed from78.85.179.29013:49:09.489'7773899': Signal - connecting to signal server
013:49:11.247 MQL5.community: activated for'IvanovSt', balance: 0.00013:49:12.322'7773899': auto connecting to a better access point demo.ru.0 a (ping is110.51 ms)
013:49:12.952'7773899': login on Alpari-Demo through demo.ru.0 a
013:49:13.927'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
013:49:14.226'7773899': previous successful authorization performed from78.85.179.29113:49:14.499'7773899': Signal - connect to (null) through proxy failed
013:49:14.502'7773899': Signal - connecting to signal server
113:49:25.371'7773899': Signal - connect to (null) through proxy failed
115:40:47.716'7773899': ping failed
015:40:56.544'7773899': login on Alpari-Demo through demo.uk.6115:40:56.922'7773899': Signal - connect to (null) through proxy failed
015:40:58.342'7773899': login datacenter on Alpari-Demo through demo.uk.6015:40:58.580'7773899': previous successful authorization performed from78.85.179.29015:41:03.561'7773899': auto connecting to a better access point demo.ru.0 a (ping is108.73 ms)
015:41:04.353'7773899': login on Alpari-Demo through demo.ru.0 a
015:41:05.442'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
015:41:05.683'7773899': previous successful authorization performed from78.85.179.29015:45:48.409'7773899': Signal - connecting to signal server
115:45:59.117'7773899': Signal - connect to (null) through proxy failed
015:50:47.683'7773899': Signal - connecting to signal server
115:50:58.576'7773899': Signal - connect to (null) through proxy failed
015:55:47.813'7773899': Signal - connecting to signal server
115:55:58.410'7773899': Signal - connect to (null) through proxy failed
016:00:47.995'7773899': Signal - connecting to signal server
116:00:58.744'7773899': Signal - connect to (null) through proxy failed
016:05:48.139'7773899': Signal - connecting to signal server
116:05:58.930'7773899': Signal - connect to (null) through proxy failed
016:55:38.388'7773899': Signal - connecting to signal server
116:55:43.512'7773899': ping failed
116:55:43.627'7773899': datacenter connecting failed [6]
016:55:44.206'7773899': login on Alpari-Demo through demo.nl.3016:55:44.929'7773899': login datacenter on Alpari-Demo through demo.nl.3016:55:45.130'7773899': previous successful authorization performed from78.85.179.29116:55:45.385'7773899': Signal - connect to (null) through proxy failed
016:55:45.387'7773899': Signal - connecting to signal server
016:55:50.102'7773899': auto connecting to a better access point demo.ru.0 a (ping is108.51 ms)
016:55:50.816'7773899': login on Alpari-Demo through demo.ru.0 a
016:55:51.740'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
016:55:51.975'7773899': previous successful authorization performed from78.85.179.29116:55:52.197'7773899': Signal - connect to (null) through proxy failed
016:55:52.199'7773899': Signal - connecting to signal server
116:56:02.885'7773899': Signal - connect to (null) through proxy failed
117:00:38.466'7773899': Signal - connect to (null) through proxy failed
017:00:38.471'7773899': Signal - connecting to signal server
117:00:49.347'7773899': Signal - connect to (null) through proxy failed
017:05:38.582'7773899': Signal - connecting to signal server
117:05:49.448'7773899': Signal - connect to (null) through proxy failed
017:10:38.814'7773899': Signal - connecting to signal server
117:10:49.448'7773899': Signal - connect to (null) through proxy failed
017:15:39.070'7773899': Signal - connecting to signal server
117:15:49.988'7773899': Signal - connect to (null) through proxy failed
017:20:39.140'7773899': Signal - connecting to signal server
117:20:50.037'7773899': Signal - connect to (null) through proxy failed
017:25:38.681'7773899': Signal - connecting to signal server
117:25:49.613'7773899': Signal - connect to (null) through proxy failed
120:28:25.312 MQL5.community: authorization failed
020:28:29.252'7773899': login on Alpari-Demo through demo.ru.0 a
020:28:30.757'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
020:28:31.037'7773899': previous successful authorization performed from78.85.179.29120:28:31.737'7773899': Signal - connect to (null) through proxy failed
020:28:31.739'7773899': Signal - connecting to signal server
020:28:32.760 MQL5.community: activated for'IvanovSt', balance: 0.00020:28:36.968'7773899': auto connecting to a better access point demo.nl.3 (ping is86.61 ms)
020:28:38.609'7773899': login on Alpari-Demo through demo.nl.3020:28:39.563'7773899': login datacenter on Alpari-Demo through demo.nl.3020:28:39.777'7773899': previous successful authorization performed from78.85.179.29120:28:40.179'7773899': Signal - connect to (null) through proxy failed
020:28:40.181'7773899': Signal - connecting to signal server
120:28:51.180'7773899': Signal - connect to (null) through proxy failed
020:33:21.958'7773899': Signal - connecting to signal server
120:33:32.570'7773899': Signal - connect to (null) through proxy failed
020:38:22.133'7773899': Signal - connecting to signal server
120:38:33.116'7773899': Signal - connect to (null) through proxy failed
020:43:21.702'7773899': Signal - connecting to signal server
120:43:32.678'7773899': Signal - connect to (null) through proxy failed
020:48:21.800'7773899': Signal - connecting to signal server
120:48:32.736'7773899': Signal - connect to (null) through proxy failed
121:09:11.873'7773899': Signal - connect to (null) through proxy failed
021:09:11.876'7773899': Signal - connecting to signal server
021:09:18.037'7773899': login on Alpari-Demo through demo.nl.3021:09:18.808'7773899': login datacenter on Alpari-Demo through demo.nl.3021:09:19.022'7773899': previous successful authorization performed from78.85.179.29121:09:19.220'7773899': Signal - connect to (null) through proxy failed
021:09:19.223'7773899': Signal - connecting to signal server
121:09:29.742'7773899': Signal - connect to (null) through proxy failed
121:14:10.611'7773899': Signal - connect to (null) through proxy failed
021:14:10.617'7773899': Signal - connecting to signal server
121:14:21.426'7773899': Signal - connect to (null) through proxy failed
121:14:24.957 MQL4 Market: failed to get list of user products (send request failed [12007])
021:19:10.762'7773899': Signal - connecting to signal server
121:19:21.578'7773899': Signal - connect to (null) through proxy failed
021:24:10.833'7773899': Signal - connecting to signal server
121:24:21.745'7773899': Signal - connect to (null) through proxy failed
021:28:01.670'7782527': one click trading has been disabled
121:28:06.836'7782527': connect failed [Неверный счет]
021:28:55.002'7773899': one click trading has been enabled
021:28:57.221'7773899': login on Alpari-Demo through demo.nl.3021:28:57.930'7773899': login datacenter on Alpari-Demo through demo.nl.3021:28:58.145'7773899': previous successful authorization performed from78.85.179.29021:28:58.205'7773899': Signal - connecting to signal server
021:29:02.333'7773899': ping to current access point demo.nl.3is85.24 ms
121:29:08.896'7773899': Signal - connect to (null) through proxy failed
121:29:10.909'7773899': Signal - connect to (null) through proxy failed
021:29:10.914'7773899': Signal - connecting to signal server
121:29:21.898'7773899': Signal - connect to (null) through proxy failed
021:34:11.095'7773899': Signal - connecting to signal server
121:34:21.636'7773899': Signal - connect to (null) through proxy failed
021:39:10.266'7773899': Signal - connecting to signal server
121:39:20.860'7773899': Signal - connect to (null) through proxy failed
021:44:10.469'7773899': Signal - connecting to signal server
121:44:21.003'7773899': Signal - connect to (null) through proxy failed
021:49:10.510'7773899': Signal - connecting to signal server
121:49:21.079'7773899': Signal - connect to (null) through proxy failed
021:54:10.745'7773899': Signal - connecting to signal server
121:54:21.699'7773899': Signal - connect to (null) through proxy failed
021:59:10.823'7773899': Signal - connecting to signal server
121:59:21.403'7773899': Signal - connect to (null) through proxy failed
022:04:10.978'7773899': Signal - connecting to signal server
122:04:21.558'7773899': Signal - connect to (null) through proxy failed
022:09:11.290'7773899': Signal - connecting to signal server
122:09:22.241'7773899': Signal - connect to (null) through proxy failed
022:14:10.278'7773899': Signal - connecting to signal server
122:14:20.963'7773899': Signal - connect to (null) through proxy failed
022:19:11.027'7773899': Signal - connecting to signal server
122:19:21.706'7773899': Signal - connect to (null) through proxy failed
022:24:10.751'7773899': Signal - connecting to signal server
122:24:21.541'7773899': Signal - connect to (null) through proxy failed
022:29:10.910'7773899': Signal - connecting to signal server
122:29:21.713'7773899': Signal - connect to (null) through proxy failed
022:34:11.061'7773899': Signal - connecting to signal server
122:34:21.960'7773899': Signal - connect to (null) through proxy failed
022:39:11.185'7773899': Signal - connecting to signal server
122:39:21.861'7773899': Signal - connect to (null) through proxy failed
022:44:10.610'7773899': Signal - connecting to signal server
122:44:21.561'7773899': Signal - connect to (null) through proxy failed
022:49:10.470'7773899': Signal - connecting to signal server
022:49:11.321'7773899': Signal - signal provider has balance 46476.69 USD, leverage 1:500022:49:11.332'7773899': Signal - subscriber has balance 10000.00 USD, leverage 1:500022:49:11.334'7773899': Signal - percentage for volume conversion selected according to the ratio of balances and leverages, newvalue10% (old value0%)
122:49:11.335 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
022:49:11.335'7773899': Signal - synchronization finished successfully
022:49:11.428'7773899': Signal - ping to signal server 93.22 ms
222:53:12.849 Expert MACD Sample AUDUSD,H1: removed
022:53:31.768 Alpari Limited MT4 build 840 stopped
022:53:35.480 Alpari Limited MT4 build 840 started (Alpari Limited)
022:53:35.480 Data Folder: C:\Program Files (x86)\Alpari Limited MT4
222:53:37.272 Expert MACD Sample AUDUSD,H1: loaded successfully
022:53:38.866'7773899': login on Alpari-Demo through demo.nl.3022:53:39.739'7773899': login datacenter on Alpari-Demo through demo.nl.3022:53:39.971'7773899': previous successful authorization performed from78.85.179.29022:53:40.427'7773899': Signal - 'Alex Week DEMO'for'IvanovSt' subscription found, 2015.10.21 expiration, enabled
022:53:40.427'7773899': Signal - money management: use 50% of deposit, equity limit: 0.00 USD, deviation/slippage: 0.5 spreads, copy SL/TP: enabled
022:53:40.427'7773899': Signal - connecting to signal server
022:53:40.845'7773899': Signal - signal provider has balance 46476.69 USD, leverage 1:500022:53:40.845'7773899': Signal - subscriber has balance 10000.00 USD, leverage 1:500022:53:40.847'7773899': Signal - percentage for volume conversion selected according to the ratio of balances and leverages, newvalue10%
122:53:40.848 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
022:53:40.848'7773899': Signal - synchronization finished successfully
022:53:40.946'7773899': Signal - ping to signal server 98.58 ms
022:53:41.671 MQL5.community: activated for'IvanovSt', balance: 0.00022:53:44.117'7773899': ping to current access point demo.nl.3is87.75 ms
Степан Иванов: Olá, mais interessante ainda, abriu automaticamente uma operação no aud/usd, fechou com take profit +50$, o provedor de sinal usa apenas o par eur/usd e tal operação em seu histórico não encontrei de onde veio? Eu realmente quero entender tudo, me ajudem!
Agora vamos dar uma olhada no diário, nas linhas que estão destacadas em cores:
106:49:57.901 MQL5.community: authorization failed
106:49:59.548'7773899': connect failed [Нет связи]
006:50:10.404'7773899': login on Alpari-Demo through demo.nl.3006:50:11.052'7773899': login datacenter on Alpari-Demo through demo.nl.3006:50:11.246'7773899': previous successful authorization performed from78.85.179.29006:50:11.904'7773899': Signal - connecting to signal server
006:50:12.473'7773899': Signal - signal provider has balance 44163.13 USD, leverage 1:500006:50:12.473'7773899': Signal - subscriber has balance 10000.00 USD, leverage 1:500006:50:12.475'7773899': Signal - percentage for volume conversion selected according to the ratio of balances and leverages, newvalue10%
106:50:12.476 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
006:50:12.476'7773899': Signal - synchronization finished successfully
006:50:12.572'7773899': Signal - ping to signal server 95.66 ms
006:50:12.575 MQL5.community: activated for'IvanovSt', balance: 0.00006:50:27.740'7773899': auto connecting to a better access point demo.nl.3 a (ping is87.93 ms)
006:50:28.342'7773899': login on Alpari-Demo through demo.nl.3 a
006:50:29.354'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
006:50:29.581'7773899': previous successful authorization performed from78.85.179.29007:17:29.289'7773899': instant order sell 1.00 AUDUSD at 0.69978 sl: 0.00000 tp: 0.69928107:17:29.669 Notifications: invalid MetaQuotes ID setting (Tools->Options->Notifications)
007:17:29.669'7773899': order was opened : #297283674 sell 1.00 AUDUSD at 0.69978 sl: 0.00000 tp: 0.69928007:17:35.925 Trades: use hosting service to speed up the execution - 1.74 ms via 'Netherlands (Webzilla Inc.)' instead of 87.93 ms
007:46:17.865 System to be shutdown, request for close Alpari Limited MT4
207:46:18.257 Expert MACD Sample AUDUSD,H1: removed007:46:19.955 Alpari Limited MT4 build 840 stopped because system shutdown
016:35:16.278 Alpari Limited MT4 build 840 started (Alpari Limited)
016:35:16.278 Data Folder: C:\Program Files (x86)\Alpari Limited MT4
216:35:25.740 Expert MACD Sample AUDUSD,H1: loaded successfully
...
A primeira linha - uma ordem de execução instantânea foi aberta para o AUDUSD e a segunda linha destacada mostra que o Expert Advisor MACD foi removido do gráfico AUDUSD, H1. Não há falha do serviço de sinais aqui - há uma presença clara do Expert Advisor MACD no gráfico do AUDUSD e 99% de que foi o Expert Advisor que abriu a ordem (ou você manualmente).
Agora vamos dar uma olhada no registro, nas linhas que estão destacadas em cores:
A primeira linha - uma ordem de execução instantânea foi aberta no AUDUSD e a segunda linha destacada mostra que o Expert Advisor MACD foi removido do gráfico AUDUSD, H1. Não há culpa do serviço de sinais aqui - há uma presença clara do Expert Advisor MACD no gráfico do AUDUSD e 99% de que foi o Expert Advisor que abriu a ordem (ou você manualmente).
Não culpo ninguém, de forma alguma! Só quero entender e conseguir a cópia automática das negociações).
Степан Иванов: Não culpo ninguém de forma alguma, apenas quero entender e realizar a cópia automática das negociações) ....
A cópia funcionou - você pode ver isso no arquivo de registro (provavelmente você atualizou o Windows XP para o SP3). A cópia funcionará a partir de segunda-feira. Vejo que você alugou uma hospedagem compartilhada - a hospedagem compartilhada também tem um arquivo de log e é útil examiná-lo para ver quais transações foram copiadas.
Stepan Ivanov: ... Eu não operei manualmente.
O especialista em MACD anexado ao gráfico AUDUSD,H1 fez isso para você.
Karputov Vladimir: A cópia funcionou - você pode ver isso no arquivo de registro (provavelmente você atualizou o Windows XP para o SP3). A cópia funcionará a partir de segunda-feira. Vejo que você alugou uma hospedagem compartilhada - a hospedagem compartilhada também tem um arquivo de log e é útil consultá-lo para ver quais transações foram copiadas.
Verei como isso funcionará na segunda-feira. De qualquer forma, muito obrigado por sua paciência e pela explicação detalhada de tudo o que precisa ser feito.)
Olá, o serviço dec é silencioso, escrevo aqui, não consigo assinar o sinal. Faço tudo da mesma forma que nas assinaturas anteriores, mas a assinatura não acontece, as seguintes mensagens são exibidas no registro:
2015.09.28 18:42:14.259 '1448120': Sinal - erro ao comprar o produto '???i' [129499] - 2015.09.28 18:42:10.022 '1448120': Sinal - iniciar assinatura no sistema de pagamento 'MQL5.Community' do sinal 'Tashimi' por 25,00 $ 2015.09.28 18:42:09.591 '1448120': Sinal - selecionou o sistema de pagamento 'MQL5.Community' para o sinal de assinatura 'Tashimi' por 25,00 $
Olá, o serviço dec é silencioso, escrevo aqui, não consigo assinar o sinal. Faço tudo da mesma forma que nas assinaturas anteriores, mas a assinatura não acontece, as seguintes mensagens são exibidas no registro:
2015.09.28 18:42:14.259 '1448120': Sinal - erro ao comprar o produto '???i' [129499] - 2015.09.28 18:42:10.022 '1448120': Sinal - iniciar assinatura no sistema de pagamento 'MQL5.Community' do sinal 'Tashimi' por 25,00 $ 2015.09.28 18:42:09.591 '1448120': Sinal - selecionou o sistema de pagamento 'MQL5.Community' para o sinal de assinatura 'Tashimi' por 25,00 $
Por favor, me ajude a entender.
Você tem fundos livres suficientes (não congelados) em sua conta MQL5 para a assinatura?
Você faz a assinatura pelo terminal MetaTrader 4 ou pelo site?
Olá, mais interessante ainda, abriu automaticamente uma operação no aud/usd, fechou com take profit +50$, o provedor de sinal usa apenas o par eur/usd e tal operação em seu histórico não encontrei de onde veio? Eu realmente quero entender tudo, me ajudem!
Então os sinais estão funcionando? Se sim, é bom. O arquivo de registro da guia "Journal" o ajudará a resolver o problema.
Olá, mais interessante ainda, abriu automaticamente uma operação no aud/usd, fechou com take profit +50$, o provedor de sinal usa apenas o par eur/usd e tal operação em seu histórico não encontrei de onde veio? Eu realmente quero entender tudo, me ajudem!
Agora vamos dar uma olhada no diário, nas linhas que estão destacadas em cores:
A primeira linha - uma ordem de execução instantânea foi aberta para o AUDUSD e a segunda linha destacada mostra que o Expert Advisor MACD foi removido do gráfico AUDUSD, H1. Não há falha do serviço de sinais aqui - há uma presença clara do Expert Advisor MACD no gráfico do AUDUSD e 99% de que foi o Expert Advisor que abriu a ordem (ou você manualmente).Agora vamos dar uma olhada no registro, nas linhas que estão destacadas em cores:
A primeira linha - uma ordem de execução instantânea foi aberta no AUDUSD e a segunda linha destacada mostra que o Expert Advisor MACD foi removido do gráfico AUDUSD, H1. Não há culpa do serviço de sinais aqui - há uma presença clara do Expert Advisor MACD no gráfico do AUDUSD e 99% de que foi o Expert Advisor que abriu a ordem (ou você manualmente).Não culpo ninguém de forma alguma, apenas quero entender e realizar a cópia automática das negociações) ....
A cópia funcionou - você pode ver isso no arquivo de registro (provavelmente você atualizou o Windows XP para o SP3). A cópia funcionará a partir de segunda-feira. Vejo que você alugou uma hospedagem compartilhada - a hospedagem compartilhada também tem um arquivo de log e é útil examiná-lo para ver quais transações foram copiadas.
... Eu não operei manualmente.
A cópia funcionou - você pode ver isso no arquivo de registro (provavelmente você atualizou o Windows XP para o SP3). A cópia funcionará a partir de segunda-feira. Vejo que você alugou uma hospedagem compartilhada - a hospedagem compartilhada também tem um arquivo de log e é útil consultá-lo para ver quais transações foram copiadas.
Olá, o serviço dec é silencioso, escrevo aqui, não consigo assinar o sinal. Faço tudo da mesma forma que nas assinaturas anteriores, mas a assinatura não acontece, as seguintes mensagens são exibidas no registro:
2015.09.28 18:42:14.259 '1448120': Sinal - erro ao comprar o produto '???i' [129499] -
2015.09.28 18:42:10.022 '1448120': Sinal - iniciar assinatura no sistema de pagamento 'MQL5.Community' do sinal 'Tashimi' por 25,00 $
2015.09.28 18:42:09.591 '1448120': Sinal - selecionou o sistema de pagamento 'MQL5.Community' para o sinal de assinatura 'Tashimi' por 25,00 $
Por favor, me ajude a entender.
Olá, o serviço dec é silencioso, escrevo aqui, não consigo assinar o sinal. Faço tudo da mesma forma que nas assinaturas anteriores, mas a assinatura não acontece, as seguintes mensagens são exibidas no registro:
2015.09.28 18:42:14.259 '1448120': Sinal - erro ao comprar o produto '???i' [129499] -
2015.09.28 18:42:10.022 '1448120': Sinal - iniciar assinatura no sistema de pagamento 'MQL5.Community' do sinal 'Tashimi' por 25,00 $
2015.09.28 18:42:09.591 '1448120': Sinal - selecionou o sistema de pagamento 'MQL5.Community' para o sinal de assinatura 'Tashimi' por 25,00 $
Por favor, me ajude a entender.
1. Sim, há fundos suficientes na conta.
2. Clico em Assinar no site e o terminal é aberto. Agora funcionou com a versão antiga build 840 em outro computador. Não funcionou na versão 880.
A pergunta foi cancelada porque não posso demonstrar o problema novamente.