Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
The TG465 edge computing gateway supplied by METRAVON provides a platform for local data processing, protocol conversion and project-specific inference applications. Its published computing configuration is a quad-core Cortex-A55 processor, 2 GB RAM, 16 GB eMMC and a 1 TOPS NPU. Those hardware figures are a starting point for workload evaluation, not a guarantee that a particular application or model will run at the required speed.
Describe the workload before selecting the software image
Separate device acquisition, calculations, local storage and network reporting. State the number of devices, record rate and simultaneous processing tasks. If an inference model is involved, provide its format, input dimensions, precision requirements and expected response time. Include preprocessing and output handling in the test workload.
OpenWrt, Ubuntu and Docker are listed configuration choices. Specify the supported image, architecture, runtime and drivers as part of the deliverable. An existing container may depend on libraries or acceleration support absent from the selected image; container availability does not remove compatibility testing.
TG465 hardware for an application assessment
| Resource | Listed data | Task check |
|---|---|---|
| CPU / NPU | Quad-core Cortex-A55; 1 TOPS NPU | Check supported model operations and measure complete application latency under representative load. |
| Memory | 2 GB RAM; 16 GB eMMC | Allow space for the operating image, runtime, logs and records rather than assigning all storage to data. |
| Ethernet | 4 Gigabit ports | Confirm port roles and application traffic; local port rate does not define cellular bandwidth. |
| Serial | 1 RS232; 6 RS485 | Schedule polling and retries across the required instrument connections without starving other tasks. |
| Digital I/O | 4 DI; 4 relay outputs | Verify electrical ratings, load interfaces and the expected states during application failure. |
| Expansion | USB 3.0/2.0; TF; optional CAN/HDMI/SSD | Order the required hardware and verify driver availability for each intended peripheral. |
Make storage and software maintenance part of the design
A local database or image archive needs a retention and full-storage policy. Specify the sustained write rate and required storage medium; an optional SSD must be included in the order if the application depends on it. Define what is recoverable after an abrupt power loss and test that behaviour before deployment.
Keep application packages, configuration and data recovery separate. Agree who supplies updates, which versions are supported and how a failed update can be rolled back. Limit management access to authorised users and preserve a known working image for replacement hardware.
The protocol list includes MQTT client/broker functions, Modbus RTU/TCP, OPC UA and firmware-dependent DNP3 or IEC 101/104. Specify the required role and implementation. A protocol name does not establish a tested integration with a utility system or an industry certification.
Size the installed system, not just the processor
Cellular options include 5G NR or 4G LTE, with Wi-Fi 6 optional. Match the module and antennas to the operating region. Additional functions such as GNSS, backup energy storage or extra display interfaces require explicit confirmation rather than inference from a family description.
The published supply range is 5-60 V DC and the enclosure measures 162 x 125 x 55 mm. IP30 and the stated -35 to +75 deg C, non-condensing environment require an appropriate installation cabinet. Assess heat with the actual processor load, radio activity and storage devices; an ambient range is not a substitute for testing the assembled system.
Run acquisition, processing and reporting together during acceptance. Record memory use, response times, missing records and recovery after a controlled application or network interruption. Agree numeric acceptance limits from the project requirement before testing rather than inventing a generic benchmark.
Development and inference questions
Q1. Does 1 TOPS specify the number of video channels?
No. Model operators, precision, input size, preprocessing and runtime support affect achievable performance. Test the proposed model and channel count on the offered image; a peak compute figure alone cannot establish frame rate or detection quality.
Q2. Is Docker installed on every delivered unit?
Docker is a configuration option to specify with the operating system and runtime version. Confirm the application image, storage allocation and deployment method in the software delivery list.
Q3. When is a simpler gateway sufficient?
If the job is standard instrument polling and reporting without substantial local software, compare TG453. Select the computing platform when the defined workload or lifecycle requirements justify its development and maintenance scope.
Q4. Who maintains a custom application after handover?
That responsibility belongs in the project agreement. Identify ownership of source code, deployment packages, third-party licences and updates, as well as the process for restoring service on a spare gateway.
Request a workload-based quotation
Provide METRAVON with the TG465 application specification, instrument maps, processing task, storage demand and deployment environment. Request a hardware and software bill of supply plus an agreed acceptance test, so the offer does not confuse an edge-computing platform with a finished application.
