Lierda Cat.1 NT26FxDx OpenKit TiRTC Feature Demo Guide

Chinese

This guide is for feature verification, customer demonstrations, and acceptance testing. It covers SET, AI, WX, DEV, and LIVE. Complete compilation, flashing, first boot, device binding, and the first AI test with the TiRTC Quick Start Guide.

Applicable project: examples/NT26FxDx_OpenKit_TiRTC
Applicable hardware: L-CT4IT00-YP00W-01_V04, NT26F6D0, F6D_A, 128×64 SSD1306 OLED, three buttons, and ES8311 audio.

1. Pre-demo checks

  1. The NT26FxDx_OpenKit_TiRTC firmware is flashed.

  2. The device is registered on 4G, web-bound, and on the home page.

  3. The OLED, microphone, and speaker work correctly.

  4. Record the demo account, device name, and test contact before starting.

  5. Wait for the device to return to the home page after each feature.

AI, WX, DEV, and LIVE share one TiRTC connection and audio resources. While the device is dialing, in a call, processing an incoming call, or releasing resources, another feature may be rejected or delayed.

2. SET audio settings

2.1 Function

SET is a local device function for adjusting speaker volume and microphone gain. It does not require a web session or a call peer.

2.2 Preparation

  • One powered-on device on the home page;

  • A connected microphone and speaker.

2.3 Procedure

  1. On the home page, use KEY0 to select SET.

  2. Press KEY1 to enter the settings page.

  3. Use KEY0 to cycle through V+, V-, M+, and M-.

  4. Press KEY1 to adjust the selected item by one level.

  5. Press KEY2 to return to the home page.

2.4 Acceptance and limitations

  • The OLED shows the current setting and value.

  • Changes are written to the runtime configuration immediately.

  • Later AI, WX, DEV, and LIVE sessions use the new volume and gain.

  • Values return to defaults after a power cycle.

  • The SET page does not show low-level audio-driver errors; use the serial log for diagnosis.

3. AI voice intercom

3.1 Function

The device exchanges voice with the AI agent bound to it on the TiRTC platform.

3.2 Preparation

  • The device is web-bound;

  • An AI agent is bound to the device under “My Devices” on the platform;

  • The device is on the home page;

  • The microphone and speaker work correctly.

3.3 Procedure

  1. Select AI on the home page and press KEY1.

  2. Wait for the OLED to show LISTENING.

  3. Speak into the microphone.

  4. Wait for AI SPEAK and confirm that the speaker plays the AI response.

  5. After playback, the device returns to LISTENING for another utterance.

  6. Press KEY2 to end the session and return to the home page.

3.4 Acceptance and limitations

  • The state changes from LISTENING to AI SPEAK.

  • Microphone capture and speaker playback are both normal.

  • AI is half-duplex; microphone capture pauses while a response is playing.

  • Push-to-talk is not supported.

  • An AI command cannot actively initiate a DEV call.

  • Without an AI-agent binding, an error normally appears during GET TOKEN.

4. WX WeChat call

4.1 Function

WX provides two-way voice calls between the device and a user of the “Tange Xiaotai” WeChat mini program.

4.2 Preparation

  • The device is web-bound;

  • The WeChat login account is the same as the web-platform account;

  • Device VoIP authorization and reporting are complete in “Tange Xiaotai”;

  • The device is not using AI, DEV, or LIVE audio resources.

4.3 Call WeChat from the device

  1. Select WX on the home page and press KEY1 to open the contact page.

  2. Use KEY0 to select a contact and press KEY1 to call.

  3. Answer on WeChat; the device shows WX TALK.

  4. Press KEY2 on the device to hang up and wait for the home page.

4.4 Call the device from WeChat

  1. Select the target device in the WeChat mini program and start a voice call.

  2. The device shows INCOMING.

  3. Press KEY1 to answer or KEY2 to reject.

  4. After connection, the device shows WX TALK.

  5. Press KEY2 on the device to hang up.

4.5 Acceptance and limitations

  • Both the device and WeChat side can hear two-way voice.

  • Up to eight WX contacts are cached.

  • A call ends automatically after about 45 seconds without an answer.

  • Web binding and WeChat VoIP authorization are independent steps.

5. DEV device call

5.1 Function

DEV provides two-way voice calls between two bound and online TiRTC devices.

5.2 Preparation

  • Two identical or compatible TiRTC devices;

  • Both devices online, bound, and on their home pages;

  • The server has delivered the peer-device contact to both devices;

  • The microphone and speaker work on both devices.

5.3 Procedure

  1. On the caller’s home page, select DEV and press KEY1 to open the device list.

  2. Use KEY0 to select the callee and press KEY1 to call.

  3. On the callee, press KEY1 to answer or KEY2 to reject the incoming call.

  4. After connection, both devices show DEV TALK.

  5. Press KEY2 on either device to hang up and wait for both to return home.

5.4 Acceptance and limitations

  • Both devices can hear two-way voice.

  • DEV contacts are delivered by the server; they cannot be added or approved manually on the device.

  • A call ends automatically after about 45 seconds without an answer.

  • The current device has no camera. Even if a video-type call is received, only audio can be verified.

6. LIVE web real-time voice

6.1 Function

LIVE is real-time voice initiated by the platform web page; it is not a menu item on the device home page.

6.2 Preparation

  • The device is online, bound, and TiRTC runtime initialization is complete;

  • The device remains on the actual home page;

  • AI, WX, and DEV are idle;

  • The web account has LIVE permission.

6.3 Procedure

  1. Confirm that the device is on the home page and is not dialing, in a call, or releasing another service.

  2. Select the target device on the platform web page and start LIVE.

  3. After the web page reports a successful connection, confirm that it receives the device microphone audio.

  4. Send voice from the web page and confirm that the device speaker plays it.

  5. Press KEY1 on the device to end LIVE.

6.4 Acceptance, security boundary, and limitations

  • After LIVE is established, the device continues to show its normal home page; there is no dedicated LIVE page or icon.

  • KEY0 only changes the home-page menu; KEY2 cannot hang up LIVE.

  • The current device transmits audio only and does not send camera video.

  • When admission conditions are met, the remote side may capture the device microphone without a device-key confirmation.

  • A blank video area on the web page is expected because the current implementation has no camera.

7. Detailed state and troubleshooting

This guide covers demonstration flows only. For complete OLED states, key behavior, error codes, timeouts, and recovery strategies, see:

examples/NT26FxDx_OpenKit_TiRTC/tirtc/docs/当前设备操作.md

For code architecture, module responsibilities, and maintenance boundaries, see:

examples/NT26FxDx_OpenKit_TiRTC/tirtc/docs/代码与流程详解.md