- Posts: 4402
Support for walkera telemetry.
- PhracturedBlue
- Offline
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
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'.
Please Log in or Create an account to join the conversation.
- FDR
- Offline
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.
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
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?
Please Log in or Create an account to join the conversation.
- Eriskio
- Offline
- Posts: 19
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?
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
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)
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
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?
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
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.
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
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
Please Log in or Create an account to join the conversation.
- FDR
- Offline
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...
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
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
Please Log in or Create an account to join the conversation.
- FDR
- Offline
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...
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
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
Please Log in or Create an account to join the conversation.
- vlad_vy
- Offline
- Posts: 3333
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.
Please Log in or Create an account to join the conversation.
- Andrey
- Topic Author
- Offline
- Posts: 11
Total flight time on this firmware for more than 2 hours. All OK.PhracturedBlue wrote: Here is a test build with GPS support
Please Log in or Create an account to join the conversation.
- dobosatti
- Offline
- Posts: 16
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
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- Support for walkera telemetry.