Seems there is a timing problem.

see here:
https://www.neutrino-images.de/board/viewtopic.php?f=26&t=3759&start=20

there is a big timing difference to my TV-timing. Maybe the delay starts at the beginning of the telegram an not at the end of the telegram.

Origin commit data
------------------
Branch: ni/coolstream
Commit: a88f822bee
Author: IngoF <ingo.fischer@arcormail.de>
Date: 2019-08-22 (Thu, 22 Aug 2019)



------------------
This commit was generated by Migit
This commit is contained in:
IngoF
2019-08-22 17:09:53 +00:00
parent 33762a47bb
commit 86a931206e

View File

@@ -1724,7 +1724,7 @@ uint32_t CFrontend::sendEN50494TuningCommand(const uint32_t frequency, const int
}
fop(ioctl, FE_SET_VOLTAGE, SEC_VOLTAGE_18);
usleep(20 * 1000); /* en50494 says: >4ms and < 22 ms */
sendDiseqcCommand(&cmd, 80); /* en50494 says: >2ms and < 60 ms */
sendDiseqcCommand(&cmd, 120); /* en50494 says: >2ms and < 60 ms -- it seems we must add the lengthe of telegramm itself (~65ms)*/
fop(ioctl, FE_SET_VOLTAGE, unicable_lowvolt);
}
return ret;
@@ -1761,7 +1761,7 @@ uint32_t CFrontend::sendEN50607TuningCommand(const uint32_t frequency, const int
high_band; /* high_band == 0x01 */
fop(ioctl, FE_SET_VOLTAGE, SEC_VOLTAGE_18);
usleep(20 * 1000); /* en50494 says: >4ms and < 22 ms */
sendDiseqcCommand(&cmd, 80); /* en50494 says: >2ms and < 60 ms */
sendDiseqcCommand(&cmd, 120); /* en50494 says: >2ms and < 60 ms -- it seems we must add the lengthe of telegramm itself (~65ms)*/
fop(ioctl, FE_SET_VOLTAGE, unicable_lowvolt);
}
return ret;