Practical answers. Clear conditions.

Send the application, equipment and interface list, installation country, power source, network conditions and expected quantity. Include the exact PLC, sensor or meter model where relevant. We can then confirm a model, regional modem, accessories and a project acceptance checklist.

Do not select by “4G” or “5G” alone. Match the full modem model and regional suffix, supported bands, carrier/SIM requirements and antenna configuration to the deployment country. A product-family label is not confirmation that a particular regional configuration is suitable.

Dual SIM on these products normally selects between cards using one modem. It does not provide two simultaneous independent cellular connections. Confirm the selected model, switching rules and recovery requirements for your project.

No. Both YZW400 cellular versions have five 10/100 Mbps Ethernet ports. The 5G modem option changes the cellular configuration, not the wired-port speed. Use a Gigabit model if the wired network requires it.

Check the model’s physical ports. YZWK001 provides RS232 or RS485 as an order alternative, not both. Models with separate RS232 and RS485 interfaces can use separate ports for different services, but each physical serial port must have one application owner. Check wiring and the active serial service before commissioning.

Provide the register map, slave address, function code, data type, byte order, scaling and polling interval, plus broker address, authentication, TLS requirements, topic and payload. First verify one known read-only register, then confirm the value and timestamp at the broker and application. Use the guide for the selected platform.

Agree timestamps, data-expiry rules and communication status in the point list and payload. Verify a known value, then interrupt the source or network and check the application’s indication and recovery. Do not treat an old retained value or an online gateway icon as proof of a fresh measurement.

No. VPN and DTU provide a communication path. Native PLC acquisition also needs a matching driver, supported address format, firmware and physical interface. MT7628/MT7621 provide the documented Modbus acquisition and remote-service paths; MT7981 PLC drivers are confirmed against the actual controller and project.

No universal guarantee is made. Confirm the exact PLC/HMI, engineering-software version, connection method, IP subnets, routing, discovery behavior and site permissions. Validate diagnosis first. Program upload/download or debugging must be tested with the real equipment and approved maintenance window. A working tunnel alone does not prove those tasks.

An IP route or VPN does not by itself guarantee Layer 2 broadcast discovery. Establish whether the vendor tool can connect by a specified address, verify return routing and service ports, and confirm any bridging or serial-mapping requirement separately. Do not assume standard firmware provides every discovery method.

The chosen VPN or m2mCloud design must include a reachable peer or platform and an approved device-initiated path where required. Confirm SIM restrictions, routing, account ownership and licensing. Carrier NAT does not provide a publicly reachable device address, and cloud service or licences should not be assumed to be free or included.

YZW300L and YZW900L document local ChirpStack. YZW300X uses a Semtech UDP packet forwarder and requires a reachable external LNS. Choose the server location, ownership, regional hardware and integration method before selecting a gateway.

A proprietary LoRa device is not automatically a LoRaWAN node. Check the node’s LoRaWAN support, regional channel plan, activation settings and payload decoder. Verify join, decoded measurement and application delivery with the actual node.

The regional plan must match the fitted concentrator and RF hardware as well as the node. Confirm the deployment country and ordered hardware before changing channel settings. Software configuration alone is not evidence that another regional RF band is supported.

There is no single guaranteed range or capacity for every site. Terrain, obstructions, antenna installation, regional limits, payload size and reporting interval all matter. Survey the difficult locations and agree traffic and acceptance conditions for the actual network.

The catalogue lists standard Node-RED capability for YZW001L, YZW800, YZW300L, YZW900L and YZW1000. Verify the delivered runtime, dependencies and access interface. YZW900 needs optional eMMC and its matching runtime. Node-RED is not documented for the MT7628/MT7621 models in this catalogue.

No. Confirm the required nodes, runtime version, credentials, message schema and target platform. Durable storage and replay need an agreed implementation and acceptance test; they are not implied by a Node-RED editor. Back up flows and dependencies before changes, and start with a read-only test.

No. YZW800 uses MT7981, 1 GB DDR4, standard 4 GB eMMC, one RS232 and three RS485 ports. YZW800L uses MT7621, 512 MB DDR3, 16 MB NOR, one RS232 and one RS485. Equal Ethernet-port counts do not establish equal serial or application capabilities.

No. Most models in this catalogue do not support PoE. YZW1000 provides the documented PSE capability with a suitable 52–55 V supply and a verified power budget. YZW900 receives 48 V af/at PoE through WAN; PSE output is an order option. YZW900L is DC powered and has no PoE support.

No. The bundled 12 V adapter does not meet the 52–55 V PSE input requirement. Select the supply for the actual PD standard, startup and sustained loads, cable losses and environment. The 90 W-per-port and 720 W-total design limits are not an unconditional available power budget.

GPS and Wi-Fi are mutually exclusive options on YZW300L because they share an antenna position. Confirm the selected option and actual connectors/accessories in the order. This is model-specific and should not be generalized to every gateway.

YZW900 is an outdoor cellular CPE with three Gigabit ports and WAN PoE-PD input, without serial I/O. YZW900L is an outdoor LoRaWAN gateway with local ChirpStack, two Gigabit ports, internal RS485 and 9–48 V DC input, without PoE. Their power wiring and application roles are not interchangeable.

No. Confirm the exact model, hardware revision, storage layout, customer configuration and current version before requesting firmware. Back up the configuration and use the matching upgrade and recovery procedure. This website publishes the available technical PDFs; firmware is provided through the model-verification request process.

Those functions are not a blanket capability of this catalogue. The camera reference solution provides connectivity and an engineered PoE design; NVR, VMS, recognition software and licences are separate project equipment or services. Define the AI workload and verify suitable compute, runtime, storage and thermal requirements before proposing a system.

Start with the process description, point list, I/O electrical types, controller and safety responsibilities, power, installation environment and local/remote modes. Agree the BOM, drawings, control sequence and factory/site acceptance plan. The heating/pump page is a reference design, not a claimed deployed performance case.

Confirm the exact product and regional modem, serial options, antennas, GPS, power supply, mounting and software/runtime. State who supplies SIMs, network servers, platform accounts, licences and commissioning. Use the delivery checklist to record what is included and what remains project-supplied.