TNAP 3.2 Blind Scan Of Closely Spaced Frequencies With OS mio+

[clubfoot]

Hi,

Using a mio+ with TNAP 3.2 image, the blind scan on 95W seems to be variable. For quick successive blind scans it sometimes registers frequencies, other times it misses some of them. This satellite has quite a few closely spaced frequencies with 4MHz or less separation between them, some with low SR or 1036, others with SR of 3303.

Are there any settings that can be adjusted to improve the success rate of the blind scan? I use an EBS Pro scan with a TBS6903 card as the reference guide, it seems to register most frequencies.

[el bandido]

A TBS6903 card could be thought of as a plug-in type tuner that costs around $300.00 U.S. The MIo+ is fta receiver. So you are comparing a high priced tuner to to a fta receiver that costs around $200 U.S.

Anyway, I have done many scans of 95w, and I understand what you are talking about. Lots of times, it may be possible to get different transponders by setting the low symbol rate to 1 and scanning, then change the low symbol rate to 2 and immediately scan again. It would be nice if the Mio+ could find all the transponders on 1 scan as it does in 2 for this satellite. The pandemic has caused a decrease in transponders on this satellite too.

I do not know if many improvements can be made in this area. The Mio receivers seem to have respectable scans when compared to other fta receivers, but they are not high priced tuner cards, and really cannot be expected to scan as well as a tuner card.

What channels does the Mio miss that the tuner card gets? Please provide details, and maybe some sort of a pattern will appear that can be improved on. Logging transponders really does not mean anything as compared to logging transponders that have services.

T2MI drivers for the Mio seem to scan better than non-T2MI drivers. But the T2MI drivers confuse services on transponders around 4 MHz apart or less which is why I do not use them. Edision has done a lot of work on the tuners, and puts effort into blindscan performance. If a pattern of what is missed or other information can be provided, then Edision may be able to improve the blindscan further. The developers do not have direct access to the 95w satellite!

Recent kernel and tuner upgrades seem to help my scans of 95w. At the moment, stability is not where it should be, and some things are not working correctly. Maybe in another 3-4 weeks, these upgrades can be put into an image for North America and you can see if anything has improved. But finding a pattern or logging what is being missed is important. Telling us a tuner card outperforms a fta receiver does not help much without the detailed information of what is missed.

Attached are a few scan logs of 95w. They do not really tell us much because they have not been compared to what was found at the same time using a different receiver or card. But they do show what I think is a respectable blindscan of a difficult satellite using a fta receiver. Use notepad++ or similar to view them, or change the extension to .txt.

[clubfoot]

Thank you for the detailed reply.

An example from today, active now is the 3904V, SR3303 signal from 95.0W. It registers OK in a transponder scan as a unique frequency but when a channel scan is performed it gets bleed over into it from 3908V, SR3303. This results in two channels of the same name on 3904V and 3908V, the source of which is 3908V and the true signal from 3904V is lost.

[el bandido]

Post a screenshot of the About page (Menu--->About).
Those transponders work fine for me as shown below.

16950


16951

[clubfoot]

Post a screenshot of the About page (Menu--->About).
Those transponders work fine for me as shown below.

16950


16951



I will have to flash TNAP 3.2 back on to the mio+, I flashed it with another image to see if it gave different results.

[Megatron817]

I will have to flash TNAP 3.2 back on to the mio+, I flashed it with another image to see if it gave different results.

You can put up to four images on multiboot in the mio4k and mio4k+. This makes it faster for comparing images. Only TNAP comes with the NO T2mi driver module preloaded and in the downloadable plugins only TNAP 3.2 you can change the t2mi module. look in extra. There's NO-t2mi and t2mi.

[clubfoot]

You can put up to four images on multiboot in the mio4k and mio4k+. This makes it faster for comparing images. Only TNAP comes with the NO T2mi driver module preloaded and in the downloadable plugins only TNAP 3.2 you can change the t2mi module. look in extra. There's NO-t2mi and t2mi.


I will try to flash the TNAP 3.2 image back into the mio+ in one of the multiboot slots. After a quicj search of the forum I think I have the correct procedure, could anyone please confirm?

