Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13
  1. Collapse Details
    #11
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    6,553
    Post Thanks / Like
    Contribute If you enjoy reading the
    content here, click the below
    image to support our site.
    Click Here To Contribute To Our Site
    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.
    Reply With Quote
     

  2. Thanks MikeB, ViP3R, Babadem thanked for this post
  3. Collapse Details
    #12
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    6,553
    Post Thanks / Like
    Here is the same satellite scanned using modded image(TNAP)
    [Only registered and activated users can see links. ]


    Here is the Free scan results.
    [Only registered and activated users can see links. ]
    15 out of 16.
    Blindscan found 16 transponders, but enigma2 deleted one of them as a duplicate. (The duplicate transponder check in blindscan is OFF.)
    Reply With Quote
     

  4. Thanks MikeB, ViP3R thanked for this post
    Likes norman881 liked this post
  5. Collapse Details
    #13
    Join Date
    Dec 2010
    Location
    Atlanta, Ga.
    Posts
    6,553
    Post Thanks / Like
    Blindscan generates a transponder file after the blindscan finishes and puts this file in the /tmp folder of the receiver. It has been this way for years.
    The modded SatDreamgr image we call TNAP generates a report after the Servicescan completes. The reports are generated for satellite and ATSC. The Service scan report is alos stored in the /tmp directory of the receiver, but provisions are made to store both the blindscan and the service scan reports on an usb drive if proper folders are made for them. The /tmp folder in the receiver is dumped or cleaned during a reboot of the receiver.

    Both the Blindscan report and the Service scan report are designed to be viewed using Notepad++ or another decent .xml editor. Below is an example of how to use these files or reports.

    Our example is a blindscan of 95w that returned 20 transponders.
    The Service scan was sent the 20 transponders from the blindscan, but enigma2 deleted one as a duplicate.
    [Only registered and activated users can see links. ]

    We can look at the blindscan file and the Service scan report to find out what happened.
    [Only registered and activated users can see links. ] [Only registered and activated users can see links. ]

    From above, we can see tp 3966 was scanned, and tp 3967 was deleted.
    TP 3967 is manually scanned since it was deleted, with this as a result.
    [Only registered and activated users can see links. ]

    We cannot really ask the image makers to do anything about this because if you go any less than 2 MHz today on the duplicate check, then you will probably end up with some duplicate channels on other enigma2 receivers. At least we have information available from the scans to tell us what happened or what was deleted. Sometimes it pays to look when the number of blindscan transponders is different than what was scanned.

    The files or reports shown above are attached. This was a "free" or unencrypted search.
    Attached Files Attached Files
    Last edited by el bandido; 09-20-2019 at 06:31 PM.
    Reply With Quote
     

  6. Thanks MikeB, norman881, ViP3R, Babadem thanked for this post
Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •