> 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-ref/krubakku/cbtoconet_vrxevent.md).

# cbToCoNet\_vRxEvent()

## Explanation

This function is called after receiving a radio packet. The argument [`tsRxDataApp`](broken://pages/-LCSQBsTPXoLivWdwxrd) `*psRx` is passed, the received data (packet contents, address information, etc.) will be stored. The structure is only valid within the calling scope of this callback function, once you leave the function the value is not guaranteed.

{% hint style="warning" %}
This function should not be delayed if it is received frequently. This may cause delays in releasing the receive queue and may result in missed data.

Incoming packets are stored in a FIFO queue by an internal MAC layer interrupt. When it comes under the control of the application loop, it is fetched from this queue and a callback function is executed.
{% endhint %}

## Argument

| Type                                                     | Name   | Remark                                                                                           |
| -------------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------ |
| [`tsRxDataApp`](broken://pages/-LCSQBsTPXoLivWdwxrd) `*` | `psRx` | The data received is stored in this structure. See the description of the structure for details. |

## Returns

None

## Sample code

```c
// display packet content 
void cbToCoNet_vRxEvent(tsRxDataApp *pRx) {
	int i;
	static uint16 u16seqPrev = 0xFFFF;
	uint8 *p = pRx->auData; // pointer to the payload

	// print control info
	vfPrintf(&sSerStream, LB"[PKT Ad:%04x,Ln:%03d,Seq:%03d,Lq:%03d,Tms:%05d \"",
			pRx->u32SrcAddr, // source address
			pRx->u8Len, // payload size
			pRx->u8Seq, // seq number
			pRx->u8Lqi, // LQI
			pRx->u32Tick & 0xFFFF); // time stamp
	// print first 32 bytes
	for (i = 0; i < pRx->u8Len; i++) {
		if (i < 32) {
			sSerStream.bPutChar(sSerStream.u8Device,
				(pRx->auData[i] >= 0x20 && pRx->auData[i] <= 0x7f) ? pRx->auData[i] : '.');
		} else {
			vfPrintf(&sSerStream, "..");
			break;
		}
	}
	vfPrintf(&sSerStream, "C\"]");
}
```


---

# 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, and the optional `goal` query parameter:

```
GET https://sdk.twelite.info/en/twelite-net-api-ref/krubakku/cbtoconet_vrxevent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.