Posts by TMS

    Hallo Klaus,


    ich bin der Vater von Tim. Gerne können wir einen Termin vereinbaren, damit du dir den CORE live ansehen kannst. Das gilt auch für weitere Interessenten aus der Region ("Ruhrgebiet"). Bei Bedarf einfach melden. Ich schreibe dir gleich via deiner Temp.email...


    bis bald


    Thomas

    Hi John,


    understand, also thought about experimenting with that since CF is growing more and more in high-end airframes, regardless of aircraft type (sail/engine). But cause lack of time inhibits me, I haven´t done this so far.


    In theory, I would use patches (microstrip on flex copper foil base) with correct polarization, i.e. RHCP in this case. But the mounting hight to ground plane has great influence on the antenna performance and feed point.


    You have one RF antenna expert in your neighbourhood. Since you drive a professional project, it may be useful to check with a RF expert (if you didn´t already)


    https://orbanmicrowave.com/ and


    http://orbanmicrowave.com/wp-c…tch-Antennas-2009-rev.pdf



    Tell us your results if you are allowed to share them...



    cu


    Thomas

    Hi Alan,


    didn´t forget about finding a time slot for a nightly talk as we used to have in the past. Guess Tim will be with us then. But have much work to do in my company. That´s also the reason why Tim has mostly to develop on P² on his own these days. Must say I´m proud of what he has already done so far :-)


    The SIM IF is only one first stage of his development and mainly done to test his own P² library functions. Next will be other sensors, blackbox function and so on...


    Regarding the patches in the CORE: Up to now haven´t opened the case so far. But I think Richard can give you/us this information (LHCP or RHCP) as this should not be considered confidential... But according to your first test, I guess it will be RHCP, like used by WEA.


    "cool" regards to Leicester


    Tim & Tom

    Hi John,


    nice to meet you here again, same as with Alan :-) Guess the last time we met was when you visited us in my workshop in Dortmund....


    Regarding your question, there was a nice article published in an Aviation Magazine. I attached one informative table which shows the impact of polarisation on antenna positioning and the resulting signal. As one can see, the WEA TX patches are RHCP (same is true for GNSS / GPS satellites).


    When using an LHCP RX antenna in conjunction with a RHCP TX antenna, you will get poor results. It will function in near field, cause both types pick up a small portion of the different oriented radiation, but with the distance getting bigger, you will expirience a dramatic loss of signal. That is why this constellation is not in the table.


    What is your motivation to use a linear pol. patch rather than using the dipoles fitted as standard ?



    best regards to NL and have a nice day


    Thomas

    ...die Funktion "Sender an, letztes Modell sofort steuerbar" finden wir aber aus Gewohnheit gut Ist nicht top wichtig, aber wenn mal Zeit ist wäre es schon prima das wieder zu haben. Da es keine Gleichkanal-Probleme mehr gibt, ist die Funktion auch unkritisch für andere Piloten.


    Ich kann ja selbst bestimmen ob mein Modell steuerbar ist, indem ich es entweder aus oder einschalte. Insofern vermisse ich keine Frage "HF aktivieren". Was ganz gut war, war die Frage ob tatsächlich ausgeschaltet werden soll, sofern nioch HF-Kontakt zum Modell / Empfänger bestand...


    Immerhin triggert der Taster einen shutdown. Richard wird wissen ob er den Power-Button im LINUX abfragen kann...

    Auch wenn LINUX sehr stabil ist, hat ein frisch gebootetes System gewisse Vorteile. Es könnte sonst sein, das der Kernel von einem Sleep in den nächsten kommt und man müsste einen Zwangsreboot einbauen...


    LG


    T&T

    ...nachdem Richard schrieb er will das mit dem nächsten Update beheben, ignorieren wir alles zum Thema Lautstärke bis dahin.


    Damit ist ja klar, das es in diesem Bereich Änderungen geben wird. Wir werden einfach abwarten.


    Anders wäre es, wenn Richard geschrieben hätte "...die Ticks sind deutlich hörbar..."



    LG


    T&T

    ... uns ist aufgefallen, dass das aktustische Feedback ("Ticks") der Trimm-Taster _sehr_ leise (fast nicht hörbar) ist. Hingegen ist der Ton bei Nulldurchgang gut hörbar, wenngleich auch nicht zu laut. (Lautstärke-Einstellung steht bereits auf max.)


    Ich nehme an, dass das noch eine Software-Sache ist, da der Speaker prinzipiell, z.B. bei den "Warnings" kräftige Töne von sich gibt. Oder gibt es 2 Speaker (LSP und Piezo ?) Habe den Sender bisher noch nicht geöffnet....



    LG


    T&T

    Hallo MC-24,


    kannst du die Schritte kurz auflisten, die definitiv zu diesem Verhalten führen ?


    Würde das mal versuchen nachzuvollziehen.


    Neben fehlerfreiem Code ist fehlerhafter Code der eindeutig reproduzierbare Fehler hat wohl das größte Geschenk für Programmierer.

    Da kann man gut bug-tracen ...



    LG


    Tom

    Norman, this is the translation for you (sorry about the dealy, had a lot of work to do):

    ---

    Until your requested function is natively implemented in the CORE software, you can help yourself by applying the following steps.


    (see the fotos above for reference)


    Principle of operation:


    As usual you have the ordinary throttle-timer, (we named it RUNTIME here), including a timer reset switch. We configured it as count-down type.


    For your requested feature, you need to create two AUX-Timers, each in count-down mode. They are only set at 1 sec, therefore they sound the

    configured alarm type at once. This is because the CORE internaly compares the actual timer value against "< 1", which is instantly given. (0.9999)

    (If it would start at 1.99999 sec. this solution would not work, the signal would be given with approx. 1 sec delay which would be nearly useless.)


    Those two AUX Timers have to appear on the standard telemetry screen. They can be as small as possible; their content is of no further interest.

    The CORE outputs only alarms for timers, which a currently shown on the active screen. So that is the reason why.


    Regarding the fotos from in the post above, those AUX timers are named Engine ON and Eingine OFF respectively.


    Additionally you need to configure two virtual switches. Tim named them same way like he did with the AUX timers.


    One of those virtual switches lets also start/stop the regular throttle-timer.


    Furthermore, these two virtual switches are configured in a kind of "vice-versa" style. The percantage value can be adjusted as you like to, but keep in mind

    that the difference is not more than 1%. You can see this on the fotos above.


    Each of these two virtual switches start an AUX-timer and in turn resets the other one to one second.



    Hope this works for you. If not, leave us a note.


    Have a nice day.


    (BTW, we live in Dortmund...)

    Hi Elvio,


    we observed the same issue.... after manual install of the driver, the update worked flawlessly... :)


    T&T

    Bis diese Funktion nativ im CORE eingebaut worden ist, kann man sich wie folgt helfen:


    Zunächst gibt es den regulären Timer RUNTIME, der die Gas-Laufzeit zählt. Bei uns als Count-down Timer.

    Zusätzlich gibt es einen gewöhnlichen Schalter um die RUNTIME zurückzusetzen, wie üblich.


    Nun legt man zwei Count-down Hilfs-Timer an, die bei erreichen der Zeit ein Signal (DAS Signal) auslösen,. das man beim Motor-Timer Start/Stop Übergang hören möchte.

    Diese Hilfs-Timer können als kleinstes Widget eingestellt werden; die Zeitanzeige dieser Hilfs-Timer ist ohne Bedeutung und kann ignoriert werden.

    Jedoch ist es wichtig, das diese Timer auf dem aktuell angezeigten Telemetrie-Bildschirm liegen, da andernfalls der Alarm (Vibration/Ton) nicht ausgegeben wird...

    Diese Hilfstimer werden auf 1 Sekunde gestellt, sie lösen also SOFORT aus, sobald sie loslaufen, da sie sofort einen Wert < 1 Sekunde annehmen (0.9999...)

    In den folgenden Bildschirmfotos heißen diese Engine ON und Engine OFF.


    Des Weiteren sind zwei virtuelle Schalter notwendig. Diese sind auf den Bildschirmfotos ebenfalls mit Eingine ON und Engine OFF benannt.

    Einer der beiden läßt auch den regulären RUNTIME-Timer starten/stoppen.

    Ansonsten sind die beiden gegensätzlich eingestellt, siehe Fotos. Der eingestellte Prozentwert muss den eigenen Bedürfnissen angepasst werden und die Differenz

    sollte möglichst nur 1% betragen.

    Diese zwei virtuellen Schalter starten jeweils einen der Hilfs-Timer und setzen den jeweils anderen Hilfs-Timer wieder auf 1 Sekunde zurück.


    Die nachfolgenden Fotos zeigen die oben beschriebenen, notwendigen Einstellungen:












    Viel Spaß



    Tim & Tom

    Hi Alan,


    best wishes for your health. Think we should have a skype session sometime in the future as we used to have with WEA :-)


    I´am not sure if we will be at JetPower since it´s possible that we are at a competition. But let´s se what time brings.

    Have fun with your CORE and best reagards to your wife


    Tim & Tom

    Hi Richard,


    will follow shortly; just doing some first dev on P²... makes fun as Dirk already stated.


    Congratulations for a real sucessor to the BAT6x family, taking good and proven concepts from the past and relaunch it with up to date and state of the art HW components.

    We tracked the development of the CORE in the past and finally we have one in our hands. Very Nice!


    T&T

    Hi Alan,


    nice to meet you here again. Just saw you experiments with the patches which we had also successfully applied to some of our SMART8 in F3J planes for competitions...

    (we had one ordinary dipol and one WEA patch)

    ---

    The core makes a good impression to me and Tim. He checked out the "3D-haptics" for his personal feel already. "At least it just feels like home" was his sttatement after some flights with the CORE :)


    Let´s stay in contact....


    regards from GER


    Tim & Tom

    Update easy and successful. Love the servo lists under functions, much easier to alter the servo you need. I still find the timer settings a bit confusing but sorted it in the end, a case of trying all options. Can you set a sound (or vibration) when a timer on the throttle stick goes from off to on or vice versa?

    Hi Norman,


    we were just inspired by your request for a signal when the throttle stick passes the point where a timer will start or stop...

    Told it my son by the way and he starts thinking about it how it can be solved with the already given functionality of the CORE (rel v1.4). Five minutes later he came back to me an presents a solution by using 2 addintional "AUX" timers. Now he has sound and/or vibration on his throttle stick when the timer starts / stops.


    Maybe this is giving you an idea how to do it. If not, Tim would be glad to tell you the necessary steps. This is of course a kind of workaround, but it is safe to use, no impact on reliability. Both AUX timers have to be on the currently shown telemetry screen (as small as possible) to sound the wanted signal(s). They have no primary function.


    (By trying that he discovered btw that only alarms triggered by timers that are displayed on the currently shown telemetry screen are signaled, regardless if tone or vibration.)


    Have a nice day and best reagards to britian


    Tim & Tom

    ....just saw the other mounting location. The ANT in the circle is not well positioned; in parallel and very close to the other wires. But it can be changed easily to an alternate position...




    (Or I maybe simply miss "the real" problem of your mountig situation.)


    What about this ? You have circular polarisation by the patches in the CORE, but never the less, this way you have both polarisation layers at the RX side....


    regards