Event Counter


Featured functions

  • 5 counters included
  • Any switch, logical, voice, app etc. can be used
  • Name of counter is adjustable by user
  • Events are stored in persistent memory
  • Events can be manually adjusted from application
  • Counter 1 and 2 can be put to main screen as telemetry windows
  • Counter 1 and 2 have adjustable alarm-value, operates a switch

Also available for DC/DS-16, difference is 2 counters instead of 5. All functions are the same.

Have you ever wondered how many times some event or function is used in a model? Do you have a maintenance interval of 50 events on for example retracts? Well, let’s keep track on them!


In short: Copy the .lc (or .lua, the .lc is memory-optimized) file from github here to your transmitters Apps-folder, if there is a translation file copy the .jsn file to Apps/Lang-folder on your transmitter. Head on to “Applications” -> “User applications” and add the app. Guide on installation of Lua-apps available here if you need some more in-depth guide.

Setting up and using Event Counter

After opening the app you are welcomed with configuration screen in traditional Jeti-fashion:


Rules of usage are simple. Select a switch (any physical, logical etc) for a counter. Every time this switch is ON the counter-number is increased with one. You can also adjust the value of “Current count” manually if you need to.

Counters 1 and two are multi-function counters. Both have their own telemetry-window you can put on your main screen and both have own alarms. Simply adjust the alarm-value to for example 10 and make a sound on event to use the switch “Counter 1 Alm” to activate a desired sound-file. When value of counter goes to (in this case) 10 the switch gets activated. Switch is deactivated when counter is below alarm-value again either bu raising the alarm-value or lowering the counter-value. Both are adjustable by user.

If alarm-value is set to zero the alarm-function is disabled.


The windows to main screen are added the normal way, go to “Timers/Sensor” -> “Displayed Telemetry” and add the desired window as usual, here I have renamed one counter to “Autorotation”:


The size is not adjustable, window will always be displayed in the small version, here with 9 autorotations done on one counter and two flights on the second counter:


That’s how easy that is!

About counter-numbers

The amount of counters are stored in persistent memory every time they change, this means when you restart your transmitter etc the values are there. They are not reset when powering off the model for example. Values are stored per model.

If you have need to alter the event-count for specific counter this is possible from the application.

Version history

  • 1.0 Original version
  • 1.1 Moved to “one app”
  • 1.2 Removed from “One app”, added two counters, code comments
  • 1.3 Added alarm possibility to counter 1 and 2
  • 1.4 Added multi-language, languages available EN, DE
  • 1.5 Added French translation – Courtesy of Daniem Memin
  • 1.6 Fixed: Error when used together with all other apps
  • 1.7 Added Spanish translation by César Casado, fixed label width
  • 1.8 DC/DS-16 version released
  • 1.9 Character bug fixed
  • 2.0 Memory improvements


Some rules do of course apply!

  • Never use LUA to control a function that would take the model down if misbehaving!
  • Always, always test the function thoroughly!
  • If you do not know, then don’t!
  • RC-Thoughts or myself is NOT responsible for anything this application does
  • Applications are free to use (MIT-license) and linking to this page is encouraged!