Shown below is a good example of what we want in a blindscan, or at least what we want the blindscan to be capable of.
[Only registered and activated users can see links. ]

You cannot blindscan a group of transponders like that unless the duplicate check in blindscan is disabled. Some of the transponders shown are around 2 MHz apart in frequency spacing and are about identical in polarity, symbol rate, fec, type...etc. If the duplicate check that is in blindscan sees this group, it would delete some of them.

There is also a duplicate check built into the enigma2 image. This duplicate check is active anytime a group of transponders is sent to Service scan for a channel search. Enigma2 images used to delete a pair of transponders that were almost identical like the ones shown above, The only way you can see this is to know how many transponders were sent to Service scan to be checked for channels, and then count how many transponders actually get scanned. This is why you see the number of transponders scanned out of how many were sent to be scanned in the Service scan that I modded. if nothing is deleted, the numbers will be the same, such as "25 of 25 transponders" scanned. If enigma2 deletes something, the numbers will not match.

Currently, most enigma2 images have the duplicate transponder check set to allow anything above 2 MHz spacing to be scanned, and anything below 2 MHz in spacing will result in one of two transponders being deleted. But several months ago when I last checked, there are some images that will delete one of two transponders that are found less than 4 MHz apart. Again, the only way to catch this is to know how many transponders are supposed to be scanned as compared to how many were actually scanned.

To put this another way, there are two checks for duplicate transponders in enigma2 when a group of transponders will be scanned. The duplicate transponder check in blindscan can be turned off, but the duplicate transponder check in enigma2 cannot.