Topic: Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic] - page 41. (Read 416703 times)

humm yea, maybe because you have to have enough on each side of the trade? I got this too and that was the reason, I think.

cant really trade on crypsty the trade amount choices are all to cock wont let you go all in or to higher number for set amount % cant calulate



same on btce invaild trade amounts in debug window

There is a poll on the bottom right hand corner of the website, Mintpal is not on the list but you could vote for "other".

Not sure if anyone mentioned it, but has Mintpal been suggested as an exchange to add?

after 2 days bot work increasing cpu usage again - above 15% of my i7. I dont care about it, but had not previously been

Won't save tradebots again. I'll puke if I have to set them up one more time. ;(

Supported Exchanges:
Btc-e
Bitstamp
CampBX
Cex.io
Cryptsy

Beginner: up to 2 bots running (for example one on btc-e and one on bitstamp)
Not all indicators are included.

Simple: up to 3 bots running (for example two on btc-e and one on bitstamp )
Not all indicators are included.

Advanced: Unlimited bots, all indicators included (for example trade all pairs at btc-e while trading on bitstamp and cryptsy all at the same time)

I see that you made a new license for more entry-level trials.  It seems unattractive though.  If someone were to want to just try it out, it seems to me that it would be much better if it were 1/10th the cost for only 2 months.  That way someone could play around with it for a minimal investment and see if they like it before paying for a full license.  After all, isn't that the general idea with this low-cost license?

I didn't see a list of supported exchanges on your site, nor a comparison of versions.  Could this be added to help us make a more informed purchase decision?

@cpusher:
We are trying to make it work using the spread orders.

BTW The coming targets/features are also listed to on the test-version page. This information is not posted here because i would like to avoid disappointment if a new feature fails.

@silverston:
This is by design. The roof-out sells the coins above the threshold and the roof-in buys the coins above the threshold. So they do different things and they should not be used at once.

@Hpotsirc:
Thanks for getting back to it and your advice to the readers. Its was indeed the trade-amount and it have to be at least a number with 2 decimals at Bitstamp. (for example: x.xx)

This problem was solved for me by Stephan. So i got to say: Thank you very much for the great support 
Anyway i just wanted to let you guys know that the problem was that my trade amount was to small for the API to process it even though amounts that small can be traded manually at Bitstamp. So if you have a similar problem you might want to increase your trade amount.

@Stephan

Safeties
 Dynamic adjusted roof-out safety and Dynamic adjusted roof-in safety show same charts. Roof-in price same as Roof-out price.

Stephan,

could you please add an insurance "switch coin position only after x% filled" (check with actual wallet and open orders)

Today i switched coin position with only 0,0000166% filled of the trade amount. i had cancel order insurance after 2 minutes, but it was filled for only 0,0000166% , the position was switched and the order was not canceled. (i was hoping it was canceled and after 2 minutes a new order was placed for a new price)

or other ways to deal with this like preventing to make buy/sell walls like spreading the trade.


this is also important to protect your investments with the droploss safeties. if it only sells a small part and hts thinks it's done(order not 100% filled), we're screwed !


hope you understand the importance and so you can improve this situation as soon as possible.

I did not do anything and say that the order was executed on 0%
so I write, this is strange

I have my doubts thats this is true. The log you posted showed the order was filled. This can only be if the order was not found anymore at the open order list.

The software sends out a cancel on the open order if it is still open after 10 minutes. This procedure only can fail is the order was filled for a part or if you are resetting the signals by pressing clear statistics.

order was filled after hour in new uptrend. why software dont close order after 10min? order was filled 0%.

Filling orders is of course done at the exchange itself. I think in your order was filled for a part. This gives the software the idea the order is done and there you go.

increased the size of the memory buffer - see what will happen next.

---------------------------------------------------------------------------------

and again - order not filled, but order still open at exchange

I am not really sure what has happened to your trade-bot. We did make some changes to the save system and its behind automated tests to. I did not expect to see anymore trade-bots that gets lost. (please note, inside your TradeBots -folder there is almost always a backup of your trade-bot in case you lost it. You only have to rename it back to .XML to restore the trade-bot.

At the current moment we are not (yet) planning version 0.9.9.4. The current version is looking to be working smoothly for now (except Hpotsirc below here, but that will be solved). So we already started to continue development on the new exchanges and features over here.

For Cex.IO i have 2 good recommendations. First of all try to trade with low amounts like 1 or 2 coins per bot. Secondly i can recommend to use the CancelOrder and set it to 3 minutes (or 4minutes). By default we are at 10minutes and this is to long for Cex.IO at the moment.

With these recommendations is it still not fully sure if the orders get trough, but it gets you really close. I have the same issue here and this is the solution as far as i have seen.

Version 0.9.9.3 has a solid feeovercome insurance. You can even test it yourself, it just a matter of setting up a trade-bot with the BlindSignal indicator and the insurance that you want to test. Then run a backtest and see what happens. (its for 99.9% sure that you see earnings/profits with this test setup, but still beware of the BlindSignal indicator, it does not give momentum. It only gives a blind signal to trade, so you are trading on the fee alone with this setup.)


Can you please contact me per PM or support ticket about bitstamp? I would like to see why this does not work or whats happening at your computer.

About the backtest... there are 2 reasons why you might see different results. First of all the start position of the coins (you saw this one already) and secondly the last record buy and sell prices. However, if you press Clear, Backtest and Clear again then the next backtest should show exactly the same results. This output must the equal.

About the auto tuning... this technology works very well, but its not said this technology is prefect. What the auto-tune does is trying to make the indicator active so they become responsive within 24-hours. Once there is a profitable buy and sell signal the tuning itself stops. However, sometimes this is just not possible. Maybe the market does not move enough or the settings of the indicators would become invalid. I that situation the auto-tune fails.

Just to tell... the auto-tune as it is right now works well, but we are still only at 33% of what is possible. We still have a few tricks to make this tuning even better that it is right now.


It is possible to see a little higher CPU usage if you compare version 0.9.9.2 and 0.9.9.3. If just the fee that has been read/verified each time. But this difference is very, very small. I did not even register it in the tests. (i need to say i have not updated my Atom here yet)

If you have performance problems then i recommend to:
- Reduce the memory usage (see server settings)
- Reduce the cache buffer size (see server settings)
- Disable the exchanges that you are not using (see server settings)

But i do not expect this would be needed at all, unless your memory is very limited or unless you want to reduce internet bandwidth.

maybe try to change the buffer size in the server settings.

in 0.9.9.3 I see big cpu usage in comparison with the previous version