Google Chat:---
+86-0755-88291180
sales@spotpear.com
dragon_manager@163.com
tech-support@spotpear.com
zhoujie@spotpear.com
WhatsApp:13246739196
WhatsApp:13424403025
| Item | Description |
|---|---|
| Screen Size | 10.1 inch |
| Native Resolution | 800 × 1280 |
| Display Panel | IPS panel |
| Display Colors | 16.7M |
| Viewing Angle | 178° |
| Brightness | 300 cd/m² |
| Contrast Ratio | 800:1 |
| Response Time | 35 ms |
| Refresh Rate | 60 Hz |
| Touch Type | Capacitive multi-touch; the actual number of touch points depends on the software system |
| Touch Interface | I2C |
| Touch Panel | Tempered glass, optical bonding |
| Mainboard Connection | UNO Q's JMEDIA, JMISC board-to-board connectors |
| Camera Interfaces | CAMERA0, CAMERA1 |
| Audio | Two built-in speakers, two 3.5 mm audio jacks |
| Backplate Material | Metal |

| Number | Interface or Component | Description |
|---|---|---|
| 1 | CSI0 / CAMERA0 | External camera interface |
| 2 | CSI1 / CAMERA1 | External camera interface |
| 3 | Type-C port | 5 V power input |
| 4 | Microphone Input / Headphone Output | 3.5 mm combo audio interface |
| 5 | Headphone Output | 3.5 mm audio output interface |
| 6 | RGB LED | Carrier board indicator light |
| 7 | JMISC Connector | Mates with the UNO Q |
| 8 | JMEDIA Connector | Mates with the UNO Q |

Before installing or removing the UNO Q, the carrier board, and the camera cable, shut down the system and disconnect all power. Do not hot-plug the JMEDIA, JMISC, or camera cable.
Place the screen on a support surface that will not press against and damage the panel, exposing the carrier board on the back.
Align the JMEDIA and JMISC connectors of the UNO Q and the carrier board, and stack and connect them in the direction shown in the figure.

After confirming that the connector positions are correct, press evenly to avoid misalignment or forcing insertion at an angle.

Choose one of the following methods to power the UNO Q. Both the power port and the cable must meet the 5 V / 3 A requirement:
Power adapter supply: Connect the power adapter to the UNO Q's USB-C port.

Computer USB port supply: Use a USB-C cable that supports data transfer to connect the UNO Q to a computer, providing both power and data communication.
This product is equipped with two 22 PIN CSI camera interfaces, and only supports connecting IMX219 camera modules. If you do not need to use a camera, you can skip this step.
Shut down the system, disconnect the power, and remove the UNO Q mainboard.
Check the CSI interface pin definitions, and confirm the interface specifications and contact orientation of the camera module and cable.

Correctly insert the cable into the CSI interface and lock the connector. After confirming that the connection is correct, reinstall the UNO Q mainboard and connect the power.
Note: The image is for connection reference only. The specific connection direction of the cable should be based on the interface definition of the camera module, to avoid reverse connection or misalignment.

Some earlier versions of the Arduino UNO Q system may lack the drivers and device tree files required by the screen, causing the screen to fail to work properly. Please follow the steps below to check the system and complete the screen configuration.
Please use Arduino App Lab 0.8.0 or later. If you are using an older version, update it first before configuring the expansion board.
Open Arduino App Lab on your computer. For detailed operations, please refer to the App Lab Usage. Use a Type-C cable to connect the UNO Q to the computer.
After completing the initial setup and account password configuration as prompted, click the Settings (⚙) icon in the lower left corner of Arduino App Lab to enter the Settings page, find the Carriers option, and enable Enable external carriers.

The following prompts may appear when enabling:
Attach carrier board: Please confirm that the UNO Q has been powered off and the screen expansion board has been correctly installed according to the Hardware Connection and Interface Description. After confirming, click "Ok, Got it" to continue.

Update required: This indicates that the current system version does not support the Media Carrier. Click "Update Board" and follow the on-screen prompts to complete the system update and restart. After updating, return to "Settings" > "Carriers" and enable the expansion board feature.

If the system update prompt does not appear, you can continue directly with the subsequent configuration.
Confirm that Enable external carriers is enabled, and select 10-dsi-touch-a in the display device options. If no camera is connected, set both CAMERA0 and CAMERA1 to none.