1. create a folder named downloaded_images on the root of a FAT32 formatted USB drive
2. copy the zipped image file named tnap-3.2-osmio4kplus_multiboot_ofgwrite into the folder named downloaded_images
3. put the flash drive in usb slot of the mio4k
4. menu sequences of menu --> setup --> software management --> Flash online --> press ok button to view the downloaded_images folder --> press ok button to open the downloaded_images folder and view the file named tnap 3.2 osmio4k_multiboot_ofgwrite.zip -> press green button to flash --> select slot 1,2,3 or 4

Once I have the TNAP 3.2 back in the mio+ I will upload a screen grab of the About page

[el bandido]

That sequence seems to be correct. Try it and see.

[MikeB]

I will try to flash the TNAP 3.2 image back into the mio+ in one of the multiboot slots. After a quicj search of the forum I think I have the correct procedure, could anyone please confirm?

1. create a folder named downloaded_images on the root of a FAT32 formatted USB drive
2. copy the zipped image file named tnap-3.2-osmio4kplus_multiboot_ofgwrite into the folder named downloaded_images
3. put the flash drive in usb slot of the mio4k
4. menu sequences of menu --> setup --> software management --> Flash online --> press ok button to view the downloaded_images folder --> press ok button to open the downloaded_images folder and view the file named tnap 3.2 osmio4k_multiboot_ofgwrite.zip -> press green button to flash --> select slot 1,2,3 or 4

Once I have the TNAP 3.2 back in the mio+ I will upload a screen grab of the About page

Just make sure there's enough empty space left on the usb drive, so it can unpack the file during installation.

[clubfoot]

Hi,

I have got the mio+ back with the TNAP 3.2 image on it and did the software updated from the feed. It now shows no updates available. Returning to my comment about the blind scan functionality of the TNAP 3.2 image there is an example today on 95.0W. Frequency 3992V, SR3303, FEC 5/6, 8PSK will scan in on a blind scan in transponder scan mode but when I go to scan in the channel it misses it.

A mio+ running OpenViX connected to the same dish and scanned at the same time locks and stores the channel.

The channel is named Delaware HD Media and is different to the Delaware HD Dirty channel on 3984V. This feed will be active for the next 5 hours if anyone wishes to check it out. I have attached the Info screen of the mio+ that was requested earlier in this topic.

16974

[Megatron817]

Happens with some services here too. I just keep an eye on the service scan and if nothing scans in I use signal finder and put in the Transponder info and scan it again if there is a signal found.

[clubfoot]

Happens with some services here too. I just keep an eye on the service scan and if nothing scans in I use signal finder and put in the Transponder info and scan it again if there is a signal found.

I tried the signal finder option in the TNAP 3.2 image, it locked the frequency OK but when I scanned the channel it found nothing. Other receivers lock this channel OK and give a picture. An identical mio+ running OpenViX locks the channel OK with a picture as does another make of receiver running OpenATV. All receivers attached to the same dish.

16975

16976

16977

16978

[Megatron817]

Is that frequency slow to lock with Tnap and signal finder? If so might try adjusting the frequency down or up by one number and see if the lock is faster then rescan the transponder.

[clubfoot]

Is that frequency slow to lock with Tnap and signal finder? If so might try adjusting the frequency down or up by one number and see if the lock is faster then rescan the transponder.


I had previously tried a manual scan using an offset on the frequency both above and below the centre frequency, no channel lock. I think there may be some parameter in the ts stream that TNAP 3.2 is not coping with when it comes to locking the channel. The transponder part of the scan is OK, it is the scanning of the channel where the issue lies.

This is not the only time and only frequency where this issue has occurred. I posted the details today as the frequency was going to be active for around 5 hours after I posted which might have given a window of opportunity for others the check it out.

[el bandido]

The only difference in the 2 images is the tuner drivers.
Please let us know when you find another transponder like that. Thanks.

[el bandido]

Looks like the feed may be back tomorrow...
[Only registered and activated users can see links]

[clubfoot]

Looks like the feed may be back tomorrow...
[Only registered and activated users can see links]


Same again, scanned in as the frequency then failed to scan in as the channel.

There are two Delaware frequencies currently active on 3984V (Dirty) and 3992V (TVG BU). The 3984V frequency scans in as the channel with TNAP 3.2 but the 3992V frequency fails to scan in as the channel with TNAP 3.2 Another mio+ receiver running OpenViX scans both frequencies in as the channel.

It is a TNAP 3.2 issue, hopefully it can be resolved in the new image?

[el bandido]

What version of OpenVix??? (Menu--->About)

OpenVix (ver.39) misses 3984, then duplicates 3988 and 3992
16981 16982

