> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/multitech-gateways/certifications.md). # Certifications **MFC Safe Pty Ltd**\ **Certificate of Hardware Compliance** This is to certify that the following hardware has been reviewed and approved by MFC Safe Pty Ltd as meeting the operational, compliance, and technical standards required for deployment within wireless temperature monitoring systems across hospitality, food safety, and commercial refrigeration applications. *** **Hardware Type:** LoRaWAN Gateway\ **Model Family:** Multitech Conduit Series (e.g., Conduit AP)\ **Manufacturer:** Multitech Systems, Inc. **Certified Capabilities:** * CE, FCC, IC, and RoHS certified * IP30/IP67 Ingress Protection (model dependent) * Operating temperature: -30°C to +70°C (industrial SKUs) * LoRaWAN Class A/B/C support (v1.0.x & 1.1) * OTA firmware updates & VPN/SSH secure configuration * MTBF > 500,000 hours This certificate confirms the Multitech Conduit Series gateways as suitable for MFC Safe’s platform integrations and operational conditions. *** **Certification Date:** 2 April 2025\ **Report Reference:** MFC-HW-AUDIT-2025-001 **Authorised By:**\ Morag Meikle\ Technology Director\ MFC Safe Pty Ltd\ Email: *** **End of Certificate** *** **Detailed Assessment** | Category | Requirement / Check | Purpose | Status | Notes | | ---------------------------------- | -------------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | Gateway Certification | CE / FCC / IC / RoHS | Ensure compliance with telecom and hazardous safety | CE / FCC / IC / RoHS certified (e.g., Conduit AP models) | (certification section) | | Ingress Protection | Confirm IP30 or industrial-grade IP67 for rugged models | Validate hardware for indoor or outdoor deployments | IP30 standard, IP67 available for rugged outdoor models | Datasheet confirms IP30 for indoor, IP67 for outdoor rugged models | | Power Supply & UPS Compatibility | Must support 9–32V DC, UPS fallback optional | Support stable power input with optional redundancy | Supports 9–32V DC input, optional UPS adapters available | Power input specs: | | LoRaWAN Compatibility | Supports LoRaWAN 1.0.x and 1.1, Class A/B/C | Interoperability with sensor nodes and LoRa network | LoRaWAN 1.0.x and 1.1 supported (Class A/B/C) | LoRaWAN certified: | | Network & Security Configuration | SSL/TLS, VPN, SSH access and admin password policies | Ensure gateway can operate securely within client networks | TLS/SSL, SSH access, firewall & VPN available in AEP | Security features: AEP UI and CLI tools support advanced configurations | | Firmware & OTA Management | Support OTA via AEP (Application Enablement Platform) | Remote maintenance and firmware control | AEP-based OTA update supported via Web UI/API | Firmware tools: | | Data Throughput Performance | Packet forwarder throughput benchmarked at >1000 pkt/min | Assess gateway responsiveness for dense deployments | Supports >1000 packet/min throughput in test environments | Lab-tested throughput benchmarks available in technical whitepaper | | Environmental Operating Conditions | Operating range typically -30°C to +70°C | Ensure gateway tolerates environmental conditions | Operating temp -30°C to +70°C (industrial SKUs) | Environmental data from industrial series datasheet | | Hardware Reliability | MTBF rating published by manufacturer | Assess reliability over expected operational lifespan | MTBF >500,000 hours reported on product datasheets | Reliability (MTBF) listed in extended product lifecycle documents | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.didge.io/home/foodcore-sensors/technical/hardware-specs/multitech-gateways/certifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.