Start with the Application
A useful configuration starts with the site and its operating requirements. Tell us what needs monitoring or control, where the equipment is located, which events require an alarm and which system receives the data. Existing drawings, a device list and the required response times help establish the scope.
Separate routine measurements from control commands and safety-related functions. They can have different communication, power and acceptance requirements. We review the proposed use before defining the gateway, interfaces and software work, including what the local system must do if the connection to the control center is unavailable.
Wired Devices and Wireless Sensors
Motorola's May 2026 data sheet describes wired and LoRa sensor connectivity, local processing and radio or LTE backhaul options. It also identifies ThingPark integration for LoRaWAN networks. These are platform capabilities; the purchased configuration must include the appropriate hardware, software and regional options.
For wired equipment, provide the signal types, quantities, electrical ranges and distance from the panel. For wireless sensors, identify the exact sensor models, installation locations, update intervals and available network coverage. Sensor compatibility, radio coverage and the path from the gateway to the destination application need separate checks. A wireless connection does not remove the need to plan power, maintenance and loss-of-data indications.
Communications and Host Integration
Motorola lists MDLC networking and protocols including DNP3, Modbus and MQTT in the current data sheet. We confirm the required interface against the selected equipment and software version. The host-side review covers addressing, data mapping, timestamps, quality indications, authentication and the information the operator needs to diagnose a failed connection.
Radio and cellular choices depend on the installation region and available infrastructure. Include the existing radio system, antenna arrangements and any owner requirements for network access. Where a fallback connection is needed, define the changeover behavior and recovery test with the communications and SCADA teams before ordering the configuration.
Local Processing and Security Requirements
MC-Edge can handle processing near the connected equipment. The project should state which filtering, logging or control decisions belong at the site and which belong in the central application. We also define how buffered records, time synchronization and changing values are handled when communications return.
Security features must be matched to the owner's design and the supported product configuration. Review user access, certificate and key responsibilities, network boundaries, firmware maintenance and permitted remote support. An encryption option alone is not a complete system security design. The proposal and acceptance record should identify the configured functions and who maintains them.
Power, Installation and Commissioning
The current manufacturer data sheet lists a 9–30V DC input range. Size the actual supply for the selected controller, interfaces, radio operation and connected equipment, using the relevant model ratings. Panel layout also needs space for termination, antenna routing, service access and the environmental protection required at the site.
Commissioning follows the agreed application and interface requirements. Checks can include device readings, scaling, commands, alarms, communication interruption, power recovery and the resulting host indications. We identify documentation and training in the scope so the customer's staff can operate and maintain the delivered configuration.
Request an MC-Edge Configuration
MC-Edge equipment is available through a configuration inquiry. Send the application description, device list, communications requirements, site country and required schedule. We can then review equipment availability and separate the hardware, licenses, engineering and installation elements of the quote.
For a migration from another Motorola platform, include the existing controller and radio revisions plus application backups. A common protocol or manufacturer does not make a new gateway a drop-in replacement. The review must account for wiring, application logic, data exchange and the planned field changeover.