Messages

1

Beginners & Help / Re: DOUBLE_UP_CAP Values

« on: December 05, 2017, 01:49:27 PM »

Thanks for the link.  I had already found this:

"When averaging down, it is recommended to invest a lot more than your initial investment. The more you invest, the lower the average price to sell will be and the sooner you can get rid of your bags. Because of this, it is not recommended to enable DOUBLE_UP for many pairs at the same time. You can control how much funds is used to average down by configuring DOUBLE_UP_CAP."

However, what am I missing here?  What section defines the value assigned to DOUBLE_UP_CAP and its effect?

2

Beginners & Help / Re: Switching from bbrsistepgain to bbrsitssl

« on: December 03, 2017, 05:51:29 PM »

I am too curious about tssl vs stepgain.  Please post your findings

3

Beginners & Help / DOUBLE_UP_CAP Values

« on: December 03, 2017, 05:50:08 PM »

Hi,

DOUBLE_UP_CAP is set to "1" by default.  Does this mean 1x the TRADING_LIMIT already assigned on a coin pair?

Thanks

4

Technical Support & Development / Re: Gunbot 6.0.1 General Questions

« on: December 02, 2017, 12:28:38 AM »

Excellent.  Thanks again.

5

Beginners & Help / Re: MAX_VOLUME_TO_SELL Variable?

« on: December 02, 2017, 12:27:36 AM »

Cool.  Thanks

6

Technical Support & Development / Re: Gunbot 6.0.1 General Questions

« on: December 01, 2017, 05:00:07 AM »

Ah... that makes sense.  In the wiki example, as well as the Stepgain strategy in 6.0.x, there are four SELLLVL variables:

SELLLVL
SELLLVL1
SELLLVL2
SELLLVL3

The same goes for BUYLVL.

I did not understand that the named variable (without an int) was used to select entry / exit point instead of the bot starting at 1 and working up through 3.

Thank you

7

Beginners & Help / Tips&Tricks: BTC-OMG can be averaged!!!

« on: December 01, 2017, 04:47:27 AM »

2017/11/30 22:30:27: There are some trading opportunities for BTC-OMG at bittrex. Scanning Trade History
 ɢƱҊɃѺŁ XT Edition  Tips&Tricks: BTC-OMG can be sold!!!
2017/11/30 22:30:27: There are some trading opportunities for BTC-OMG at bittrex. Scanning Trade History
 ɢՍΠβםŁ XT Edition  Tips&Tricks: BTC-OMG can be averaged!!!
2017/11/30 22:30:27: Last Bid price BTC-OMG: 0.00082494 | Last Ask: 0.00082582
2017/11/30 22:30:27: Balance BTC: 1.10778499
2017/11/30 22:30:27: Balance OMG: 21.6635435
2017/11/30 22:30:27: On Orders OMG: 0
Processing strategy bbrsi for BTC-OMG on bittrex
2017/11/30 22:30:27: Entering sell cycle
┌───────────────────┬────────────┬───────────────┬───────────────┬────────────┬────────────┬────────────┬─────────┐
│ ɢՍƝß๏Ł XT Edition │ SMA        │ LowBB         │ HighBB        │ Last       │ OMG        │ Last Buy   │ Pair    │
├───────────────────┼────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼─────────┤
│ Sell cycle        │ 0.00081606 │ 0.00079888768 │ 0.00083323512 │ 0.00082494 │ 21.6635435 │ 0.00092321 │ BTC-OMG │
└───────────────────┴────────────┴───────────────┴───────────────┴────────────┴────────────┴────────────┴─────────┘
************************************************************************************************
Gunbot XT says: RSI is too low!!! Waiting to sell
************************************************************************************************

I'm still testing 6.0.2 and I really like what I see so far.  Thanks Gunthy and devs!

Does this mean that the price of BTC has gone up sufficiently that (in this case) selling at a lower amount of BTC than the purchase price will result in a profit? 

Does 6.0.2 track the price of BTC at the time a coin is purchased?

8

Technical Support & Development / Re: Gunbot 6.0.1 General Questions

« on: November 25, 2017, 11:03:23 PM »

Thanks for the reply and clarification.   

I did read the wiki.  I'm coming from 3.3.2 where there were only the 3 buy / 3 sell variables to be assigned.  The fourth variable seemed redundant as an exit point, as using gain (plus a little math on the fly) would produce a similar effect.  I assume then that setting SELLLVL to a null value would either throw an error, or simply prevent any exit on that cycle.

