250 replies to this topic

[Huevos]

One log from SCR8 and one log from SCR9.

Edit: Can't get uploader to work.

http://images.satell.../putty.logs.zip

Edited by Huevos, 14 December 2016 - 20:40.

[athoik]

It seems that you get error -7 (errNoSourceFound in eDVBResourceManager::allocateFrontend).

< 76349.133> [eDVBResourceManager] allocate channel.. 0809:0002
< 76349.134> [eDVBServicePMTHandler] allocate Channel: res -7
< 76349.134> [eDVBServicePlay] DVB service failed to tune - error 10

Maybe because on SCR9 you get also that error?

< 76340.103> [NimManager] Reading terrestrial.xml
< 76340.147> [InitNimManager] tunerTypeChanged error:  global name 'self' is not defined
< 76340.558> eDVBSatelliteEquipmentControl::clear()

[littlesat]

Athoik is this jess related in the scr9 log I do not see the lnb is called at jet (lines marked with ***

Sorry no team to anaylise it exactly.... But we should find the nasty mistake...

Edited by littlesat, 14 December 2016 - 21:34.

[athoik]

The error in NimManager might cause the tuner not configured correctly and not recognized by allocate frontend, so it never gets to the tune step where Jess command is send out.

[littlesat]

I think I got it... In sec.h in line 275 we forgot to set MAX_SATCR to 32.....

Sorry I'm not capable of test it right now with just having access to my iPad mini...

Edited by littlesat, 14 December 2016 - 22:03.

[Eragon]

That would suggest that the wrong protocol is used. JESS switches should be backward compatible and my experience with the Jultec switch is that you can even mix Unicable and JESS commands even from the same tuner (within the limits of Unicable, of course).

It looks like your switch is strict in how each user band must be addressed.

How did you configure your tuner in the configuration that did not work? Did you explicitly choose JESS as the protocol, did you check the position parameter, what User Band number did you use (because that must match to what the switch expects), etc.

 

 

Thank you very much for your support, Erik!

 

As I like testing , and as during the last months I followed the discussion on the board about the new JESS support, I decided to install the latest available OpenATV, image (that I don't like at all ), but just worth to see if JESS works there.

 

Well.... I must say it works perfectly...

 

I can freely select any combination of the 12 EN50607 user bands (5 to 16) and assign them to the 2 tuners, in any order (A=higher/B=lower, A=lower/B=higher) and even non contiguously.

 

Note: I tested on OpenATV the same exact setting combinations I tested without success on OpenPLi (except for the only one that worked also on OpenPLi, as I posted before).

 

For example, following there is one of the working combinations I successfully tested on OpenPLi (this one doesn't work on OpenPLi):

 

 

Tuner settings

 

 

 

Tuner A

 

 

 

 

 

Tuner B

 

Edited by Eragon, 14 December 2016 - 22:46.

[littlesat]

Lat this moment scrs above 8 do indeed not work... I thing due to max satcr is 8 at this moment... See my previous post...

[Eragon]

Ok, but in my test on OpenPLi only 5 and 6 work, and only if assigned 5 to tuner A and 6 to tuner B...

Of course I'm going to test JESS again when the max 8-limit will be fixed.

[littlesat]

FYI...

 

https://github.com/O...1cc4cb9581202ae

 

Not nice.... it seems in OpenATV you can not see which tuner do configure...

 

@#

Eragon

How do you connect your stuff.... Tuner A looped to tuner B, two different switches...it is not fully clear...

 

When you loop you probably somehow have to say that it is looped... You have to config that the other port is connected via a different port. I see you select connected via port A... That should work... But with ATV you select SCR index 8 and 12... not 5 or 6....

Edited by littlesat, 14 December 2016 - 23:41.

[Eragon]

 

Eragon

How do you connect your stuff.... Tuner A looped to tuner B, two different switches...it is not fully clear...

 

When you loop you probably somehow have to say that it is looped... You have to config that the other port is connected via a different port. I see you select connected via port A... That should work... But with ATV you select SCR index 8 and 12... not 5 or 6....

Hi littlesat,

my installation is very simple and straightforward, as I posted earlier:

LNB Quattro -> dCSS multiswitch Unitron-Johansson 9732 --> direct sat cable --> Tuner A of my Vu+ Duo2

 

No splitters, no switches, no other receivers, no whatsoever in between...only a straight sat cable directly connected from the multiswitch to Tuner A of my Vu+ Duo2.

It couldn't be more simple!

 

Both in OpenPLi and OpenATV the Tuner A and B have been configured in the way I shown here:

https://forums.openp...ndpost&p=630064

Tuner B is necessarily configured in settings as "Connect to A"

 

I kept always that tuner configuration.

Clearly, for testing purposes the only setting I had to change every time was the user band assignment, therefore nothing else than the user band was changed in the configuration.

I tested a lot of different combinations of EN50607 user bands to the 2 tuners.

 

My findings were that my simple installation always works correctly in OpenATV, regardless of the EN50607 user band combination assigned to the 2 tuners, while in OpenPLi it only correctly worked when assigning the user band 5 to Tuner A and the user band 6 to Tuner B.

 

[littlesat]

The user band should be a don't care...  that is not logical... 

 

But which box are you using (sorry when I missed that).

[Eragon]

I'm using a Vu+ Duo2

 

Other findings...

IMHO there is also something not correctly cleared by OpenPLi in the setting file when changing the tuner configuration.

 

For example, after finished testing with the JESS tuner settings, I was trying to test a standard (Unicable I) configuration, assigning to my Duo2 tuners 2 of the 4 compatible EN50494 user bands provided by my multiswitch

But unfortunately there was no way to make this configuration work.

 

So I opened the setting file and I saw that the "jess" string were still present in the tuner "nims.0" and "nims.1" settings, even if I had selected a non-JESS Unicable I matrix (a classic Inverto matrix providing the same Unicable I user bands as my multiswitch), so I manually deleted those 2 "jess" lines, rebooted and the tuners started working perfectly with those Unicable I user bands.

Edited by Eragon, 15 December 2016 - 10:33.

[littlesat]

Yes... sometimes previous settings are remembered... But this should not lead to wierdness... It is only easy when you set some thinks back to what it was...

 

But what you describe now I'm a bit 'blind'.... Did you also close enigma2 and then check the setting file. It might also be I need to add some additional save config stuff... and while configuring the setting file is not instantly updated by each change...

 

As far I know the internal 'loop' in VU boxes is made from tuner A to B... so you need to connect to tuner B to get both work....

Edited by littlesat, 15 December 2016 - 10:37.

[Eragon]

I used INIT 4 and INIT 3, and moreover I often rebooted the receiver between the tests, and always checked the settings file content.

 

About my Vu+ Duo2, the cable physically connected to Tuner A (and the Tuner B configured as "Connected to Tuner A") has always worked for me in the last two years with my previous Unicable I multiswitch (running OpenPLi)

 

This connection also worked running now OpenPLi with my new JESS/EN50607 multiswitch, using all the Unicable I user bands and using the JESS/EN50607 user band 5 and 6.

With OpenATV it works with all user bands in any combination.

 

Curiously in my tests, as I initially posted, OpenPLi actually didn't work using the JESS/EN50607 user bands 5 and 6 when the cable was connected to the Tuner B and the Tuner A configured as "Connected to Tuner B"...

Edited by Eragon, 15 December 2016 - 11:03.

[littlesat]

Can you post some logs, like huevos did... so we can see what happens... I think we solved huevos issue due to the logs. In addition it might be helpfull to have screenshots from your config..

And try to connect to B and then connect A to B.... instead of connect to A and then connect B to A... Just as double check please...

(but as far I understand the tuners do have an external loop.... so this should be a don't care... it could be a timing issue with the powersupply and pulses on the coax.. OpenATV did a lot of work-a-rounds to cover these kind of 'driver in combination with hardware' related issues... then we simply should find a good timing config for the VU DUO2 by playing with the diseqc timing parameters - you can adjust with a special plugin).

Edited by littlesat, 15 December 2016 - 12:29.

[Eragon]

Can you post some logs, like huevos did... so we can see what happens... I think we solved huevos issue due to the logs.

 

What files do you need?

[Zuppelan]

So indeed, as I said: "if hardware is DiSEqC-capable the (amended) firmware should be able to control it.". Nothing wrong with that.

Allthough I don't know the details of Unicable/JESS, I would expect Diseqc 1.x capable hardware to be unable to be upgrade to Unicable/JESS, because the electronical implementation is quite dependent on the 22KHz analog tonebursts to control universal LNB's. This analog dependency does not exist with Diseqc 2.x.

[littlesat]

See post #79 or #80

[Huevos]

Possible "config.isChanged()" is not working properly on this type of complex object and tuner config is not getting pushed to the settings file until reboot. None of the OE-Alliance images use isChanged() here. If the user presses save why would you want to use isChanged()?

 

https://github.com/O...tconfig.py#L592

Edited by Huevos, 15 December 2016 - 19:36.

[Erik Slagter]

Eragon, please note that both user interface and underlying code for JESS support are completely different between OpenATV and OpenPLi, we started from scratch (with, in my humble opinion better code and functionality in the end, and yes I know some people disagree, and now it's still in evolution). That to start with, I will read the others posts now.

 

BTW did you check if the position field (which ATV doesn't have) is correct?

 

Can you post screenshots of your config on OpenPLi?

Edited by Erik Slagter, 15 December 2016 - 19:50.