> For the complete documentation index, see [llms.txt](https://sdk.twelite.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.twelite.info/en/twelite-net-api-expl/twenet-fur/fur-1.md).

# flow: Wireless events

## Events of receving or transmit complete.

![](/files/-LB48ZL6ekn5cHnsq-AE)

* 無線割り込み(受信・送信完了など): Radio interrupt (e.g. reception, transmission complete)
* システム内処理: In-system processing
* イベントFIFO: Event FIFO
* 取り出し: extraction
* 無線イベントの処理は、割り込みで（内部処理）得られた無線イベントを割り込みハンドラ中でイベントFIFOに登録します。登録後メインループ中からイベントFIFOを処理します。:The processing of radio events obtained by interrupts (internal processing) is registered in the event FIFO in the interrupt handler. After registration, the event FIFO is processed from the main loop.
* 割り込み待ち: waiting for interruption
* 無線イベント処理: Wireless event handling
  * 受信データなどのシステム処理: System processing of incoming data etc.
* 受信FIFO: Receive FIFO
* 無線イベント処理(送信完了): Radio event processing (transmission complete)
  * システム処理=>cbToCoNet\_vTx(): System processing=>cbToCoNet\_vTx()
* 無線イベント処理(他): Radio event processing (others)
  * システム処理=>cbToCoNet\_vNwkEvent(): System processing=>cbToCoNet\_vNwkEvent()
* 無線受信処理(受信パケットの処理): Radio reception process (processing of incoming packets)
  * システム処理=>cbToCoNet\_vRx(): System processing=>cbToCoNet\_vRx()
* 割り込み待ち: Waiting for interruption
* 取り出したイベント種別により、いずれかが実行される。同時に複数イベントが登録されている場合はフロー順に呼び出される。: Depending on the type of event retrieved, one of them will be executed. If multiple events are registered at the same time, they are called in order of flow.
* 割り込み待ち: Waiting for interrupt.

## Detailes when transmitting

![](/files/-LB48dlOYVEyLtduQXM-)

* 割り込み待ち: Waiting for interrupt.
* 送信完了無線イベント: Transmission complete radio event
* 送信処理中?: Sending in progress?
  * 送信キューから取り出して、送信処理中のデータに格納: Removed from the transmission queue and stored in the data being transmitted.
  * ToCoNet\_bMacTxReq(), ToCoNet\_Nwk\_bTx() APIによりアプリケーションから送信要求を投入。: ToCoNet\_bMacTxReq(), ToCoNet\_Nwk\_bTx() APIs to submit a request for transmission from the application.
  * 送信FIFO: Send FIFO
  * ※ 送信要求が呼び出された直後の TickTimer を起点として送信処理が行われます。全ての処理が終わった時点でcbToCoNet\_vTx()により結果が報告されます。: note:  The transmission process is performed starting from the TickTimer immediately after the transmission request is called. When all the processing is finished, the result is reported by cbToCoNet\_vTx().
  * 条件に合うもの（送信遅延等）を送信処理中データから一つ選ぶ: Select one of the data in the transmission process that matches the conditions (e.g. transmission delay)
  * 802.15.4 MAC 層へ送信要求を出し、送信完了待ち状態に設定: 802.15.4 Request transmission to MAC layer and set to waiting for completion of transmission
* 送信完了?: Is transmission complete?
  * cbToCoNet\_vTx()を呼び出す: Call cbToCoNet\_vTx()
  * 送信処理中のデータを空にし、送信処理中を解除: Empties the data in the transmission process and releases the transmission process
  * 送信処理中のデータ: Data in the transmission process
* 割り込み待ち: Waiting for interrupt


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sdk.twelite.info/en/twelite-net-api-expl/twenet-fur/fur-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.