Click Apply and Reboot, and after the UNO Q restarts, check whether the screen display and touch functions work properly.
You can also enter the UNO Q terminal via SSH or ADB and configure the screen using the command line.
1. View supported devices
sudo arduino-linux-config carrier list
Confirm that the device list contains media-carrier, and that the display device options contain 10-dsi-touch-a.
2. Enable the screen
When no camera is connected, run:
sudo arduino-linux-config carrier enable media-carrier camera0=none camera1=none display=10-dsi-touch-a
If a compatible IMX219 camera is connected to the CAMERA0 interface, you can use:
sudo arduino-linux-config carrier enable media-carrier camera0=type1-2lanes camera1=none display=10-dsi-touch-a
3. Check the configuration
sudo arduino-linux-config carrier show media-carrier
Confirm that the display configuration for the next boot is 10-dsi-touch-a.
4. Restart the device
sudo reboot
After the UNO Q restarts, check the screen display and touch functions.
Turn off the UNO Q and disconnect the power. Connect the camera to CAMERA0 according to the Hardware Connection and Interface Description, and confirm the cable orientation is correct before supplying power.
In App Lab's "Settings" > "Carriers", set CAMERA0 to type1-2lanes, CAMERA1 to none, keep the display as 10-dsi-touch-a, and click "Apply and Reboot".

You can also run the following commands in the UNO Q terminal to complete the configuration.
Using one camera:
sudo arduino-linux-config carrier enable media-carrier camera0=type1-2lanes camera1=none display=10-dsi-touch-a
sudo reboot
Using two cameras:
sudo arduino-linux-config carrier enable media-carrier camera0=type1-2lanes camera1=type1-2lanes display=10-dsi-touch-a
sudo reboot
When you need to take photos or record videos on the desktop, install Cheese in the UNO Q terminal:
sudo apt update
sudo apt install cheese -y
After the installation is complete, open the application from "Applications" > "Multimedia" > "Cheese" on the device desktop.

You can also run the following command in a terminal that is already logged into the desktop, without sudo:
cheese
Before use, exit other programs that are occupying the camera. When you need to test two cameras, first enable CAMERA0 and CAMERA1 according to the steps above.
Open the menu in the upper right corner of Cheese, select "Preferences", and go to the "Webcam" page.

In "Device", select the camera, and set both "Photo resolution" and "Video resolution" to 816 × 616.

Close Preferences and wait a few seconds to observe the image. If capture previously failed, exit and reopen Cheese.
In "Photo" mode, click the capture button and confirm that the photo can be opened.
Switch to "Video" mode, click record, wait about 4 seconds, then click stop and confirm that the recording can be played.
When two cameras are connected and enabled, return to Preferences, select the other camera, check both resolutions again, and repeat the photo and video tests.
Photos are saved by default to ~/Pictures/Webcam/, and recordings are saved by default to ~/Videos/Webcam/. If the system pictures or videos directory has been renamed, or a different save location has been set, the actual local directory shall prevail.
The baseboard provides 2 3.5 mm audio interfaces and has two built-in speakers, which can be used for audio input and output.
Open "Volume Control" from "Applications" > "Multimedia" on the device desktop.

Check the "Profile" configuration in "Configuration". After selecting the desired configuration, check the actual output in "Output Devices", unmute, and set a lower volume first.

