AW: MCA Development Talk
so siehts aus, wenn mehr als ein client den selben sender schaut
und trotzdem noch freezer, hat also überhaupt nix mit den signallaufzeiten zu tun
Bitte wenns geht den debug-level auf ALL (65535) stellen für zukünftige Logs (das geht übers Webinterface).
An den Signallaufzeiten von der Karte zu oscam wird es wohl nicht liegen, da hast du recht,
allerdings gibt es noch andere stellen, wo es zu Verzögerungen kommen kann.
Nach Auswerten einiger Logs von a1, sieht es so aus als ob die ECMS ebenfalls rechtzeitig bei oscam ankommen,
meine Vermutung ist daher, das die CWs vom mcam nicht rechtzeitig an den Receiver übermittelt werden.
auch der start des fernsehers aus dem standby direkt in einen s*y-sender mit entschlüsselung klappt. allerdings dauert das eeeeeeewig. über sechs minuten zeigt der log, aber das kann ich eigentlich nicht glauben, muß ich mal mit stoppuhr messen...
Das liegt, daran, das der mcam dem oscam keine Daten über das Programm liefert, ein kurzes Hin- und Herschalten sollte aber Abhilfe schaffen.
Hi mrweb und co. thank you very much for your hard work.
i have one request if its possible..?
could you make so that the cam also support caids 0500?
CAID 0500 is allready included in the Firmware, the list of supported CAIDs is only relevant for some Receivers,
others ignore the list and also work with CAIDs not included in the list.
and is it possible to remove the featers in the mca twitter weahter and so on.
Removing twitter & co, would not improve the performance of the MCA, since they are only executed when selected in the menu.
I was thinking of trying to remove these options from the menu so it is becomes clearer, this would only be cosmetic though.
To change this I will have to patch the mcam, since we do not have sources and it doesn't really help improve performance,
this is currently not on top of our todo-list.
Great job dirtyharry123 and mrweb.
Can you post the sources of oscam version and the patch?.
I will provide the sources in a couple of days once I had a chance to do some more testing and improvements myself
(I am waiting to get a new receiver which hopefully supports the MCA)
I propose another change that may be of interest.
I've seen inside the CAM leading Apache, remains inactive. This has links wifi settings and other data from the CAM.
I did some testing a few weeks ago but activating the apache server but I have not managed to make changes.
The MCA indeed contains a webserver with a configuration-interface which is deactivated by default,
The interface is pretty buggy which likely is the reason it has been deactivated.
We were planning to implement a new interface ourselves using the busybox included httpd, this will take some time however.