← 返回支持中心
proAV

系统集成与商业项目支持

查看支持范围

如问题涉及处理器控制、视频路由、安装设计、集成问题或 proAV 设备 OpenAPI,请从这里开始。

  • 商业安装、处理器、切换器、定标器和分发系统
  • proAV 设备 OpenAPI 控制问题
  • 已落地项目中的系统集成、部署和故障排查

开始支持对话

告诉我们您的设备型号和问题,或选择一个示例问题。

支持知识

从左侧目录选择文章后,在此查看完整内容。

FAQ / Q16pro / Q16pro Startup And Signals

Q16pro startup, connection, and signal troubleshooting

Overview

This article consolidates the most common Q16pro support issues: startup confusion, software discovery failures, black edges, board compatibility, and 4K signal recognition.

Applies to

Q16pro, Q16pro Gen2

Device does not start

  • The front-panel Q button is the power-on control. Confirm the operator is using the front-panel button rather than assuming the unit starts automatically after mains power is applied.

Device not found in XPOSE

  • In software settings, choose the correct device model first.
  • Put the computer and Q16pro on the same network segment before refreshing the device list.
  • On older Windows systems, verify the USB serial driver is installed correctly if the workflow depends on that interface.

Black edge on the source image

  • Confirm the source itself is not already outputting a framed or scaled desktop.
  • In layer management, make sure the layer fills the intended output area.
  • On the source PC, adjust the GPU scaling or zoom mode to Full Screen and reboot if required.

Board and hardware notes

  • Gen1 and Gen2 boards are not interchangeable.
  • In Gen2, the 1U hardware is not common with the larger U-number versions.
  • Communication boards may be basic or PVW-capable, so missing Genlock or PVW connectors can be a hardware-variant issue rather than a fault.

4K recognition and blinking

  • Some 4K boards require the desired interface to be explicitly enabled before the source is recognized.
  • If the connected source blinks, verify the source output resolution and frame rate are supported by the Q16pro.

Firmware guidance

  • Use firmware from the official RGBlink site for the exact model.
  • Do not self-upgrade casually on critical systems without confirming compatibility and rollback planning.