 Show Posts
|
|
Pages: [1] 2 3 »
|
Is there a log file that I can look through to see what is causing an issue? I added a restart crontab as a hacky fix for now. Unsure if it will work. On Asus DCII 280x x 6 : {
"pools": [
{
"name": "TradeMyBit_X11",
"url": "stratum+tcp://west01.us.trademybit.com:4010",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "darkcoin-mod",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_X13",
"url": "stratum+tcp://west01.us.trademybit.com:4011",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "marucoin-mod",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_X15",
"url": "stratum+tcp://west01.us.trademybit.com:4012",
"user": "x",
"pass": "x",
"algorithm": "bitblock",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_Nist5",
"url": "stratum+tcp://west01.us.trademybit.com:4013",
"user": "x",
"pass": "x",
"algorithm": "talkcoin-mod",
"profile": "Nist5"
},
{
"name": "TradeMyBit_Scrypt-N",
"url": "stratum+tcp://west01.us.trademybit.com:2220",
"user": "x",
"pass": "x",
"profile": "Scrypt-N"
},
{
"name": "TradeMyBit_Scrypt",
"url": "stratum+tcp://west01.us.trademybit.com:3330",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "zuikkis"
}
],
"profiles": [
{
"name": "X-Coins",
"intensity": "16",
"gpu-engine": "1100",
"gpu-memclock": "1800"
},
{
"name": "Scrypt-N",
"intensity": "13",
"gpu-threads": "1",
"gpu-engine": "1000",
"gpu-memclock": "1500",
"thread-concurrency": "10240"
},
{
"name": "Nist5",
"worksize": "64",
"intensity": "18",
"hamsi-expand-big": "1",
"gpu-powertune": "8"
}
],
"hamsi-expand-big": "4",
"worksize": "256",
"thread-concurrency": "8192",
"gpu-threads": "2",
"gpu-powertune": "20",
"gpu-engine": "1070",
"gpu-memclock": "1600",
"auto-fan": true,
"gpu-fan": "50-85",
"temp-target": "75",
"temp-cutoff": "95",
"temp-overheat": "85",
"api-listen": true,
"api-port": "4028",
"api-mcast-port": "4028",
"api-allow": "W:127.0.0.1",
"queue": "0",
"expiry": "1",
"show-coindiff": true,
"no-submit-stale": true,
"failover-only": true,
"failover-switch-delay": "30",
"extranonce-subscription": true,
"no-extranonce": true,
"hotplug": "5",
"no-restart": true,
"remove-disabled": true
}hmm have you tried all the different algo's individually to make sure they all work? i know TC for nscrypt is about half of what it is for scrypt also if you recently updated to 14.6 drivers TC will need to be reevaluated other than that, your cards seem to be able to run way higher mem clocks than any of mine (sapphire 290x BF4 edition, and gigabyte 290 windforce) mine crash if i go above 1400 for any length of time They all do work by themselves. I just added the scrypt-n today, so I know it didn't cause the locks in the past few days. Going to remove scrypt-n for now just to keep things simple. In sitting here at work, I have watched it switch back and forth multiple times without issue. Do these things kinda pop up randomly? Work great with no HW errors or rejects and then boom dead? I appreciate your help!  |
|
|
|
Has anyone found a solution for the full machine lockup?
I searched through this thread and found a few people also running into this, but without resolution.
I'm assuming it has to do with a GPU going sick and bringing down the whole shabang.
My mine is headless, so it's hard to tell what happened other than after about 24 hours it sometimes becomes unresponsive and requires a power cycle. :-/
hard to say without knowing more about your setup but generally it has to do with setting TC or clocks too high I cant stress enough how important it is to curb your GPU clocks to keep the switching working right. If you are pushing one algo too hard and a switch comes along, chances are the card will go SICK and DEAD after the driver crashes.
Is there a log file that I can look through to see what is causing an issue? I added a restart crontab as a hacky fix for now. Unsure if it will work. On Asus DCII 280x x 6 : {
"pools": [
{
"name": "TradeMyBit_X11",
"url": "stratum+tcp://west01.us.trademybit.com:4010",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "darkcoin-mod",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_X13",
"url": "stratum+tcp://west01.us.trademybit.com:4011",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "marucoin-mod",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_X15",
"url": "stratum+tcp://west01.us.trademybit.com:4012",
"user": "x",
"pass": "x",
"algorithm": "bitblock",
"profile": "X-Coins"
},
{
"name": "TradeMyBit_Nist5",
"url": "stratum+tcp://west01.us.trademybit.com:4013",
"user": "x",
"pass": "x",
"algorithm": "talkcoin-mod",
"profile": "Nist5"
},
{
"name": "TradeMyBit_Scrypt-N",
"url": "stratum+tcp://west01.us.trademybit.com:2220",
"user": "x",
"pass": "x",
"profile": "Scrypt-N"
},
{
"name": "TradeMyBit_Scrypt",
"url": "stratum+tcp://west01.us.trademybit.com:3330",
"user": "x",
"pass": "x",
"nfactor": "10",
"algorithm": "zuikkis"
}
],
"profiles": [
{
"name": "X-Coins",
"intensity": "16",
"gpu-engine": "1100",
"gpu-memclock": "1800"
},
{
"name": "Scrypt-N",
"intensity": "13",
"gpu-threads": "1",
"gpu-engine": "1000",
"gpu-memclock": "1500",
"thread-concurrency": "10240"
},
{
"name": "Nist5",
"worksize": "64",
"intensity": "18",
"hamsi-expand-big": "1",
"gpu-powertune": "8"
}
],
"hamsi-expand-big": "4",
"worksize": "256",
"thread-concurrency": "8192",
"gpu-threads": "2",
"gpu-powertune": "20",
"gpu-engine": "1070",
"gpu-memclock": "1600",
"auto-fan": true,
"gpu-fan": "50-85",
"temp-target": "75",
"temp-cutoff": "95",
"temp-overheat": "85",
"api-listen": true,
"api-port": "4028",
"api-mcast-port": "4028",
"api-allow": "W:127.0.0.1",
"queue": "0",
"expiry": "1",
"show-coindiff": true,
"no-submit-stale": true,
"failover-only": true,
"failover-switch-delay": "30",
"extranonce-subscription": true,
"no-extranonce": true,
"hotplug": "5",
"no-restart": true,
"remove-disabled": true
} |
|
|
|
|
Has anyone found a solution for the full machine lockup?
I searched through this thread and found a few people also running into this, but without resolution.
I'm assuming it has to do with a GPU going sick and bringing down the whole shabang.
My mine is headless, so it's hard to tell what happened other than after about 24 hours it sometimes becomes unresponsive and requires a power cycle. :-/
|
|
|
|
I've added port 4012 to the multi-multi.. this is for x15.
I know some of you may still only be mining x11 and x13.. so a solution to keep mining those algos is to setup your sgminer config so that:
pool 0 - 4011
pool 1 - 4440
or
pool 0 - 4010
pool 1 - 5550
For those wanting to use all 3, I suggest using a normal multi as a failover, so something like this:
pool 0 - 4012
pool 1 - 4011
pool 2 - 4440
This way, regardless of what happens, you'll at least be mining on 4440
Thanks!
Also, if anyone has a 100% working sgminer5 x15 multi config, would you mind putting it in pastebin so I can add it to the getting started section?
Here is a working config in case someone needs it. http://pastebin.com/Te0i4Me9X11/X13/X15/Scrypt-n I would really love a Scrypt-N multiport so we can get plain scrypt in the list as well. |
|
|
|
I ended up figuring it out. I had to update to the .NET Framework 4.5 version. It would be nice I'm sure for other potential users if this information was clearly documented somewhere. Other than that looks pretty neat! Thank you!  This should be listed somewhere. Good point. |
|
|
|
Cryptsy is just Crapsy, they just cant get their act together. Buy and Sell orders dont go through or disappear ect.
We need an alternative to Cryptsy, maybe mintpal if they have an ok api , what other exchange with lots of coins has good volume?
Honestly I think mintpal is the best option. They have some of the highest volumes for the most active coins. I think they have a API that is currently in beta, hopefully it get released soon. God I would love that... |
|
|
|
Hi Bajawah
Thank you for the insight - yes, it was clever.
The orders were sent to crypsty but stayed there in the queue forever, or they were only partially executed. As a result the wallet at haas did not match the actual status up there at the programmed time for the next signal detection-
I think I better switch to another pair and/or exchange - this is a headache -any suggestion of a good candidate to start with ?- the goal is not making great profits (yet) but putting the machine to work seamlessly by trying the different indicators available.
Cheers
Pick a pair that has super high volume and swings in price ( ignoring DOGE ). I would say DRK, but thats just madness right now... lol Sort by volume, look at charts and go from there. Best profit I find is when the price just sin waves horizontally for a while. Long time thread lurker first time poster.
I have been getting more and more frustrated with some of the changes in this new version. I am probably doing something silly so I figured before it get's worse maybe I should ask. For the example I bring up lets assume we are using 2 bots. One on btc-e and one on bitfinex and lets also assume we are using a trade value of 3 btc.
My issue's are with placing and pulling orders. The current max timer value for an order to be left open seems to be 10 minutes (I say this cause the UI won't accept a value larger than that for me). In my opinion this sometimes isn't long enough to allow for the entire order to get filled. So you run into one of two scenarios. Your order gets half filled then pulled which leads to the bot getting permanently stuck because if he sold .20 btc out of 3btc it now only has 2.8 btc left and it isn't keeping track of that so it just throws endless error after error that the current available wallet value isn't right.
Only way I have found to get the bot unstuck is to force a buy or sell command or manually change the trading value (to a value of $totaltrade - $filledportion) and then change it back after the trade is successful. Both aren't the best solutions due to the current bot setup because it requires console access.
I guess my point here is it needs to be tracking how much of the order was filled so that it doesn't still try and trade the full amount after it would also be nice to be able to adjust that time above 10 mins (unless i'm clearly missing a case where a bunch of attempted buy orders not getting filled is a bonus). Perhaps this will get fixed when the split order command returns. Maybe I should be using more bots with a smaller trading value so it doesn't take so long to fill orders?
This seems like a pretty silly one. I can't really complain though even with the bots getting stuck they are still up a few hundred fiat dollars. Just frustrating to return to check the bot progress a day later and realize its been trying to sell 3 btc's 32 times but one of the random orders got 1% filled and stuck the bot.
I have never tried using anything more than 10min, so I can't comment on that. But, to fix your other problem, use percentage trade instead of a fixed value. That way, if it doesn't fill all the way, it doesn't get stuck. |
|
|
|
Hi all, first post, I'm just a noob at trading and I am finding a stange behaviour in my first steps with the haas, can someone tell me if I am doing something wrong? - I put some DOGE (approx 20K) in the wallet and I am trying to trade them @cryptsy - I am running the beginners license, either with the classic or web front-ends - After much thinking I managed to set up a "bulletproof" bot consisting of a standard RSI plus two insurances, i.e. overcome fee costs and never sell below last buy. The idea was not to lose it all too early eaten by trade fees so I was extra cautious - The backtests went well and showed small profits, then I cleared the stats and activated the trading. - I let it run for a while and found out that the 1st trade buy or sell always works well, but right after that, the wallet amount reading goes crazy and prevents further trading. It doesn't match the real amount left in the Exchange. e.g. the 20.000 initial Doges, minus the trade amount which is currently 5000 - but it could be a lower or higher value, in the end it does not seem to impact the weird behaviour... After the first trade the log reads something like "The current trade amount(5000) exceeds the current available wallet amount (80,98785389)" or a similar tiny amount vs. what is actually left in the invested side... - I can't find where to edit the wallet contents in order to restore the right amount and carry on... Any ideas? Thanks so much in advance! Can you check your logs to see if the orders went through correctly? My guess is they didn't. Cryptsy along is a pain to work with because you can't cancel orders. Then DOGE is impossible because the volume is insane and nothings seems to ever get fully executed. So, it's the perfect storm of crazy. Why the wallet reading is off (what I think) is your bot is losing track of it's position and thinks its ready to buy when it has not sold yet. etc. |
|
|
|
@Stephan224;
Is it possible to make 'CancelOrderAfterXmin’ Insurance work in Cryptsy?
It is very inconvenient that I have to keep manually cancel unfulfilled orders in Cryptsy all the time.
I saw another Bot can cancel orders in Cryptsy, so maybe Cryptsy still has some ways to support order cancellation?
How can you cancel unfulfilled orders manyally from Crapsy? My 'cancel order' button says that "order cancelling not supported for Cryptsy". What would be a good trading strategy to not to get orders stuck all the time? I have modified my strategies at Crypsy to not care about the inability to cancel. ex. Using EarningsOnProcentagetrade, it doesn't matter if it doesn't fill because you are going to buy/sell at once price anyway. Down side is that it might sit for a bit and then have to be manually fixed / poked at. In good volume ( DRK right now ), it works well. For a general devaluing set the down % higher than up. Reverse that for a coin gaining value. Hope that helps. |
|
|
|
|
One way I have been working the VTC volume is using multiple bots. Fixed amount trade, earnings on percentage trade indicator, and cancel order ( like it does anything on f-ing Cryptsy ). I set each bot a bit different. ex 0.5/0.5 % change, 1.0/0.5 % change, and 0.5/1.0 % change. This way the bots tried different things and buy/sell at different points. Then you can set a manual drop sell point in case it falls through the floor. Or dynamic if you want, w/e.
|
|
|
|
the other thing make the situation worst is it seems like Haasbot not use the last price as limit order price, it tend to use a price slightly low/high than last price. This kind of strategy can generate more profit in a flat market, but just a disaster in a trend market…order never get chance to be executed
I have seen this as well. Unsure if it is due to the market moving between 1min ticks or what. |
|
|
|
Is it possible to let either ‘Marketing Order’ or ‘Cancel Order’ work on Cryptsy?
Limit order has very low chance to be executed in a quick downtrend. (and cancel order insurance is just not work also.)
Thanks.
This would be great. Trying to limit sell a stop loss is nigh impossible on Crapsy. As a whole, per bot ( or even safety! ) toggle for market / limit ( buy/sell ) would be really really really useful! |
|
|
|
I'm not sure if im the only one but I have been having trouble over past 3 days buying a beginner licence.
have emailed 4 seperate times including a 5th as a trouble ticket to Haasonline.
Looking for any feedback on what might be going wrong (for me i got through order process and it sends me to bitpay area and screen goes blank).
any feedback from you guys would be great and its been fun reading up to page 28 and counting!
regards,
A.
I have always gotten a response via support ticket in ~24 hours. It's a software?
I think it is a website before?
Dose it free of charge?
Wut? |
|
|
|
|
This looks awesome!
Will we be able to one click submit arbitrage limit orders?
|
|
|
|
Hi
Can anyone help me with the following questions? (I've only just purchased the software, so I am not yet sure about things)
1. Once I've setup my bot and used auto setup to generate the settings, will redoing auto setup on a daily basis help the bot or should I leave it alone.
2. If my bot places an order which doesn't complete in time for the bot, should I cancel it so the bot can use the coins or ignore it (since if I wait long enough the order will probably be fulfilled eventually).
Thanks!
1 - Depends heavily on the type of indicator. Something like a high/low indicator would benefit from that or just manually moving it. 2 - This is the bane of all things. Depending on your trade amount type, the exchange, and the cancel order insurance the answer is... maybe. For things like Cryptsy you are kinda just boned because order just sit there forever. On BTCe BTC/USD I never have any issues. You run the risk of the bot trying to buy at 10, then the order sitting because you have all your coins allocated to that position and it can never do anything until you fix it. Especially if the price never comes back to 10. Not using Cryptsy, using 'all in' or 'percentage' for your trade amount and 'cancel order insurance' helps this heavily. I have really grown to hate Cryptsy... Thanks Bajawah, that's a big help, your advice is very much appreciated. I've moved some funds from Cryptsy to BTCe and I am seeing what happens. It really comes down to API quality, and volume. It is possible to get dead trades on BTCe, but the volume is so much higher than Crapsy that the chance is a lot lower. I have not compared the API. Stephan
im really wondering why we, People that only have beginnerversion, cant use storsi indicator.
i think its essential. why ist not in all verions ?
Personally when I had the beginner license I would have rather had a dynamic stop-loss. So it's a "to each is own" situation. Guess you have to draw the line somewhere? lol |
|
|
|
Hi
Can anyone help me with the following questions? (I've only just purchased the software, so I am not yet sure about things)
1. Once I've setup my bot and used auto setup to generate the settings, will redoing auto setup on a daily basis help the bot or should I leave it alone.
2. If my bot places an order which doesn't complete in time for the bot, should I cancel it so the bot can use the coins or ignore it (since if I wait long enough the order will probably be fulfilled eventually).
Thanks!
1 - Depends heavily on the type of indicator. Something like a high/low indicator would benefit from that or just manually moving it. 2 - This is the bane of all things. Depending on your trade amount type, the exchange, and the cancel order insurance the answer is... maybe. For things like Cryptsy you are kinda just boned because order just sit there forever. On BTCe BTC/USD I never have any issues. You run the risk of the bot trying to buy at 10, then the order sitting because you have all your coins allocated to that position and it can never do anything until you fix it. Especially if the price never comes back to 10. Not using Cryptsy, using 'all in' or 'percentage' for your trade amount and 'cancel order insurance' helps this heavily. I have really grown to hate Cryptsy... |
|
|
|
|
Has anyone had any luck with the [EarningsOnPercentageTrade Indicator]?
During backtests it seemed very very profitable, but in practice it went no where.
From watching the indicator graph, the best I can guess is that the bot will only buy if [last sell price - X%] and it will only sell if [last buy price + X%].
The issue I had was when trading yesterday was I bought in at (example #s) $9.00 and then sold at $10.20 for a profit.
Price then climbed to $11.00 and didn't come down for the rest of the day.
But because it never returned to within [last sell price - X%], the bot stuck and wouldn't trade.
Unless I am using this indicator wrong, it seems like it will always miss upward trends.
----
The indicator almost seems like a combination of [BlindSignal Indicator] and [PercentageChange Insurance], yea?
----
I'm tempted to throw it .25 BTC and see what [EarningsOnPercentageTrade Indicator] can do over a week. haha
|
|
|
|
MACD follows the trend, using it alone is not a good idea.
Right, I totally get that. But it's giving the opposite advice it should. I'm not on my home computer, so I can't post the logs until tonight. |
|
|
|
|
Has anyone found a solution to the MA/MACD giving inverse indicators? Upon searching this thread, it appears to be a old issue.
New bot, with a MACD-Histogram (default settings) will 99.9% of the time buy high and sell low.
So, the question is, how do we reverse this? lol
When I get home I am going to see if I can make two indicators and push one response right and one response left. Then set one as only giving sell indicators and the other only giving buy. May work, may not.
At this point though, the MA/MACD is almost pointless...
Unless I have missed something?
|
|
|
|
Has anyone noticed it's almost impossible to trade DOGE on Cryptsy due to the volume sitting at each price?
Bot or not.
Unless you are wanting to move 15 BTC orders it seems like your order will never get filled.
Perhaps you need to move in 5+ BTC orders?
Anyone have any experience in this?
I don't know if I'm having the same issue as you, but I can say that in all the time that I've had a bot attempting to trade DOGE/BTC on Cryptsy (~ a month) that Cryptsy has never once accepted either a buy or sell order from the bot. There have never been any STB-related errors in the logs, either - just messages indicating that Cryptsy did not fill the order. Yea, thats the same business. Go look at the cryptsy page. At each point it's about 10+ BTC. Unless you are going to drop that much (in the hopes of half fill), it seems like a lost cause. Anyone elses input? example Sell orders Price (BTC) DOGE Total (BTC) 0.00000107 14483797.69219337 15.49766353 0.00000108 16753228.75780187 18.09348706 0.00000109 22503629.94780660 24.52895664 0.00000110 23507417.07510483 25.85815878 0.00000111 22877414.54066831 25.39393014 0.00000112 27836106.42102879 31.17643919 0.00000113 30206255.14351613 34.13306831 0.00000114 31094320.31424473 35.44752516 0.00000115 38765994.24077795 44.58089338 0.00000116 7744745.81621080 8.98390515 Buy Orders Price (BTC) DOGE Total (BTC) 0.00000106 578849.53788753 0.61358051 0.00000105 21991071.45495910 23.09062503 0.00000104 32729119.48711389 34.03828427 0.00000103 17944188.65152126 18.48251431 0.00000102 17812444.97280750 18.16869387 0.00000101 18817150.73901424 19.00532225 0.00000100 33207574.43434447 33.20757443 0.00000099 22531746.97109096 22.30642950 0.00000098 21344514.58565430 20.91762429 0.00000097 16883186.89236294 16.37669129 |
|
|
|
|
