johndon
Newbie
Offline
Activity: 37
Merit: 0
|
|
August 27, 2014, 09:24:05 PM |
|
Please if its possible add HitBTC exchange.
Thanks!
|
|
|
|
Askit2
|
|
August 28, 2014, 09:11:33 PM |
|
Ok, I got another crash. This time while I was sleeping. This should be good news. Well to me it is. I did miss an opportunity to sell the bought bitcoins again. Since I wasn't on changing anything I didn't cause this one. It happened after a buy so I got hung up executing one of the rules after the buy.
execute immediately group or script (3 different scripts.) one or two may have been started. (I think this is the location of the problem.)
My sell rule up 1% from last buy sell. (I can't say for sure it ever started.) I don't believe the problem is with this specific line as it seems odd waiting for a condition to become true killed it.
I am making a small assumption because the NMC trading window using 1 rule set for range trading and a different rule for planned profit taking. Range trading only enables itself. Profit taking only enables itself. This setup hasn't crashed yet. Same computer, same account on BTCe same trading bot. Only change is slightly how the rules work.
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 28, 2014, 09:16:05 PM |
|
Ok, I got another crash. This time while I was sleeping. This should be good news. Well to me it is. I did miss an opportunity to sell the bought bitcoins again. Since I wasn't on changing anything I didn't cause this one. It happened after a buy so I got hung up executing one of the rules after the buy.
execute immediately group or script (3 different scripts.) one or two may have been started. (I think this is the location of the problem.)
My sell rule up 1% from last buy sell. (I can't say for sure it ever started.) I don't believe the problem is with this specific line as it seems odd waiting for a condition to become true killed it.
I am making a small assumption because the NMC trading window using 1 rule set for range trading and a different rule for planned profit taking. Range trading only enables itself. Profit taking only enables itself. This setup hasn't crashed yet. Same computer, same account on BTCe same trading bot. Only change is slightly how the rules work.
I found crash on circle executing with 0 delay only. Please try to set 1 second delay to all your execute immediately groups and tell me results.
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
idee2013
|
|
August 29, 2014, 10:33:07 PM |
|
HI, i think that i have found a bug or i do not understand the syntax of the rules. Ask Price is for example 510 USD With this rule qt trader does nothing ( does not cancel orders). But it it should execute it because the ask price is over 100 usd. When Ask Price (BTC/USD) > Ask Price (BTC/USD) + 100.49 (Realtime comparation) then Cancel All Orders With this following rule (operator changed) there comes this message. This should be not executed immediately because ask price is NOT under 100 USD. When Ask Price (BTC/USD) < Ask Price (BTC/USD) + 100.49 (Realtime comparation) then Cancel All Orders There is the same issue when making for example a buy order instead of cancel the orders.
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 29, 2014, 10:42:05 PM |
|
HI,
i think that i have found a bug or i do not understand the syntax of the rules.
Thank you. Yes it is a bug. I'll fix it in upcoming bugfix release.
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
idee2013
|
|
August 29, 2014, 10:44:56 PM |
|
HI,
i think that i have found a bug or i do not understand the syntax of the rules.
Thank you. Yes it is a bug. I'll fix it in upcoming bugfix release. Ok thank you, too
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 29, 2014, 10:49:56 PM |
|
Ok thank you, too
Sorry, misunderstand you first time. Everything is correct. Rule "When Ask Price (BTC/USD) < Ask Price (BTC/USD) + 100.49" means that it compare Ask Price to Ask Price + 100.49 For example ask price is 500, this means it comparing 500<500+100.49 what is true To set exact comparing, you should chose "When Ask Price (BTC/USD) < Exact value (BTC/USD) 110.49"
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
idee2013
|
|
August 29, 2014, 11:01:38 PM |
|
Ok thank you, too
Sorry, misunderstand you first time. Everything is correct. Rule "When Ask Price (BTC/USD) < Ask Price (BTC/USD) + 100.49" means that it compare Ask Price to Ask Price + 100.49 For example ask price is 500, this means it comparing 500<500+100.49 what is true To set exact comparing, you should chose "When Ask Price (BTC/USD) < Exact value (BTC/USD) 110.49" ahh ok...now i understand it. Thank you!
|
|
|
|
derrend
|
|
August 30, 2014, 01:14:35 AM Last edit: August 30, 2014, 01:29:56 AM by derrend |
|
Hello, long time user first time poster. Love your work! Running a fresh ubuntu 14.04 and installing the dependencies as instructed in the OP I get this error when running $ qmake-qt4 QtBitcoinTrader_Mobility.pro WARNING: Failure to find: addrulewindow.cpp WARNING: Failure to find: audioplayer.cpp WARNING: Failure to find: exchange_cryptsy.cpp WARNING: Failure to find: addrulewindow.h WARNING: Failure to find: audioplayer.h WARNING: Failure to find: exchange_cryptsy.h WARNING: Failure to find: addrulewindow.ui Then $ make make: *** No rule to make target `addrulewindow.ui', needed by `.ui/ui_addrulewindow.h'. Stop. QtBitcoinTrader_Desktop.pro compiles and installs without error but using BTC-E exchange I am unable to cancel any of my placed orders. I have tried no other exchanges. Source obtained from git master git clone https://github.com/JulyIGHOR/QtBitcoinTrader.git Thanks again, very useful app
|
|
|
|
Askit2
|
|
August 30, 2014, 04:15:31 AM |
|
Ok, I got another crash. This time while I was sleeping. This should be good news. Well to me it is. I did miss an opportunity to sell the bought bitcoins again. Since I wasn't on changing anything I didn't cause this one. It happened after a buy so I got hung up executing one of the rules after the buy.
execute immediately group or script (3 different scripts.) one or two may have been started. (I think this is the location of the problem.)
My sell rule up 1% from last buy sell. (I can't say for sure it ever started.) I don't believe the problem is with this specific line as it seems odd waiting for a condition to become true killed it.
I am making a small assumption because the NMC trading window using 1 rule set for range trading and a different rule for planned profit taking. Range trading only enables itself. Profit taking only enables itself. This setup hasn't crashed yet. Same computer, same account on BTCe same trading bot. Only change is slightly how the rules work.
I found crash on circle executing with 0 delay only. Please try to set 1 second delay to all your execute immediately groups and tell me results. No crashes overnight. It seems the disable all doesn't trigger the items after the first rule this way either. With 3 or 4 items to start or stop depending on the rule that triggers though the 1 second per each rule is a tad wasteful. I have re-ordered the rules to try to compensate but some items are 3 data pulls from the server after a condition was met. Possibly could this be reduced? I see that my options are currently 0 and 1. Maybe there could be a decimal in it so it could be less then 1 but greater then 0.
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 30, 2014, 08:24:54 AM |
|
Hello, long time user first time poster. Love your work! Running a fresh ubuntu 14.04 and installing the dependencies as instructed in the OP I get this error when running $ qmake-qt4 QtBitcoinTrader_Mobility.pro WARNING: Failure to find: addrulewindow.cpp WARNING: Failure to find: audioplayer.cpp WARNING: Failure to find: exchange_cryptsy.cpp WARNING: Failure to find: addrulewindow.h WARNING: Failure to find: audioplayer.h WARNING: Failure to find: exchange_cryptsy.h WARNING: Failure to find: addrulewindow.ui Then $ make make: *** No rule to make target `addrulewindow.ui', needed by `.ui/ui_addrulewindow.h'. Stop. QtBitcoinTrader_Desktop.pro compiles and installs without error but using BTC-E exchange I am unable to cancel any of my placed orders. I have tried no other exchanges. Source obtained from git master git clone https://github.com/JulyIGHOR/QtBitcoinTrader.git Thanks again, very useful app Thanks, fixed. No crashes overnight. It seems the disable all doesn't trigger the items after the first rule this way either. With 3 or 4 items to start or stop depending on the rule that triggers though the 1 second per each rule is a tad wasteful. I have re-ordered the rules to try to compensate but some items are 3 data pulls from the server after a condition was met.
Possibly could this be reduced? I see that my options are currently 0 and 1. Maybe there could be a decimal in it so it could be less then 1 but greater then 0.
So this is confirmation that is no crashes with 1 second delay? I'll make more steps to delays, 100 ms step for example.
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
idee2013
|
|
August 30, 2014, 08:37:22 AM |
|
Hi,
is somewhere a documentation with rule examples?
|
|
|
|
|
Askit2
|
|
August 30, 2014, 08:58:26 AM |
|
No crashes overnight. It seems the disable all doesn't trigger the items after the first rule this way either. With 3 or 4 items to start or stop depending on the rule that triggers though the 1 second per each rule is a tad wasteful. I have re-ordered the rules to try to compensate but some items are 3 data pulls from the server after a condition was met.
Possibly could this be reduced? I see that my options are currently 0 and 1. Maybe there could be a decimal in it so it could be less then 1 but greater then 0.
So this is confirmation that is no crashes with 1 second delay? I'll make more steps to delays, 100 ms step for example. Yes, Sorry I added the 1 second delays and it didn't seem to crash overnight, or at all today. I have had one hiccup. I have a rule Buy then sell up that isn't self triggering. It is triggered by 1% up. Buy then sell up triggers 1% up and once it completes the buy then sell up should be re-enabled. The hiccup is two fold. Firstly was my fault I had a minus 1% when it should have been plus 1%. So the buy on up triggered immediately after my sell. (totally my fault stupid putting them together immediately before sleep). I expected 1 sell and 1 buy followed by 1% up waiting to trigger. I am not sure how I got it but I had 0 pending sells. I had 2 sells (not sure how that happened it wasn't up 1% at all) and 7 buys. The arrangement makes me wonder. I had in order 1 sell, one buy, one sell, six buys. I understand partially the first 4 trades. The first sell followed by the first buy is 30 seconds. The second sell is within 2 seconds (possibly it didn't calc off the last buy price like it should have and the buy in question hadn't placed completely or something. Everything after that is just freaky. I am either missing 6 sells that should have either executed today or I had a rule fire 6 times in a row. The only thing that seemed to stop the repeated firing was it ran out of USD to buy back. I appreciate the bot and it really does work very well. I am glad you have made it so useful. I know I only come on when I have a problem. Thinking back most things I say sound a bit negative. The bot may have a couple of usually small issues. You fix them quickly and I really do like the bot and the service. Thank You!
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 30, 2014, 09:06:41 AM |
|
Yes, Sorry I added the 1 second delays and it didn't seem to crash overnight, or at all today.
I have had one hiccup. I have a rule Buy then sell up that isn't self triggering. It is triggered by 1% up. Buy then sell up triggers 1% up and once it completes the buy then sell up should be re-enabled. The hiccup is two fold. Firstly was my fault I had a minus 1% when it should have been plus 1%. So the buy on up triggered immediately after my sell. (totally my fault stupid putting them together immediately before sleep). I expected 1 sell and 1 buy followed by 1% up waiting to trigger. I am not sure how I got it but I had 0 pending sells. I had 2 sells (not sure how that happened it wasn't up 1% at all) and 7 buys. The arrangement makes me wonder. I had in order 1 sell, one buy, one sell, six buys. I understand partially the first 4 trades. The first sell followed by the first buy is 30 seconds. The second sell is within 2 seconds (possibly it didn't calc off the last buy price like it should have and the buy in question hadn't placed completely or something. Everything after that is just freaky. I am either missing 6 sells that should have either executed today or I had a rule fire 6 times in a row. The only thing that seemed to stop the repeated firing was it ran out of USD to buy back.
I appreciate the bot and it really does work very well. I am glad you have made it so useful. I know I only come on when I have a problem. Thinking back most things I say sound a bit negative. The bot may have a couple of usually small issues. You fix them quickly and I really do like the bot and the service. Thank You!
Tell me more info. Did you used 100% amount rules? Did you forget to add "- fee" to amount? If amount to trade is higher than your balance, then it fails.
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
Askit2
|
|
August 31, 2014, 08:31:26 AM |
|
Yes, Sorry I added the 1 second delays and it didn't seem to crash overnight, or at all today.
I have had one hiccup. I have a rule Buy then sell up that isn't self triggering. It is triggered by 1% up. Buy then sell up triggers 1% up and once it completes the buy then sell up should be re-enabled. The hiccup is two fold. Firstly was my fault I had a minus 1% when it should have been plus 1%. So the buy on up triggered immediately after my sell. (totally my fault stupid putting them together immediately before sleep). I expected 1 sell and 1 buy followed by 1% up waiting to trigger. I am not sure how I got it but I had 0 pending sells. I had 2 sells (not sure how that happened it wasn't up 1% at all) and 7 buys. The arrangement makes me wonder. I had in order 1 sell, one buy, one sell, six buys. I understand partially the first 4 trades. The first sell followed by the first buy is 30 seconds. The second sell is within 2 seconds (possibly it didn't calc off the last buy price like it should have and the buy in question hadn't placed completely or something. Everything after that is just freaky. I am either missing 6 sells that should have either executed today or I had a rule fire 6 times in a row. The only thing that seemed to stop the repeated firing was it ran out of USD to buy back.
I appreciate the bot and it really does work very well. I am glad you have made it so useful. I know I only come on when I have a problem. Thinking back most things I say sound a bit negative. The bot may have a couple of usually small issues. You fix them quickly and I really do like the bot and the service. Thank You!
Tell me more info. Did you used 100% amount rules? Did you forget to add "- fee" to amount? If amount to trade is higher than your balance, then it fails. Sorry for the delay. My sell was 0.01 btc. The buy back was 0.010202 (makes it easy to see what rule triggered if you have slightly different amounts. Anyways I didn't use the 100%. I didn't calculate the fee add or subtracted. I did want it to fail if it didn't have enough cash. Each buy or sell rule uses a different price. All more or less 0.01 the BTCe minimum.
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 31, 2014, 10:46:17 AM |
|
Sorry for the delay. My sell was 0.01 btc. The buy back was 0.010202 (makes it easy to see what rule triggered if you have slightly different amounts. Anyways I didn't use the 100%. I didn't calculate the fee add or subtracted. I did want it to fail if it didn't have enough cash. Each buy or sell rule uses a different price. All more or less 0.01 the BTCe minimum.
I see bug and fixed it, can you test private build I sent to you via PM?
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
August 31, 2014, 11:28:38 PM Last edit: September 01, 2014, 02:00:27 AM by IGHOR |
|
v1.07.99 Bugfix 6 released. Fixed script engine bugs that caused crash. Fixed http engine bugs. Fixed enable/disable group bug. Added new functions to script language to get order book data by price and volume. JL Script manual available here: http://forum.centrabit.com/viewtopic.php?f=3&t=4161
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
|
IGHOR (OP)
Legendary
Offline
Activity: 1035
Merit: 1065
|
|
September 01, 2014, 03:00:02 AM Last edit: September 01, 2014, 03:19:25 AM by IGHOR |
|
Wouldn't it be great if you can use the API from Cryptotrader.org in Qt Bitcoin Trader to have trend indicators like Moving Averages inside Trader? Then you could build some really intelligent Bots with the Trader. Don't worry, all trend indicators will be in Qt Bitcoin Trader later too.
|
Qt Bitcoin TraderVerify digital signature of the app in the file properties every time you download it.
|
|
|
|