This is an old revision of the document!


Die TOP 1 Frage die wir ständig erhalten:

* Warum kauft mein Bot nicht oder warum ist mein Possible Buy Log leer ??

Häufig gestellte Fragen


Manchmal ist dein “Total Coin Value” weniger als dein “Total Potential Value” in der GUI. Dies ist weil Profittrailer nach deinen Angaben, z.b. GAIN den Wert bereits kalkuliert. Ist TCV höher als TPV, hast du entweder DUST in deinem Account (ProfitTrailer ignoriert den Wert des Dust), oder es fehlt bei einem Coin der “bought” Preis (dies solltest du in den Logfiles und der CMD Konsole sehen).

Leider ist dieser Dust in Binance am höchsten, da Binance nur den Kauf und Verkauf ganzer Coins erlaubt, aber vom ganzen Coin die Gebühren abzieht, sofern BNB nicht als Fee Coin aktiviert wurde.


TCV ist die aktuelle Gesamtsumme deiner gekauften Coins welcher in Pairs, DCA, and Pending Logs ist. DUST ist hier nicht inkludiert, daher kann der Wert abweichen.

TOP


Hinweis: Diese Option ist erst seit Version v1.2.6.9 verfügbar.

Gebe folgende URL in deinen Browser ein:

http://localhost:8081/stop

Dieser Link funktioniert nur wenn du ein GUI Passwort in der application.properties gesetzt hast.

Ebenfalls kann der Bot in CMD mit der Tastenkombination CTRL C gestoppt werden. Bei Linux mit pm2, wird der Bot über die Prozess ID gestoppt. Gebe dazu z.b. ID 2 vorrausgesetzt, pm2 stop 2 ein.

TOP


Warum kauft der Bot nicht ? Trotz Werte in possible buy log (PBL) kauft er nicht ? Warun ist PBL leer ?

The PBL is populated based on several settings in your Pairs.configuration and Indicators.configuration files. These include:

Your Balance or your TCV (Total Coin Value)

A zero balance in your exchange and/or a TCV of zero will keep the bot from adding any coin pairs to your PBL.


Pairs.configuration file:

Settings in this file that affect the PBL

ALL_trading_enabled = true

If this is “false” the bot will not populate the PBL


ALL_sell_only_mode = false

If this is “true” the bot will not populate the PBL


all_max_trading_pairs

If the coin pairs in the Pairs log + the DCA log = ALL_max_trading_pairs, then the PBL will not be populated. If you want more in the PBL, increase this number.


ALL_buy_available_volume_trigger = 150

If the volume of the coin is below the trigger amount, it will not be considered in the PBL.


ALL_min_buy_volume = 500

If the volume in the base currency that you are using to trade (e.g. BTC, or USDT) is below the amount you set, the pair will not be included in the PBL.


ALL_min_buy_price = 0.00000500

If the price of the pair is below this minimum price, the pair will not be included in the PBL.



How different BUY strategy settings affect the PBL

Buying with BB strategies (LOWBB, HIGHBB)

Buying with LOWBB
ALL_buy_strategy = LOWBB
ALL_buy_value = X

When using LOWBB, the main setting that affects the PBL is ``ALL_buy_value`` (which, remember, is a percentage). For a coin pair to be bought using LOWBB, the ALL_buy_value must be equal to or less than the value of the LOWBB band multiplied by (1 + ALL_buy_value expressed as a percentage). So, in other words,

Buy Price < = LOWBB value * (1 + ALL_buy_value/100)

So, for the PT bot to even being to consider a coin pair to be put on the PBL, it needs to be close to the Buy Price. How close the current price needs to be is a closely guarded secret, but it must be reasonably close, say within 10%.

Thus, as an example, if you have no items in the PBL, and your ALL_buy_value is set to 0 (which would make the buy price be exactly the LOWBB value), and you look at your exchange and see that all the current coin pairs are up 10 or 20%, then your Buy Price calculation is not close enough current prices of all the coin pairs and the ALL_buy_value may need to be increased.

