Mooncell Sending Controllers: MTB400E vs MTB2000E
Only two Mooncell sending controllers make up this family, and their difference is one sentence: the MTB400E loads 4 Gigabit ports (2.6M pixels) at 4K@30Hz-class intake; the MTB2000E loads 20 ports (10.4M pixels) at full 4K@60Hz. The sending controller is the “transmit-only” link in a control chain – it takes an already-processed picture and broadcasts it to receiving cards. If your plan involves picture scaling, windowing or color work, that belongs to a video processor (or a 2-in-1), and this comparison explains exactly how far each controller goes before your architecture needs the next box up.
Quick Answer: Which Mooncell Sending Controller Fits Your Build?
Under 2.6M pixels, 4K@30Hz-class sources → MTB400E. From 2.6M to 10.4M pixels, or any 4K@60Hz source → MTB2000E. Above 10.4M pixels, or once you need multi-window processing in the same box → step out of the sending-controller tier into a 2-in-1 processor such as the MVB12E (7.8M) or M40 (26M), which do both jobs.
Start from the three numbers that define the tier – ports, pixels and input capability – then decide. The table below puts the two controllers side by side before we look at use cases.
MTB400E vs MTB2000E: Specifications Compared
| Specification | MTB400E | MTB2000E |
|---|---|---|
| Network ports | 4× GbE | 20× GbE |
| Max load | 2.6M px | 10.4M px |
| Main video input | 1× HDMI 1.4, up to 3840×2160@30Hz | 1× HDMI 2.0, up to 3840×2160@60Hz |
| Additional input | 1920×1200@60Hz-class | DP1.2 video input |
| Input frame rates | 30 / 50 / 60 / 120Hz compatible | 30 / 50 / 60 / 120Hz compatible |
| Cascading | USB control interface for multi-unit setups | USB cascading across multiple sending cards |
| Diagnostics | Gigabit Ethernet error rate detection | Gigabit Ethernet error rate detection |
| 3D support | – | Active 3D display reported in spec |
| Central control | – | RS232 wired to control panels |
| Spec version cited | V4.0 | V4.0 |
The per-port math deserves a note, because it surfaces a real difference between tiers. The 2-in-1 V-Series engines and the 40-port 2-in-1 sit at roughly 650,000 pixels per port (1280×512 load per sheet), but the MTB2000E’s 10.4M over 20 ports averages closer to 520,000 per port. Same port standard, different advertised total – which is exactly why you quote against the published total, not the per-port rule of thumb.
MTB400E: The 4-Port Controller for Small and Mid-Sized Screens
The MTB400E is the compact member: 4 ports, 2.6M pixels, a single HDMI 1.4 main input with backward compatibility (3840×2160@30Hz top, plus 1920×1200@60Hz-class intake), and the same 30/50/60/120Hz input frame-rate tolerance as the big unit. Typical match: screens from about a 1M-pixel window display up to 2.6M-pixel walls whose sources are 1080p-class or 4K@30Hz.
Two smaller specs deserve honest weight in a quote. It supports Gigabit Ethernet error rate detection – a diagnostic line item that finds failing cables before a client does. And its USB control interface is built for controlling multi-unit setups, which keeps multi-screen projects on one handset without an extra computer.
MTB2000E: 20 Ports and 10.4M Pixels for Large Walls
The MTB2000E is the tier’s flagship: 20 ports, 10.4M pixels, full 4K×2K@60Hz image processing and transmission, an HDMI 2.0 main input (3840×2160@60Hz backward compatible) plus a DP1.2 input. That combination covers most medium-to-large venue walls in a single unit – the canvas where 4K@60Hz sources appear and the unit count stays at one.
It also carries the interface set for professional rooms: RS232 for central control, LAN 100M host debugging, and active 3D display support reported in the specification – relevant if your content plan includes 3D or fast-motion creative frames. Note the DP path: with HDMI 2.0 plus DP1.2 on the same box, no adapter is needed for a laptop-first conference wall.
Cascading, Frame Rates and Diagnostics: What the Spec Sheets Skip
Cascading. Both units can be controlled in multi-unit setups – a long video wall or a signal-logic project that needs two controllers in one chain is a supported topology when the control interfaces connect over USB. What the spec does not say: each unit shows up as its own port group, so the mapping software owns the arrangement spanning multiple devices.
Frame rates 30/50/60/120Hz. This compatibility line is a practical escape valve: sources that run at 50Hz (European projector chains), 120Hz (content with flicker-sensitive camera work or high-speed motion) or standard 60Hz all feed into either controller. The catch is on the input resolution side – the MTB400E’s main jack is HDMI 1.4 (4K@30Hz), so 4K@60Hz sources are the MTB2000E’s requirement, not an option.
Error rate detection. When a field visit starts with a few deadish modules and ends with a drop-in cable, the diagnose step is exactly this: error rate detection over the Gigabit links points at the bad run without a scope. It is present on both models, which is one of the underrated reasons to keep a spare unit tested in the same rack.
When You Should NOT Use a Sending Controller
When your wall needs processing. The sending controller transmits; it does not rescale or create windows. Four scenarios that move you off this tier: a 4K60 source into a non-4K wall, multi-source video walls, oversized canvases with custom aspect ratios, and content with color-critical playback – the LED video processor guide covers the processor chain in detail. A 2-in-1 such as MVB4S Pro (2.6M, 4 ports) or MVB20E-G (13M, 20 ports) fills the gap when that processing belongs in the same box as the sending.
When content is offline signage. A sending controller demands a live source. For digital signage with playlist content and no PC at the wall, the MB401 media player is the class that belongs – our LED display media player guide draws the offline-versus-live line precisely.
When the wall exceeds 10.4M pixels. Past the MTB2000E, the answer is not a bigger sending controller – it is a 26M-pixel 2-in-1 or a hot-swap splicer chassis. See the Mooncell 2-in-1 comparison for the pixel-by-pixel decision table.
Selection Table: MTB400E vs MTB2000E by Build
| Build profile | Recommended | Why |
|---|---|---|
| Single screen up to 2.6M px, 4K30 source, small wall | MTB400E | Four ports cover the wall; input matches a common 4K signal |
| Large wall or ceiling run up to 10.4M px | MTB2000E | 20 ports and the highest published load in the sending tier |
| 60Hz or high-frame-rate source into mixed walls | MTB2000E (verify) | Higher input tolerance per spec; confirm the rate against your source |
| Multi-unit wall over one box’s load | MTB2000E cascaded | USB cascade keeps the units in one control group; wire unit-to-unit, not video-to-video |
| 26M+ px or multi-source canvas | Move off this tier | 2-in-1 processors or a splicer chassis – sending controllers are not the right class |
What is a Mooncell sending controller?
A device that broadcasts an already-processed video signal to LED receiving cards through Gigabit Ethernet ports. It does not scale or window the picture – it sends it. Mooncell offers two models by load capacity: MTB400E (4 ports, 2.6M px) and MTB2000E (20 ports, 10.4M px).
What is the difference between MTB400E and MTB2000E?
Port count, load and input generation: the MTB400E has 4 ports and 2.6M pixels with HDMI 1.4 up to 3840×2160@30Hz; the MTB2000E has 20 ports and 10.4M pixels with HDMI 2.0 up to 3840×2160@60Hz plus DP1.2 and RS232.
Can the MTB2000E drive a 4K LED screen?
Yes – its load ceiling is 10.4M pixels, which covers a 4K canvas (8.3M) with room, and its HDMI 2.0 and DP1.2 inputs accept 3840×2160@60Hz. It also supports 3D display in the specification and carries RS232 for central control.
How many pixels per network port does a sending controller load?
The sheet examples show 655,360-pixel-per-port loading at 1280×512 for Mooncell controllers, but advertised total loads are not all equal: the MTB2000E’s 20 ports total 10.4M, not the arithmetic maximum. Always match against the published total of the unit, not the per-port number.
Do I need a separate processor with a sending controller?
Yes – in the classic three-box architecture. The sending controller takes the processed picture out; the processor does the picturing. If you want one box, the 2-in-1 family is the alternative, and for most walls under 10.4M it is the cleaner choice.
Which frame rates are supported?
Both controllers tolerate 30Hz, 50Hz, 60Hz and 120Hz input frame rates per the official specifications. The input resolution tier is the real gate: MTB400E is 4K@30Hz-class, MTB2000E is 4K@60Hz-class.
Can sending controllers be cascaded?
Yes. The MTB2000E specification describes USB communication control cascading multiple sending cards, and both units support handsets for multi-unit setups. Map the same pattern across units in the software, each unit keeping its own port group.
How do I know which cable has a problem?
Use the Gigabit Ethernet error rate detection that both units support: run detection per network port and the poor link points itself out. Rack-mounted cabinets with thousands of modules is where that diagnostic saves the client a service call.
Should I buy a sending controller or a 2-in-1 processor?
Ask if the wall needs processing. If the source signal and canvas match (scaling not required) and the load fits the controller tier, a sending controller is the more direct box. If you need scaling, windows or mixed sources in one unit, the 2-in-1 family replaces both boxes for the same wall.
What is the maximum load of the MTB400E?
2.6 million pixels across its 4 ports. At 655,360 pixels per port full load (1280×512), that is the natural capacity; 4K@60Hz-class sources are handled better by the MTB2000E’s HDMI 2.0 input.
Bottom Line: Pick by Ports, Pixels and Input Gen
2.6M and 1080p/4K30 sources → MTB400E. 10.4M and 4K60 sources → MTB2000E. Anything that needs processing, multi-window, or more load — move up to a 2-in-1. Send your screen size and sources for a one-line control stack recommendation with factory-direct pricing.
For the fundamentals of the whole chain – processor, sending, receiving – read the LED control system guide first.
Specification sources: official Mooncell MTB400E Specification V4.0 (4×GbE, 2.6M px, 1×HDMI 1.4 up to 3840×2160@30Hz, 1920×1200@60Hz-class input, 30/50/60/120Hz input frame rate compatibility, Gigabit Ethernet error rate detection) and MTB2000E Specification V4.0 (20×GbE, 10.4M px, full 4K×2K@60Hz, 1×HDMI 2.0 up to 3840×2160@60Hz, DP1.2 input, USB cascading, RS232, active 3D reported) – published via www.mooncell.com.cn. Per-port load figures are sheet notations; verifiable totals are the advertised capacities above. Performance claims remain manufacturer-specified maximums under stated conditions.
