PIKA Forum FAQ

Here you can find answers to questions about how the board works. Use the links or search box below to find your way around.

Error (-104) Resource Busy


Affected DSP Applications 
-- Audio (Play / Record) 
-- RTP (Encode/Decode) 
-- FSK 

Symptoms: 
   1) PK_DRV_E_RESOURCE_BUSY return code received when calling an Audio, RTP, or FSK API function. 
   2) Channel always busy or appears "locked" 
   3) Could appear as a "Channel leak" to the application 

Mostly like to appear: 
- The "intercall" delay is very short ( Wait for the IDLE event and call termination conditions before accepting or placing another call ) 
- IVR system playing multiple PROMPTS ( Not waiting for the IDLE after calling a STOP and Adding more buffers. 
- Memseting the buffer or buffer size before the IDLE even is received will also show the condition of resource busy. 

What to do: 
- Since the PIKA API is asynchronous, it is important to wait for the IDLE event before starting the next audio play on the channel. 

- Don't memset or reset the buffers or the "size" field until the IDLE event is received by the application. 

- Turn ON API logging using PikaSetup for the API and Events in use, and watch the resource handles for the port or ports 
  that appear to be BUSY. Make sure that after the STOP that the IDLE event is received before reusing the application
  buffers passed to the MonteCarlo API ( Before ADDing or STARTing on that resource port again )

Search FAQ

Select this option if you would like your search to look in the text of FAQ items as well as their titles.

Select an option here to specify how you would like your search query to be treated. 'Any words' will return the most numerous but possibly least relevant results, while 'Complete phrase' will return only results that contain exactly what you are searching for.