OrderMan - Ordering interface for NOW + Amibroker
- Thread starter TracerBullet
- Start date
Instead of AXISBANK future it places order on ABIRLANUVO future. Where am I wrong? AXISBANK_F is present in RTDMan.ini
2) Scrip details should match with what you have in Order window. Its not amibroker alias. AXISBANK_F is not found, so it seems it remain as default
3) AXISBANK_F = Amibroker Alias = ini file name = name in Orderman.ini. I think i have mentioned all of this in ini file, if something can be added let me know.
4) Still, i thought in case such as this, AHK will give exception since input value is not dropdown. Anyway, in future, we can add verification code to check whether each field in order window matches with what we expect. This will avoid wrong order creation/updation. Will do it later, as its not that imp.
AXISBANK_F = Amibroker Alias = ini file name = name in Orderman.ini.
Of course it is like that. You can see the name of file in my image. It is AXISBANK_F. It is present in Orderman.ini. Therefore, Drop down is AXISBANK_F. That is also seen in the image. The name of scrip is also AXISBANK_F in Amibroker. I picked up entry stop and target from Amibroker.
Checked with Autosubmit=false. It enters ABIRLANUVO.
Of course it is like that. You can see the name of file in my image. It is AXISBANK_F. It is present in Orderman.ini. Therefore, Drop down is AXISBANK_F. That is also seen in the image. The name of scrip is also AXISBANK_F in Amibroker. I picked up entry stop and target from Amibroker.
Checked with Autosubmit=false. It enters ABIRLANUVO.
Last edited:
are boss, please read again.
"Scrip details should match with what you have in Order window. Its not amibroker alias. "
What you put in that 1 line should be same as what we must set in Buy/Sell window. How else will it fill that data? So for AXISBANK
your AXISBANK_F.ini will have below ( not tested, just copied from Marketwatch)
Scrip = NFO,FUTSTK,AXISBANK,,,1
In Orderman.ini, you can set which scrip ini to read and use.
So, there you can put "ScripList = AXISBANK_F" This should match with Amibroker/RTDMan.
I will add one more line in SBIN.ini to mention that it should be same.
"Scrip details should match with what you have in Order window. Its not amibroker alias. "
What you put in that 1 line should be same as what we must set in Buy/Sell window. How else will it fill that data? So for AXISBANK
your AXISBANK_F.ini will have below ( not tested, just copied from Marketwatch)
Scrip = NFO,FUTSTK,AXISBANK,,,1
In Orderman.ini, you can set which scrip ini to read and use.
So, there you can put "ScripList = AXISBANK_F" This should match with Amibroker/RTDMan.
I will add one more line in SBIN.ini to mention that it should be same.
Last edited:
git updated with Initial Partial Target support. You now have box to enter target size, actual target order size will not be more than open position size - so you can enter more but we will only create correct size that covers our position.
Note, i am still testing and bugfixing it in live markets. So far ran fine but yesterday got 1 issue which isn't fixed yet. Problem is that after partial target executes, the orderbook tracker thread may switch off ( status is shown in status bar). Stop order size was reduced ok, so no immediate impact but if this happens, you will need to restart Orderman for future triggers to be handled. On restart, it worked ok (orders are automatically linked). This will be fixed later when i can reproduce and debug it, releasing build so people can test their use cases and report additional bugs if any.
Also, while there are some more things left to do, OM is in reasonably good shape. I am taking a break from major updates, will resume later. Only bug fixes and small code changes for now. This will also allow us to get a stable tested release if enough people use it.
@josh - how has it worked for you? Are you interested in adding stuff - settings gui / swing support etc. If yes, i can work on some guidelines for code structure and we can discuss what and how to do it here ..
Note, i am still testing and bugfixing it in live markets. So far ran fine but yesterday got 1 issue which isn't fixed yet. Problem is that after partial target executes, the orderbook tracker thread may switch off ( status is shown in status bar). Stop order size was reduced ok, so no immediate impact but if this happens, you will need to restart Orderman for future triggers to be handled. On restart, it worked ok (orders are automatically linked). This will be fixed later when i can reproduce and debug it, releasing build so people can test their use cases and report additional bugs if any.
Also, while there are some more things left to do, OM is in reasonably good shape. I am taking a break from major updates, will resume later. Only bug fixes and small code changes for now. This will also allow us to get a stable tested release if enough people use it.
@josh - how has it worked for you? Are you interested in adding stuff - settings gui / swing support etc. If yes, i can work on some guidelines for code structure and we can discuss what and how to do it here ..
@TB,
I still have to get a hang of it. Like, I could not modify an order or target once placed. So I had to open Order Book and modify from there. Similarly, it doesn't allow to place order without target or SL. So I did not try it last week. Normally, I do not set fix target when I enter a trade.
Any way, I have bought a new house and I think I shall be busy doing interiors and shifting etc. tilll 15th July. I may not be able to do lot of coding till then. Though I am studying your AHK code.
I still have to get a hang of it. Like, I could not modify an order or target once placed. So I had to open Order Book and modify from there. Similarly, it doesn't allow to place order without target or SL. So I did not try it last week. Normally, I do not set fix target when I enter a trade.
Any way, I have bought a new house and I think I shall be busy doing interiors and shifting etc. tilll 15th July. I may not be able to do lot of coding till then. Though I am studying your AHK code.
If you need, i can show how it works over Remote desktop when we are both free. Best to test with small qty stock to get used to it and test your workflows.
1) Order update should be possible, Once order is open, update button should become visible and then you can enter new update price / qty and then click on update. Adds are supported too.
2) Target can be empty or 0, then no target order will be created.
Stop cannot be empty. In future, we can add option to create stop at a default distance from entry to allow quick Market order type entry but for now, need to enter stop price. Stop will be mandatory as its one of the main reasons for the tool.
3) Code will be frozen for some time, so you can look at it when free - it wont change much for few months. Also, when you want to add something, discuss it here first - you can maybe begin with GUI stuff and look at order code later as its more sensitive.
congrats for new house.
1) Order update should be possible, Once order is open, update button should become visible and then you can enter new update price / qty and then click on update. Adds are supported too.
2) Target can be empty or 0, then no target order will be created.
Stop cannot be empty. In future, we can add option to create stop at a default distance from entry to allow quick Market order type entry but for now, need to enter stop price. Stop will be mandatory as its one of the main reasons for the tool.
3) Code will be frozen for some time, so you can look at it when free - it wont change much for few months. Also, when you want to add something, discuss it here first - you can maybe begin with GUI stuff and look at order code later as its more sensitive.
congrats for new house.