Where the object is placed is dependant on what is or was in the current memory image before you started. The scanner will attempt to not re-use an object ID until all previously unused object IDs have been used, at which point it will start to reuse them as needed until all are gone.
Well... sorta...
When the scanner creates a
new object in memory (PGM NEW, PGM EDIT DUPE, etc.), it searches for an ObjectID to use for that new object. It starts searching at the
last ObjectID used for creating a new object, looks from there up to 1851 (maximum ObjectID value), then wraps to zero (minimum ObjectID value).
So... if you had already used up ObjectIDs 0-9 for a Mot TSYS, plus 10-59 for 50 TGRP objects, the radio would start "new object" assignment starting at ObjectID 60 - presuming you'd either a) done a 0-1 Init as described by Mike above and uploaded from software or b) started with an "empty" scanner (0-1 init or factory state) and programmed all the existing objects by hand (those would both "reset" the "last used" ObjectID to 0, so the next available ID would be 60).
Continuing the above example... presume you created a new CONV object and it was assigned ObjectID 60 as described above. Then you go and delete the TSYS at ObjectID 0 (along with all of its TGRPs 10-59). If you now create a new object, it will be assigned ObjectID 61 - not 0. This is because the scanner remembers that the last assigned ID was 60, and starts looking for new, free IDs from that point.
The scanner does this to "spread out" writes to its internal memory. Flash memory devices have a finite number of write cycles before they start failing, and cycling through all possible ObjectID values helps minimize this effect.