9

Beginners & Help / MAX_VOLUME_TO_SELL Variable?

« on: November 25, 2017, 05:25:19 PM »

Hi,

I just had an idea, but didn't see it in the wiki.  Maybe I'm just blind... 

Say you setup an USDT/BTC (yeah, I know...) trading pair, bbrsipp, and you have 2 BTC sitting in your account.

You think that BTC is going to hit 9k, but you only want Gunbot to sell half of the volume of BTC you're sitting on in your account. 

Does anyone know of a MAX_VOLUME_TO_SELL variable or something like it, that could be set (in this case) to only sell the 1.0 BTC when the RSI_SELL_LEVEL and PP_SELL conditions are met?

Thanks

10

Technical Support & Development / Gunbot 6.0.1 General Questions

« on: November 24, 2017, 07:56:01 PM »

Hi folks,

I've been through the wiki and several vids and still have a few questions. If these are addressed elsewhere in the forum, please let me know.

1)  The SELLLVL variable:  When set to an integer (2 for example), does it:

     (a)  instruct the bot to attempt to sell up through to the stepgain SELLLVL denoted 
       (tries SELLLVL1, SELLLVL 2, and skips SELLLVL 3 as price is rising)

     (b)  or instruct the bot to sell ONLY at that SELLLVL (ignore SELLLVL1 and SELLLVL3)

      How does the bot behave if a stepgain strategy is used and SELLLVL variable is removed or set to zero?


2)  How does the user change the trading pair priority in a given setup? 
     (e.g. in most browsers, one can grab the tab and move it to the right or left.)


3)  When a trading pair config is changed, does clicking the UPDATE button at the bottom of the window update only
      that pair's changes or all pairs in a given setup?


4)  If trading pair configs are changed in the config.js file, will the APPLY CHANGES button on the Dashboard screen
     load the new changes, or does this require a complete restart of gunthy-gui?


5)  I like Firefox, but it's become bloatware.  After an update, I finally got TradingView charts to appear on the page of
     each trading pair.  Chrome runs gunthy-gui much better, and has been updated, but all I get is a spinning wheel
     as it tries to load TradingView charts.

     I've already tried reloading trading pair pages with the firewall completely off, and suspect its a Chrome setting
     somewhere.  Anyone have any ideas?

11

Technical Support & Development / Re: Keep getting 'Jsongui stopped working' !!

« on: November 22, 2017, 06:45:46 PM »

Heh.  I have that problem too on my v3.3.2 on Win 7 VPS.

I slam the "CANCEL" buttons after I wait a good 3-4 minutes.   I have to cancel many times to get control back because I have tons of trading pairs.

The work around I've found is to re-create the trading pairs I want, hit SAVE, then START.  i.e. I let it start and after it takes too long I hit cancel a bunch of times.  Whatever pairs aren't started properly I CLOSE.  Then I re-create the pairs, hit SAVE, then START.  It's slow but it works for me.

I have two instances of v3.3.2 running.  One for BTC pairs, and one for ETH pairs.  I've never had issues with the ETH trading pair instance.... which makes me think that the Jsongui issue may be related to running too many pairs in one instance of the bot.  My BTC instance has a ton of trading pairs all running in full BB.

I suspect Cryptosticks is correct.  It has something to do with resources allocated to each instance of jsongui running a trading pair.  I'm still learning how to tweak XT, so I'm still running pairs on 3.3.2 

I've noticed that GunBot slows down considerably, and lately, after starting about the 6th trading pair (manually, the way Cryptosticks describes).  It will only run for a few hours or overnight before jsongui crashes.  Is this a case where more memory needs to be allocated to the java heap or something?  Gb Devs?  Buehler?  Buehler?

I would really like to know how to resolve this.  Even after switching over to XT, I'd still like to setup another box with my ol' pal 3.3.2 on it without problems.  Any software that pays for itself within the first two weeks deserves to be kept running. 

BTW, this is not running on a VPS,  this is on a spare engineering workstation I have with two E5-2623V3 3.2 Ghz processors and 16GB of RAM.  Available resources are not a problem. Nothing else running on the system except 64bit Win-doze 7 (for now) and the usual crapola for an older nvidia graphics card.