stick50jr

The mistake is this:
 
#SERVICE 1:0:1:250:251:1010:EEEE0000:0:0:0:http%3A//192.168.178.35%3A8002/1%3A0%3A1%3A250%3A251%3A1010%3AEEEE0000%3A0%3A0%3A0:ABC News 24

You assign a service reference with a SERVICE 1:  but you also define the EEEE0000 and I guess that the remote Duo2 where you define this entry also have a DVB-T tuner inside.

Since you tell your box that you are using a SERVICE 1: (DVB) and to use the DVB-T tuner (EEEE0000) this is what it is trying to do, but since nothing is connected to your DVB-T tuner or it cannot receive this channel you have go the no PAT message. If you copy the lamedb from one box to the other one then the entry for this channel exist in it and the box will try to use it from your tuner and not from the stream.

 

So if you really want to use SERVICE 1:  than change the EEEE00000 to 0  or if you don't use the DVB-T tuner at all in your remote box, disable the DVB-T tuner in your remote Duo2.

 

If you use SERVICE 4097:  your box know that it should not try to use your internal tuner and then it works.

But since it is a stream the best practice is to use SERVICE 4097:

Thanks for your suggestion and explanation.  Your assumption that I have DVB-T in both local and remote Duo2 is correct. 

Anyhow I've followed our advice and I have used

#SERVICE 1:0:1:250:251:1010:0:0:0:0:http%3A//192.168.178.35%3A8002/1%3A0%3A1%3A250%3A251%3A1010%3AEEEE0000%3A0%3A0%3A0:ABC News 24

but I still get the PAT message on this 8002 transcode port.

Just for comparison, I tried the same approach (replacing EEEE0000 with 0) with the 8001 non-transcode port

#SERVICE 1:0:1:250:251:1010:0:0:0:0:http%3A//192.168.178.35%3A8001/1%3A0%3A1%3A250%3A251%3A1010%3AEEEE0000%3A0%3A0%3A0:ABC News 24

This also so gets the PAT message but is fine when the 0 is returned to EEEE0000. 

So it seems I must stick to 4097 for the transcoded 8002 port.

The problem was only the PAT and the PMT not being repeated, it was only sent once. Which in itself isn't a crime, but it's better to repeat them. In this case enigma relies on the tables being repeated every once in a while. All of VU+, Mut@ant and Xtrend have patched their drivers so the tables get repeated and it works, tested it.

Hi Erik,

Apologies to return to this old thread, but I missed this last reply from you!  I've been using Service type 4097 as a work around but then I saw this old reply from you and thought I should try Service type 1 once again.  I used OpenPLi 7.2 release dated 31 Dec 2019 on both Duo2's but got the 'timeout reading PAT' message.  Perhaps the drivers were only fixed for Mut@ant and Xtrend?

Have I understood your post correctly that you tested VU+ successfully on OpenPLi?