From 6fb8e60b5fc855e391721e74b6e083509ceb1ffc Mon Sep 17 00:00:00 2001 From: Scott Powell Date: Mon, 30 Mar 2026 11:53:27 +1100 Subject: [PATCH] * number_allocations.md data-type range changes --- docs/number_allocations.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/number_allocations.md b/docs/number_allocations.md index ea36f830..7f7e9372 100644 --- a/docs/number_allocations.md +++ b/docs/number_allocations.md @@ -8,9 +8,11 @@ The `PAYLOAD_TYPE_GRP_DATA` payloads have a 16-bit data-type field, which identi To make sure multiple applications can function without interfering with each other, the table below is for reserving various ranges of data-type values. Just modify this table, adding a row, then submit a PR to have it authorised/merged. -The 16-bit types are allocated in blocks of 16, ie. the lower 4-bits is the range. +NOTE: the range FF00 - FFFF is for use while you're developing, doing POC, and for these you don't need to request to use/allocate. -| Data-Type range | App name | Contact | -|-----------------|--------------------------|------------------------------------------------------| -| 000x | -reserved- | | -| FFFx | -reserved- | | +(add rows, using the range 0100 - FEFF for custom apps) + +| Data-Type range | App name | Contact | +|-----------------|-----------------------------|------------------------------------------------------| +| 0000 - 00FF | -reserved for internal use- | | +| FF00 - FFFF | -reserved for testing/dev- | |