Repository navigation
TechDescription
In this section you will find descriptions that can make usage easier in certain cases, while at the same time requiring minimal IT experience and great care.
Always make a backup, study the sample files!
The batteries and their model relationships are stored in the files located in the ./batfiles folder of the BattUse Widget.
batteries.csv : The list and data of the batteries.
batmodel.csv : Contains the model and battery relationships.
Note that the files are delimited with Unix line endings (LF). Manual modification requires care. Always make a backup!
The scripts do not tolerate faulty files or incorrectly filled fields.
It is advisable to archive these files from time to time for safety reasons!
The model settings (Inputs, Behavior) are stored in a csv-type file named /WIDGETS/BattUse/models/[MODEL_NAME].cfg in the widget folder. By copying this file, you can easily create identical settings for similar models, and you can also implement the backup and archiving of the settings. The model name in the file name must be exact!
Never modify its content manually!
At the end of every flight, BattUse creates an entry that contains the data described below. A daily flight log is created for easier manageability.
Its save location can be set in the "Behavior” / “Log Path" field.
The flight log is CSV type, the columns are separated by “,”, line ending is LF, it must contain the header row. It can be read and processed with any spreadsheet application.
The name of the file containing the flight log: "FlyLog_"[YYYYMMDD]_[model name].csv For example: "FlyLog_20260131_TRex 700X.csv"
The flight log contains the following columns.
| Field | Description |
|---|---|
| startFly | The date and time of the start of the flight. |
| endFly | The date and time of the end of the flight. |
| flyTime | The active time of the flight, while the model was not in Normal Mode. Based on Timer. |
| batteryID | The unique identifier of the selected, used battery. |
| batteryProduct | The name of the manufacturer of the selected, used battery. |
| startCount | How many times the battery has been flown ( batteryfile.earlyCount + batteryfile.count ) |
| startBatVolt | The voltage of the battery at the moment of connection. |
| startBatPercent | The charge percentage of the battery based on its voltage at the moment of connection. |
| endBatVolt | The voltage of the battery at the moment of disconnection. |
| endBatPercent | The charge percentage of the battery based on its voltage at the moment of disconnection. |
| mAmpFly | The amount of mAh flown out during the start. |
| maxAmp | The highest instantaneous consumption during the start, in Amperes. |
The best way is to create the list containing the batteries using the "BattUse Log Viewer" tool script, but you can also do it manually, which may be faster during the first commissioning. The table can be created with any spreadsheet application, or even with a text editor, its format is csv, the columns are separated by ",", line ending LF (Unix), it must contain the following header: “id,maxCapacity,product,cells,maxVolt,earlyCount,count,firstStartDate,retireDate,lastStartDate,capacity"
The character data in the columns must be between quotation marks. See the sample file!
The prepared table must be placed in the /WIDGETS/Battuse/batfiles folder, mandatory under the name batteries.csv. The batteries appear in the selection in the order found in the table.
You can download a sample table from here.
Attention! The program does not check the data, it expects them to be correct. Incorrect data result in incorrect operation!!
| Field name | Description |
|---|---|
| id | The unique identifier of the battery, mandatory to fill. Preferably display it on the battery. Alphanumeric, max 6 characters, must be unique in the table. |
| maxCapacity | The capacity of the battery in mAh. Numeric integer, 1-99999, mandatory to fill. Factory value that is indicated on the battery. |
| product | The manufacturer of the battery, 12 characters |
| cells | The number of cells of the battery, 1-99, numeric integer, mandatory to fill. |
| maxVolt | The cell voltage of the battery charged to 100%. Generally “4.2”, if higher the battery receives the “HV” mark. |
| earlyCount | The number of starts before the use of BattUse. |
| count | The number of starts counted by BattUse, initial value 0. The number of starts of the battery = count + earlyCount. |
| firstStartDate | The date of the first start, for administrative purposes, in date format. See its format at the end of the description. Empty in the case of a never used battery, BattUse fills it. |
| retireDate | Date of withdrawal from use. If filled, the battery will not be selectable, initially empty. |
| lastStartDate | date and time of the last start, initially empty field filled automatically by BattUse. |
| capacity | <= maxCapacity, Numeric integer, 1-99999, mandatory to fill. The capacity in mAh that can be maximally utilized from the battery. Depends on the age of the battery, the starts completed, its condition. This is the basis for determining the % depletion target. |
The date format mandatory to use in the table: YYYYMMDDHHMMSS example: 20260314103505
The best way is to create the list linking the batteries to models using the "BattUse Log Viewer" tool script, but you can also do it manually. This may be faster during the first commissioning. The table can be created with any spreadsheet application, or even with a text editor, its format is csv, the columns are separated by ",", line ending LF (Unix), it must contain the following header:
"batID,modelName"
The content of the fields is character-based therefore the data are between quotation marks, see the sample table!
Attention! The program does not check the data, it expects them to be correct. Incorrect data result in incorrect operation. Multiple models can be linked to one battery, in multiple rows.
| Field name | Description |
|---|---|
| batID | The value of the "id" field of the battery specified in the battery table. |
| modelName | The name of the model linked to the battery. Only those models are interpreted on whose screen the BattUse Widget has been set up (the [model name].cfg file exists in the BattUse/models folder) |