Posts made by Andermaiden2nd

@xiroko1 este tema no debería estar en esta sección ya que es la de tutoriales y en su lugar debería ir en la sección de preguntas y respuestas. Habiendo dicho esto, permíteme aclarar bien lo que es Renko y que no es.

Renko no es un indicador si no un modo diferente de trazar las cartas de precio. Las cartas Renko son un tipo de carta en donde las velas en lugar de abrirse y cerrarse con el paso del tiempo se abren y cierran con el avance del precio (en el eje vertical) ya sea en uno u otro sentido. Al poner un "indicador renko" en una carta de Meta Trader lo que aparece en la carta es un botón que al presionarlo abre una nueva ventana que dice "offline chart" o sea "carta fuera de línea" donde genera las barras renko a partir de los datos de tick. A esta nueva carta que se genera se le pueden cargar todos los mismos indicadores que a la carta común, las mismas medias móviles y demás y los mismos EAs. Por ende la pregunta no es como se hace un EA para velas renko porque cualquier EA va a funcionar si lo pones en una carta con velas Renko, si no más bien ¿como hacemos para hacer backtesting con velas renko?. En ese sentido ya hay gente que ha encontrado una forma y te paso el link https://www.forexfactory.com/showthread.php?t=572375 .

Por último hay algo que tener en cuenta y es no confundir las cartas renko con un indicador (no recuerdo su nombre) que emula en las cartas comunes
las velas renko dibujando rectángulos en la carta, pero esto es sólo visual ya que el resto de los indicadores se siguen calculando a base de las velas comunes, lo que desvirtua el propósito de las velas Renko.

Saludos

Nevermind. It seem trades do inherit the preceding pending order's ticket number after all.

Hello. Does anybody know how to refer to a trade that comes from a specific order?
What I mean is that you can save the ticket number of a trade or an order and keep check of it but, when a pending order turns into a trade the ticket number changes and you cannot refer to the event of an order triggering. When a trade closes you can check how it was closed but you cannot check how a trade is open, to check if it was open by a specific pending order you have a ticket number from.

@purplecash Creo que entiendo lo que quieres hacer, pero no te va a funcionar con esos bloques por varias razones.

1. Para empezar te vendería en cada tick (luego de hacer cuatro veces unos cuantos chequeos que no afectan nada porque no están conectados a nada) si no fuera porque antes te va a dar un error lo que nos lleva al siguiente punto.
2. Lo que viene luego del bloque de bucle hace lo siguiente: primero asigna a una variable "periodhigh" el valor -10 (las variables son cero por defecto) y luego intenta asignarle a una variable "vela high" el precio más alto de un período de velas que está en negativo por lo que va a dar un error por que esas velas todavía no ocurrieron (la ID de las velas aumenta en números positivos cuanto más atras uno vaya siendo la de ID "cero" la vela actual, la "uno" la anterior, la "dos" la de dos velas para atrás, etc.)

Esto debería funcionar aunque no lo he probado.
https://fxdreema.com/shared/z6zQXvFud

@richard96816 I have two questions:

1. The tests you did that you say are profitable, which data are they made with?

I say this because if you use MT4's default tick data (which is Metaquote's tick data) you'll be in the realm of fantasy more times than not (more so if you go for scalpers or anything price-sensitive). For MT4 the only sort of solution I've found is "Birth's Tick Data Suite", a program that merges with MT4 and let's you use actual tick data from some brokers (at first it was only from this swiss broker called Dukascopy but now there is from a couple other brokers too). It's not free, it costs about a hundred bucks and you'll also have to download some Gigabytes of tickdata but it's worth it.
If you use MT5 though, I think it comes with better tick data or at least with spread, but I don't know how reliable it is 'cause I don't have experience with it.

2. I don't know what you ment by "Expect a few margin calls due to fxDreema aggressive risk management of 0.01 lots" so please explain.

As for the other points I don't see any fault.

@yader-mayorga Con esa configuración, reseteando el contador, debería seguir abriéndote operaciones en cada cruce. A no ser que sea en MT5 que te agrupa todo en una operación, creo. Chequeá los bloques "Counter: Reset" que tengan el número bien.

You can always make a custom betting progression.

@timmyhanke yes, for what I'm seeing in other topics the timer seems to be the way to go (specially that way, setting the timer to 1 second and skipping X seconds).

@miro1360 , @timmyhanke you are both right, I've made some tests and the "on Tick" check seems to happen not necessarily at the start of the candle but rather whenever a new tick is made.
The reason why I'm looking for a way to do time related checks is because of news trading (being able to leave an oco order let's say 3 seconds before the news is useful as it reduces the chance of it being hit prematurely before the news rather than a whole minute before). I've managed to get to work something involving the delay block to have accuracy in seconds (sort of...)

The problem with the delay block is that the delay doesn't start exactly at the start of the new M1 bar so the delay between the start of the candle and the first tick will transfer and add to the expected delay. That way if you want to set a pending order 10 seconds before the news you could have it placed anything from 10 seconds before to a few seconds after the news, so while it's better than nothing, it's still not accurate enough (my goal was actually to leave an order 3 second before the news as I usually do manually).
I will try to play around with the timer and see if I can do some advance in that field. I'll let you know if I find something.

Hello everyone, I was wondering... does a new M1 bar count as a new tick even if there was no change in the price? I guess what I'm asking is if a block in the "on tick" section will be checked at the start of any bar regardless of whether there was an actual change in price in that moment or only if ther is change... (i.e. a new M1 bar starts but the price keeps in the same tick and there's a new tick only after 10 seconds)

If what you are trying to do is to open a trade when it crosses an MA and then close it when it crosses that same MA again then you need to know ther is a parameter in the "price vs indicator" block (at least when you choose to make the cross with an MA) that says "Minimum turnover distance". That is the distance it has to go away (from the MA) before crossing it again to effectively count it as another cross.

@david197 linking a block after the turn on/off block will only execute said block. If you don't write the ID of the block you want to turn on/off in the specified input field (of that turn on/off block) then that block won't do anything.

@cheaponreay01 check for a link in this topic https://fxdreema.com/forum/topic/5155/how-do-i-use-the-edit-field for a tutorial about the edit field made by miro1360 which you'l find to be very useful.

@alvarez you can draw two blocks to have double top and double bottom. Remember though to remake by hand the constants as they do not translate well in the shared example. The details of said constants are on the topic.

@fxDreema Yes, they do dissappear from the project. Both the blocks with characters in their ID as well if you set a block ID as 0 (zero).

check here, you might find the example given there useful at least to some extent. https://fxdreema.com/forum/topic/5108/boxes/11

@mpantogi can you explain a little furter what you want to achieve? You can set a distance (trailing offset) from where the trailing stop would start and if you want to set it in break even before the trailing starts then you need to set a break even set point before said trailing start.

@ali1 You might find useful to check the examples to get started https://fxdreema.com/examples#Constants-and Variables
Now for the sake of this case, constants are inputs that are unchangable to the program while variables are changable inputs the program can manipulate (this is the kind of input with which you will manipulate data inside any program).

Edit: I forgot to change on the right side too the mutiplier which should also go in the adjust field below (where it says "Adjust the result (optional):" just above the variable field) instead of the one above in the area marked in red.

@ali1 for "Candle High– Candle Low" you can pick it from "candle/candle total size (pips)" and if you want it for last candle just set candle ID to 1. Here it goes a visual example as to how the formula block should look.

@antbytes here you go