Over 16 scanning Spectra Codeplug!

[linkinpark9812]

Well, it looks like we are on the verge of this happening EASILY. This happened to someone else on batlabs. It has now happened to me and I saved the codeplug. I already posted this on batlabs, so here is what I said so far:

Well, There was another member on the forum on here that did the same thing. Something got mixed up and got a 17 out of 16 Max Scanning modes in one of his zones in his codeplug.

Well apparently I did too! And it was on my 2 Meter Amateur Zone!!! YAY!!!

Anyways, I am trying to figure out how I did it.

What I was doing was moving modes around. I had weather frequencies that were not all together and a few "unknown" frequencies for my town that were not organized. I had to use the mode utility extensively. I had to delete two modes, create two more, and copy a bunch around.

I may post the codeplug up here, but I am going to try to retrace my steps and recreate what I did.

and this is the next post, but as of the posting of this topic, it hasn't been approved there yet.

Ok I would like to post an update.

I thought that because I was doing all of that crazy copying that this happened. Well apparently not. I went to my codeplug before I did the copying and it was like that. The furthest I can go back is when I was editing to expand the modes that was found out by someone else on the board. It still said "17 of 16 Max".

This means that I cannot really trace back to when this happened. However, I have found out some more things on how this works. Even though it says 17 of 16, there are only 16 (including SEL MODE) modes selected to scan. What is weird is that if I disable all of the modes for scanning, it says 2 of 16, even though for all of the other zones that don't have this "problem" will say 1 of 16, because only SEL MODE is selected. Because of this, I think the "modes selected to scan" number is stored somewhere, rather than the RSS seeing what modes are selected and produce a number using simple addition.

Also, If you do drop the scanned modes below the 17, then the "glitch" is fixed, and now the program says "max number selected" or whatever.

This leaves me to believe that the software does NOT do a math calculation when seeing if you can go over that amount of modes. If it did, it wouldn't let me select more that 16 modes, even with this error. Even though it says 17, if I tried to add one, the program would do a math calculation and find out you are over 16. It seems that the software just COMPARES the selected scan modes to a static "16". So when you hit the limit 16, it sees that the 16 you selected equal the static 16 that is in the RSS, and gives you the "max limit of scan modes". However, since it glitched or whatever to 17, it tries to compare and sees that 17 does not equal 16 and lets you select more modes to scan.

This leads me to believe that a little hex editing in the RSS could make this possible for everyone.

Also, this "glitch" is programmed into my radio. I read my radio with my computer, and it gives me the 17 of 16. However, when front programming the scan list, the radio identifies that it is at max and won't let me select more modes to scan like the RSS lets me in this "glitched" zone.

I am wondering if bit banging could also make this possible. Apparently the number of modes that will be scanned for a zone is stored somewhere. I think this because the RSS says 17 modes are selected to scan, but only 16 are. It isn't doing a calculation seeing how many modes are selected to scan and producing a number. It seems to be stored separate, probably for each zone.

Also, this is Zone number 21 that has "glitched".

Anyone have comments, suggestions, ideas? What do you guys think about it?

I would post my codeplug, but I really don't want my serial number out in the open.