342 replies to this topic

[Erik Slagter]

1) I should check whether simulate is recognised as such and prevents the SCR code from actually sending commands, I think it is that way, but I want to be sure
2) I don't understand. I tested on a release-6.2 image, does that matter? Which "the fix", fix for what?
3) yes indeed that is, I think, the cause, now the question is how to fix/workaround that. I can add an additional delay "command" to the queue, but I'd rather not do that if it's not necessary.
 

See sec.cpp, from line 1762 onwards, that's where the SEC commands are built and a.o. delays and voltage changes are added. So I think you should try DELAY_AFTER_LAST_DISEQC_CMD, but one of the other delay settings might work as well or better.

 

sec_sequence.push_back( eSecCommand(eSecCommand::SEND_DISEQC, diseqc) );
sec_sequence.push_back( eSecCommand(eSecCommand::SLEEP, m_params[DELAY_AFTER_LAST_DISEQC_CMD]) );
sec_sequence.push_back( eSecCommand(eSecCommand::SET_VOLTAGE, VOLTAGE(13)) );

 

[Erik Slagter]

I see something that worries me, btw. The member function eDVBSatelliteEquipmentControl::prepare has this as first line:

bool simulate = ((eDVBFrontend*)&frontend)->is_simulate();

But this local variable is never used.

 

Maybe the use of the "simulated" frontends refrains the SEC commands from being actually sent, fingers crossed...

[Abu Baniaz]

2) I don't understand. I tested on a release-6.2 image, does that matter? Which "the fix", fix for what?

The "Fix" being referred to is
https://github.com/O...c62317670a7fc5d

This avoids the problem and is not an actual fix. But as mentioned several times in the thread, the root problem should be fixed.

This is not in 6.2 images

[littlesat]

This solved also a different problem...

[ccs]

This solved also a different problem...

You've mentioned this many, many times - what is this "different problem"?

[littlesat]

Encrypt (oscam) and recordings starting at the same time

[Erik Slagter]

 

2) I don't understand. I tested on a release-6.2 image, does that matter? Which "the fix", fix for what?

The "Fix" being referred to is
https://github.com/O...c62317670a7fc5d

This avoids the problem and is not an actual fix. But as mentioned several times in the thread, the root problem should be fixed.

This is not in 6.2 images

That is not a fix. It's a workaround for testing. So it shouldn't be the base for fixing. Is it in the deveop code base? Then it should be removed asap. Who merged this?

[Erik Slagter]

Encrypt (oscam) and recordings starting at the same time

Yes, that one I've seen as well. The recording is fine, but only starts decrypting after a few seconds. That's an OScam issue, it would be silly to workaround that in enigma.

[littlesat]

Agree.. and sometimes even doesn’t start at all... since this work-a-round all is ok... and solving it in Oscam doesn’t happen... I just did test here if this solves the Oscam issue... and it did... and it also works-a-round partly the unicable/Jess issue.... so arranging recordings do not start at exect the same second isn’t that bad...

Edited by littlesat, 13 October 2018 - 09:08.

[Erik Slagter]

Whatever happens, we are not going to workaround this in enigma.

 

I am pretty sure that if you deliver a patch to the oscam guys that solve this, they will apply it.

 

BTW it could very well be the ecm limiter that we probably both have enabled.

[Abu Baniaz]

Hello Erik, everyone is waiting for a proper and real fix. Can you assist please?

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[Erik Slagter]

I am already doing for this for like, three weeks? I don't have the problems, I can't debug it, you will have to do that for me. Did you already test tweaking the SEC delays I've been asking for weeks now?

[littlesat]

Mayby you need to power the switch by the box to get issues???

[Erik Slagter]

