SL300 chatty scan LED after firmware upgrade

[sjxts3000]

Updated the firmware on my SL300 to the latest (and updated CPS as well) and read the codeplug and re-wrote with no changes. On scanning (several DMR and a couple analog personalities), I get a chatty scan LED now. Not just the normal flashing amber (to indicate scan is on), but also seeing a lot of flashing green in the LED indicating traffic on other talkgroups and timeslots (not just the ones I've programmed in and am monitoring). It never used to do this before the firmware and CPS upgrade. Before, it would only indicate green LED on traffic on any of the specific talkgroups/personalities I'm scanning.

I'm sure there's a new checkbox I'm missing and I've scoured CPS to no avail. What am I missing?

Thanks in advance for the help!

 

[sjxts3000]

Mods. If this post should be in the programming sub-forum, can you please move it? Thanks! (And sorry for the incorrect forum post)

 

[millma]

I hate to just throw in a simple "me too", but I've also noticed this on multiple XPR 7550s ever since updating to 2.4 firmware. Oddly enough, I've also talked to a few other people who have never seen it happen on their portables.

The behavior of the LED is pretty much exactly as you describe it though, like it's both scanning and receiving (but not unmuting to) traffic on a digital channel at the same time and randomly switching between the two colors.

My guess has always been that it must've been something in the codeplug, but I have never found any new or changed settings that might affect it.

 

[kc2obw]

I've seen this too on my XPR3500 when scanning a connect plus system conventionally, I don't see this on my 4500 which is a Gen 1 radio.

 

[Notarola]

It looks like a bug in the firmware where the led is being triggered by activity rather than by active desired TGs. Its kind of like the led is being activated by 'carriers" on a conventional channel rather than by the output of the PL code detector.

I have 2 7550 one has been updated and has the issue the other programmed identically and not updated does not have the issue.

 

[sjxts3000]

It looks like a bug in the firmware where the led is being triggered by activity rather than by active desired TGs. Its kind of like the led is being activated by 'carriers" on a conventional channel rather than by the output of the PL code detector.

I have 2 7550 one has been updated and has the issue the other programmed identically and not updated does not have the issue.

Bingo...this is exactly the confirmation I needed. I'm with you...I think it's a bug. This never occurred before the firmware upgrade. Guess we'll have to wait even more months before the next fix (if any).