239 replies to this topic

[Robinson]

What has been implemented by Pure2?

[athoik]

And where is the git repo?

[dzumba]

What has been implemented by Pure2?

Fix for power measurement!

[WTE]

It seems Pure2 is an enigma2 image which is actually called pur-e2 and support comes from HDSC.
I haven't heard till now of this image and it seems they violate the GPL as I couldn't find the sources in any git.
 

To force power measurement inside the image works well but this is not a fix but an ugly workaround.

Openpli provide an enigma2 fix to solve the locking problem during motor movement but a new image will been provide probably in the next days.

It seems every 7 days a new image Openpli is publish.

Edited by WTE, 25 March 2018 - 21:01.

[WanWizard]

It seems every 7 days a new image Openpli is publish.

 

If you are referring to release images, yes, they are build every monday, but they only contain emergency fixes. For new features added in develop you'll have to wait for the next version (we're expecting 6.2-rc within a few days).

[MCelliotG]

OpenVix seems to have the power management option enabled.

 

https://github.com/O...ns/Satconfig.py

if SystemInfo["CanMeasureFrontendInputPower"]:
						self.advancedPowerMeasurement = getConfigListEntry(_("Use power measurement"), currLnb.powerMeasurement, _("Power management. Consult your receiver's manual for more information."))
self.list.append(self.advancedPowerMeasurement)

I haven't tried it, but I don't really think this option is turned to false for no reason.

[WTE]

OpenVix seems to have the power management option enabled.

 

https://github.com/O...ns/Satconfig.py

if SystemInfo["CanMeasureFrontendInputPower"]:
						self.advancedPowerMeasurement = getConfigListEntry(_("Use power measurement"), currLnb.powerMeasurement, _("Power management. Consult your receiver's manual for more information."))
self.list.append(self.advancedPowerMeasurement)

I haven't tried it, but I don't really think this option is turned to false for no reason.

 

No, they use the enigma2 fix from openpli
https://github.com/O...258e4d868b54acc

[dhwz]

@MCelliotG
Dream has no powermeasurement as this is not available in hw. Dish rotation is calculated in a other way.

[Neo64]

Come on guys, I do not think it's so hard to implement a solution. On the other hand, teams with less experience of you do it.

Thanks

[MCelliotG]

@MCelliotG
Dream has no powermeasurement as this is not available in hw. Dish rotation is calculated in a other way.

There are no words to describe how flawlessly the Silabs tuners work on Dreamboxes.

- Live tuner values supported fully (no 10600 and 9750 shown as frequencies)

- Dish rotation calculated correctly

- No rounded values, all increments are reported correctly (0.25 for silabs demods)

- No pixellation on RAI HD while zapping

- Blind lock supported (from what I've seen, I may be wrong)

- Blindscan with live constellation monitoring fully supported

 

Now the question is how did they do that? What did they do to push Silabs issue the correct driver that brings out all this tuner's capabilities? And why don't other manufacturers push for that driver version?

It's such a pity to have HD51  - that otherwise is an excellent receiver - with a tuner driver that brings so many problems!

Edited by MCelliotG, 26 March 2018 - 10:15.

[dhwz]

Dream is just 100% writing their own drivers no foreign work is used.

PS: constellation is only available on BCM, SiLabs is not able to provide such livedata.

Edited by dhwz, 26 March 2018 - 11:14.

[WanWizard]

And because of that, they also have access to all NDA material, both from Broadcom and the tuner manufacturers, including documentation and SDK's.

[zeros]

Dm920 works reaaallly well with that Silabs tuners ;-) (at least with my config)
I read many of the concerns, but they don’t occur on me.

Edited by zeros, 26 March 2018 - 17:09.

[Neo64]

You are releasing two new releases with a date of 26 .03 and there are no changes by engine issue, so that.  ONLY that you implement this engine solution and remains the same, is it so complicated?

Edited by Neo64, 27 March 2018 - 21:37.

[MCelliotG]

The problem is that the power measurement fixes one issue, creates others! I could install a PureE2 image on HD51 and see what they have in their satconfig.py, but I don't know how it would help...

[MCelliotG]

I installed purE2 and what I saw is that they do offer the Power Measurement option, however I was mostly surprised that the motor works well even without this option enabled!

I can send any file you like, just let me know. For the moment what I see in the satconfig.py is this:

        if SystemInfo['CanMeasureFrontendInputPower'] or getMachineBuild() in ('hd51', 'h7'):
            self.advancedPowerMeasurement = getConfigListEntry(_('Use power measurement'), nim.powerMeasurement)
            list.append(self.advancedPowerMeasurement)
            if nim.powerMeasurement.value:
                list.append(getConfigListEntry(_('Power threshold in mA'), nim.powerThreshold))
                self.turningSpeed = getConfigListEntry(_('Rotor turning speed'), nim.turningSpeed)
                list.append(self.turningSpeed)
                if nim.turningSpeed.value == 'fast epoch':
                    self.turnFastEpochBegin = getConfigListEntry(_('Begin time'), nim.fastTurningBegin)
                    self.turnFastEpochEnd = getConfigListEntry(_('End time'), nim.fastTurningEnd)
                    list.append(self.turnFastEpochBegin)
                    list.append(self.turnFastEpochEnd)
        elif nim.powerMeasurement.value:
            nim.powerMeasurement.value = False
            nim.powerMeasurement.save()

[Huevos]

 

I installed purE2 and what I saw is that they do offer the Power Measurement option, however I was mostly surprised that the motor works well even without this option enabled!

I can send any file you like, just let me know. For the moment what I see in the satconfig.py is this:

        if SystemInfo['CanMeasureFrontendInputPower'] or getMachineBuild() in ('hd51', 'h7'):
            self.advancedPowerMeasurement = getConfigListEntry(_('Use power measurement'), nim.powerMeasurement)
            list.append(self.advancedPowerMeasurement)
            if nim.powerMeasurement.value:
                list.append(getConfigListEntry(_('Power threshold in mA'), nim.powerThreshold))
                self.turningSpeed = getConfigListEntry(_('Rotor turning speed'), nim.turningSpeed)
                list.append(self.turningSpeed)
                if nim.turningSpeed.value == 'fast epoch':
                    self.turnFastEpochBegin = getConfigListEntry(_('Begin time'), nim.fastTurningBegin)
                    self.turnFastEpochEnd = getConfigListEntry(_('End time'), nim.fastTurningEnd)
                    list.append(self.turnFastEpochBegin)
                    list.append(self.turnFastEpochEnd)
        elif nim.powerMeasurement.value:
            nim.powerMeasurement.value = False
            nim.powerMeasurement.save()

What a nasty hack. If they did want to do that it should have been added in SystemInfo.py. e.g. (with branding module)..

SystemInfo["CanMeasureFrontendInputPower"] = getMachineBuild() in ('hd51', 'h7') or eDVBResourceManager.getInstance().canMeasureFrontendInputPower()

Edited by Huevos, 28 March 2018 - 08:28.

[Robinson]

The code is not clear to me. What does it do? Does it force Power Measurement to off?

[Huevos]

It doesn't force the option either way. The default value remains the same. Just allows the option to show in the GUI.

[MCelliotG]

They only added HD51 and H7 to the powermeasurement option via boxbranding, only changed three lines from the openATV satconfig.py. I transfered their satconfig.py to OpenATV and it works. However it's still a workaround!

I saw another change on OpenVIX that actually Huevos commited

https://github.com/O...021e88e4db9320c

 

Does it fix the issue completely?