Posts made by safv6

@fxDreema
I've been a paying subscriber for over 3 years now and I must say I am really disappointed by the lack of support. I'm not saying it's your responsibility to reply or to address every issue, I'm just saying I didn't expect to get no support whatsoever. I am now using a custom MQL4 code block to bypass the issue.
I do appreciate the awesome software, just didn't expect to be alone on this one.

@fxdreema @miro1360

Hi guys, I truly think that it has become impossible to make binary options EA's with fxDreema since a little while, maybe because of an update to fxDreema or something? It used to work, but I'm convinced it doesn't work anymore. Not on any broker, not for anyone who'd try.

I've tried everything, I've read every thread on binary options on this forum as well as everything there is to find on error 133 using Google before I started this thread 3 days ago. Maybe it's the "BO exp:" comment that's not properly added to the OrderSend line anymore, or maybe it's something else entirely, but again, I really think something broke. Either that, or it's user error somehow, but I really really doubt it.

I'm stuck here guys! And I'm sure I'm not the only one.

I'm really hoping for your support on this one!

Best regards

@fxdreema Hi Radoslav, I was rephrasing my question while you sent your reply just now. I tried my EA project and this example test EA on multiple brokers. All return the same error. The old EA that uses the same buy now block settings works fine, BUT when I generate a new mq4 file in fxDreema after loading OR reimporting the old working EA, the newly generated EA will not work at all.

So my answer to your question is: Yes, I'm sure that one EA (the one that I generated with fxDreema in the past) works fine and any EA I generate now doesn't. Same Buy now settings, same symbol, same broker. I'm not ruling out that it's user error somehow, but I just can't imagine what I could be doing wrong. I mean you see the example EA there, it should be working, right?

Thanks again for your time.

I'd like to rephrase my question in a way that may be a bit more clear if that's ok:
The example EA below should be suited to make binary options bets, right? In the past it worked fine, but now every broker I try it on returns this error: "Trade is disabled (133)". I've tried goMarkets, GDMFX and a bunch of others. All brokers return the same error. My old fxDreema EA's that trade the same size and expiry and everything, with the same "Buy now" block settings all work fine (unless I generate a new mq4 file for the old project; this newly generated version of my old working EA will not work either).

Simple binary option EA example: https://fxdreema.com/shared/Qz2H9VFBc

