Hi Shepmac

Yes you can reconfigure the actions while importing a new layout page (not if you make a full backup). You can select within the import dialog for each action a new device / command. Maybe you have already find out, that you can send an data export direct to an other device over Wifi direct. The Datatransfer tool is very powerfull.

With the free IRControl App, the number of layout pages is limited to 4. With the Plus App there is no limitation. But it is maybe also a question of fairness. We offer the free version with full functionality and without any advertisment popup. It is therefore convienient for you to evaluate, if this is the right software for you. You have also free support here in our support fourm. I think this is generous. So it is fair, if you regularly use our App, also to buy it - and the price isn't expensive. You help to make it possible to continue the further development of IRControl.

Kind regards,
Urs

Hi Shepmac

We have not test it yet. But the RM Mini 3 has the same Interface like RM pro, so theoretically it should. RM Pro features (RF signals and temperature sensore) will not work of course.

Please let us know if it works successfully.

best regards,
Urs

Hallo Benny

Wir haben das auch getestet. Dies vor allem aus dem Grund, da es vielleicht Nutzer gibt, die nur ein Smartphone mit eher kleinerem Display haben und das da drauf betreiben möchten. Das ist grundsätzlich möglich, für die Konfiguration braucht es aber etwas einen grösseren Bildschirm. Da kommt die Idee ins Spiel, das auf einem Emulator unter Windows laufen zu lassen und dort drauf zu konfigurieren.

Wir haben das nur mit MEmu zum laufen gebracht, wobei die Netzwerkkonfiguration da etwas tricky ist und auch nicht einfach so funktioniert (wie Du ja festgestellt hast). Sieh mal in unsrem Handbuch unter http://ircontrol.cec.gmbh/handbuch/spez ... -executor/. Dort findest Du einen Link, wie man MEmu ans Netzwerk anbindet.

Viele Grüsse und viel Spass damit
Urs

Hoi Benjamin

Danke für die Blumen, smile.

Genau die Implementation davon hat eben dieses Problem ausgelöst. Im Handbuch, Command Action findet sich die Anleitung, wie man diese Buttons beeinflusst.

Viele Grüsse
Urs

Hoi Benjamin

Ich hab das Problem nun gefunden. Wenn Du eine eigene Farbe im Header definierst, überdeckt es die Buttons. Ich muss noch schauen, ob wir da einen Service-Release machen oder ob wir bis zum nächsten Major-Release warten können.

Danke und viele Grüsse
Urs

Hallo Benjamin

Na zumindest können wir nun das Problem etwas eingrenzen. Diese Icons (preferences-icon.png und Menu.png) werden aus dem Directory geladen, in dem sich alle vorinstallierten Icons befinden (/pic). Kannst Du mal im Layout auf einem Image View oder Image Button in das Verzeichnis schauen gehen, ob die dort vorhanden sind?

Viele Grüsse
Urs

Hallo Benny

Wir führen mit jeder Version Systemtests mit einem Android 4.4 durch. Das verhalten, welches Du beschreibst ist seltsam. In Version 2.30 wird der Setupmenu-Button sogar noch wesentlich früher im Ablauf erstellt (gleich nach der Initialisierung des Grafiksystems), da kann eigentlich nichts zuvor crashen. Wird den die Seite sonst ausgegeben, oder erscheint gar nichts? Diese Menus lassen sich ja nicht nur durch den Button, sondern auch durch eine Wischbewegung vom Rand reinfahren. Geht das denn?

Viele Grüsse
Urs

Hi SciMan

I have to say, that I have not yet analyzed how RF Codes exactly are buillt and what the Broadlink device do with it. I did not expect that the Broadlink can recognize if the sequence was sent multiple times. This is the reason that that repeate byte is set in sequence 2 + 3. So it is also obvious that the sequence is shorter and has the same length. (btw, the Broadlink header has 4 Bytes: 1 -> frequecy, 2 -> repeat Count, 3+4 length of sequence).

This 3 seqences looks similar for me. You have to know, that this is an amplitude curve and not a digital code. This values represents a puls length in 32,84ms units. You can imagine that the receiver of this code (in this case the Broadlink device) can't recognize this puls length exactly, so this are only roght values. It seams that the Broadlink device can't recognize, when the seqeuence starts, because they are shiftet. But I think this doesn't matter if the sequence is sent multiple times, because the receiver can recognize (or should) when the sequence starts. You can see there is a value significant higher than the others (around 70). I think this is a part of the start sequence.

I can't say definitely what's the Problem when sending Sequence 2/3 within a macro. What else is in this macro? Other Broadlink RC Actions? If it is so, you should separete them with an Sleep Command (Command Action, Parameter Sleep and as value the time in milliseconds). Otherwise they will be sent to close.

Why Sequence 1 is not working? I don't know. I think the Broadlink RF parts works well if it is irrelevant how long the sequence will be sent. In your usecase it seams to be a bit tricky.

Kind regards,
Urs

Hi SciMan

The Broadlink device does not have any capabilities to send infrared or RF signals continously as long as any key is pressed (or somthing similar). But it has the possibility to encode into the command sequence how many times the sequence should be repeated. This is normlally set to 0 repeats. Actually the IRControl App has no functionality to manipulate this repeat attribute, but it is a good idea to implement. So I can plan this for the next version of IRControl, but it is not clear, when it will be released.

So - yes you can also manipulate this repeat attribute in the command your device definintion if you are familar with XML files and Base64 encoding. All the configuration data of IRControl are stored in XML Files. You can export and import them with the Datatransfer function (Setup menu). You will find the RF sequences in the tag "irsequence" in the command part of the device XML file. This sequence (binary) is Base64 encoded for the Broadlink device. You will find there as fist byte a 0xb2 or 0xb7 (depending on sequence frequency) and as second byte a 0. This second byte specifys the repeat count (0 means no repeat, 1 means 1 repeat, ...). You can try to set this repeat byte, store the new sequence (again Base64 encoded) in the XML and reimport it in IRControl. Mybe a little bit an adventure, but not impossible.

Kind regards,
Urs

Hi SciMan

It does not have any differences between the triggers on an Action how the command is sent to the Broadlink device (except trigger timing is differnt). So this is not the problem. I propose to take trigger onclick for normal "button actions".

I can imagine that the stored radio control sequence is not corret or includes the same sequence several times. To learn radio control sequences with the Broadlink device is a little bit ugly. It have to be done in 2 steps. In the first step, which the device use to determine the radio control frequency, you have to press and hold the button of your remote control device up to the continue button appears. The second step is used to decode the radio control sequence. So you have to press the button on your remote control device only very short (the sequence should be sent only once to the Broadlink device). If the sequence is stored correctly in this way, I think it should work.

Kind regards,
Urs