What are normal values for ALL_buy_value for LOWBB? Values normally range between -20 for very, very conservative (things are going down in the market and you want to make sure you don’t buy unless the coin is 20% below its normal LOWBB line), to 0 for somewhat conservative, to 10-15% for somewhat aggressive, to 25-45% for very aggressive.


Buying with HIGHBB

HIGHBB is the opposite of LOWBB. It buys when the price of the coin is ALL_buy_value % above the HIGHBB line if the value is positive, and ALL_buy_value % below the line if the value is negative. See LOWBB above to understand how this works for populating the PBL.



Buying with SMA or EMA strategies (SMA/EMAGAIN, SMA/EMASPREAD, SMA/EMACROSS)

ALL_buy_strategy = SMAGAIN (or SMASPREAD, SMACROSS)
ALL_buy_value = X
ALL_buy_value_limit = Y

Note: SMA and EMA buy strategies are very similar. Simple Moving Average and Exponential Moving Average are calculated somewhat differently, but the strategies trade very similarly, so we will not duplicate the explanations here. Just replace EMA with SMA in your strategy if you wish.

Buying with SMAGAIN

When using SMAGAIN, the main setting that affects the PBL is ``ALL_buy_value`` (which, remember, is a percentage). For a coin pair to be bought using SMAGAIN, the ALL_buy_value must be equal to or less than the value of the lower SMA band multiplied by (1 + ALL_buy_value expressed as a percentage). So, in other words,

Buy Price < = Lower SMA value * (1 + ALL_buy_value/100)

So, for the PT bot to even being to consider a coin pair to be put on the PBL, it needs to be close to the Buy Price. How close the current price needs to be is a closely guarded secret, but it must be reasonably close, say within 10%.

Thus, as an example, if you have no items in the PBL, and your ALL_buy_value is set to 0 (which would make the buy price be exactly the low SMA value), and you look at your exchange and see that all the current coin pairs are up 10 or 20%, then your calculation of Buy Price is not close enough current prices of all the coin pairs and the ALL_buy_value may need to be increased.

What are normal values for ALL_buy_value for SMAGAIN? Values normally range between -2 for very, very conservative (things are going down in the market and you want to make sure you don’t buy unless the coin is 2% below the low SMA line), to 0 for somewhat conservative, to 1-1.5% for somewhat aggressive, to 2% for very aggressive.

ALL_buy_value_limit in SMAGAIN puts a lower limit on your ALL_buy_value setting so that you will not, for example, go below -X% of the low SMA line. See Buy & Sell Strategies for details on this setting, but it will affect PBL if your coin pair price is below that limit.


Buying with SMASPREAD

This is similar to SMAGAIN, but the ALL_buy_value is a percentage spread between the fast and slow SMA lines. If your coin pairs are not populating the PBL, consider the current spread of the SMA lines, and adjust your ALL_buy_value accordingly.


Buying with SMACROSS