TNAP 3.2 and TNAP 4 scan 3984, but miss 3992. A manual scan of 3993 will get the channel in either of these images.
16983


For what it is worth, these two channels are showing basically the same thing. It would be nice if this issue could be fixed. However, I do not know if it will be fixed, or if it is fixed, how long it will take. For the current time or as a work-around, you can view the 3992 channel by doing a manual scan 1 MHz higher.

[el bandido]

1:00 AM Is Not the best time to scan this satellite, and the weather is not the best.
Anyway, I made a few adjustments and the results are shown below. Further tests are needed before Victory or Success can be declared.
16986

[clubfoot]

1:00 AM Is Not the best time to scan this satellite, and the weather is not the best.
Anyway, I made a few adjustments and the results are shown below. Further tests are needed before Victory or Success can be declared.
16986


Is there a way to force the channel scan to narrow the frequency range it uses when scanning? This might prevent bleed over from adjacent close frequencies.

Most of these close frequencies on 95.0W are 4MHz apart with a bandwidth of approximately 3.6MHz. If the channel scan could reject bleed over from an adjacent frequency by using a limit of +/- 1MHz of the locked transponder frequency it might limit the bleed over and improve the channel locking? Obviously if the tuner hardware is the limiting factor then it may not be possible?

[el bandido]

The tuner drivers are different in TNAP and do not have T2MI capability. But right now, about the only T2MI transponders that are available for our viewing are at 40w c band, circular polarization.

Anyway, the adjustment I found seems to have fixed it. The channels are blank right now, so let's wait until they go live before declaring victory. It seems other channels are now being scanned on the skinny transponders besides 3992 that were being missed before the adjustments.

16987

[el bandido]

Try scanning today with TNAP 3.2 and see what the results are.
It looks like the problem has been fixed in TNAP 3.2, and the adjustments I made might be useless.

[clubfoot]

Try scanning today with TNAP 3.2 and see what the results are.
It looks like the problem has been fixed in TNAP 3.2, and the adjustments I made might be useless.


If the problem has been fixed in TNAP 3.2 does that mean I need to download a software update to the mio+?

[clubfoot]

The tuner drivers are different in TNAP and do not have T2MI capability. But right now, about the only T2MI transponders that are available for our viewing are at 40w c band, circular polarization.

Anyway, the adjustment I found seems to have fixed it. The channels are blank right now, so let's wait until they go live before declaring victory. It seems other channels are now being scanned on the skinny transponders besides 3992 that were being missed before the adjustments.

16987


So how do I get these adjustments into the mio+ ?

[el bandido]

I have not added any adjustments to a public image. TNAP 3.2 is working "As Is" for these channels. Try it and see...

[el bandido]

Today, the 3984 and 3992 transponders are active, but again 3992 will not scan in. 3992 Will Scan if the frequency is manually moved to 3993. I do not understand why this works sometimes, but not all the time. I will continue to look at this, but I do not know if it can be fixed.

[clubfoot]

Today, the 3984 and 3992 transponders are active, but again 3992 will not scan in. 3992 Will Scan if the frequency is manually moved to 3993. I do not understand why this works sometimes, but not all the time. I will continue to look at this, but I do not know if it can be fixed.


This is the issue that I have been finding regularly.

It seems that the adjacent frequency that is 4MHz away often bleeds over into the other frequency resulting in it either blocking the other frequency from correctly scaning or generating a duplicate of the adjacent frequency. I have concluded that it is either due to the blind scan drivers in the image or the Avilink tuner in the mio.

As you state above, a manual scan using an offset of around 3MHz to 4MHz from the correct frequency and further away from the adjacent interfering frequency results in the channel being locked OK.

[el bandido]

An unaltered TNAP 3.2 image Does Not make duplicate channels on any transponders that are around 4 MHz apart, and have a similar symbol rate that I know of. Other images will usually make duplicates of transponders that are spaced around 4 MHz apart, and have a similar symbol rate, unless they are altered.

For the 3992v 3303sr transponder on 95w, scanning it at 3993v 3303sr will allow the channel to be seen. This is not a difference of 3 or 4 MHz. This is a one MHz difference. And at times, the channel can be seen at 3992 MHz.

[el bandido]

The Edision receiver is not perfect, but it does a respectable job for any fta receiver on satellites with closely spaced transponders. The correct driver has to be installed or you will get duplicate channels or skipped scans on closely spaced transponders.

