Organization & exact models
Identify your organization, your role and contact. Record the manufacturer, exact model, firmware and hardware variant for each requested scope. Use “unknown” when a value has not been established.
EdgeIOT · For manufacturers, solution providers & integrators
Request support for your protocol & devices
Prepare technical identity, documentation and samples, then continue their review in your EdgeIOT account. Support starts with a clear scope and verifiable evidence.
Start with a clear technical brief
Use the template to gather what engineering needs to understand your protocol and define the required tests. Partial information is useful when its gaps are explicit.
Sign-in and a registered test device you own are required. Downloading the template does not submit a request.
What belongs in the package?
Protocol documentation
Provide the official reference, version and date, transport, message structure, device identification, byte order, checksum, and ACK or retry behavior. Include document links and the relevant technical excerpts.
Samples with reference values
Pair raw samples with capture time and timezone, message direction and origin: physical device, simulator or documentation example. Record expected values, units and how each value was independently checked.
Capabilities & requested scope
Describe the use case and required capabilities, such as location and speed, measurements or alarms. Separate claims needing verification from advertised features, and state whether a device or test session can be made available later.
A reviewable sample
Raw frame + context + expected outcome
These are sample fields to provide, not test evidence or an approved capture. Preserve the relationship between samples and references when redacting sensitive data, and disclose each redaction.
- Origin
- Physical device / simulator / document example
- Context
- Model, firmware, transport, time & direction
- Content
- Raw bytes or text, with ACK references as needed
- Reference
- Expected values, units & independent verification method
From submitted evidence to bounded support
- 01
Prepare your evidence package
Download the template and gather identity, references and samples. Different models or versions need separate scopes; a shared protocol does not establish shared support.
- 02
Open a private case
Sign in and register a test device you own from Devices if needed. Create its onboarding case and attach text documentation. The case is associated with the device and its owner account.
- 03
Complete evidence review
Attach a discovery result when available and request engineering review. Further samples, independent reference measurements or a physical-device test may be required.
- 04
Follow the reviewed scope
Review establishes accepted capabilities, limitations and proven versions. Publication in the shared register and activation remain separate decisions.
Submitting a case or completing discovery does not automatically grant support or production activation. Results do not generalize beyond the proven manufacturer, model, firmware, hardware variant, transport and capabilities. Unknown information remains unknown.
Before you submit
Does the protocol have to be known?
You can prepare a request for an unlisted protocol. Include what is known and explicitly mark unknown information. A prior compatibility claim is not required to start review.
Are documentation or simulator samples enough?
Documents and samples support analysis. Simulator evidence stays labeled as simulation. Production verification requires physical-device evidence within a proven scope.
Can I request several models?
List them in the package with separate identities, versions and samples. The current workflow creates a case for each registered device. One case does not grant support for other models.
What if a test device is not available?
Prepare the documentation and package first. The current case workflow requires a registered device you own. This public page does not yet accept device-independent submissions.
Will my documents and samples become public?
This page contains guidance and a blank template only. Submit evidence through the authenticated onboarding workflow. The public register displays approved public support scope, excluding private evidence content.