00023 problem

[Allyboy]

I have this issue again in 00023 area. Have done a fresh scan and all the info in the service seems to be the same but it returning can't read data?

[abu baniaz]

I have this issue again in 00023 area. Have done a fresh scan and all the info in the service seems to be the same but it returning can't read data?

Can you run the NitAnalyser in post 1 of this thread
https://www.world-of-satellite.com/showthread.php?38120-Virgin-NetID-amp-Tuning-Frequencies-(Nit-Analyser)

Please make sure you are on an active cable channel when you do so

[abu baniaz]

Can you enable debug logs in image, enable extra debug in ABM. Restart. Run ABM again then attach the debug log.

[Allyboy]

Have attached the NIT scan.58129

[Allyboy]

Debug log58130

[Allyboy]

Trying to look at the NIT files they seem to be empty, are they correct or did I not do something correctly?

[abu baniaz]

Not sure. Try again.

[abu baniaz]

Update provider file and try ABM with 00021. It worked for someone else.
If it does not, enable debug log in image, enable extra debug, restart, run ABM, attach debug log to forum

[Allyboy]

Changing to 00021 has fixed the issue maybe they have changed NI to one area now.

[Allyboy]

Area 21 and 23 not working now 21 is saying Failed to tune on tuner B, 23 is cannot read data. Have attached log hope it helps.

58145

UPDATE - Got it fixed the Frequency and Modulation got changed on the latest provider files update so changed them back to 643000 and 5 still using area 21.

[abu baniaz]

Please clear/remove your cable service. restart, scan not using ABM, restart, attach both lamedb files.

I got that frequency from another user.

[Allyboy]

Service removed and full scan done lamedb attached

58146