Buying with SMACROSS is similar to SMAGAIN, but the two SMA lines must have crossed within the last SMA_cross_candles (set in Indicators.configuration) value, minus one candle (e.g. if SMA_cross_candles is 5, then the cross must have occurred within the last 4 candles). In addition, the current value of the coin must be below the lower SMA line by ALL_buy_value % (again, similar to SMAGAIN explained above and in Buy & Sell Strategies.

Thus if your PBL is not being populated, adjust both your SMA_cross_candles value (in Indicators.configuration file) and your ALL_buy_value in Pairs.configuration.



Buying with LOSS strategy

Buying with LOSS says that to buy, the current coin pair price must be equal to or below ALL_buy_value loss % of the coin pair within the last 24 hours. Thus, the buy price is calculated:

Buy Price < = Current Coin Price * (1 - [ALL_buy_price/100])

The PBL will not be populated with possibly buys if they are not near the Buy Price calculated above. If you are not getting PBL listings, try adjusting the ALL_buy_value closer to 0, to allow for a smaller loss.

Common Values for ALL_buy_value with LOSS 0 is the lowest possible value. Using 0 says that the coin should be purchased if the current value of the coin is equal to or less than the loss on that coin in the past 24 hours. If that coin is up in price in the past 24 hours, therefore, it will not be considered for the PBL unless that gain is close to zero. Any value greater than 0 is more conservative.



Indicators.configuration file

The following settings affect the PBL.

BB_period = 300
BB_sma = 20

The longer the BB_period setting, the smoother the BB lines will be. There will be fewer times that the coin pair current price will get near the lower or upper BB lines, and therefore fewer possible buys. However, this is not bad, as often times the longer settings avoid pump and dump volatility.

To populate the PBL, you need to pay attention to the length of your candles. 5 and 15 minute candles are common in bot trading, although longer candle lengths of 30 minutes, 1 hour and 4 hours are not out of the question if you want more conservative trends.

The period length determines the candle size on your chart. 300 (seconds) is 5 minutes. 900 is 15 minutes, 1800 is 30 minutes, etc.

BB_sma is the number of periods to use in calculating the SMA average. The more periods, the smoother the line, and the less reactive the BB lines are to price swings. This may affect the PBL.


SMA_period = 300
SMA_1 = 24
SMA_2 = 12
SMA_cross_candles = 5

The SMA_period, SMA_1, SMA_2 are similar to the BB_period and BB_sma above. The SMA_cross_candles was discussed in the Buying with SMACROSS section above.


EMA_period = 300
EMA_1 = 24
EMA_2 = 12
EMA_cross_candles = 2

The EMA_period, EMA_1, EMA_2 and EMA_cross_candles are similar to their SMA counterparts above.

TOP




[authored originally by @iAmVae_Victus 2017.12.26]

No, you do not. The changes are applied to the bot as soon as you save the file (if you are editing the configuration files manually with a text editor). Also, as of 1.2.6.1, you may change the settings once the bot is up an running from inside the Web browser via HotConfig.

TOP




[authored originally by @iAmVae_Victus 2017.12.27]

It is pretty easy actually. Below are the main PAIRS and DCA properties files changes you need to make.

PAIRS.properties

See the pairs.properties wiki page

# Comments marked with ### Comment ### are for USDT specifically
 
### change this to USDT ###
MARKET = USDT
 
###################################################### 
##                                                  ## 
##         B U Y  A R E A   B I T T R E X           ## 
##                                                  ## 
######################################################
 
ALL_trading_enabled = true
 
# (or false or -1, -2, etc)
ALL_DCA_enabled = true 
ALL_sell_only_mode = false
ALL_panic_sell_enabled = false
 
#ALL_enabled_pairs = ALL or
ALL_enabled_pairs =  USDT-OMG, USDT-LSK
 
# ALL_buy_strategy (LOWBB, HIGHBB, LOSS, SMAGAIN, EMAGAIN, SMASPREAD, EMASPREAD, DISABLED)
ALL_buy_strategy = LOWBB
ALL_buy_value = 0
ALL_trailing_buy = 0.25
 
###  (this is $50 USDT) ###
ALL_max_cost = 50
ALL_max_trading_pairs = 0
ALL_max_cost_percentage = 0
 
### (this is $50 USDT) ###
ALL_min_buy_balance = 50
### (this is $1,000,000 - pick your own level) ###
ALL_min_buy_volume = 1000000
ALL_min_buy_price = 0.001
ALL_max_buy_spread = 1.5
 
######################################################
##                                                  ##
##         S E L L   A R E A   B I T T R E X        ##
##                                                  ##
######################################################
ALL_sell_strategy = GAIN
ALL_sell_value = 1
ALL_min_profit = 1
ALL_trailing_profit = 0.25
 
All_stop_loss_trigger = -60
ALL_stop_loss_timeout = 0
 
#there are other settings to include here, see the Pairs.properties Wiki page

DCA.properties

See the DCA.properties wiki page

# Comments marked with ### Comment ### are for USDT specifically

######################################################
##                                                  ##
##                B U Y  A R E A                    ##
##                                                  ##
######################################################
ignore_sell_only_mode = false

### (This is $500 USDT) ###
max_cost = 500
max_buy_times = 4
### (this is $50 USDT) ###
min_buy_balance = 50
min_buy_balance_percentage = 0

trailing_buy = 0.17

buy_strategy = ANDERSON
buy_style = DOUBLEDOWN
buy_trigger_1 = -2
buy_trigger_2 = -3
buy_trigger_3 = -3
buy_trigger_4 = -4
buy_trigger_5 = -4
buy_trigger_6 = -4

stop_loss_trigger = 0

max_buy_spread = 2

######################################################
##                                                  ##
##                  S E L L  A R E A                ##
##                                                  ##
######################################################
sell_strategy = GAIN
sell_value = 1
sell_trigger = 1
trailing_profit = 0.25

buy_available_volume_trigger = 125

pending_order_wait_time = 0

TOP




All properties starting with “ALL_” in the pairs.configuration file can also be set as “coinpair_” to act on a specific coin. This is useful when you want to do something (or a series of things) to one or more coins, differently from your main buy or sell strategy.

Most options can be turned off by indicating “false” or setting a value of 0, and turned on by “true”.
A coin pair setting takes priority over ALL_ settings

Look in Pairs.configuration to see which settings are able to be used for single coin pairs. It is denoted by COIN-PAIR ENABLED below each setting if it can be used.

ALL coin pair examples on this page are for Poloniex exchange.


Example: Turn off trading for a single coin

In addition to ALL_trading_enabled = true you would add BTC_ETH_trading_enabled = false


Example: I want to panic sell a single coin.

Add BTC_ETH_panic_sell_enabled = true to your pairs.configutation file.

This is assuming you are on Poloniex and selling your ETH bought with BTC.

COIN-PAIR syntax: Poloniex coin pairs are defined like BTC_ETH
Bittrex coin pairs are defined like BTC-ETH
Binance coin pairs are defined like ETHBTC


Example: I want to not sell a particular coin

Add BTC_ETH_trading_enabled = false to your pairs.configuration file.

This is assuming you are on Poloniex and selling your ETH bought with BTC.

COIN-PAIR syntax: Poloniex coin pairs are defined like BTC_ETH
Bittrex coin pairs are defined like BTC-ETH
Binance coin pairs are defined like ETHBTC

TOP




TOP




Sell value is the amount you want as profit, if you dont set trailing profit, as soon as the price reaches that amount - BOOM! The bot sells.

Now you say. I want 0.5% trailing_profit. meaning. I want to risk 0.5 in order to gain more. Why risk ?

If you have sell_value at 2%, the bot will not sell anymore when it reaches 2%,because we gave it 0.5% breathing room, so, if the price goes to 2.3%, we mark that down as the highest value. Now the price goes down to 1.9%, the bot won't sell, because it is under our 2% gain value and 0.4% change is still within our breathing room: 0.4% = 2.3 - 1.9 That is the risk I am talking about. The profit reached 2% but the bot did not sell because of trailing profit.

Now if the price continues to go down, you are left with a bag. But not this time!

The price goes up to 2.8% then 3.5%. So we mark down 3.5% a our highest value, then the price reaches for 3.7% profit!

So when will we sell? Our gain was set at 2%!

In a sudden movement the price goes down to 3.1% just like that: 3.7% - 3.1% = 0.6%

Our trialing profit was set at 0.5% and 0.6% is > 0.5% so enough risk. Now we sell!

TOP




While ProfitTrailer does not endorse or recommend any particuar VPS vendor, there are several that have been reported to be compatible by other users. Following are some of those. This is not a complete list.

TOP




[Edited by @iAmVae_Victus 2018.01.01]

So you want it to start buying, even though the price is still in your not buy range for BTC drop? You can set ALL_price_drop_trigger=0 then set drop_recover_triger to a value that will reset the price. On the next buy attempt, the btc price check will occur and then sell only mode will be disabled.

Sell Only Mode (SOM) is turned on in the PT bot when the triggers that are in the Pairs.configuration file are tripped by rising or falling BTC, or by consecutive buys. Read about those triggers here.

But what if you want to turn off SOM? That's not quite straightforward and deserves some explanation. When SOM is on, there are conditions that might cause prices of alt coins to go down steeply, based on historical patterns, and therefore it is not advisable to be trading at the current time. But, if you want to turn off SOM, here is what you can do.

1) Determine why the SOM is triggered by holding the mouse over the SOM in the browser window and read the message that pops up. This will guide you to which trigger to adjust.

