Strategy Settings with Stoxxo Intelligent Trading Bridge

Requirements


Traders may have multiple strategies to trade with different rules for each strategy. It is possible that he
may expect a 3:1 Risk Reward ratio in one strategy where he may have 2:1 in another. Strategy for NSE
may have an end time of 15:00 whereas strategy for MCX may have 23:00.
In Bridge you can create multiple strategies with their own settings which will be independent of other
strategies. Multiple Symbol Mappings can also be created for different strategies and even single mapping
can be used for multiple strategies.
Here you can even link strategies to the particular user(s) / Broker. So that strategy will run only on that
particular account. Below are the fields that can be set for a strategy with their description.
STRATEGY SETTINGS PARAMETERS

S.NOPARAMETE
R
VALID
INPUT
DESCRIPTIONREMARKS / EXAMPLE
1IsEnabledTick BoxYou can enable / disable Strategy.
Bridge will check for enabled
strategies only.
2Strategy
Tag
Alpha
Numeric
Text
In other means it is Strategy Name.
This can be of Alphanumeric and will
be matched from Signal’s Strategy
to map with particular strategy.
This will be used to identify any
strategy.
Example : DEFAULT, STG1,
MCX_CRUDE, OPT_HEDGE etc.
3No
Duplicate
Signals for
Seconds
(Optional)
NumberIt can be used to save from Strategy
Misfire. In some cases, strategy
coding keeps sending the same
signal for a certain time due to any
reason, however you may wish to
place just 1 order.
By using this field, you can avoid
duplicate signals for the mentioned
seconds.
To identify the unique signals, it
uses the Source Symbol, Strategy
Tag, Transaction Type and Quantity.
If these fields remain the same for
the mentioned seconds, in that case,
next signals would be ignored till
mentioned seconds.
Example: If you mentioned this as
300 and Signal came for ACC, STG1,
LE, 100 then bridge will ignore all
signals with same values till next 300
seconds, however if ACC, STG1, LX,
100 signal came, that will be
processed as it will be treated a
different signal.
This will be very helpful in stopping
duplicate signals or to save from
strategy Misfire.
If you do not want to use this, just
keep it as 0 (Zero)
This will be applicable for Entry and
Exit both signals.
Assume the first signal received and
went for order processing and due to
any reason that order was rejected by
the broker, and another signal came
within 300 seconds, then those
signals will be ignored even if the
previous signal’s order was rejected
by the broker.
4Start Time
(Optional)
Time
Format
00:00:00
Start time for the strategy. Any order
arriving before the start time will be
rejected by the Bridge.
Example: 09:15:00 or 10:30:00 etc.
This setting will be ignored If this field
is left blank, or set as 00:00:00.
5End Time
(Optional)
Time
Format
00:00:00
End time for the strategy. Any order
arriving after the end time would be
rejected by the Bridge.
Do not confuse this with SquareOff
time as this will only stop processing
new orders whereas existing placed
orders will not be cancelled / exitted.
Example: 14:30:00 or 15:00:00 etc.
This setting will be ignored If this field
is left blank, or set as 00:00:00.
6Sq Off Time
(Optional)
Time
Format
00:00:00
SquareOff time for the strategy.
All others belonging to the strategy
will be cancelled (if Opened) or
Exitted and it will make Net Position
as Zero.
It is important to note that it will not
Cancel / Exit CNC / NRML orders
until you enable this feature in
settings.
Example: 15:15:00 or 15:10:00 etc.
This setting will be ignored If this field
is left blank, or set as 00:00:00.
7User
Account
Drop
Down
User Account (s) which will be used
to place the orders for strategy. You
may select one or more accounts as
per the allowed limits.
You can select only Enabled User
Accounts, To populate any user here,
first you need to save the user in the
User tab.
8Unique ID
Req for
Order
Tick BoxIn signal function, it is strongly
recommended that some unique
numeric ID should be provided in the
SignalID field.
This ID can be used to identify the
particular signal in case of Exit
Signal and this will also be very
useful to filter the duplicate signals.
This totally depends upon how your
AFL, MQL, NinjaScript was coded. If
that is coded to provide a unique ID
for each signal, then TICK this field.
VERY IMP : If Unique ID is ticked,
then EXIT signal must have
corresponding Entry Order ID so that
particular Entry order will be exited.
9Cancel Previous Open
Signal
Stop & Reverse
These are the signal rules and your
signal processing depends upon it.
Please Refer Signal Rules for
more details.
10Entry Order
Retry
Tick BoxIf ticked, then only Bridge will retry
for Entry Order as per set values.
11Retry
Count
NumberIt specifies the number of times the
bridge will retry for the order if order
placement got failed.
Default Value is: 5, means in case of
any failure, bridge will retry order for 5
times.
12Retry Wait
(Seconds)
NumberIt specifies the waiting time in
seconds between each retry.
Entry Order retry wait seconds
should be atleast 2, minimum
suggested value is 5
Default Value is: 15 seconds, means
in case of any failure, the bridge will
wait for 15 seconds and then it will
retry again till Retry Counts.
13Max Wait
(Seconds)
NumberIt specifies the maximum waiting
time in seconds, after this bridge will
not retry even if there were retry
counts still remaining.
Each request to the broker can have
its own delay and in case of very
slow internet requests may take
longer time. This field is useful for
those cases. This will ensure that it
should not retry if Max Wait time is
over.
Default Value is: 80 seconds, means
before any retry, bridge will first check
total elapsed time is less than then
Max Wait.
14Exit Order
Retry
NumberIf ticked, then only Bridge will retry
for Exit Order as per set values.
All fields have the same meaning as
the Entry Order; the only difference
is their default values.
15Retry
Count
NumberIt specifies the number of times the
bridge will retry for the order if order
placement if failing.
Default Value is: 15, means in case of
any failure, bridge will retry order for
15 times.
16Retry Wait
(Seconds)
NumberIt specifies the waiting time in
seconds between each retry.
Entry Order retry wait seconds
should be atleast 2, minimum
suggested value is 10
Default Value is: 15 seconds, means
in case of any failure, the bridge will
wait for 15 seconds and then it will
retry again till Retry Counts.
17Max Wait
(Seconds)
NumberIt specifies the maximum waiting
time in seconds, after this bridge will
not retry even if there were retry
counts still remaining.
Each request to the broker can have
its own delay and in case of very
slow internet requests may take
longer time. This field is useful for
those cases. This will ensure that it
should not try if Max Wait time is
over.
Default Value is: 300 seconds, means
before any retry, bridge will first check
total elapsed time is less than then
Max Wait.

Leave a Reply

Your email address will not be published. Required fields are marked *