appeler les données de télémetrie
3 participants
Page 1 sur 1
appeler les données de télémetrie
je cherche comment appeler les données de télémétrie dans le script LUA
je cherche à avoir A1 A2 qui sont des tensions batterie Tx RSSI Tx RSSI Rx
visiblement batterie TX s'appelle par tx-voltage
mais les autres ???
je cherche à avoir A1 A2 qui sont des tensions batterie Tx RSSI Tx RSSI Rx
visiblement batterie TX s'appelle par tx-voltage
mais les autres ???
Invité- Invité
Re: appeler les données de télémetrie
Voici toute la liste des informations qu'il est possible de récupérer avec la commande getValue
il faut passer l'id à la fonction, le nom du champ ne marche pas pour tout
List of all fileds for OpenTX version 2.0.6:
field id: 1 name: "input1" desc: "Input [I1]"
field id: 2 name: "input2" desc: "Input [I2]"
field id: 3 name: "input3" desc: "Input [I3]"
field id: 4 name: "input4" desc: "Input [I4]"
field id: 5 name: "input5" desc: "Input [I5]"
field id: 6 name: "input6" desc: "Input [I6]"
field id: 7 name: "input7" desc: "Input [I7]"
field id: 8 name: "input8" desc: "Input [I8]"
field id: 9 name: "input9" desc: "Input [I9]"
field id: 10 name: "input10" desc: "Input [I10]"
field id: 11 name: "input11" desc: "Input [I11]"
field id: 12 name: "input12" desc: "Input [I12]"
field id: 13 name: "input13" desc: "Input [I13]"
field id: 14 name: "input14" desc: "Input [I14]"
field id: 15 name: "input15" desc: "Input [I15]"
field id: 16 name: "input16" desc: "Input [I16]"
field id: 17 name: "input17" desc: "Input [I17]"
field id: 18 name: "input18" desc: "Input [I18]"
field id: 19 name: "input19" desc: "Input [I19]"
field id: 20 name: "input20" desc: "Input [I20]"
field id: 21 name: "input21" desc: "Input [I21]"
field id: 22 name: "input22" desc: "Input [I22]"
field id: 23 name: "input23" desc: "Input [I23]"
field id: 24 name: "input24" desc: "Input [I24]"
field id: 25 name: "input25" desc: "Input [I25]"
field id: 26 name: "input26" desc: "Input [I26]"
field id: 27 name: "input27" desc: "Input [I27]"
field id: 28 name: "input28" desc: "Input [I28]"
field id: 29 name: "input29" desc: "Input [I29]"
field id: 30 name: "input30" desc: "Input [I30]"
field id: 31 name: "input31" desc: "Input [I31]"
field id: 32 name: "input32" desc: "Input [I32]"
field id: 75 name: "rud" desc: "Rudder"
field id: 76 name: "ele" desc: "Elevator"
field id: 77 name: "thr" desc: "Throttle"
field id: 78 name: "ail" desc: "Aileron"
field id: 79 name: "s1" desc: "Potentiometer 1"
field id: 80 name: "s2" desc: "Potentiometer 2"
field id: 81 name: "s3" desc: "Potentiometer 3"
field id: 82 name: "ls" desc: "Left slider"
field id: 83 name: "rs" desc: "Right slider"
field id: 85 name: "cyc1" desc: "Cyclic 1"
field id: 86 name: "cyc2" desc: "Cyclic 2"
field id: 87 name: "cyc3" desc: "Cyclic 3"
field id: 88 name: "trim-rud" desc: "Rudder trim"
field id: 89 name: "trim-ele" desc: "Elevator trim"
field id: 90 name: "trim-thr" desc: "Throttle trim"
field id: 91 name: "trim-ail" desc: "Aileron trim"
field id: 92 name: "sa" desc: "Switch A"
field id: 93 name: "sb" desc: "Switch B"
field id: 94 name: "sc" desc: "Switch C"
field id: 95 name: "sd" desc: "Switch D"
field id: 96 name: "se" desc: "Switch E"
field id: 97 name: "sf" desc: "Switch F"
field id: 98 name: "sg" desc: "Switch G"
field id: 99 name: "sh" desc: "Switch H"
field id: 100 name: "ls1" desc: "Logical switch L1"
field id: 101 name: "ls2" desc: "Logical switch L2"
field id: 102 name: "ls3" desc: "Logical switch L3"
field id: 103 name: "ls4" desc: "Logical switch L4"
field id: 104 name: "ls5" desc: "Logical switch L5"
field id: 105 name: "ls6" desc: "Logical switch L6"
field id: 106 name: "ls7" desc: "Logical switch L7"
field id: 107 name: "ls8" desc: "Logical switch L8"
field id: 108 name: "ls9" desc: "Logical switch L9"
field id: 109 name: "ls10" desc: "Logical switch L10"
field id: 110 name: "ls11" desc: "Logical switch L11"
field id: 111 name: "ls12" desc: "Logical switch L12"
field id: 112 name: "ls13" desc: "Logical switch L13"
field id: 113 name: "ls14" desc: "Logical switch L14"
field id: 114 name: "ls15" desc: "Logical switch L15"
field id: 115 name: "ls16" desc: "Logical switch L16"
field id: 116 name: "ls17" desc: "Logical switch L17"
field id: 117 name: "ls18" desc: "Logical switch L18"
field id: 118 name: "ls19" desc: "Logical switch L19"
field id: 119 name: "ls20" desc: "Logical switch L20"
field id: 120 name: "ls21" desc: "Logical switch L21"
field id: 121 name: "ls22" desc: "Logical switch L22"
field id: 122 name: "ls23" desc: "Logical switch L23"
field id: 123 name: "ls24" desc: "Logical switch L24"
field id: 124 name: "ls25" desc: "Logical switch L25"
field id: 125 name: "ls26" desc: "Logical switch L26"
field id: 126 name: "ls27" desc: "Logical switch L27"
field id: 127 name: "ls28" desc: "Logical switch L28"
field id: 128 name: "ls29" desc: "Logical switch L29"
field id: 129 name: "ls30" desc: "Logical switch L30"
field id: 130 name: "ls31" desc: "Logical switch L31"
field id: 131 name: "ls32" desc: "Logical switch L32"
field id: 132 name: "trn1" desc: "Trainer input 1"
field id: 133 name: "trn2" desc: "Trainer input 2"
field id: 134 name: "trn3" desc: "Trainer input 3"
field id: 135 name: "trn4" desc: "Trainer input 4"
field id: 136 name: "trn5" desc: "Trainer input 5"
field id: 137 name: "trn6" desc: "Trainer input 6"
field id: 138 name: "trn7" desc: "Trainer input 7"
field id: 139 name: "trn8" desc: "Trainer input 8"
field id: 140 name: "trn9" desc: "Trainer input 9"
field id: 141 name: "trn10" desc: "Trainer input 10"
field id: 142 name: "trn11" desc: "Trainer input 11"
field id: 143 name: "trn12" desc: "Trainer input 12"
field id: 144 name: "trn13" desc: "Trainer input 13"
field id: 145 name: "trn14" desc: "Trainer input 14"
field id: 146 name: "trn15" desc: "Trainer input 15"
field id: 147 name: "trn16" desc: "Trainer input 16"
field id: 148 name: "ch1" desc: "Channel CH1"
field id: 149 name: "ch2" desc: "Channel CH2"
field id: 150 name: "ch3" desc: "Channel CH3"
field id: 151 name: "ch4" desc: "Channel CH4"
field id: 152 name: "ch5" desc: "Channel CH5"
field id: 153 name: "ch6" desc: "Channel CH6"
field id: 154 name: "ch7" desc: "Channel CH7"
field id: 155 name: "ch8" desc: "Channel CH8"
field id: 156 name: "ch9" desc: "Channel CH9"
field id: 157 name: "ch10" desc: "Channel CH10"
field id: 158 name: "ch11" desc: "Channel CH11"
field id: 159 name: "ch12" desc: "Channel CH12"
field id: 160 name: "ch13" desc: "Channel CH13"
field id: 161 name: "ch14" desc: "Channel CH14"
field id: 162 name: "ch15" desc: "Channel CH15"
field id: 163 name: "ch16" desc: "Channel CH16"
field id: 164 name: "ch17" desc: "Channel CH17"
field id: 165 name: "ch18" desc: "Channel CH18"
field id: 166 name: "ch19" desc: "Channel CH19"
field id: 167 name: "ch20" desc: "Channel CH20"
field id: 168 name: "ch21" desc: "Channel CH21"
field id: 169 name: "ch22" desc: "Channel CH22"
field id: 170 name: "ch23" desc: "Channel CH23"
field id: 171 name: "ch24" desc: "Channel CH24"
field id: 172 name: "ch25" desc: "Channel CH25"
field id: 173 name: "ch26" desc: "Channel CH26"
field id: 174 name: "ch27" desc: "Channel CH27"
field id: 175 name: "ch28" desc: "Channel CH28"
field id: 176 name: "ch29" desc: "Channel CH29"
field id: 177 name: "ch30" desc: "Channel CH30"
field id: 178 name: "ch31" desc: "Channel CH31"
field id: 179 name: "ch32" desc: "Channel CH32"
field id: 180 name: "gvar1" desc: "Global variable 1"
field id: 181 name: "gvar2" desc: "Global variable 2"
field id: 182 name: "gvar3" desc: "Global variable 3"
field id: 183 name: "gvar4" desc: "Global variable 4"
field id: 184 name: "gvar5" desc: "Global variable 5"
field id: 185 name: "gvar6" desc: "Global variable 6"
field id: 186 name: "gvar7" desc: "Global variable 7"
field id: 187 name: "gvar8" desc: "Global variable 8"
field id: 188 name: "gvar9" desc: "Global variable 9"
field id: 189 name: "tx-voltage" desc: "Transmitter battery voltage [volts]"
field id: 190 name: "clock" desc: "RTC clock [minutes from midnight]"
field id: 196 name: "timer1" desc: "Timer 1 value [seconds]"
field id: 197 name: "timer2" desc: "Timer 2 value [seconds]"
field id: 198 name: "swr" desc: "Transmitter antenna quality [less is better]"
field id: 200 name: "rssi" desc: "RSSI [more is better]"
field id: 202 name: "a1" desc: "A1 analogue value [units as configured]"
field id: 203 name: "a2" desc: "A2 analogue value [units as configured]"
field id: 204 name: "a3" desc: "A3 analogue value [units as configured]"
field id: 205 name: "a4" desc: "A4 analogue value [units as configured]"
field id: 206 name: "altitude" desc: "Variometer altitude [meters]"
field id: 207 name: "rpm" desc: "Rotational speed [revolutions per minute]"
field id: 208 name: "fuel" desc: "Fuel level [???]"
field id: 209 name: "temp1" desc: "Temperature 1 [degrees celsius]"
field id: 210 name: "temp2" desc: "Temperature 2 [degrees celsius]"
field id: 211 name: "gps-speed" desc: "GPS speed [???]"
field id: 212 name: "distance" desc: "GPS distance [meters]"
field id: 213 name: "gps-altitude" desc: "GPS altitude [meters]"
field id: 214 name: "cell-min" desc: "LiPo sensor - lowest current cell voltage [volts]"
field id: 215 name: "cell-sum" desc: "LiPo sensor - current summ of all cell voltages [volts]"
field id: 216 name: "vfas" desc: "Current sensor - voltage [volts]"
field id: 217 name: "currentent" desc: "Current sensor - current [ampers]"
field id: 218 name: "consumption" desc: "Current sensor - consumption [mili amper hours]"
field id: 219 name: "power" desc: "Current sensor - power [wats]"
field id: 220 name: "accx" desc: "G sensor - acceleration in X axis [g]"
field id: 221 name: "accy" desc: "G sensor - acceleration in Y axis [g]"
field id: 222 name: "accz" desc: "G sensor - acceleration in Z axis [g]"
field id: 223 name: "heading" desc: "GPS heading [degrees]"
field id: 224 name: "vario" desc: "Variometer vertical speed [m/s]"
field id: 225 name: "air-speed" desc: "Air speed [knots]"
field id: 226 name: "dte" desc: "Total energy [???]"
field id: 232 name: "a1-min" desc: "A1 analogue value minimum [units as configured]"
field id: 233 name: "a2-min" desc: "A2 analogue value minimum [units as configured]"
field id: 234 name: "a3-min" desc: "A3 analogue value minimum [units as configured]"
field id: 235 name: "a4-min" desc: "A4 analogue value minimum [units as configured]"
field id: 236 name: "altitude-min" desc: "Lowest altitude [meters]"
field id: 237 name: "altitude-max" desc: "Highest altitude [meters]"
field id: 238 name: "rpm-max" desc: "Highest rotational speed [revolutions per minute] [meters]"
field id: 239 name: "temp1-max" desc: "Highest temperature 1 [degrees celsius]"
field id: 240 name: "temp2-max" desc: "Highest temperature 2 [degrees celsius]"
field id: 241 name: "gps-speed-max" desc: "Highest GPS speed [???]"
field id: 242 name: "distance-max" desc: "Biggest GPS distance [meters]"
field id: 243 name: "air-speed-max" desc: "Highest air speed [knots]"
field id: 244 name: "cell-min-min" desc: "LiPo sensor - all time lowest cell voltage [volts]"
field id: 245 name: "cell-sum-min" desc: "LiPo sensor - all time lowest summ of all cell voltages [volts]"
field id: 246 name: "vfas-min" desc: "Current sensor - lowest voltage [volts]"
field id: 247 name: "currentent-max" desc: "Current sensor - highest current [ampers]"
field id: 248 name: "power-max" desc: "Current sensor - highest power [wats]"
il faut passer l'id à la fonction, le nom du champ ne marche pas pour tout
List of all fileds for OpenTX version 2.0.6:
field id: 1 name: "input1" desc: "Input [I1]"
field id: 2 name: "input2" desc: "Input [I2]"
field id: 3 name: "input3" desc: "Input [I3]"
field id: 4 name: "input4" desc: "Input [I4]"
field id: 5 name: "input5" desc: "Input [I5]"
field id: 6 name: "input6" desc: "Input [I6]"
field id: 7 name: "input7" desc: "Input [I7]"
field id: 8 name: "input8" desc: "Input [I8]"
field id: 9 name: "input9" desc: "Input [I9]"
field id: 10 name: "input10" desc: "Input [I10]"
field id: 11 name: "input11" desc: "Input [I11]"
field id: 12 name: "input12" desc: "Input [I12]"
field id: 13 name: "input13" desc: "Input [I13]"
field id: 14 name: "input14" desc: "Input [I14]"
field id: 15 name: "input15" desc: "Input [I15]"
field id: 16 name: "input16" desc: "Input [I16]"
field id: 17 name: "input17" desc: "Input [I17]"
field id: 18 name: "input18" desc: "Input [I18]"
field id: 19 name: "input19" desc: "Input [I19]"
field id: 20 name: "input20" desc: "Input [I20]"
field id: 21 name: "input21" desc: "Input [I21]"
field id: 22 name: "input22" desc: "Input [I22]"
field id: 23 name: "input23" desc: "Input [I23]"
field id: 24 name: "input24" desc: "Input [I24]"
field id: 25 name: "input25" desc: "Input [I25]"
field id: 26 name: "input26" desc: "Input [I26]"
field id: 27 name: "input27" desc: "Input [I27]"
field id: 28 name: "input28" desc: "Input [I28]"
field id: 29 name: "input29" desc: "Input [I29]"
field id: 30 name: "input30" desc: "Input [I30]"
field id: 31 name: "input31" desc: "Input [I31]"
field id: 32 name: "input32" desc: "Input [I32]"
field id: 75 name: "rud" desc: "Rudder"
field id: 76 name: "ele" desc: "Elevator"
field id: 77 name: "thr" desc: "Throttle"
field id: 78 name: "ail" desc: "Aileron"
field id: 79 name: "s1" desc: "Potentiometer 1"
field id: 80 name: "s2" desc: "Potentiometer 2"
field id: 81 name: "s3" desc: "Potentiometer 3"
field id: 82 name: "ls" desc: "Left slider"
field id: 83 name: "rs" desc: "Right slider"
field id: 85 name: "cyc1" desc: "Cyclic 1"
field id: 86 name: "cyc2" desc: "Cyclic 2"
field id: 87 name: "cyc3" desc: "Cyclic 3"
field id: 88 name: "trim-rud" desc: "Rudder trim"
field id: 89 name: "trim-ele" desc: "Elevator trim"
field id: 90 name: "trim-thr" desc: "Throttle trim"
field id: 91 name: "trim-ail" desc: "Aileron trim"
field id: 92 name: "sa" desc: "Switch A"
field id: 93 name: "sb" desc: "Switch B"
field id: 94 name: "sc" desc: "Switch C"
field id: 95 name: "sd" desc: "Switch D"
field id: 96 name: "se" desc: "Switch E"
field id: 97 name: "sf" desc: "Switch F"
field id: 98 name: "sg" desc: "Switch G"
field id: 99 name: "sh" desc: "Switch H"
field id: 100 name: "ls1" desc: "Logical switch L1"
field id: 101 name: "ls2" desc: "Logical switch L2"
field id: 102 name: "ls3" desc: "Logical switch L3"
field id: 103 name: "ls4" desc: "Logical switch L4"
field id: 104 name: "ls5" desc: "Logical switch L5"
field id: 105 name: "ls6" desc: "Logical switch L6"
field id: 106 name: "ls7" desc: "Logical switch L7"
field id: 107 name: "ls8" desc: "Logical switch L8"
field id: 108 name: "ls9" desc: "Logical switch L9"
field id: 109 name: "ls10" desc: "Logical switch L10"
field id: 110 name: "ls11" desc: "Logical switch L11"
field id: 111 name: "ls12" desc: "Logical switch L12"
field id: 112 name: "ls13" desc: "Logical switch L13"
field id: 113 name: "ls14" desc: "Logical switch L14"
field id: 114 name: "ls15" desc: "Logical switch L15"
field id: 115 name: "ls16" desc: "Logical switch L16"
field id: 116 name: "ls17" desc: "Logical switch L17"
field id: 117 name: "ls18" desc: "Logical switch L18"
field id: 118 name: "ls19" desc: "Logical switch L19"
field id: 119 name: "ls20" desc: "Logical switch L20"
field id: 120 name: "ls21" desc: "Logical switch L21"
field id: 121 name: "ls22" desc: "Logical switch L22"
field id: 122 name: "ls23" desc: "Logical switch L23"
field id: 123 name: "ls24" desc: "Logical switch L24"
field id: 124 name: "ls25" desc: "Logical switch L25"
field id: 125 name: "ls26" desc: "Logical switch L26"
field id: 126 name: "ls27" desc: "Logical switch L27"
field id: 127 name: "ls28" desc: "Logical switch L28"
field id: 128 name: "ls29" desc: "Logical switch L29"
field id: 129 name: "ls30" desc: "Logical switch L30"
field id: 130 name: "ls31" desc: "Logical switch L31"
field id: 131 name: "ls32" desc: "Logical switch L32"
field id: 132 name: "trn1" desc: "Trainer input 1"
field id: 133 name: "trn2" desc: "Trainer input 2"
field id: 134 name: "trn3" desc: "Trainer input 3"
field id: 135 name: "trn4" desc: "Trainer input 4"
field id: 136 name: "trn5" desc: "Trainer input 5"
field id: 137 name: "trn6" desc: "Trainer input 6"
field id: 138 name: "trn7" desc: "Trainer input 7"
field id: 139 name: "trn8" desc: "Trainer input 8"
field id: 140 name: "trn9" desc: "Trainer input 9"
field id: 141 name: "trn10" desc: "Trainer input 10"
field id: 142 name: "trn11" desc: "Trainer input 11"
field id: 143 name: "trn12" desc: "Trainer input 12"
field id: 144 name: "trn13" desc: "Trainer input 13"
field id: 145 name: "trn14" desc: "Trainer input 14"
field id: 146 name: "trn15" desc: "Trainer input 15"
field id: 147 name: "trn16" desc: "Trainer input 16"
field id: 148 name: "ch1" desc: "Channel CH1"
field id: 149 name: "ch2" desc: "Channel CH2"
field id: 150 name: "ch3" desc: "Channel CH3"
field id: 151 name: "ch4" desc: "Channel CH4"
field id: 152 name: "ch5" desc: "Channel CH5"
field id: 153 name: "ch6" desc: "Channel CH6"
field id: 154 name: "ch7" desc: "Channel CH7"
field id: 155 name: "ch8" desc: "Channel CH8"
field id: 156 name: "ch9" desc: "Channel CH9"
field id: 157 name: "ch10" desc: "Channel CH10"
field id: 158 name: "ch11" desc: "Channel CH11"
field id: 159 name: "ch12" desc: "Channel CH12"
field id: 160 name: "ch13" desc: "Channel CH13"
field id: 161 name: "ch14" desc: "Channel CH14"
field id: 162 name: "ch15" desc: "Channel CH15"
field id: 163 name: "ch16" desc: "Channel CH16"
field id: 164 name: "ch17" desc: "Channel CH17"
field id: 165 name: "ch18" desc: "Channel CH18"
field id: 166 name: "ch19" desc: "Channel CH19"
field id: 167 name: "ch20" desc: "Channel CH20"
field id: 168 name: "ch21" desc: "Channel CH21"
field id: 169 name: "ch22" desc: "Channel CH22"
field id: 170 name: "ch23" desc: "Channel CH23"
field id: 171 name: "ch24" desc: "Channel CH24"
field id: 172 name: "ch25" desc: "Channel CH25"
field id: 173 name: "ch26" desc: "Channel CH26"
field id: 174 name: "ch27" desc: "Channel CH27"
field id: 175 name: "ch28" desc: "Channel CH28"
field id: 176 name: "ch29" desc: "Channel CH29"
field id: 177 name: "ch30" desc: "Channel CH30"
field id: 178 name: "ch31" desc: "Channel CH31"
field id: 179 name: "ch32" desc: "Channel CH32"
field id: 180 name: "gvar1" desc: "Global variable 1"
field id: 181 name: "gvar2" desc: "Global variable 2"
field id: 182 name: "gvar3" desc: "Global variable 3"
field id: 183 name: "gvar4" desc: "Global variable 4"
field id: 184 name: "gvar5" desc: "Global variable 5"
field id: 185 name: "gvar6" desc: "Global variable 6"
field id: 186 name: "gvar7" desc: "Global variable 7"
field id: 187 name: "gvar8" desc: "Global variable 8"
field id: 188 name: "gvar9" desc: "Global variable 9"
field id: 189 name: "tx-voltage" desc: "Transmitter battery voltage [volts]"
field id: 190 name: "clock" desc: "RTC clock [minutes from midnight]"
field id: 196 name: "timer1" desc: "Timer 1 value [seconds]"
field id: 197 name: "timer2" desc: "Timer 2 value [seconds]"
field id: 198 name: "swr" desc: "Transmitter antenna quality [less is better]"
field id: 200 name: "rssi" desc: "RSSI [more is better]"
field id: 202 name: "a1" desc: "A1 analogue value [units as configured]"
field id: 203 name: "a2" desc: "A2 analogue value [units as configured]"
field id: 204 name: "a3" desc: "A3 analogue value [units as configured]"
field id: 205 name: "a4" desc: "A4 analogue value [units as configured]"
field id: 206 name: "altitude" desc: "Variometer altitude [meters]"
field id: 207 name: "rpm" desc: "Rotational speed [revolutions per minute]"
field id: 208 name: "fuel" desc: "Fuel level [???]"
field id: 209 name: "temp1" desc: "Temperature 1 [degrees celsius]"
field id: 210 name: "temp2" desc: "Temperature 2 [degrees celsius]"
field id: 211 name: "gps-speed" desc: "GPS speed [???]"
field id: 212 name: "distance" desc: "GPS distance [meters]"
field id: 213 name: "gps-altitude" desc: "GPS altitude [meters]"
field id: 214 name: "cell-min" desc: "LiPo sensor - lowest current cell voltage [volts]"
field id: 215 name: "cell-sum" desc: "LiPo sensor - current summ of all cell voltages [volts]"
field id: 216 name: "vfas" desc: "Current sensor - voltage [volts]"
field id: 217 name: "currentent" desc: "Current sensor - current [ampers]"
field id: 218 name: "consumption" desc: "Current sensor - consumption [mili amper hours]"
field id: 219 name: "power" desc: "Current sensor - power [wats]"
field id: 220 name: "accx" desc: "G sensor - acceleration in X axis [g]"
field id: 221 name: "accy" desc: "G sensor - acceleration in Y axis [g]"
field id: 222 name: "accz" desc: "G sensor - acceleration in Z axis [g]"
field id: 223 name: "heading" desc: "GPS heading [degrees]"
field id: 224 name: "vario" desc: "Variometer vertical speed [m/s]"
field id: 225 name: "air-speed" desc: "Air speed [knots]"
field id: 226 name: "dte" desc: "Total energy [???]"
field id: 232 name: "a1-min" desc: "A1 analogue value minimum [units as configured]"
field id: 233 name: "a2-min" desc: "A2 analogue value minimum [units as configured]"
field id: 234 name: "a3-min" desc: "A3 analogue value minimum [units as configured]"
field id: 235 name: "a4-min" desc: "A4 analogue value minimum [units as configured]"
field id: 236 name: "altitude-min" desc: "Lowest altitude [meters]"
field id: 237 name: "altitude-max" desc: "Highest altitude [meters]"
field id: 238 name: "rpm-max" desc: "Highest rotational speed [revolutions per minute] [meters]"
field id: 239 name: "temp1-max" desc: "Highest temperature 1 [degrees celsius]"
field id: 240 name: "temp2-max" desc: "Highest temperature 2 [degrees celsius]"
field id: 241 name: "gps-speed-max" desc: "Highest GPS speed [???]"
field id: 242 name: "distance-max" desc: "Biggest GPS distance [meters]"
field id: 243 name: "air-speed-max" desc: "Highest air speed [knots]"
field id: 244 name: "cell-min-min" desc: "LiPo sensor - all time lowest cell voltage [volts]"
field id: 245 name: "cell-sum-min" desc: "LiPo sensor - all time lowest summ of all cell voltages [volts]"
field id: 246 name: "vfas-min" desc: "Current sensor - lowest voltage [volts]"
field id: 247 name: "currentent-max" desc: "Current sensor - highest current [ampers]"
field id: 248 name: "power-max" desc: "Current sensor - highest power [wats]"
Invité- Invité
Re: appeler les données de télémetrie
je vous présente mes désirs
mais pour l'instant ca ne marche pas comme je veux voir ca ne marche pas du tout
@ntoine
mais pour l'instant ca ne marche pas comme je veux voir ca ne marche pas du tout
@ntoine
Invité- Invité
Re: appeler les données de télémetrie
Si jamais, il y a pas mal d'explication ici : https://docs.google.com/document/d/1ILh9lSW4d05qJD2rSKxep0WnJUfNCcAPCafKZeESweE/edit
Dernière édition par Sacre100 le Ven 25 Juil 2014 - 20:41, édité 1 fois
Sacre100- Messages : 1889
Date d'inscription : 30/11/2013
Age : 66
Localisation : Blonay - Suisse
Re: appeler les données de télémetrie
pour ecrire A2
lcd.drawText(100, 0, getValue(203), XXLSIZE)
x, y, valeur de A2, taille de la font XXL
Pour les valeur avec barre graph
local percent1 = (getValue(203) * 100) / 12.9
lcd.drawNumber(145, 45, percent1, LEFT+MIDSIZE)
lcd.drawText(lcd.getLastPos(), 45, "%", MIDSIZE)
lcd.drawGauge(110, 42, 88, 18, percent1, 100)
percent1 calcul
drawNumber affiche la valeur au milieu du barre graph
drawtext ajoute %
drawGauge dessine le barre graph x,y, taille x, taille y, valeur
pour CH3 je pense qu'un drawGauge avec les bonnes valeurs devrait permettre de visualiser la position
tu peut t'inspirer du fichier que j'ai mis dans l'autre sujet
lcd.drawText(100, 0, getValue(203), XXLSIZE)
x, y, valeur de A2, taille de la font XXL
Pour les valeur avec barre graph
local percent1 = (getValue(203) * 100) / 12.9
lcd.drawNumber(145, 45, percent1, LEFT+MIDSIZE)
lcd.drawText(lcd.getLastPos(), 45, "%", MIDSIZE)
lcd.drawGauge(110, 42, 88, 18, percent1, 100)
percent1 calcul
drawNumber affiche la valeur au milieu du barre graph
drawtext ajoute %
drawGauge dessine le barre graph x,y, taille x, taille y, valeur
pour CH3 je pense qu'un drawGauge avec les bonnes valeurs devrait permettre de visualiser la position
tu peut t'inspirer du fichier que j'ai mis dans l'autre sujet
Invité- Invité
Re: appeler les données de télémetrie
ca y est suis arrivé a faire mon petit script
mes valeurs de tension sont en dur les formules pour les calculs de pourcentage
visiblement pas de possibilité de faire de gauge verticale pour le moment donc l'affichage de ch3 viendra plus tard
@ntoine
mes valeurs de tension sont en dur les formules pour les calculs de pourcentage
visiblement pas de possibilité de faire de gauge verticale pour le moment donc l'affichage de ch3 viendra plus tard
@ntoine
- Fichiers joints
Invité- Invité
Re: appeler les données de télémetrie
Bonsoir @ntoine
Je pense que cela est possible d'avoir une gauge verticale, voici les caractéristiques de la fonction
lcd.drawGauge(x, y, width, height, value, max)
x, y point de départ
width largeur
height hauteur
Tu devrais commenter ton code car aujourdhui tu sais ce que tu a fait, mais plus tard tu aura oublié, changé ta facon de coder, et tu risque de galérer pour comprendre ce que tu a fait, et puis cela aidera ceux qui son moins avancé en Prog
Je pense que cela est possible d'avoir une gauge verticale, voici les caractéristiques de la fonction
lcd.drawGauge(x, y, width, height, value, max)
x, y point de départ
width largeur
height hauteur
Tu devrais commenter ton code car aujourdhui tu sais ce que tu a fait, mais plus tard tu aura oublié, changé ta facon de coder, et tu risque de galérer pour comprendre ce que tu a fait, et puis cela aidera ceux qui son moins avancé en Prog
blonblon- Messages : 214
Date d'inscription : 25/03/2014
Age : 73
Localisation : pres d'Uzes (Gard)
Re: appeler les données de télémetrie
blonblon a écrit:
Je pense que cela est possible d'avoir une gauge verticale, voici les caractéristiques de la fonction
lcd.drawGauge(x, y, width, height, value, max)
la descrition de la fonction présente sur GitHub
précise Draws a horisontal gauge (bar) from top left corner (x,y) of specified width and height
blonblon a écrit:Tu devrais commenter ton code car aujourdhui tu sais ce que tu a fait, mais plus tard tu aura oublié, changé ta facon de coder, et tu risque de galérer pour comprendre ce que tu a fait, et puis cela aidera ceux qui son moins avancé en Prog
j'attends de finaliser car j'ai pas encore tout ce que je veux car pour l'instant je retouche trop
j'ai allégé le code en supprimant les calculs des variables percent qui sont directement dans la Gauge vu que l'on peut donné la valeur max à cette fonction
voici ma nouvelle version
- Fichiers joints
Invité- Invité
Re: appeler les données de télémetrie
correction pour plus de finesse dans la gauge de tension du Tx
mes scripts sont fait pour des batteries TX lifepo4 3S A1 lipo 2S
@ntoine
mes scripts sont fait pour des batteries TX lifepo4 3S A1 lipo 2S
@ntoine
- Fichiers joints
Invité- Invité
Re: appeler les données de télémetrie
suis arrivé a faire une gauge avec un curseur et non un remplissage en trichant un peu en dessinant un rectangle cadre puis deux gauges l'une sur l'autre avec un léger décalage de la valeur
me reste plus qu'a la basculer verticalement mais ca risque d'être plus compliqué
@ntoine
me reste plus qu'a la basculer verticalement mais ca risque d'être plus compliqué
@ntoine
- Fichiers joints
Invité- Invité
Re: appeler les données de télémetrie
blonblon a écrit:Bonsoir @ntoine
Tu devrais commenter ton code car aujourdhui tu sais ce que tu a fait, mais plus tard tu aura oublié, changé ta facon de coder, et tu risque de galérer pour comprendre ce que tu a fait, et puis cela aidera ceux qui son moins avancé en Prog
voila le code commenté
- Code:
local function run(event)
lcd.drawText(180, 10, getValue(202), DBLSIZE) -- affichage valeur de A1
lcd.drawChannel(1, 1, 189, LEFT+SMLSIZE) -- affichage valeur de tx
lcd.drawChannel(1, 18, 200, LEFT+SMLSIZE) -- affichage valeur de rssi
lcd.drawGauge(27, 1, 150, 14, ((getValue(189)-7.5)*100), 270) -- représentation du voltage tx sur échelle horizontale pour lifepo4 3S multiplication par 100 pour meilleur affichage
lcd.drawText(95, 2, "Tx", MIDSIZE)
lcd.drawGauge(27, 18, 150, 14, getValue(200), 100) -- représentation du rssi
lcd.drawText(85, 19, "RSSI", MIDSIZE)
lcd.drawGauge(5, 45, 202, 18, ((getValue(202)-6)*100), 240) -- représentation du voltage A1 sur échelle horizontale pour lipo 2S multiplication par 100 pour meilleur affichage
lcd.drawText(80, 48, "BATEAU", MIDSIZE)
lcd.drawRectangle(27, 35, 182, 5, ROUND) -- cadre pour curseur ultérieur
lcd.drawGauge(27, 35, 180, 5, getValue(77)+1024, 2048) -- représentation de la position du manche throttle
lcd.drawGauge(27, 35, 180, 5, getValue(77)+1014, 2048) -- passage de la représentation en curseur
lcd.drawText(1, 33, "Voile", SMLSIZE)
end
return { run=run }
@ntoine
Invité- Invité
Re: appeler les données de télémetrie
Voila une nouvelle version avec comme correction
-les calculs de pourcentage A1 calculé sur la capacité restante pas sur la Tension
-remise en page pour agrandissement des valeurs et affichage des pourcentages en valeur sur la barre graphique
-commentaire sur l'ensemble du code
@ntoine
-les calculs de pourcentage A1 calculé sur la capacité restante pas sur la Tension
-remise en page pour agrandissement des valeurs et affichage des pourcentages en valeur sur la barre graphique
-commentaire sur l'ensemble du code
@ntoine
- Fichiers joints
Invité- Invité
Re: appeler les données de télémetrie
jpg63 a écrit:Voici toute la liste des informations qu'il est possible de récupérer avec la commande getValue
il faut passer l'id à la fonction, le nom du champ ne marche pas pour tout
List of all fileds for OpenTX version 2.0.6:
field id: 1 name: "input1" desc: "Input [I1]"
field id: 2 name: "input2" desc: "Input [I2]"
field id: 3 name: "input3" desc: "Input [I3]"
field id: 4 name: "input4" desc: "Input [I4]"
field id: 5 name: "input5" desc: "Input [I5]"
..........................................
field id: 244 name: "cell-min-min" desc: "LiPo sensor - all time lowest cell voltage [volts]"
field id: 245 name: "cell-sum-min" desc: "LiPo sensor - all time lowest summ of all cell voltages [volts]"
field id: 246 name: "vfas-min" desc: "Current sensor - lowest voltage [volts]"
field id: 247 name: "currentent-max" desc: "Current sensor - highest current [ampers]"
field id: 248 name: "power-max" desc: "Current sensor - highest power [wats]"
Attention cette liste peut changer à tous moment voir le lien sur RCG
http://www.rcgroups.com/forums/showpost.php?p=28897780&postcount=298
Armaguedon972- Messages : 571
Date d'inscription : 25/08/2013
Age : 55
Localisation : Québec Canada
Re: appeler les données de télémetrie
Bonjour
J'ai trouvé ceci pour simuler une Gauge Verticale
J'ai trouvé ceci pour simuler une Gauge Verticale
- Fichiers joints
blonblon- Messages : 214
Date d'inscription : 25/03/2014
Age : 73
Localisation : pres d'Uzes (Gard)
Re: appeler les données de télémetrie
Je suis en vacances sans Pc fixe juste l'iPhone et le portable pour regarder le forum je regarderai ça en rentrant à moins que la météo continue je prendrai le temps d'installer companion dur le portable vu que j'ai une régate fin août j'ai le bateau et la taranis je vous tiens au jus
@ntoine
@ntoine
Invité- Invité
Re: appeler les données de télémetrie
Bon une petite insomnie me suis coller devant le Pc ça marche reste les positionnements à affiner et à commenter le code en anglais cette fois
Sinon suis tombé sur un site pas mal genre base de donnée de model icône script ça vaudrait le coup de la remplir un peu
http://rcsettings.com
@ntoine
Sinon suis tombé sur un site pas mal genre base de donnée de model icône script ça vaudrait le coup de la remplir un peu
http://rcsettings.com
@ntoine
Invité- Invité
Re: appeler les données de télémetrie
viens de mettre la dernière version de mon script lua en ligne
http://rcsettings.com/index.php/viewdownload/13-lua-scripts/139-telemetry-scrren-for-sail-boat
http://rcsettings.com/index.php/viewdownload/13-lua-scripts/139-telemetry-scrren-for-sail-boat
Invité- Invité
Sujets similaires
» Données de télémétrie erronées
» X9D+ 2019 . Absence de donnees télémétrie
» Perte de données télémétrie entre taranis 9d et recepteur g rsx8r
» Nouveau Flywoo hexplorer BNF ! Si R9mm en Fport Impossible d'avoir la télémétrie sur ma Horus mais télémétrie ok dans les lunettes HD
» GPS et données
» X9D+ 2019 . Absence de donnees télémétrie
» Perte de données télémétrie entre taranis 9d et recepteur g rsx8r
» Nouveau Flywoo hexplorer BNF ! Si R9mm en Fport Impossible d'avoir la télémétrie sur ma Horus mais télémétrie ok dans les lunettes HD
» GPS et données
Page 1 sur 1
Permission de ce forum:
Vous ne pouvez pas répondre aux sujets dans ce forum
|
|