2). Change the trigger value. For example if the BTC_price_rise_trigger has tripped, and the current BTC has gone up 5%, and your trigger is set for 4%, you would need to change your trigger to more than 5%. OR, you can set that trigger to 0, and set the reset trigger, the ALL_btc_price_rise_recover_trigger in this case, to a value that will turn off SOM.

3). Save the Pairs file, then STOP AND RESTART THE BOT. If you do not stop and restart, then the SOM will NOT be turned off.

4). Alternatively, If you don't want to permanently change your trigger settings you have these options:

  • The options below only work if you have set a password for your monitoring screen!
  • Manual FORCE override

TOP




[added by @iAmVae_Victus on 2018/01/01]


WARNING: Using ProfitTrailer on one account with multiple instances of a bot is not recommended. The bot is not designed for this. Besides multiple untested side effects and trading conflicts within the PT bot itself, there is a high likelihood of flooding the exchange with API calls and getting banned from trading, putting your investment in the bot and in your time and effort at risk.

This guide assumes that you are using a second instance on 1) a new account on the same exchange (to trade USDT or ETH for example), or 2) to create a new instance on a different exchange.


For help with setting up a bot on a VPS, please see this guide in the VPS section. This has additional info on setting up a second instance in a VPS environment in Linux, and managing that remotely in a Windows environment (thanks to Diesel for his work on that)


