- Posts: 4403
Support for walkera telemetry.
- PhracturedBlue
-
- Offline
Less
More
16 Oct 2012 20:43 #2293
by PhracturedBlue
Replied by PhracturedBlue on topic Support for walkera telemetry.
Here is a test build with GPS support
- vlad_vy
-
- Offline
Less
More
- Posts: 3333
17 Oct 2012 04:01 #2296
by vlad_vy
Replied by vlad_vy on topic Support for walkera telemetry.
Ok, I will test it this evening. I havn't idea what is MMNE for except it can be - Mean Measured Noise Estimate for altitude.
- vlad_vy
-
- Offline
Less
More
- Posts: 3333
17 Oct 2012 14:25 - 17 Oct 2012 14:54 #2304
by vlad_vy
Replied by vlad_vy on topic Support for walkera telemetry.
Volt1: 5.3V
Real Voltage = 5.39V
Volt2: 3.9V (7.8V)
Real Voltage = 3.92V (7.82V)
Volt3: 3.8V (7.8V)
Real Voltage = 3.92V (7.82V)
Temp1: 24C or 33C (my fingers temp)
Temp2: 24C or 33C
Temp3: 24C or 33C
Temp4: 24C or 33C
RPM1: 6120/6240 (optical tachometer 6150rpm)
RPM2: 6480/6600 (optical tachometer 6300rpm)
RPM3: 0 ??? (only two sensors)
Long: 030 20 50.166
Lat: 059 54 46.056
Alt: 51.400m
Speed: 0.240m/s
14:00:13 2012-10-17
1) Why Volt2: 3.9V and Volt2: 3.8V are different? Real voltage is the same.
2) Sensor reading at main page doesn't changing. It changed only after visit Telemetry page and return to main page.
3) After switch off telemetry all values remains unchanged (last values).
4) Temp readings with value 'ff' will be better to replace with '00' (temp sensor disconnected) and display '0'.
Real Voltage = 5.39V
Volt2: 3.9V (7.8V)
Real Voltage = 3.92V (7.82V)
Volt3: 3.8V (7.8V)
Real Voltage = 3.92V (7.82V)
Temp1: 24C or 33C (my fingers temp)
Temp2: 24C or 33C
Temp3: 24C or 33C
Temp4: 24C or 33C
RPM1: 6120/6240 (optical tachometer 6150rpm)
RPM2: 6480/6600 (optical tachometer 6300rpm)
RPM3: 0 ??? (only two sensors)
Long: 030 20 50.166
Lat: 059 54 46.056
Alt: 51.400m
Speed: 0.240m/s
14:00:13 2012-10-17
1) Why Volt2: 3.9V and Volt2: 3.8V are different? Real voltage is the same.
2) Sensor reading at main page doesn't changing. It changed only after visit Telemetry page and return to main page.
3) After switch off telemetry all values remains unchanged (last values).
4) Temp readings with value 'ff' will be better to replace with '00' (temp sensor disconnected) and display '0'.
Last edit: 17 Oct 2012 14:54 by vlad_vy.
- FDR
-
- Offline
17 Oct 2012 14:52 #2305
by FDR
The voltage inputs are probably heavily divided to meet the input voltage specification of the ADC, and the resistors are not precise enough, I guess...
I would left them on the main page too, within a red box.
Replied by FDR on topic Support for walkera telemetry.
I think that is simply caused by the differences of the inputs.vlad_vy wrote: 1) Why Volt2: 3.9V and Volt2: 3.8V are different? Real voltage is the same.
The voltage inputs are probably heavily divided to meet the input voltage specification of the ADC, and the resistors are not precise enough, I guess...
Yep, I've already mentioned that...2) Sensor reading at main page doesn't changing. It changed only after visit Telemetry page and return to main page.
Wrote about that too, but if you think about it, those values can be useful, but the GUI should sign, that they are obsolete, for example with a red background, like the run-down timer...3) After switch off telemetry all values remains unchanged (last values).
I would left them on the main page too, within a red box.
- FDR
-
- Offline
17 Oct 2012 14:54 #2306
by FDR
Replied by FDR on topic Support for walkera telemetry.
...and one more thing about the main page telemetry boxes: I would jump to the telemetry page on click, or at least on a long click.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4403
17 Oct 2012 15:09 #2310
by PhracturedBlue
Replied by PhracturedBlue on topic Support for walkera telemetry.
The telemetry stuff still has a long way to go.
I still need to:
a) add a way to configure display (ft vs m, C vs F)
b) Configure limits for the alarm (for both critical values)
c) detect LOS (and alarm on it)
d) Quick access to the telemetry data
e) Enable a logging capability to track telemetry (and probably source/channel info) to save status to a log file to be viewed on the PC later
But I'm glad that we've got the protocol now.
I'll continue working on trying to finish the capabilities. I'm certainly interested in any insight as to the right way to interact with the telemetry. is GPS of much value without logging? is there any reason to show it on the main page? or is it more of a 'I crashed, where'd my model go' type of thing?
I still need to:
a) add a way to configure display (ft vs m, C vs F)
b) Configure limits for the alarm (for both critical values)
c) detect LOS (and alarm on it)
d) Quick access to the telemetry data
e) Enable a logging capability to track telemetry (and probably source/channel info) to save status to a log file to be viewed on the PC later
But I'm glad that we've got the protocol now.
I'll continue working on trying to finish the capabilities. I'm certainly interested in any insight as to the right way to interact with the telemetry. is GPS of much value without logging? is there any reason to show it on the main page? or is it more of a 'I crashed, where'd my model go' type of thing?
- Eriskio
-
- Offline
Less
More
- Posts: 19
17 Oct 2012 15:32 - 17 Oct 2012 15:38 #2311
by Eriskio
Replied by Eriskio on topic Support for walkera telemetry.
Well, with helis GPS has no significance at all, and used telemetry data could be restricted to Tension/Voltage of LiPo batteries (as I currently do with external Quanum unit. But the Walkera telemetry is not able to report single cell voltage, so Quanum solution is way better for me).
But some kind of "long flying"/"gliders addicted" friends told me these concept about the use of telemetry on planes:
1) last GPS position could be useful to be shown on the mainscreen in case of problem (you can check instantly if the model is gone out of sight if it is always moving, in which direction). In this case it can be useful to "hold" the last value received on screen (saved also on flash during shutdown?) so that if I turn on the radio again after a crash (and after having walked toward the supposed impact zone), I can instantly get model position (wrech maybe! and google maps and GPS phone needs).
2) All telemetry data should be logged for later analysis. It is really useful to track down not only absolute position but voltage, current and temperature (and any other data that telemetry transmit) to be able to analyze flight in deep (problem prevention / pilot skill improvement). Otherwise all these data are not really usable in real time (you have to pilot your model at first) except for specific (audible) alarm purposes (like a sound on low voltage, motor/ESC temperature too high, etc).
But less than 4 mega of free space on flash, can be enough to store all them?
But some kind of "long flying"/"gliders addicted" friends told me these concept about the use of telemetry on planes:
1) last GPS position could be useful to be shown on the mainscreen in case of problem (you can check instantly if the model is gone out of sight if it is always moving, in which direction). In this case it can be useful to "hold" the last value received on screen (saved also on flash during shutdown?) so that if I turn on the radio again after a crash (and after having walked toward the supposed impact zone), I can instantly get model position (wrech maybe! and google maps and GPS phone needs).
2) All telemetry data should be logged for later analysis. It is really useful to track down not only absolute position but voltage, current and temperature (and any other data that telemetry transmit) to be able to analyze flight in deep (problem prevention / pilot skill improvement). Otherwise all these data are not really usable in real time (you have to pilot your model at first) except for specific (audible) alarm purposes (like a sound on low voltage, motor/ESC temperature too high, etc).
But less than 4 mega of free space on flash, can be enough to store all them?
Last edit: 17 Oct 2012 15:38 by Eriskio.
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
17 Oct 2012 17:10 - 17 Oct 2012 17:21 #2313
by Andrey
V1,V2,V3, T1,T2,T3,T4, RPM2 Long, Lat, Alt, Time - all OK
Long, Lat, Alt +- 10...20м
Speed
Alt (Real value = Alt - Starting Alt)
RPM
DateTime (Value + GMT)
and alarm by V1,V2,V3, T1,T2,T3,T4
P.S. I would also like to keep the total flight time model (not reset by pushing the "EXT" and be able to enter the starting value)
Replied by Andrey on topic Support for walkera telemetry.
I'am tested:PhracturedBlue wrote: Here is a test build with GPS support
V1,V2,V3, T1,T2,T3,T4, RPM2 Long, Lat, Alt, Time - all OK
Long, Lat, Alt +- 10...20м
I would like to see on the main page:Is there any reason to show it on the main page?
Speed
Alt (Real value = Alt - Starting Alt)
RPM
DateTime (Value + GMT)
and alarm by V1,V2,V3, T1,T2,T3,T4
P.S. I would also like to keep the total flight time model (not reset by pushing the "EXT" and be able to enter the starting value)
Last edit: 17 Oct 2012 17:21 by Andrey.
- vlad_vy
-
- Offline
Less
More
- Posts: 3333
17 Oct 2012 17:49 - 17 Oct 2012 17:51 #2314
by vlad_vy
Replied by vlad_vy on topic Support for walkera telemetry.
+1 for 'Integrated Timer'
Integrated Timer (INTEGRATE TIMER) HH:MM (always shown at main page)
The Integrated Time is recorded individually for each model. When this time exceeds 100 hours, the time will return to zero. This can be used as a reference for maintenance of each aircraft. This time can also be reset to zero - set the cursor on the Integrated timer at Timer page and press the dial to reset.
Andrey, why you need set start time for Integrated Timer?
Integrated Timer (INTEGRATE TIMER) HH:MM (always shown at main page)
The Integrated Time is recorded individually for each model. When this time exceeds 100 hours, the time will return to zero. This can be used as a reference for maintenance of each aircraft. This time can also be reset to zero - set the cursor on the Integrated timer at Timer page and press the dial to reset.
Andrey, why you need set start time for Integrated Timer?
Last edit: 17 Oct 2012 17:51 by vlad_vy.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4403
17 Oct 2012 17:58 #2315
by PhracturedBlue
Replied by PhracturedBlue on topic Support for walkera telemetry.
your definition of 'integrated time' has no relevance to telemetry as far as I can tell.
I can accurately enough keep track of total time without any of this knowledge, though I'm not sure how you can accurately figure out maintenance intervals from this. Or do you intend to only count time when telemetry is being received? or maybe throttle is active?
Anyhow, it should be clear by now I don't have sufficient info about the needs to implement such a thing at this point.
If you ave a request, file an enhancement request on bitbucket with as much info as you possibly can put into it.
I can accurately enough keep track of total time without any of this knowledge, though I'm not sure how you can accurately figure out maintenance intervals from this. Or do you intend to only count time when telemetry is being received? or maybe throttle is active?
Anyhow, it should be clear by now I don't have sufficient info about the needs to implement such a thing at this point.
If you ave a request, file an enhancement request on bitbucket with as much info as you possibly can put into it.
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
17 Oct 2012 18:18 - 17 Oct 2012 18:21 #2316
by Andrey
Replied by Andrey on topic Support for walkera telemetry.
It has no relation to the telemetry, the total flight time must be considered on a timer. Summirvat time when the throttle channel is not 0 (preferably able to enter the throttle channel number manually). Opportunity to enter an initial value just will not be superfluous (replacement firmware / transmitter, etc.) do not need to write a user interface for this - just to be able to change the value in modelX.ini
Last edit: 17 Oct 2012 18:21 by Andrey.
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
17 Oct 2012 18:40 - 17 Oct 2012 18:42 #2317
by Andrey
Replied by Andrey on topic Support for walkera telemetry.
Exampl code 
After load modelX.ini
if TimerX.Type = "stopwatch" then begin
Load TotalTime from modelX.ini
end
Before power off or before change modelX.ini
if TimerX.Type = "stopwatch" then begin
Save TotalTime to old modelX.ini
end
After load modelX.ini
if TimerX.Type = "stopwatch" then begin
Load TotalTime from modelX.ini
end
Before power off or before change modelX.ini
if TimerX.Type = "stopwatch" then begin
Save TotalTime to old modelX.ini
end
Last edit: 17 Oct 2012 18:42 by Andrey.
- FDR
-
- Offline
17 Oct 2012 18:59 #2319
by FDR
Replied by FDR on topic Support for walkera telemetry.
The problem of the total timer is when it should run.
One option is to cummulate a total timer for each timer (whether they are stopwatch or countdown types) when they are running. They probably are configured to run while throttle is on.
Other option would be a third timer type: the "cummulated", which could be tied to a switch too, and would have a reset button on the config page.
But neither options would know, if there is a heli plugged in: that's where the telemetry can come handy! If you configure it's switch to a RPM, then you can count the real spinning time. Of course it supposes, that a telemetry data can be used as an input...
One option is to cummulate a total timer for each timer (whether they are stopwatch or countdown types) when they are running. They probably are configured to run while throttle is on.
Other option would be a third timer type: the "cummulated", which could be tied to a switch too, and would have a reset button on the config page.
But neither options would know, if there is a heli plugged in: that's where the telemetry can come handy! If you configure it's switch to a RPM, then you can count the real spinning time. Of course it supposes, that a telemetry data can be used as an input...
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
17 Oct 2012 19:11 - 17 Oct 2012 19:21 #2320
by Andrey
Replied by Andrey on topic Support for walkera telemetry.
It is not necessary to bind this option to telemetry, This cummulated timer is interesting for all models, and telemetry not installed on all.
That would avoid the problem of processing power down enough to write a new value at each stop cummulated timer
if "cummulated timer" stop then begin
save new value to modelX.ini
end
Only is THR channel not 0The problem of the total timer is when it should run.
That would avoid the problem of processing power down enough to write a new value at each stop cummulated timer
if "cummulated timer" stop then begin
save new value to modelX.ini
end
Last edit: 17 Oct 2012 19:21 by Andrey.
- FDR
-
- Offline
17 Oct 2012 19:43 - 17 Oct 2012 19:44 #2321
by FDR
Yep, but what if I'm just trying my settings on the monitor page without actually flying the model?
Telemetry data as a switch would be only an option...
Replied by FDR on topic Support for walkera telemetry.
Andrey wrote:
Only is THR channel not 0The problem of the total timer is when it should run.
Yep, but what if I'm just trying my settings on the monitor page without actually flying the model?
Telemetry data as a switch would be only an option...
Last edit: 17 Oct 2012 19:44 by FDR.
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
17 Oct 2012 20:39 #2322
by Andrey