| Interface / Mode | Type | Function |
|---|---|---|
| Line Out | 4Pin speaker interface | Line-level audio output, mono |
| Headphones | 3.5 mm audio interface | Supports microphone input and headphone output, stereo |
| Earphones | 3.5 mm audio interface | Headphone audio output, mono |
| Pro Audio | Audio configuration mode | Supports professional audio applications and multi-channel audio input/output |
| Off | Audio configuration mode | Disables the current audio device |
The following commands only switch the switch at the output end. They are applicable to systems where the basic playback routing has already been configured and the corresponding control items exist on sound card 0. First use aplay -l and amixer -c 0 controls to verify the sound card and control items; if the card number differs, replace 0 in the commands. If the playback routing has not yet been configured, prefer using the graphical interface above. You cannot determine that there is sound based only on a successful switch command.
Switch to Earphones:
amixer -c 0 cset name='LO_RDAC Switch' off
amixer -c 0 cset name='EAR_RDAC Switch' on
Switch to Line Out:
amixer -c 0 cset name='EAR_RDAC Switch' off
amixer -c 0 cset name='LO_RDAC Switch' on
When performing a microphone recording test, connect the microphone to the MIC-IN/HPH interface. Do not mistakenly connect it to the Earphones Out interface, as this may prevent recording.
After the connection is complete and the corresponding input is selected and enabled in "Volume Control", you can test microphone recording. The following steps assume that the recording routing has already been initialized; adjusting only the recording gain cannot enable the ADC and recording channel. If it has not been initialized, first complete the routing according to the audio configuration of the current image.
1. Install audio tools
Open a terminal and run the following commands to install the ALSA tools:
sudo apt update
sudo apt install alsa-utils -y
2. View audio devices
Run the following commands to view the recording and playback devices recognized by the system:
arecord -l
aplay -l
Confirm the sound card number and device number corresponding to the microphone. The following uses sound card 0 and recording device 2 as an example; if the actual numbers differ, modify the subsequent commands accordingly.
3. Set the microphone recording gain
After confirming that this control item exists on sound card 0 and that the allowed value range includes 70, run the following command to set the recording gain:
amixer -c 0 cset name='TX_DEC0 Volume' 70
4. Record audio
If recording.wav already exists in the current account's home directory, use a different file name first. Run the following command to record 5 seconds of audio and save it as a WAV file:
arecord -D plughw:0,2 -f S32_LE -c 1 -r 48000 -d 5 "$HOME/recording.wav"
5. Play the recording
After recording is complete, run the following command to play the recording file:
aplay "$HOME/recording.wav"
If recording reports Device or resource busy, it means the recording device may be in use by another audio service or application. Please close the software that is using the microphone, or check the device usage of the current audio service.
This product is equipped with 4 sets of RGB status indicator lights. Each set can independently control the red, green, and blue color channels, and can be used for device status indication and application feedback.
Run the following commands in the UNO Q terminal, using the first set of RGB LEDs as an example:
Light up the red LED:
echo none | sudo tee /sys/class/leds/media-carrier:red1/trigger
echo 1 | sudo tee /sys/class/leds/media-carrier:red1/brightness
Light up the green LED:
echo none | sudo tee /sys/class/leds/media-carrier:green1/trigger
echo 1 | sudo tee /sys/class/leds/media-carrier:green1/brightness
Light up the blue LED:
echo none | sudo tee /sys/class/leds/media-carrier:blue1/trigger
echo 1 | sudo tee /sys/class/leds/media-carrier:blue1/brightness
Turn off the first set of RGB LEDs:
for color in red green blue; do
echo 0 | sudo tee /sys/class/leds/media-carrier:${color}1/brightness
done
Replace the number 1 at the end of the device name with 2, 3, or 4 to control the other sets of RGB LEDs. Different color channels can be lit at the same time to achieve color mixing.
Run the following command to turn off all color channels of the 4 sets of RGB LEDs:
sudo sh -c '
for n in 1 2 3 4; do
for color in red green blue; do
path="/sys/class/leds/media-carrier:${color}${n}"
echo none > "$path/trigger"
echo 0 > "$path/brightness"
done
done
'Connect the keyboard and mouse to a USB-C Hub, connect the power supply to the Hub's PD port, and then connect the Hub to the UNO Q's USB-C port.
Use Host mode when connecting a keyboard and mouse; use Device mode when connecting to a computer via USB for App Lab.
Run the following commands in the UNO Q desktop terminal or via network SSH. The corresponding role node must exist in the system.
Check the current mode:
cat /sys/class/usb_role/4e00000.usb-role-switch/role
If the output is host, no switching is needed; check whether the keyboard and mouse work properly. Otherwise, continue to the next step.
Switch to Host mode. This operation interrupts the USB data connection to the computer.
echo host | sudo tee /sys/class/usb_role/4e00000.usb-role-switch/role
cat /sys/class/usb_role/4e00000.usb-role-switch/role
After confirming that the output is host, check whether the keyboard and mouse work.
The commands above only switch the currently running USB mode and do not configure it to start automatically at boot. If the keyboard and mouse do not work after a restart, check the USB mode again.
The following uses 90° Right (rotate 90° to the right) as an example.
On the desktop, open Settings > Display

Under Rotation, select Right, click Apply, and save.

