So, if you reset the FILT values to the inverted values -- like 1073741822 instead of (1) and 536870911 instead of (536870912), for example -- and set the mode to SUBTRACT COLOUR instead of AND it would work the same, but better, because it filters out ALL of the frequencies that the LiDAR didn't emit at the time they were emitted.
Like, if a PHOT with the Ctype (536870913) goes through, instead of (1) either or (536870912), what will happen is that it will be allowed to pass on either the Red or Blue 'modes'. The problem being that the LiDAR doesn't emit PHOT pulses with values like that, so you could guess that any signal it receives with that encoded value on it wasn't a ping from the machine.
@cjun0416, Ok, but mixed frequencies can still be allowed through the AND FILT "gates" (so to speak). If one PHOT carries 536870912 + 1 , making it purple, then it could go through to the detectors when the FILT is either red or blue. A fix would be to exclude all other colors by finding the inverted value of blue, green, and red you used, and setting the FILT tmp mode to 'subtract colour'.
@ch9473 The quartz in the emiter melts from the lightning, causing the photons to no longer scatter.
Also striking severe lightning near the emitter somehow made the LiDAR spit out blue photons in a horizontal line.
sometimes reflected particles go directly into the emitter that causes to emit small particles of the past rgb photon AND the current rgb photon. try fixing it.
@HuntaBadday Yes you got the point exactly. A single signal device can't distinguish well if the subject is near by due to the interference of the past signal. so I solved that problem by give phot its own frequencies. And that is RGB.
@c jun0416, why is it that you are using RGB? Am I correct?
I am pretty sure, otherwise there would be no use for the RGB, when the device recieves the incorrect color, it discards it until it recieves the correct value, so that is what I think is going on.