I offered the most simple implementation
Replied by Andrey on topic Support for walkera telemetry.
This is "the best"FDR wrote:
Andrey wrote:
Only is THR channel not 0The problem of the total timer is when it should run.
Yep, but what if I'm just trying my settings on the monitor page without actually flying the model?
Telemetry data as a switch would be only an option...
I offered the most simple implementation
- vlad_vy
-
- Offline
Less
More
- Posts: 3333
18 Oct 2012 04:17 - 18 Oct 2012 04:23 #2323
by vlad_vy
Replied by vlad_vy on topic Support for walkera telemetry.
Sorry for my offtopic.
1) At any case telemetry info almost unusable in time of flight.
2) Possibility to display selected sensors at 1-2 boxes at Main Page is quite enought.
3) Will be usefull to have telemetry alarms.
4) Will be nice to have logging capability.
5) Will be nice to have quick access to full telemetry information. For example, by short pressing 'Ent' button for switching between Main Page - Telemetry1 (Volt1,2,3, Temp1,2,3,4, RPM1,2) - Telemetry2(GPS Info), telemetry pages with big fonts for better readability.
1) At any case telemetry info almost unusable in time of flight.
2) Possibility to display selected sensors at 1-2 boxes at Main Page is quite enought.
3) Will be usefull to have telemetry alarms.
4) Will be nice to have logging capability.
5) Will be nice to have quick access to full telemetry information. For example, by short pressing 'Ent' button for switching between Main Page - Telemetry1 (Volt1,2,3, Temp1,2,3,4, RPM1,2) - Telemetry2(GPS Info), telemetry pages with big fonts for better readability.
Last edit: 18 Oct 2012 04:23 by vlad_vy.
- Andrey
-
Topic Author
- Offline
Less
More
- Posts: 11
22 Oct 2012 17:29 - 22 Oct 2012 17:30 #2380
by Andrey
Replied by Andrey on topic Support for walkera telemetry.
Total flight time on this firmware for more than 2 hours. All OK.PhracturedBlue wrote: Here is a test build with GPS support
Last edit: 22 Oct 2012 17:30 by Andrey.
- dobosatti
-
- Offline
Less
More
- Posts: 16
18 Jul 2013 18:48 - 22 Jul 2013 06:28 #12323
by dobosatti
Replied by dobosatti on topic Support for walkera telemetry.
I bought a devo telemetry module and installed it in a Walkera V450D03 heli. Temperature sensors and voltage measurement is perfect. It does not measure the RPM. When I turn on the radio and bind, temperature, and voltage windows are white, but the RPM window is red. When you go to the telemetry section, and return to the main window, I have a white window at RPM, but the rotation will not be measured. What is the problem, there may be some trick? I tried both module plug connectors with the sensor, but nothing. Even the telemetry window does not show anything, but they are both white box and reads zero.
This module is included:
walkerahelicoptersupply.com/products/ufo...-telemetrywk-ctl01-d
And this is the RPM sensor:
www.ebay.com/itm/RPM-Sensor-for-Telemetr...&hash=item3a829e5d96
This module is included:
walkerahelicoptersupply.com/products/ufo...-telemetrywk-ctl01-d
And this is the RPM sensor:
www.ebay.com/itm/RPM-Sensor-for-Telemetr...&hash=item3a829e5d96
Last edit: 22 Jul 2013 06:28 by FDR. Reason: language
- FDR
-
- Offline
22 Jul 2013 06:29 #12413
by FDR
Replied by FDR on topic Support for walkera telemetry.
Is there anybody with a working devo RPM sensor?
Time to create page: 0.289 seconds
-
Home
-
Forum
-
Development
-
Protocol Development
- Support for walkera telemetry.