Am I doing something wrong here, or is there something wrong with the OrderSend syntax for binary options in fxDreema nowadays? It should look something like this, right?:
" OrderSend(Symbol(),OP_BUY,Lots, Bid,3,0,0,"BO exp:60") "
Maybe the "BO exp:60" comment is not coming through as it should for some reason? (I'm just guessing here)

Any help would be very much appreciated.
Thanks in advance guys!

Hi fellow fxDreema users,

I've made quite a few binary options EA's with fxDreema in the past with no problems, but now I'm trying to make another one and all of a sudden I can't get it to trade and I keep getting this error "New trade error: Trade is disabled (133)".
I can trade manually and my old fxDreema EA's still trade fine with the same Buy Now block settings, on the same symbol and with the same broker (GDMFX). Weird, right? But it get's even weirder:
So I took my old fxDreema EA that still trades fine and I imported the mq4 file into fxDreema (I love that feature by the way), but when I do that and generate a new mq4 file right from the imported project that traded just fine, the newly generated mq4 file will again not trade!

Here's an example of the Buy Now block that works in my old EA's, but doesn't work in a new one. Looks fine, right?: https://fxdreema.com/shared/Qz2H9VFBc

I feel like I've tried everything. Thoughts anyone?

@miro1360 Right, perhaps. I'm not sure though, but I kind of think that most users would prefer this functionality to be disabled by default, or to be adjustable in the Project Options menu or something, but hey, I'm not complaining! Your solution solved my issue!
Thanks again for all the help Miro!

Hi miro, that did the trick! I can't help but wonder though, why you wouldn't want to have the EA reinitialize when you change settings, because if you don't, the changes you make will not be applied, right? I don't really see the logic in that, but hey, this works for me, so thank you for the great support. I appreciate it!

Peace!!!!

Hi Radoslav and fellow fxDreema users,

My fxDreema EA's won't reinitialize / refresh when I change timeframes or settings while the EA is running.
I tried to create a simple EA with only 2 blocks just now, to share here as an example, but to my surprise that simple EA does reinitialize just fine. My more complex EA's won't though.
Does anyone have any idea what I did wrong?

Best regards,

Saf

@miro1360

Thanks so much for the swift reply! The TDI was a great tip! Thanks for that!
Do you perhaps also happen to know of an existing indicator that can do like a Momentum indicator on an ADX or something like that? I know questions like that are not what this forum is for, but I couldn't resist to ask.

Thanks again!

Peace!!!

Hi Radoslav and forum participants,

In MT4 one can apply an indicator to an indicator. For example you can apply an MA onto an RSI by selecting "Previous Indicator's Data" or "First Indicator's Data" in the MA's "Apply to" drop-down menu. In fxDreema though, these options are not in any of the indicator's "Apply to" drop-down menu. Does anyone here know how to go about this?

Thanks in advance!
Regards,

Saf

Ah awesome! That solved it for me. One of the indicator's data type was defined as integer, while it should've been a string. Apparently this discrepancy made the EA load up the indicator multiple times.

Thanks for the help and the swift reply.
Regards,

Saf

So... I thought I'd give an example, just to be clear:
When I make a test EA with only a yellow "Comment" block that's set up to display a custom indicator's value at the top of the chart and I backtest it in virtual mode, then once I press the stop button on the mt4 strategy tester, the chart gets flooded with many instances of that one custom indicator. I noticed this before with an other indi, but I didn't bother to try and figure it out back then, because that particular indi wasn't all that heavy. The indi I'm trying to work with right now though is a bit more heavy and having all instances loaded up at the same time is just killing for the EA's performance.

I hope I'm doing something wrong here.
I'm looking forward to your reply.

Best regards,

Hi Radoslav,

Thanks again for all you do. I have a question about the way fxDreema loads up instances of custom indicators.
So it seems that when I make fxDreema read from a custom indicator's buffer, it loads it up many many times, making things real slow. If it has to load it up each time it reads a buffer value instead of reading from the same single instance, that'd be ok I guess if there's no other way, but once it loads up a second instance, why doesn't it dump the first one? Is there something I'm missing here?

Thanks in advance for your reply,
Regards,

Saf

Hi Radoslav,

I have a question about text placement. Would it be possible to have an fxd EA place a text on the left side of the chart (text placement by X coordinate), right on the green dotted trade line (text placement by price)? I was trying to achieve this using the "Draw Text" block, but it seems my only options are to use either "text placement by time and price", OR "text placement by X and Y coordinates", but not a combination of the two. You see, I'd like to have the text's X coordinate fixed to have the text on the left, no matter the timeframe or zoom factor, but at the same time, the Y coordinate should actually be (slightly above/below) the trade's open price.

Any suggestions would be highly appreciated!
Thanks again and please keep up the good work

Best regards,

Saf

Hi Radoslav,

I am trying to make a grid-based EA, using the "pending orders in grid" block, in which "(every next) Volume Size" is doubled using the Gradation Setting. Some brokers though only allow the volume size per trade to be conciderably small (like 10.0 lots). Can you give me any advice on how I can make the EA respect the broker-sided volume limitation and make the EA use multiple trades instead when the limit is gonna be reached?
For example: When a pending order in the grid has a lot size of 8.00 and the next grid level should be traded with doubled the volume (16 lots), can you think of a way to make the EA use 2 trades to get to that 16 lots instead of 1 trade? Also for the next grid level the volume size should be 32 lots. In this case there would be at least 4 trades needed to get to 32 lots if we want to respect that maximum lot limitation of 10.

I made a complex construction using multiple formula blocks to achieve this, but it got real messy and inefficient, so any advice would be much appreciated!
I hope the above makes sense. I didn't know how else to explain it

Also, (as if I didn't take enough of your time already with the question above), I would really like to make the whole grid invisible somehow and use market orders instead of pending orders while still having the ability to use the handy "Gradation Settings" for every next order and without making a big mess with a huge formula-chain. Any advice on this would be really really appreciated as well!

Thanks again for your time,
Best regards,

Saf

Ah thanks so much for the extensive answer!

Right after posting this question though, I realised that I already answered my own question by saying that boolean values are just a numeric (0 or 1) value internally. So the actual answer to my question should be: Make the right operand "Numeric" "1", instead of "Boolean" "True", and there you go! The warning message is gone!
(correct me if I'm wrong though)

https://fxdreema.com/shared/uFAvkIh7b

Gotta love fxd
Thanks again!

Cheers

Hi Radoslav,

I have a question regarding using boolean values inside conditions. I must be doing something wrong...

Whenever I make a condition like the one you see on Init in the shared example below, it works just fine, but MetaEditor returns this warning when trying to compile the mq4 file: "expression is always false".
Again, it works just fine and I understand a boolean value is basically just 0 or 1 internally, but maybe you know what I could do to prevent the warning message when using bool conditions?

Here's a working example where the condition "on Init" triggers block 6 "on Tick" to go on: https://fxdreema.com/shared/IaoNWwzae
Here's the warning MetaEditor shows when compiling: https://drive.google.com/file/d/0B9owZMPMRrkSRlpDLTZBZVpEOEk/view

Any advice or help would be much appreciated!
Best regards,

Saf

Yes! It works! That is awesome man! Thank you so, so very much!!!!

Thank you for trying it out and taking the time to post some screenshots, but the prices you are placing the orders at, end with .0 and .5. An EA based on MA's or BB's or something like that will try to order at price levels ending with .1, .2, .3, .4, .6, .7, .8 and .9 as well (try this simple EA for example: https://fxdreema.com/shared/rFOj02bZb ). This will give you errors like this 80% of the time or more:
By EA (journal): https://charts.mql5.com/8/182/ger30sep1 ... es-plc.png
By EA (experts): https://charts.mql5.com/8/183/ger30sep1 ... es-plc.png
Manually (journal: https://charts.mql5.com/8/183/ger30sep1 ... -plc-2.png
So if one would try to place a pending order manually (F9) on a price that doesnt end with .0 or .5, the server will return the error as well. I can't find a sollution and there are so many NormalizeDouble lines in the code, I can't figure out where to set what to 0.
If you might think of any sollution that would help me excluse all other decimals from being used for entry, sl and tp, I would appreciate it so much.

Thanks again,

Saf

Hi Radoslav,

Thank you for your swift response. I am quite sure I'm not doing anything wrong, but I am also sure there must be something I can do to prevent the issue from occuring.
Note that when trying to place a pending order manually on a price that ends with a decimal that's not .0 or .5, the server will return the error as well. So I would asume it's definitely a broker/data feed thing. If I would just be able to make the EA avoid those 8 other decimal digits, the issue would be solved.

Here's a broker that uses a 0.5 increment on for example the symbol Ger30Sep15: https://www.activtrades.com/
Here's a simple project that uses a 14 SMA to place its orders with an offset from the current price: https://fxdreema.com/shared/rFOj02bZb
Even if no SL or TP is being sent with the order, the server will still return an error like this 80% of the time: "'1106597': order buy stop 0.10 Ger30Sep15 opening at 11581.9 sl: 0.0 tp: 0.0 failed [Invalid S/L or T/P]"

Any help would be so much appreciated. Even if it would mean having NormalizeDouble set to 0 for all SL, TP and Entry levels the EA orders if there's no other way.

Again, thanks so much in advance,
Best regards,

Saf