< File created on Saturday, September 26, 2020 at 13:23:25 >
< Satellite = 95.0W Galaxy 3C & Spaceway 3 & Intelsat 30/31 >
< Receiver = edision osmio4kplus >
< Enigma2 Image = Tnap 4 >
< Kernel Version = 5.8.0 >
< DVB Driver Date = 2020-08-19 >
< Blindscan Frequency Range = 3200 to 4200 MHz >
< Blindscan Symbol Rate Range = 1 to 60 Msps >
< Blindscan Only Free Channels or Services? = True >
< Tuner = Tuner A: Availink AVL6261 (DVB-S2X) >


< 'DVB-S2 8PSK 3740V / 29901 / 3/4' > Tp# 1
< (1)CAM 001 /> 1:0:1:1:1:1:A5A8E9C:0:0:0:
< (2)CAM 002 /> 1:0:1:2:1:1:A5A8E9C:0:0:0:
< (3)CAM 003 /> 1:0:1:3:1:1:A5A8E9C:0:0:0:
< (4)CAM 004 /> 1:0:1:4:1:1:A5A8E9C:0:0:0:
< (5)CAM 005 /> 1:0:1:5:1:1:A5A8E9C:0:0:0:
< (6)CAM 006 /> 1:0:1:6:1:1:A5A8E9C:0:0:0:

< 'DVB-S2 8PSK 3890H / 15000 / 3/4' > Tp# 2
< (7)Punta Cana Back Up /> 1:0:1:1:1:FFFF:A5A0F32:0:0:0:

< 'DVB-S2 8PSK 3904V / 3303 / 5/6' > Tp# 3
< (8)Monmouth Park International Clean /> 1:0:1:1:1:FFFF:A5A8F40:0:0:0:

< 'DVB-S2 8PSK 3908V / 3303 / 5/6' > Tp# 4

< 'DVB-S2 8PSK 3911V / 1036 / 3/4' > Tp# 5

< 'DVB-S2 8PSK 3915V / 2000 / 3/4' > Tp# 6
< (9)Gem Shopping Network HD A /> 1:0:1:1:1:FFFF:A5A8F4B:0:0:0:

< 'DVB-S2 8PSK 3917V / 2000 / 3/4' > Tp# 7

< 'DVB-S2 8PSK 3931V / 14387 / 3/4' > Tp# 8
< (10)VISTA Encoder 1 /> 1:0:0:1:0:0:A5A8F5B:0:0:0:

< 'DVB-S2 8PSK 3964V / 1036 / 3/4' > Tp# 9
< (11)Caliente A /> 1:0:1:1:1:FFFF:A5A8F7C:0:0:0:

< 'DVB-S2 8PSK 3969V / 1036 / 3/4' > Tp# 10
< (12)De Las Americas-A /> 1:0:1:1:1:FFFF:A5A8F81:0:0:0:

< 'DVB-S2 8PSK 3971V / 1036 / 3/4' > Tp# 11
< (13)3971V SID 0x01 /> 1:0:1:1:1:0:A5A8F83:0:0:0:

< 'DVB-S2 8PSK 3974V / 1036 / 3/4' > Tp# 12
< (14)3974V SID 0x01 /> 1:0:1:1:1:0:A5A8F86:0:0:0:

< 'DVB-S2 8PSK 3976V / 3303 / 5/6' > Tp# 13
< (15)Delaware HD Media /> 1:0:1:1:1:FFFF:A5A8F88:0:0:0:

< 'DVB-S2 8PSK 3980V / 3303 / 5/6' > Tp# 14
< (16)GGF TVG HD Clean SAT /> 1:0:1:1:1:FFFF:A5A8F8C:0:0:0:

< 'DVB-S2 8PSK 3984V / 3303 / 5/6' > Tp# 15
< (17)Delaware HD Dirty /> 1:0:1:1:1:FFFF:A5A8F90:0:0:0:

< 'DVB-S2 8PSK 3988V / 3303 / 5/6' > Tp# 16
< (18)MJC Pimlico TVG HD B/U /> 1:0:1:1:1:FFFF:A5A8F94:0:0:0:

< 'DVB-S2 8PSK 3992V / 3303 / 5/6' > Tp# 17

< 'DVB-S2 8PSK 3996V / 3303 / 5/6' > Tp# 18

