Topic: Qt Bitcoin Trader [Open Source secure trading client for Mac/Windows/Linux] - page 53. (Read 383582 times)
December 21, 2013, 02:35:26 PM
Cant seem to check concurrent for the rules? I'd like to sell if at XX, and spend my funds to buy if at XX, I have both btc and usd, but it will only do one than the other?
December 21, 2013, 02:24:19 PM
Wow this is cool
December 21, 2013, 07:30:43 AM
Hello,
Workaround was pretty simple, perfect !
Thank for the quick support.
Workaround was pretty simple, perfect !
Thank for the quick support.
December 20, 2013, 07:52:19 PM
Currently it 5000 ms.
You can change it in ini file section UI, value RulesSafeModeInterval=5000
um... ya sure that is working as intended?You can change it in ini file section UI, value RulesSafeModeInterval=5000
When I had the delay turned off, my trades were going through at roughly 5-6 seconds apart, but when I turn it on, it sits there waiting... couldn't find out exactly how long it would wait, as my buy condition stopped being valid after about 20 minutes.
(I'm also working with source at least a week old, so if you made changes since then, lemme know)
[/quote]
Trade requests have high priority, so it executed immediately. But UI updates have lower priority, so there maybe delay between order request sent and order appears on UI.
As I planted, I'll make it better soon: https://github.com/JulyIGHOR/QtBitcoinTrader/issues/106
Seems to be great software, just testing now, it works very smoothly in win 8.1 on vm.
I wonder if possible to add- if market last price goes to more or less than X % of market high price or low price then execute rule?
also seems bid and ask label is reversed in last trade tab
I wonder if possible to add- if market last price goes to more or less than X % of market high price or low price then execute rule?
also seems bid and ask label is reversed in last trade tab
Percentage in rules will be added soon.
>also seems bid and ask label is reversed in last trade tab
Update to lastest build.
Hi!
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
Please, pick maximum value to buy that opens order. And send me Balance,Price,Value to PM. I'll fix this.
Here's something I just noticed...
I'm attempting to utilize the calculator function, to determine decent low-risk (if there is such a thing) rules to set.
Trouble is, I'm starting with BTC balance, and attempting to calculate a Sell-then-Buy scenario. The calculator will not allow the sell field to be edited, only calc'd automatically based on other variables. It'll also not allow for the Buy / Sell rows to be reversed.
Might be useful if it were possible to do either...
I'm attempting to utilize the calculator function, to determine decent low-risk (if there is such a thing) rules to set.
Trouble is, I'm starting with BTC balance, and attempting to calculate a Sell-then-Buy scenario. The calculator will not allow the sell field to be edited, only calc'd automatically based on other variables. It'll also not allow for the Buy / Sell rows to be reversed.
Might be useful if it were possible to do either...
Zero profit step this is what you need. Use bottom of Buy and Sell panels to calculate next order.
Hi,
Many thanks IGHOR for the great work, this is really amazing.
I have some issues while using the trader, maybe someone can enlight me.
> I'm using BTC-E and working on LTC/USD. Latest version of the client.
For example i would like to setup 2 rules
When price is > 20$ sell everything
When price is < 17$ buy everything
I have created the rules, enabled them in concurent mode but: (i'm always using "market last price"
> when rule is triggered nothing happens (order tab stays empty)
> and rule is only applied once, after it goes in "proceed" state.
I would like order to be executed and that rules can be triggered an unlimited times.
Using instant buying or selling (bot windows), everything works fine.
Where i'm wrong ?
thank you.
Many thanks IGHOR for the great work, this is really amazing.
I have some issues while using the trader, maybe someone can enlight me.
> I'm using BTC-E and working on LTC/USD. Latest version of the client.
For example i would like to setup 2 rules
When price is > 20$ sell everything
When price is < 17$ buy everything
I have created the rules, enabled them in concurent mode but: (i'm always using "market last price"
> when rule is triggered nothing happens (order tab stays empty)
> and rule is only applied once, after it goes in "proceed" state.
I would like order to be executed and that rules can be triggered an unlimited times.
Using instant buying or selling (bot windows), everything works fine.
Where i'm wrong ?
thank you.
Scalping example:
December 20, 2013, 03:28:09 PM
Hi,
Many thanks IGHOR for the great work, this is really amazing.
I have some issues while using the trader, maybe someone can enlight me.
> I'm using BTC-E and working on LTC/USD. Latest version of the client.
For example i would like to setup 2 rules
When price is > 20$ sell everything
When price is < 17$ buy everything
I have created the rules, enabled them in concurent mode but: (i'm always using "market last price"
> when rule is triggered nothing happens (order tab stays empty)
> and rule is only applied once, after it goes in "proceed" state.
I would like order to be executed and that rules can be triggered an unlimited times.
Using instant buying or selling (bot windows), everything works fine.
Where i'm wrong ?
thank you.
Many thanks IGHOR for the great work, this is really amazing.
I have some issues while using the trader, maybe someone can enlight me.
> I'm using BTC-E and working on LTC/USD. Latest version of the client.
For example i would like to setup 2 rules
When price is > 20$ sell everything
When price is < 17$ buy everything
I have created the rules, enabled them in concurent mode but: (i'm always using "market last price"
> when rule is triggered nothing happens (order tab stays empty)
> and rule is only applied once, after it goes in "proceed" state.
I would like order to be executed and that rules can be triggered an unlimited times.
Using instant buying or selling (bot windows), everything works fine.
Where i'm wrong ?
thank you.
December 19, 2013, 11:40:58 PM
Hi!
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
Buy orders won't go through if you don't have enough cash. Sometimes the rounding is off. Try reducing the amount spent by $0.01 or $0.10 and see if it goes through then.
December 19, 2013, 11:04:09 PM
Here's something I just noticed...
I'm attempting to utilize the calculator function, to determine decent low-risk (if there is such a thing) rules to set.
Trouble is, I'm starting with BTC balance, and attempting to calculate a Sell-then-Buy scenario. The calculator will not allow the sell field to be edited, only calc'd automatically based on other variables. It'll also not allow for the Buy / Sell rows to be reversed.
Might be useful if it were possible to do either...
I'm attempting to utilize the calculator function, to determine decent low-risk (if there is such a thing) rules to set.
Trouble is, I'm starting with BTC balance, and attempting to calculate a Sell-then-Buy scenario. The calculator will not allow the sell field to be edited, only calc'd automatically based on other variables. It'll also not allow for the Buy / Sell rows to be reversed.
Might be useful if it were possible to do either...
December 19, 2013, 08:16:46 PM
Hi!
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
Just want to say thanks for the great work!
One issue though. When I place a buy order through the client, the buy orders don't show and never go through. I checked my API access and it should allow the client to purchase. This is all through Bitstamp. Everything else seems to work fine. Any suggestions?
December 19, 2013, 03:20:06 PM
Hi guys,
I read several pages of this thread which is mostly about bugfixing, checked out the website and youtube but didn't find any:
I whish there was a manual which explains all the buttons, what exactely last, market, rule, high prices etc. are and what best practices should be used, i.e. what set of rules for specific trading strategies. Sorry I am a newbie and lost money in the hundreds for not understanding the software.
Has anyone written something similar?
Thanks,
Danman
I read several pages of this thread which is mostly about bugfixing, checked out the website and youtube but didn't find any:
I whish there was a manual which explains all the buttons, what exactely last, market, rule, high prices etc. are and what best practices should be used, i.e. what set of rules for specific trading strategies. Sorry I am a newbie and lost money in the hundreds for not understanding the software.
Has anyone written something similar?
Thanks,
Danman
You may learn a lot simply looking. I also lost, that's the though way of learning, any manual will make you win.
Enjoy the program, is a superb piece of software, given completely free, more than enough IMHO, the common sense must be provided by each user. (In fact I lack it completely ;-)
December 19, 2013, 11:45:35 AM
Hi guys,
I read several pages of this thread which is mostly about bugfixing, checked out the website and youtube but didn't find any:
I whish there was a manual which explains all the buttons, what exactely last, market, rule, high prices etc. are and what best practices should be used, i.e. what set of rules for specific trading strategies. Sorry I am a newbie and lost money in the hundreds for not understanding the software.
Has anyone written something similar?
Thanks,
Danman
I read several pages of this thread which is mostly about bugfixing, checked out the website and youtube but didn't find any:
I whish there was a manual which explains all the buttons, what exactely last, market, rule, high prices etc. are and what best practices should be used, i.e. what set of rules for specific trading strategies. Sorry I am a newbie and lost money in the hundreds for not understanding the software.
Has anyone written something similar?
Thanks,
Danman
December 19, 2013, 09:28:32 AM
Seems to be great software, just testing now, it works very smoothly in win 8.1 on vm.
I wonder if possible to add- if market last price goes to more or less than X % of market high price or low price then execute rule?
also seems bid and ask label is reversed in last trade tab
I wonder if possible to add- if market last price goes to more or less than X % of market high price or low price then execute rule?
also seems bid and ask label is reversed in last trade tab
December 19, 2013, 02:11:48 AM
Quote
When I have "Delay between executing orders" checked, how long is the delay? (using an unmodified build right now)
and, which configuration option controls that? (and is it in seconds or milliseconds?)
Currently it 5000 ms.and, which configuration option controls that? (and is it in seconds or milliseconds?)
You can change it in ini file section UI, value RulesSafeModeInterval=5000
When I had the delay turned off, my trades were going through at roughly 5-6 seconds apart, but when I turn it on, it sits there waiting... couldn't find out exactly how long it would wait, as my buy condition stopped being valid after about 20 minutes.
(I'm also working with source at least a week old, so if you made changes since then, lemme know)
December 18, 2013, 09:07:50 PM
Custom intervals? Like, setting each rule to its own interval? (could be very handy if you want one rule to fire slower than another one... so a rule set up to catch a big swing can fire off faster than the every-day slow one, to take most advantage of the swing before it swings back)
No. You will be able to add "Empty" rule witch just holds next rule executing by some ms.
So you can put this empty rule between required two rules and make interval.
December 18, 2013, 08:46:10 PM
Currently it 5000 ms.
You can change it in ini file section UI, value RulesSafeModeInterval=5000
Soon I'll add rule to make custom intervals.
Custom intervals? Like, setting each rule to its own interval? (could be very handy if you want one rule to fire slower than another one... so a rule set up to catch a big swing can fire off faster than the every-day slow one, to take most advantage of the swing before it swings back)You can change it in ini file section UI, value RulesSafeModeInterval=5000
Soon I'll add rule to make custom intervals.
December 18, 2013, 08:42:56 PM
Welp, finally got a working client compiled... was getting myself all worked up, I was missing something stupidly obvious, which I fixed right away after stepping away from it a couple days, and busily tinkering now.
Quick question...
When I have "Delay between executing orders" checked, how long is the delay? (using an unmodified build right now)
and, which configuration option controls that? (and is it in seconds or milliseconds?)
Quick question...
When I have "Delay between executing orders" checked, how long is the delay? (using an unmodified build right now)
and, which configuration option controls that? (and is it in seconds or milliseconds?)
Currently it 5000 ms.
You can change it in ini file section UI, value RulesSafeModeInterval=5000
Soon I'll add rule to make custom intervals.
I have a lot of suggestions, but I'll add most popular exchanges first.
Also I think to make some easy tool to generate information for adding exchanges to allow everyone submit this data to me. Than I'll add exchanges match faster.
So keep tracking updates.
December 18, 2013, 08:31:40 PM
December 18, 2013, 08:19:50 PM
Welp, finally got a working client compiled... was getting myself all worked up, I was missing something stupidly obvious, which I fixed right away after stepping away from it a couple days, and busily tinkering now.
Quick question...
When I have "Delay between executing orders" checked, how long is the delay? (using an unmodified build right now)
and, which configuration option controls that? (and is it in seconds or milliseconds?)
Quick question...
When I have "Delay between executing orders" checked, how long is the delay? (using an unmodified build right now)
and, which configuration option controls that? (and is it in seconds or milliseconds?)
December 18, 2013, 06:44:04 PM
Hello again,
Concerning API shutdowns, it seems that changing request intervals to 600ms did the trick, and keep API alive and working all night long.
Maybe if it's not too complicated, you can add an adaptive "extra delay" when api errors persist more than a few seconds.
It seems to me that client keep trying to connect and BTC persists rejecting longer each time, so when shutdown time is large (9999...) you must wait some 5 - 10 minutes before being allowed to connect again.
I can perfectly live with the program as it works now, but maybe it could be helpful on high traffic scenarios.
Again thanks for your excelent help and support.
Best whishes
Ricardo
Concerning API shutdowns, it seems that changing request intervals to 600ms did the trick, and keep API alive and working all night long.
Maybe if it's not too complicated, you can add an adaptive "extra delay" when api errors persist more than a few seconds.
It seems to me that client keep trying to connect and BTC persists rejecting longer each time, so when shutdown time is large (9999...) you must wait some 5 - 10 minutes before being allowed to connect again.
I can perfectly live with the program as it works now, but maybe it could be helpful on high traffic scenarios.
Again thanks for your excelent help and support.
Best whishes
Ricardo
Thanks for confirmation of minimum interval. I'll force all users to minimum 600 ms interval.
Also I'll add API Down solution. So it will emulate browser and cookies will be saved to solve IP ban problem.
December 18, 2013, 12:05:01 PM
Hello again and please accept my excuses for bothering you again.
I changed to 1000 interval request, but overnigth desconnection persists.
During the day I saw some API shutdowns, but those recovered after a while, 30- 45 seconds maximun.
Along the day the API rules ok, but overnight it falls and keeps down forever (9999....), I must close the program, and wait a minimum 10 minutes to recconect.
It seems that rules have no effect, API disconnets either way, with or without rules running
I have a stable and fast connection, 8Mb/4Mb Windows XP, Fixed IP address and GMT +2 zone, if it helps you.
(Sorry but I have no idea about Capcha, and didn't find it on btc)
Can you suggest a way to find the cause.
Thanks in advance and again excuse for so much trouble.
Ricardo
I changed to 1000 interval request, but overnigth desconnection persists.
During the day I saw some API shutdowns, but those recovered after a while, 30- 45 seconds maximun.
Along the day the API rules ok, but overnight it falls and keeps down forever (9999....), I must close the program, and wait a minimum 10 minutes to recconect.
It seems that rules have no effect, API disconnets either way, with or without rules running
I have a stable and fast connection, 8Mb/4Mb Windows XP, Fixed IP address and GMT +2 zone, if it helps you.
(Sorry but I have no idea about Capcha, and didn't find it on btc)
Can you suggest a way to find the cause.
Thanks in advance and again excuse for so much trouble.
Ricardo
Hi. Please contact me via email or skype (julyighor).
It seems the zero profit calculation is wrong. E.g.
BTC 1
Rate 0.00624
Total to buy 160.256
Zero Profit price 0.00726 <<<<<< that should be about 0.00630
BTC 1
Rate 0.00624
Total to buy 160.256
Zero Profit price 0.00726 <<<<<< that should be about 0.00630
What price? Zero profit price depends only from Price.
.... Unless I'm missing something it does not support Alt Coin trading from BTC-E? Or am I missing an option? Mine only show's usd/BTC, would be nice to see it list what I could have for alt's as well etc.
In order to change currency you need to remove all rules.
Ah it all make's sense now! So you can't set a rule and switch floor's. gotcha!
December 18, 2013, 05:27:55 AM
Hello again,
Concerning API shutdowns, it seems that changing request intervals to 600ms did the trick, and keep API alive and working all night long.
Maybe if it's not too complicated, you can add an adaptive "extra delay" when api errors persist more than a few seconds.
It seems to me that client keep trying to connect and BTC persists rejecting longer each time, so when shutdown time is large (9999...) you must wait some 5 - 10 minutes before being allowed to connect again.
I can perfectly live with the program as it works now, but maybe it could be helpful on high traffic scenarios.
Again thanks for your excelent help and support.
Best whishes
Ricardo
Concerning API shutdowns, it seems that changing request intervals to 600ms did the trick, and keep API alive and working all night long.
Maybe if it's not too complicated, you can add an adaptive "extra delay" when api errors persist more than a few seconds.
It seems to me that client keep trying to connect and BTC persists rejecting longer each time, so when shutdown time is large (9999...) you must wait some 5 - 10 minutes before being allowed to connect again.
I can perfectly live with the program as it works now, but maybe it could be helpful on high traffic scenarios.
Again thanks for your excelent help and support.
Best whishes
Ricardo
Jump to: