# O function not work on Signal Entry API

**URL:** https://forums.collective2.com/t/o-function-not-work-on-signal-entry-api/1361
**Category:** C2 Software Development
**Created:** [July 1, 2008, 7:52pm UTC](https://forums.collective2.com/t/o-function-not-work-on-signal-entry-api/1361 "2008-07-01T19:52:58Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Index](https://avatars.discourse-cdn.com/v4/letter/i/db5fbb/32.png) [@Index](https://forums.collective2.com/u/Index)
#### Post date: [July 1, 2008, 7:52pm UTC](https://forums.collective2.com/t/o-function-not-work-on-signal-entry-api/1361/1 "2008-07-01T19:52:58Z")

</div>

When using Signal Entry APIs, the O function does not work.  
  
  
  
[http://www.collective2.com/cgi-perl/signal.mpl?cmd=signal&systemid=32820392&pw=flounder&instrument=future&action=BTO&quant=1&symbol=NKU8&](http://www.collective2.com/cgi-perl/signal.mpl?cmd=signal&systemid=32820392&pw=flounder&instrument=future&action=BTO&quant=1&symbol=NKU8&) **stop=O%2B5** &duration=DAY  
  
  
  
or most other futures I have tried, become a market order only. It should become an O+50 order. I have tried this in many different ways or forms, but it seems the O function does not in the Signal Entry API  
  
  
  
If I directly use the O function in the trade entry screen, it works fine  
  
  
  
Ciould you check the logic, and see if anything seems amiss?