< 'DVB-S2 8PSK 4001H / 29999 / 9/10' > Tp# 19
< (19)PDG Service --- UnKnown Service Type C: /> 1:0:C:FFFE:4:FF37:A5A0FA1:0:0:0:
< (20)ABC-14 /> 1:0:1:1:4:FF37:A5A0FA1:0:0:0:
< (21)ABC-10 /> 1:0:1:2:4:FF37:A5A0FA1:0:0:0:
< (22)ABC-8 /> 1:0:1:3:4:FF37:A5A0FA1:0:0:0:
< (23)ABC-4 /> 1:0:1:4:4:FF37:A5A0FA1:0:0:0:
< (24)ABC-12 /> 1:0:1:5:4:FF37:A5A0FA1:0:0:0:
< (25)ABC-13 /> 1:0:1:6:4:FF37:A5A0FA1:0:0:0:

< 'DVB-S2 8PSK 4060V / 31251 / 3/4' > Tp# 20
< (26)4060V SID 0x0c --- UnKnown Service Type 64 /> 1:0:64:C:3C0:0:A5A8FDC:0:0:0:

< 'DVB-S2 8PSK 4080H / 31250 / 3/4' > Tp# 21
< (27)4080H SID 0x0c --- UnKnown Service Type 64 /> 1:0:64:C:3B6:0:A5A0FF0:0:0:0:

< 'DVB-S2 8PSK 4096V / 3303 / 5/6' > Tp# 22

< 'DVB-S2 8PSK 4100V / 3303 / 5/6' > Tp# 23
< (28)Remington HD TVG Backup /> 1:0:1:1:1:FFFF:A5A9004:0:0:0:

< 'DVB-S2 8PSK 4104V / 3303 / 5/6' > Tp# 24
< (29)Hoosier Park HD Clean /> 1:0:1:1:1:FFFF:A5A9008:0:0:0:

< 'DVB-S2 8PSK 4108V / 3303 / 5/6' > Tp# 25
< (30)Meadowlands HD TVG sat /> 1:0:1:1:1:FFFF:A5A900C:0:0:0:<

Blind Scan Completed in 4 Minutes 15 Seconds.
30 Channels ( TV = 30 Radio = 0) 25 of 26 Transponders Scanned.

[el bandido]

TNAP-3.2 performs similar unless the drivers are changed:



< File created on Saturday, September 26, 2020 at 13:45:06 >
< Satellite = 95.0W C-band Galaxy 3C & Spaceway 3 & Intelsat 30/31 95.1 W >
< Receiver = edision osmio4kplus >
< Enigma2 Image = Tnap 3.2 >
< Kernel Version = 5.5.16 >
< DVB Driver Date = 2020-04-09 >
< Blindscan Frequency Range = 3400 to 4200 MHz >
< Blindscan Symbol Rate Range = 1 to 60 Msps >
< Blindscan Only Free Channels or Services? = True >
< Tuner = Tuner A: Availink AVL6261 (DVB-S2X) >


< 'DVB-S2 8PSK 3741V / 29901 / 3/4' > Tp# 1
< (1)CAM 001 /> 1:0:1:1:1:1:A598E9D:0:0:0:
< (2)CAM 002 /> 1:0:1:2:1:1:A598E9D:0:0:0:
< (3)CAM 003 /> 1:0:1:3:1:1:A598E9D:0:0:0:
< (4)CAM 004 /> 1:0:1:4:1:1:A598E9D:0:0:0:
< (5)CAM 005 /> 1:0:1:5:1:1:A598E9D:0:0:0:
< (6)CAM 006 /> 1:0:1:6:1:1:A598E9D:0:0:0:

< 'DVB-S2 8PSK 3890H / 15000 / 3/4' > Tp# 2
< (7)Punta Cana Primnary /> 1:0:1:1:1:FFFF:A590F32:0:0:0:

< 'DVB-S2 8PSK 3905V / 3303 / 5/6' > Tp# 3
< (8)Monmouth Park International Clean /> 1:0:1:1:1:FFFF:A598F41:0:0:0:

< 'DVB-S2 8PSK 3909V / 3303 / 5/6' > Tp# 4
< (9)Woodbine TVG HD Sat /> 1:0:1:1:1:FFFF:A598F45:0:0:0:

< 'DVB-S2 8PSK 3911V / 1036 / 3/4' > Tp# 5

< 'DVB-S2 8PSK 3915V / 2000 / 3/4' > Tp# 6
< (10)Gem Shopping Network HD A /> 1:0:1:1:1:FFFF:A598F4B:0:0:0:

