User Manual
MDR2400/5800-SR, Orion2410/5810-SRi and Orion 5825-SR
862-01881 Issue 12c Page 109
D Appendix: MDR5800 hardware VERSION 1, 2.x
DIFFERENCES, COMPATIBILITY SUMMARY
Version 1 hardware (Indoor and RF Units) is incompatible with Version 2.x hardware.
The Digital Indoor Unit /RF Unit Twisted Pair Data Interconnection for Version 2
hardware uses 2 twisted pair cables to convey payload and RF Unit control signals
whereas Version 1 hardware uses 4 twisted pair cables.
Notes :
Version 2.x firmware (can be uploaded into the Digital Indoor Unit using the NMS’s
Maintenance option) that can be used in Version 1.x hardware must be obtained from
the product manufacturer. The file is not the same file that is used with Version 2.x
hardware.
Updated RSSI and Power control functionality have been added to Version 2.x
hardware and firmware.
Version 2.x firmware has
1. FTP upload functionality (needs to be activated via the MIB)
2. IP Bridging functionality (half and full duplex – selectable via the MIB).
Appropriate DIU hardware must be used.
3. Band Plan C
4. Refer to the MIB section of this manual and look for the † symbol to see what MIB-
related functionality is in place/activated/planned for Version 2.x + firmware.
5. Functional RF Loopback built-in test feature.
6. Ethernet packet error monitoring and buffer monitoring added to MIB
7. E1 CRC4 payload monitoring added to MIB (only applicable for a single tributary)
8. Digital Indoor Unit PCB hardware revision added to MIB
9. Periodic reporting of RF Link packet errors (adjustable in time, defaulted to 10
minutes) added to MIB.
Version 2.x NMS has
1. Ability to allow the user to connect to the Digital Indoor Unit using PPP (via a serial
cable interface to the DIU’s front panel Element Manager RS232 port) or via
Ethernet (via the front panel RJ45 connector: 10BaseT).
2. Graphical Spectrum Analyzer display
By default, firmware provided for the Digital Indoor Units does not provide a secure
login feature (thereby limiting a user’s ability to ‘set’ MIB variables). Suitably adapted
firmware versions (dependent on hardware version) need to be requested from the
product manufacturer to allow activation of this feature.