That may also be influentual. My switch is self-powered (and can be only self-powered, it won't work without the external power).

 

But according to some people here, the powering is not the issue.

[Abu Baniaz]

Erik, of the testers, only you and twol have a working switch. Twol has confirmed the issue with his switch. My switch is not listed and I cannot seem to get it to work, maybe it needs an independent power supply like yours. I posted a request to add it to the list of devices here
https://forums.openp...-13#entry943018

I am sorry, we must have missed your suggestions or they have gone above our heads. Can you post a suggested patch like athoik has please?

[littlesat]

Can you post a merge request of the change in unicable.xml.... so I also quicky see the differences for evaluation...

[Erik Slagter]

Erik, of the testers, only you and twol have a working switch. Twol has confirmed the issue with his switch. My switch is not listed and I cannot seem to get it to work, maybe it needs an independent power supply like yours. I posted a request to add it to the list of devices here
https://forums.openp...-13#entry943018

I am not debating whether you (the others) are right in saying that your devices have this problem, let's have that clear. It's just that I am refusing to try a few quick workarounds and keep whatever seems to be working, without knowing what it exactly does and having potential negative influence on existing, working setups.
 
As long as we don't know exactly what's happening, we can't make a proper fix. And as I don't have a setup that shows the symptoms, I can't debug it, agree?
 
Whether a switch is listed or not has absolutely no influence on whether it will work or not. Just set it up manually for the time being, I've done that many times before we had my switch in the list. Quickest way to get it in, is to take a look at the unicable.xml file, see how others are defined, add yours and post a patch or PR. I am really not going to that, I could spend whole days adding all possible devices.
 
Whether a certain switch needs an external power supply to function properly, I can't really help you there, can I?
 

I am sorry, we must have missed your suggestions or they have gone above our heads. Can you post a suggested patch like athoik has please?

Not a patch. There is a plugin to configure DiSEqC delays. Install that and play with the values. There must be one or two delays you can increase that should have influence. Don't take the word DiSEqC literally here, it actually means "SEC" and influences everything sent over the cable to external devices, be it LNB's or switches, legacy, toneburst, DiSEqC or SCR.

[Huevos]

That may also be influentual. My switch is self-powered (and can be only self-powered, it won't work without the external power).

 

But according to some people here, the powering is not the issue.

Powering is not the issue. Solo 4K sends power to the LNB before enigma even starts to boot. Power is always present. And anyway the LNB uses a fraction of the power that the switch does.

Edited by Huevos, 13 October 2018 - 16:53.

[Erik Slagter]

I guess 1/4th of the power of switch that drives four LNB's

[Huevos]

sec_sequence.push_back( eSecCommand(eSecCommand::SLEEP, m_params[DELAY_AFTER_LAST_DISEQC_CMD]) );

Increased that to 1000 (1 second). Makes no difference for the recording problem and just makes the STB very sluggish. Commands are still sent 1ms apart.

<  3744.336> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
<  3744.337> **** Tuning JESS
<  3744.337> **** frequency_mhz: 10847
<  3744.337> **** lo_mhz: 9750
<  3744.337> **** T: 997
<  3744.337> **** position: 0
<  3744.337> **** ub: 0
<  3744.337> **** mode: 0
<  3744.337> **** JESS: 70 03 e5 00
<  3744.337> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3744.337> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
<  3744.337> [eDVBFrontend] tuning to 1211 mhz
<  3744.337> [eDVBChannel] OURSTATE: tuning
<  3744.337> [eDVBServicePMTHandler] tune failed.
<  3744.337> [eDVBServiceRecord] RECORD service event 1
<  3744.337> [eDVBServiceRecord] record failed to tune
<  3744.337> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3744.337> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3744.337> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
<  3744.337> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3744.337> [eDVBChannel] OURSTATE: failed, retune
<  3744.337> [eDVBFrontend] (3)tune
<  3744.337> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2156, guard_offset 0
<  3744.337> **** Tuning JESS
<  3744.337> **** frequency_mhz: 11097
<  3744.337> **** lo_mhz: 9750
<  3744.337> **** T: 1247
<  3744.337> **** position: 0
<  3744.337> **** ub: 1
<  3744.337> **** mode: 0
<  3744.337> **** JESS: 70 0c df 00
<  3744.337> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3744.337> [eDVBFrontend] prepare_sat System 1 Freq 11097000 Pol 1 SR 23000000 INV 2 FEC 3 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
<  3744.337> [eDVBFrontend] tuning to 1421 mhz
<  3744.337> [eDVBChannel] OURSTATE: tuning
<  3744.337> [eDVBServicePMTHandler] tune failed.
<  3744.337> [eDVBServiceRecord] RECORD service event 1
<  3744.337> [eDVBServiceRecord] record failed to tune
<  3744.338> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3744.338> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3744.338> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 812 current: ffffffff
<  3744.338> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3744.338> [eDVBChannel] OURSTATE: failed, retune
<  3744.338> [eDVBFrontend] (4)tune
<  3744.338> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x4976, guard_offset 0
<  3744.338> **** Tuning JESS
<  3744.338> **** frequency_mhz: 10964
<  3744.338> **** lo_mhz: 9750
<  3744.338> **** T: 1114
<  3744.338> **** position: 0
<  3744.338> **** ub: 2
<  3744.338> **** mode: 2
<  3744.338> **** JESS: 70 14 5a 02
<  3744.338> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3744.338> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
<  3744.338> [eDVBFrontend] tuning to 1681 mhz
<  3744.338> [eDVBChannel] OURSTATE: tuning
<  3744.338> [eDVBServicePMTHandler] tune failed.
<  3744.338> [eDVBServiceRecord] RECORD service event 1
<  3744.338> [eDVBServiceRecord] record failed to tune
<  3744.338> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3744.338> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3744.338> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
<  3744.338> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3744.338> [eDVBFrontend] set static current limiting
<  3744.338> [eDVBFrontend] set static current limiting
<  3744.338> [eDVBFrontend] set static current limiting
<  3744.338> [eDVBFrontend] invalidate current switch params
<  3744.339> [eDVBFrontend] invalidate current switch params
<  3744.339> [eDVBFrontend] invalidate current switch params
<  3744.339> [eDVBFrontend] set sequence pos 3
<  3744.339> [eDVBFrontend] set sequence pos 3
<  3744.339> [eDVBFrontend] set sequence pos 3
<  3744.339> [eDVBFrontend] setVoltage 2
<  3744.340> [eDVBFrontend] setVoltage 2
<  3744.340> [eDVBFrontend] setVoltage 2
<  3744.341> [eDVBFrontend] setTone 0
<  3744.342> [eDVBFrontend] setTone 0
<  3744.342> [eDVBFrontend] setTone 0
<  3744.343> [eDVBFrontend] sleep 75ms
<  3744.343> [eDVBFrontend] sleep 75ms
<  3744.343> [eDVBFrontend] sleep 75ms
<  3744.474> [eDVBFrontend] sendDiseqc: 7003e500(?)
<  3744.530> [eDVBFrontend] sendDiseqc: 700cdf00(?)
<  3744.586> [eDVBFrontend] sendDiseqc: 70145a02(?)
<  3744.586> [eDVBFrontend] sleep 1000ms
<  3744.586> [eDVBFrontend] sleep 1000ms
<  3744.587> [eDVBFrontend] sleep 1000ms
<  3744.615> [eInputDeviceInit] 1 67 1
<  3744.619> [InfoBarGenerics] KEY: 103 UP
<  3744.619> [ActionMap] Keymap 'DirectionActions' -> Action = 'up'
<  3744.720> [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20181014 0111 - Channel 5 HD - Criminals_ Caught On Camera.ts
<  3744.720> [eDVBTSTools] getPTS read error
<  3744.720> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  3744.940> [eInputDeviceInit] 0 67 1
<  3744.943> [InfoBarGenerics] KEY: 103 UP
<  3745.227> [eInputDeviceInit] 1 67 1
<  3745.231> [InfoBarGenerics] KEY: 103 UP
<  3745.231> [ActionMap] Keymap 'DirectionActions' -> Action = 'up'
<  3745.332> [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20181014 0111 - BBC One HD - The NFL Show.ts
<  3745.332> [eDVBTSTools] getPTS read error
<  3745.332> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  3745.560> [eInputDeviceInit] 0 67 1
<  3745.563> [InfoBarGenerics] KEY: 103 UP
<  3745.586> [eDVBFrontend] setVoltage 1
<  3745.587> [eDVBFrontend] setVoltage 1
<  3745.588> [eDVBFrontend] update current switch params
<  3745.588> [eDVBFrontend] setVoltage 1
<  3745.588> [eDVBFrontend] update current switch params
<  3745.589> [eDVBFrontend] startTuneTimeout 5000
<  3745.589> [eDVBFrontend] update current switch params
<  3745.589> [eDVBFrontend] startTuneTimeout 5000
<  3745.589> [eDVBFrontend] setFrontend 1
<  3745.589> [eDVBFrontend] setting frontend 0
<  3745.589> [eDVBFrontend] (0)fe event: status 0, inversion off, m_tuning 1
<  3745.589> [eDVBFrontend] startTuneTimeout 5000
<  3745.589> [eDVBFrontend] setFrontend 1
<  3745.589> [eDVBFrontend] setting frontend 3
<  3745.589> [eDVBFrontend] sleep 500ms
<  3745.589> [eDVBFrontend] (3)fe event: status 0, inversion off, m_tuning 1
<  3745.589> [eDVBFrontend] setFrontend 1
<  3745.589> [eDVBFrontend] setting frontend 4
<  3745.589> [eDVBFrontend] sleep 500ms
<  3745.589> [eDVBFrontend] (4)fe event: status 0, inversion off, m_tuning 1
<  3745.589> [eDVBFrontend] sleep 500ms
<  3745.631> [eDVBFrontend] (0)fe event: status 7, inversion off, m_tuning 2
<  3745.631> [eDVBFrontend] (4)fe event: status 7, inversion off, m_tuning 2
<  3745.631> [eDVBFrontend] (3)fe event: status 7, inversion off, m_tuning 2
<  3746.089> [eDVBFrontend] set dynamic current limiting
<  3746.089> [eDVBFrontend] set dynamic current limiting
<  3746.089> [eDVBFrontend] set dynamic current limiting
<  3750.589> [eDVBChannel] OURSTATE: failed, retune
<  3750.589> [eDVBFrontend] (0)tune
<  3750.589> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0xe3, guard_offset 0
<  3750.589> **** Tuning JESS
<  3750.589> **** frequency_mhz: 10847
<  3750.589> **** lo_mhz: 9750
<  3750.589> **** T: 997
<  3750.589> **** position: 0
<  3750.589> **** ub: 0
<  3750.589> **** mode: 0
<  3750.589> **** JESS: 70 03 e5 00
<  3750.589> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3750.589> [eDVBFrontend] prepare_sat System 1 Freq 10847000 Pol 1 SR 23000000 INV 2 FEC 2 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
<  3750.589> [eDVBFrontend] tuning to 1211 mhz
<  3750.589> [eDVBChannel] OURSTATE: tuning
<  3750.589> [eDVBServicePMTHandler] tune failed.
<  3750.589> [eDVBServiceRecord] RECORD service event 1
<  3750.589> [eDVBServiceRecord] record failed to tune
<  3750.589> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3750.589> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3750.589> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 802 current: ffffffff
<  3750.589> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3750.589> [eDVBChannel] OURSTATE: failed, retune
<  3750.589> [eDVBFrontend] (3)tune
<  3750.589> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x2156, guard_offset 0
<  3750.589> **** Tuning JESS
<  3750.589> **** frequency_mhz: 11097
<  3750.589> **** lo_mhz: 9750
<  3750.589> **** T: 1247
<  3750.590> **** position: 0
<  3750.590> **** ub: 1
<  3750.590> **** mode: 0
<  3750.590> **** JESS: 70 0c df 00
<  3750.590> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3750.590> [eDVBFrontend] prepare_sat System 1 Freq 11097000 Pol 1 SR 23000000 INV 2 FEC 3 orbpos 282 system 1 modulation 2 pilot 2, rolloff 1, is_id -1, pls_mode 1, pls_code 0
<  3750.590> [eDVBFrontend] tuning to 1421 mhz
<  3750.590> [eDVBChannel] OURSTATE: tuning
<  3750.590> [eDVBServicePMTHandler] tune failed.
<  3750.590> [eDVBServiceRecord] RECORD service event 1
<  3750.590> [eDVBServiceRecord] record failed to tune
<  3750.590> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3750.590> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3750.590> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 812 current: ffffffff
<  3750.590> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3750.590> [eDVBChannel] OURSTATE: failed, retune
<  3750.590> [eDVBFrontend] (4)tune
<  3750.590> [eDVBSatelliteEquipmentControl] [prepare] UnicableTuningWord 0x4976, guard_offset 0
<  3750.590> **** Tuning JESS
<  3750.590> **** frequency_mhz: 10964
<  3750.590> **** lo_mhz: 9750
<  3750.590> **** T: 1114
<  3750.590> **** position: 0
<  3750.590> **** ub: 2
<  3750.590> **** mode: 2
<  3750.590> **** JESS: 70 14 5a 02
<  3750.590> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
<  3750.590> [eDVBFrontend] prepare_sat System 0 Freq 10964250 Pol 0 SR 22000000 INV 2 FEC 4 orbpos 282 system 0 modulation 1 pilot 2, rolloff 0, is_id -1, pls_mode 1, pls_code 0
<  3750.590> [eDVBFrontend] tuning to 1681 mhz
<  3750.590> [eDVBChannel] OURSTATE: tuning
<  3750.590> [eDVBServicePMTHandler] tune failed.
<  3750.590> [eDVBServiceRecord] RECORD service event 1
<  3750.590> [eDVBServiceRecord] record failed to tune
<  3750.590> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
<  3750.590> [eDVBServicePMTHandler] incorrect namespace. expected: 11a0000 current: ffffffff
<  3750.590> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 809 current: ffffffff
<  3750.590> [eDVBServicePMTHandler] incorrect original_network_id. expected: 2 current: ffffffff
<  3750.591> [eDVBFrontend] set static current limiting
<  3750.591> [eDVBFrontend] set static current limiting
<  3750.591> [eDVBFrontend] set static current limiting
<  3750.591> [eDVBFrontend] invalidate current switch params
<  3750.591> [eDVBFrontend] invalidate current switch params
<  3750.591> [eDVBFrontend] invalidate current switch params
<  3750.591> [eDVBFrontend] set sequence pos 3
<  3750.591> [eDVBFrontend] set sequence pos 3
<  3750.591> [eDVBFrontend] set sequence pos 3
<  3750.591> [eDVBFrontend] setVoltage 2
<  3750.592> [eDVBFrontend] setVoltage 2
<  3750.592> [eDVBFrontend] setVoltage 2
<  3750.593> [eDVBFrontend] setTone 0
<  3750.594> [eDVBFrontend] setTone 0
<  3750.594> [eDVBFrontend] setTone 0
<  3750.595> [eDVBFrontend] sleep 75ms
<  3750.595> [eDVBFrontend] sleep 75ms
<  3750.595> [eDVBFrontend] sleep 75ms