< 'DVB-S2 8PSK 3917V / 2000 / 3/4' > Tp# 7

< 'DVB-S2 8PSK 3932V / 14385 / 3/4' > Tp# 8
< (11)VISTA Encoder 1 /> 1:0:0:1:0:0:A598F5C:0:0:0:

< 'DVB-S2 8PSK 3964V / 1036 / 3/4' > Tp# 9
< (12)Caliente A /> 1:0:1:1:1:FFFF:A598F7C:0:0:0:

< 'DVB-S2 8PSK 3969V / 1036 / 3/4' > Tp# 10
< (13)De Las Americas-A /> 1:0:1:1:1:FFFF:A598F81:0:0:0:

< 'DVB-S2 8PSK 3974V / 1036 / 3/4' > Tp# 11
< (14)3974V SID 0x01 /> 1:0:1:1:1:0:A598F86:0:0:0:

< 'DVB-S2 8PSK 3977V / 3303 / 5/6' > Tp# 12
< (15)Delaware HD Media /> 1:0:1:1:1:FFFF:A598F89:0:0:0:

< 'DVB-S2 8PSK 3981V / 3303 / 5/6' > Tp# 13
< (16)GGF TVG HD Clean SAT /> 1:0:1:1:1:FFFF:A598F8D:0:0:0:

< 'DVB-S2 8PSK 3985V / 3303 / 5/6' > Tp# 14
< (17)Delaware HD Dirty /> 1:0:1:1:1:FFFF:A598F91:0:0:0:

< 'DVB-S2 8PSK 3989V / 3303 / 5/6' > Tp# 15
< (18)MJC Pimlico TVG HD B/U /> 1:0:1:1:1:FFFF:A598F95:0:0:0:

< 'DVB-S2 8PSK 3993V / 3303 / 5/6' > Tp# 16

< 'DVB-S2 8PSK 3997V / 3303 / 5/6' > Tp# 17

< 'DVB-S2 8PSK 4001H / 30003 / 9/10' > Tp# 18
< (19)PDG Service --- UnKnown Service Type C: /> 1:0:C:FFFE:4:FF37:A590FA1:0:0:0:
< (20)ABC-14 /> 1:0:1:1:4:FF37:A590FA1:0:0:0:
< (21)ABC-10 /> 1:0:1:2:4:FF37:A590FA1:0:0:0:
< (22)ABC-8 /> 1:0:1:3:4:FF37:A590FA1:0:0:0:
< (23)ABC-4 /> 1:0:1:4:4:FF37:A590FA1:0:0:0:
< (24)ABC-12 /> 1:0:1:5:4:FF37:A590FA1:0:0:0:
< (25)ABC-13 /> 1:0:1:6:4:FF37:A590FA1:0:0:0:

< 'DVB-S2 8PSK 4060V / 31253 / 3/4' > Tp# 19
< (26)4060V SID 0x0c --- UnKnown Service Type 64 /> 1:0:64:C:3C0:0:A598FDC:0:0:0:

< 'DVB-S2 8PSK 4081H / 31248 / 3/4' > Tp# 20
< (27)4081H SID 0x0c --- UnKnown Service Type 64 /> 1:0:64:C:3B6:0:A590FF1:0:0:0:

< 'DVB-S2 8PSK 4097V / 3303 / 5/6' > Tp# 21

< 'DVB-S2 8PSK 4101V / 3303 / 5/6' > Tp# 22
< (28)Remington HD TVG Backup /> 1:0:1:1:1:FFFF:A599005:0:0:0:

< 'DVB-S2 8PSK 4105V / 3303 / 5/6' > Tp# 23
< (29)Hoosier Park HD Clean /> 1:0:1:1:1:FFFF:A599009:0:0:0:

< 'DVB-S2 8PSK 4108V / 3303 / 5/6' > Tp# 24
< (30)Meadowlands HD TVG sat /> 1:0:1:1:1:FFFF:A59900C:0:0:0:<

Blind Scan Completed in 3 Minutes 55 Seconds.
30 Channels ( TV = 30 Radio = 0) 24 of 24 Transponders Scanned.

[clubfoot]

Are the correct drivers for best scanning performance included in the default TNAP 3.2 image or do they need to be added afterwards from the software update or manually?

[el bandido]

TNAP 3.2 is set for the best scan unless you change the driver.