* number_allocations.md data-type range changes
This commit is contained in:
@@ -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.
|
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 |
|
(add rows, using the range 0100 - FEFF for custom apps)
|
||||||
|-----------------|--------------------------|------------------------------------------------------|
|
|
||||||
| 000x | -reserved- | |
|
| Data-Type range | App name | Contact |
|
||||||
| FFFx | -reserved- | |
|
|-----------------|-----------------------------|------------------------------------------------------|
|
||||||
|
| 0000 - 00FF | -reserved for internal use- | |
|
||||||
|
| FF00 - FFFF | -reserved for testing/dev- | |
|
||||||
|
|||||||
Reference in New Issue
Block a user