Specifications
MCTRL660-LED-Display-Controller-Specifications-V1.4.4.pdf
NovaStar MCTRL660
Prepare an LED display with MCTRL660: source, map, receivers and sending. Ask GLMedia about rental or purchase and the setup your event requires.
To choose LED sending, first relate the source to the screen map and receiving cards. GLMedia can help evaluate that combination and whether content needs processing before reaching the controller.
MCTRL660 is a sending controller for LED displays with compatible receiving hardware. It accepts video and distributes it to the tiles, serving installations and events with a defined display configuration.
Check the model label: this guide covers the original MCTRL660. MCTRL660 PRO and MCTRL600 have separate documentation. Identify the receiver, tile and firmware before applying configuration files.
For a stage LED wall, we can prepare content to the pixel map and review sending through MCTRL660. If the show alternates computers, cameras or formats, evaluate an upstream switching and image-processing stage. This separates content, source changes and tile sending instead of choosing the system solely by its connectors.
Tell us which display you need to feed and which sources you need to switch between. A pixel map and computer output details help, but provisional information is welcome. This lets us separate controller scope from upstream mixing, adaptation, and operation to quote.
Tiles with compatible receiving cards and their exact configuration file, a video source, signal and data cables, power, and access to the saved setup. Prepare NovaLCT and USB for irregular displays.
Define pixel width and height, each port path, source frame rate and bit depth. At 8 bits, the official page specifies 1920×1200 at 60 Hz; at 12 bits, 1440×900 at 60 Hz. A maximum dimension does not permit any width/height combination.
A test pattern does not verify the source content size or position. Compare the actual computer output with the canvas and map, then check Offset Position. Display area plus offset must fit within the graphics-card output resolution.
EDID advertises a format to the source; it does not automatically fit all content to the wall. Prepare the canvas and scaling at the source or an appropriate processor, and check the result using a reference image.
Request a test image with a visible border and reference labels: the intended area should remain correct with actual content. If media does not match the map, we can evaluate content adaptation or upstream processing before changing receiver settings.
The manual states that both 10 and 12 bits halve loading capacity compared with 8 bits. Recalculate the system and each path before changing modes; a connected cable is not sufficient.
The four port limits cannot be added to override device input and loading limits. Verify format, frame rate and receiving hardware in the same mode planned for operation.
No. In quick configuration, the initial active ports must load equal cabinet counts, in multiples of rows or columns; the last port may load fewer. Each path must follow the configured direction, with the first port starting the physical connection.
The manufacturer directs irregular screens to NovaLCT. If columns are reversed or skipped, compare mapping and wiring before loading a different receiving-card file.
Agree on an output format and test each computer before the event. The manual’s EDID setting configures the resolution requested from the graphics card; then verify its actual output and fit within the map.
We can evaluate upstream switching or processing to normalize sources and prepare presentation backup. The proposal should define source changes and the picture reaching the controller during each change; separate inputs alone do not establish a clean transition.
One possibility is that the correct parameters were not saved to the receiving cards. The manual distinguishes importing a cabinet file into the controller from Save to RV Card, which retains current screen parameters on the receiving cards after power-off. The symptom alone does not establish that cause.
With the system identified and a validated configuration, we can review what was applied and saved. Preserve original files and also record the actual source output; do not try another panel’s file. We can scope preparation, an operator, an off-show startup rehearsal, and recovery using the correct files and units.
| Symptom | Check | Next decision |
|---|---|---|
| Black display | Video availability, Display Control set to Normal, brightness and active ports. | Distinguish a missing input from blocked output. |
| Cropped image | Actual format, canvas, map and Offset Position. | Adjust content without treating EDID as a scaler. |
| Scrambled columns | Data Flow and physical order from the first port. | Correct a map that does not match wiring. |
| Changes do not persist | Check saving to receiving cards after validation. | Distinguish temporary adjustments from retained settings. |
Documented power: 100–240 V AC, 50/60 Hz; rated consumption is 16 W. This is not the power requirement for the entire LED wall.
Do not choose a cabinet file by pitch or brand alone. Preserve the original and verify the tile, receiver and revision before writing. Do not begin troubleshooting with a reset or update.
The model supports port redundancy and master/backup modes. These require a compatible design and a planned failure test; UART control or a video cascade alone does not establish working redundancy.
Choose the document for the model, revision and language shown. Read it here or download the original PDF.
MCTRL660-LED-Display-Controller-Specifications-V1.4.4.pdf
MCTRL660-LED-Display-Controller-User-Manual-V1.4.4.pdf
MCTRL660-LED-Display-Controller-Specifications-V1.4.3.pdf
Find VMP/COEX, ViPlex, NovaLCT, VICP and other tools by platform and version. Check each program’s requirements before downloading.
View software catalogueManual V1.4.4 is dated 2025-06-11. Compare available options with the installed firmware before making changes.
Columns display misplaced image sections although the computer plays the correct design.
We can study the source canvas, physical map, port routing, and receiver configuration; distinguish content errors from distribution errors.
Compare content mapped for that layout or external processing when sources need adaptation; do not attribute scaling to MCTRL660.
Display a pattern naming and orienting each block; inspect every column, then test real content. Preserve the approved configuration before changing it.
A sketch or setup photos, sample content, and available receiver details are enough to begin.
No. The manual directs irregular screens to NovaLCT; cabinet-file import has separate limitations.
No. Identify the system and preserve its parameters first; prepare changes outside live operation.
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.