SD365 Malfunction?

Today I was at the dentist’s office, and while I was waiting, I was looking at the fire alarm system. pretty typical new Honeywell system, with an ANN-80, BG12LX’s, and SD365’s. Probably had a newer Fire-Lite Panel. While I was waiting I was looking at the SD365, and the LED’s went solid red. I expected the alarms to start sounding, but nothing happened. after a couple of seconds, the LED went back to normal, polling as usual. during this, the detector was on CLIP, and was polling red. does anyone know of this happening to any other Honeywell detectors? I have never seen that before, and there was no smoke or steam that could have activated the detector, and the system stayed normal.

FireLite LiteSpeed doesn’t poll green, so you can’t really tell whether a FireLite panel is running on CLIP or LiteSpeed without digging deeper. Having fumbled around with my NFW2-100 (rebranded MS-9200UDLS), I’ve seen this happen sometimes at random with these kinds of detectors. My guess is that detector was initializing or running some test process where the LED was on for an extended period of time. In this case, the system was probably running on LiteSpeed since CLIP doesn’t offer advanced detector testing.
An off-shoot case was maybe something like dust triggered the detector, but it ran through verification and found nothing wrong so it went back to normal.

Just my 2 cents, I’m not a tech/inspector so I can’t say for sure.

Thanks for the response, and I do think that it is possible that dust got into the detector, because the panel never went into trouble, or anything like that.

According to the Notifier NFS2-3030 programming manual, FlashScan detectors light steady green for a “few seconds” while they are being automatically tested. I have seen the Notifier 951 detector where I live illuminate solid green for more than a few seconds, the “few seconds” is probably an underestimate. I think the solid red may have been a similar testing process to that on Notifier systems.

I have also seen Notifier detector LEDs output a cadence where they rapidly flash a few times, pause, and flash once, a process that takes about 1 second. In the dark, the rapid flashes look like a steady green light for a fraction of a second. This cadence occurs on each detector once every 16 flash cycles, and it appears to occur in increasing order with decade number. However, since this description is inconsistent with the description of the testing LED, I suspect that this is actually the FACP polling individual detectors to ensure they are online, since it is not otherwise possible to detect an offline device when decade polling.

This is firelite not notifier

Panel wouldnt have to go into trouble

I have a system of SD355s, they all poll solid red for a few seconds. They go one detector at a time and i wasn’t able to get them to activate while polling red.

I know, but I would also expect some similarities because the detectors come from the same place. @sam.csp’s description sounds a lot like how a detector should behave in general while it is being tested.

Usually my smoke detector doesn’t go solid but it blinks red, very rapidly, for around 2 seconds. It’s a FSP-851 but it’s running on LiteSpeed.