Loading...
 
Products »  Extender »  XD600

XD612 and XD614: FAQ

XD612

X612 and CCSPRO compatibility

  • XD612 can work with CCSPRO series smoothly, including mouse switch/Free-Flow.

Are USB headsets supported?

  • XD612 has a USB sound card at the transmitter side (USB socket#2) but analogue audio only at the receiver side. The USB audio will be transformed to the analogue one so USB headsets can't be used at the receiver, unfortunately.

Frozen video once PC is awoken from sleep mode

  • Using a Dell Precision 3630 AMD wx3200 graphics with Redhat 7.7, driving daisy chained monitors at the TX. After the PC was awoken from sleep mode it was noticed that the video and USB were frozen. The only way to recover is to restart the PC. The problem also occurs without the XD612 connected.

No video seen on screen #1 or local pass-through monitor until user logs in

  • Intermittently, a Win10 source PC connected to an MST Hub may decide not to display the desktop on screen 1 of the connected monitors. eg) it may decide to display desktop on screen 2. If this happens, the user may see no video on the local pass-through monitor until the user logs in to windows on the RX.

Upgrade failure observed about 1 in 10 attempts

  • Repeating the upgrade process will be successful in 9 out of 10 attempts.

RX reboot with no local pass-through monitor connected: 50% of time takes about 20 secs to show video

  • Note that the LEDS show GYRG(Green-Yellow-Red-Green) whilst waiting for the video to be displayed. This issue has only been observed with video cards using the Intel UHD630.

If the Local pass-through monitor is using DisplayPort version 1.2, the video does not recover if the Transmitter is rebooted.

  • If a DP1.2 monitor or 2 daisy-chained monitors are used, the user should power the monitor(s) off/on for the video to recover.


XD614

No Video if MST mode is enabled on a monitor when using an MST Hub

  • When using an MST hub on the XD614, make sure that any monitors connected to the hub have MST capabilities turned off. This can cause the number of branched devices to exceed the limit, resulting in no video.

Video flicker on local pass-through port

  • It has been noted that the video on the local pass-through port will judder or flicker every 30-60 seconds. No such disturbance was observed at the RX. This has only been observed on using an old Asus ProArt PA249 1920x1200 monitor, which doesn’t train to the full link rate.

Can not use lower resolution on local pass-through port than at RX

  • The EDID presented to the PC is based upon the RX port 1. If the local pass-through port monitor cannot this resolution, then the display will be blank. This is also mentioned in the user manual.

Frozen video once PC is awoken from sleep mode

  • Using a Dell Precision 3630 AMD wx3200 graphics with Redhat 7.7, driving daisy-chained monitors. After the PC was awoken from sleep mode it was noticed that the video and USB were frozen. The only way to recover is to restart the PC. The problem also occurs without the XD614 connected.

No video on U2415 Dell monitors in a 4-unit daisy chain

  • When using Dell U2415 monitors connected in a daisy chain, it was found that when power cycling, one or more of the monitors video did not resume occasionally. The problem was not observed when using a daisy chain with 3 monitors. Dell have confirmed that they have "Tested this in USA monitor lab. There are known issues with daisychaining with this monitor. The U2415 MST hub has been found to be unstable in certain conditions with later MST DP streams. The monitor was designed in 2014 for release in 2015 and has a very early MST hub specification. Advise is to not daisychain but use DP port to port (Source to Sink)."

Playout of independent DP audio streams with Windows 10

Video displayed out of order when monitors switched off and on again

  • Using Dell Precision 3420 with Ubuntu 20.04, Nvidia P1000 GPU and Startech MST124DP hub. Switched off all 4 connected monitors. However, the Dell P2414HB monitor was still seen buy the GPU, so when the monitors were switched back on, they were presented out of order. The problem was not observed with any other monitors. The problem also occurs without the XD614 connected.

RX becomes unresponsive

  • This scenario has only been observed with the Dell P2715Q monitor and Startech MSTDP124DP hub.
  • If the DP cable between the MST hub and monitor is connected with all equipment powered on, then the RX may become unresponsive. The RX needs rebooting to resolve the issue.
  • Note that the issue has not been observed when any of the equipment is powered after the DP cable has been connected.

Daisy chained HBR3 monitors may present video issues

  • With a daisy chain of mixed HBR2 and HBR3 monitors, it generally works correctly. However, if all monitors are powered off, then on again, occasionally the HBR3 monitor (Dell U2520 in test) would not show video. A reboot of the RX resolved the issue. The problem also occurs without the XD614 connected.

Monitor does not start up with expected 1080p resolution

  • Very occasionally, one or more of the 4 monitors connected to a Startech hub start up in 1024x768 (Windows default). The problem is rectified by changing the resolution in Display Settings. The problem has not been observed if the PC is powered up after the TX and local pass-through monitor. The problem occurs more frequently without the XD614 connected.

No video seen on screen #1 or local pass-through monitor until user logs in

  • Intermittently, a Win10 source PC connected to an MST Hub may decide not to display the desktop on screen 1 of the connected monitors. eg) it may decide to display desktop on screen 2. If this happens, the user may see no video on the local pass-through monitor until the user logs in to windows on the RX.
  • To overcome this, log in to Windows, select the monitor 1 in windows on Display control panel and check box for 'make this my main display'

No video seen with Club3D MST hub

  • No video observed at any of the RX monitors. Recommend using Startech or Prophecy hubs instead.

Upgrade failure observed about 1 in 10 attempts

  • An inconvenience. Repeating the upgrade process will be successful in 9 out of 10 attempts.



Page last modified on Wednesday September 7, 2022 08:13:36 GMT-0000