Setting up a second (or 3rd or 4th) instance of the ProfitTrailer bot is simple.

1. Shut down the first PT bot and make a copy of the folder containing all the PT files.

2. Restart your first bot and keep making Lambo profits!

3. Change the settings in the configuration files as follows:

  • Change the Port in the application.properties file to another unique, unused port. The default is 8081. For example, make the next bot use 8083, and the next one 8085, etc. If you get an error that the port is in use, change it.
  • If you are changing to a new exchange, if you have not yet registered the license for that new exchange, you will need to go to PT Assistant bot and register that license along with one new public API key from that exchange (get that first). Go here to talk to that bot: https://telegram.me/ProfitTrailerAssistantBot. Detailed instructions on registering your bot are here.
  • If you are changing to a new exchange (BITTREX, POLONIEX, or BINANCE), then enter the correct exchange in the trading.exchange setting in application.properties.
  • If you are changing to a new exchange, make sure any reference to coin pairs are modified to be the correct format for the new exchange (BTC-ETH is Bittrex, BTC_ETH is Poloniex, ETHBTC is Binance format).
  • If you are trading on the same exchange but to a new account, get your new API keys and put them in the configuration.properties file. You will also need to register that API key with your PT license so the bot will work. Go here to talk to that bot: https://telegram.me/ProfitTrailerAssistantBot. Detailed instructions on registering your bot are here.
  • Make sure your Dust settings are added properly for your exchange. Go here for more info on Dust in configuration.properties.
  • If you want to make any adjustments to your buy or sell settings, do that based on this info.

TOP


  • de/faq.1517841352.txt.gz
  • Last modified: 17 months ago
  • by t1m3c