Create the configuration directory (this can also be run if it already exists):
sudo mkdir -p /etc/X11/xorg.conf.d
Open the touch configuration file:
sudo nano /etc/X11/xorg.conf.d/99-goodix-dsi-rotation.conf
If the file is empty, add the following configuration; if a configuration already exists, modify only the TransformationMatrix line.
Section "InputClass"
Identifier "Goodix DSI touchscreen rotation"
MatchProduct "Goodix Capacitive TouchScreen"
MatchIsTouchscreen "on"
Driver "libinput"
Option "CalibrationMatrix" "5.2 0 0 0 3.2 0 0 0 1"
Option "TransformationMatrix" "0 1 0 -1 0 1 0 0 1"
EndSection
The example above is for 90° Right. If you need another orientation, replace the TransformationMatrix line with the corresponding content below, keeping only one:
# Default portrait, 0°:
Option "TransformationMatrix" "1 0 0 0 1 0 0 0 1"
# 90° Right:
Option "TransformationMatrix" "0 1 0 -1 0 1 0 0 1"
# 180° Inverted:
Option "TransformationMatrix" "-1 0 1 0 -1 1 0 0 1"
# 270° Left:
Option "TransformationMatrix" "0 -1 1 1 0 0 0 0 1"

Press Ctrl+O → Enter to save, and press Ctrl+X to exit. After saving other work, reboot the UNO Q:
sudo reboot
After rebooting, tap the center and four corners of the screen to confirm that the touch positions are correct.
Open the LightDM configuration file on the UNO Q. Keep a backup of the existing configuration before modifying; if the backup file below already exists, use a new name:
sudo cp -n /etc/lightdm/lightdm.conf /etc/lightdm/lightdm.conf.before-uno-q-desktop
sudo nano /etc/lightdm/lightdm.conf
Set the following items in the existing [Seat:*] section; add it only if the file does not have that section. Do not add the section name repeatedly or overwrite other configurations:
[Seat:*]
autologin-guest=false
autologin-user=arduino
autologin-user-timeout=0

Replace arduino with the actual desktop account returned by whoami. This only configures Linux desktop login; it will not automatically log in to website accounts, nor will it disable the standby lock screen. Once enabled, anyone with access to the device can use that account directly.
Save the file and other work, then reboot:
sudo reboot
Confirm that you can enter that account without entering the desktop password. If the login screen still appears, check the account name and whether other LightDM configurations override the above settings.
This method is set when the X server starts, and is applicable to desktops where X11 is started by LightDM. It does not disable the password lock screen; Xfce power management or the screen saver may still reset the timers, so you need to check the display timer in Xfce "Power Manager" and the idle activation settings of the screen saver.
Before modifying, keep a configuration backup using the method in Auto-Login to the Desktop at Boot, then open:
sudo nano /etc/lightdm/lightdm.conf
In the existing [Seat:*] section, find #xserver-command=X, uncomment it, and change it to:
xserver-command=X -s 0 -dpms

-s 0: Set the X server screen saver timeout to 0, disabling that timer.-dpms: Disable the X server's display power management (DPMS).The current screenshot uses [Seat:*], and no longer creates the old-style [SeatDefaults]. If an existing xserver-command contains other parameters, keep the necessary parameters; keep only one effective configuration in the same section.
After saving your work, reboot:
sudo reboot
Open /etc/lightdm/lightdm.conf
sudo nano /etc/lightdm/lightdm.conf
Add -nocursor to the xserver-command in the existing [Seat:*] section.

To only hide the cursor:
xserver-command=X -nocursor
When the always-on setting is also needed, combine the parameters on the same line:
xserver-command=X -s 0 -dpms -nocursor
Do not add a second xserver-command, otherwise it may overwrite the original setting. Keep the three auto-login configuration items; setting only -nocursor will not enable auto-login or fullscreen web pages.
Save your work and run sudo reboot.
Execute in the desktop terminal of the UNO Q's current account; sudo is not required.
xfce4-session-settings
In "Session and Startup", go to "Application Autostart".
Find "Arduino App Lab" and uncheck it.

Close the settings and App Lab windows, log out and log back in or reboot, and check whether App Lab no longer opens automatically.
Monday-Friday (9:30-6:30) Saturday (9:30-5:30)
Email: services01@spotpear.com