pascallanger
13b8475c54
Add FY805 in Multi.txt for ersky9x
2016-12-09 16:51:55 +01:00
pascallanger
d3d52b44ee
Revert "Bayang: change A1 and A2 back to maximum resolution"
...
This reverts commit d2886432b7becdb5bfe66692b396f9c6c61d7de6.
2016-12-09 16:51:17 +01:00
pascallanger
d2886432b7
Bayang: change A1 and A2 back to maximum resolution
2016-12-09 16:50:56 +01:00
pascallanger
3904c36a6e
New MT99xx subprotocol FY805
...
Protocol: MT99xx (number 17)
Subprotocol: FY805 (number 4)
Supports headless and flip. For flip I'm not sure of the flag since it
was missing from the dumps.
Untested protocol...
2016-12-09 10:19:35 +01:00
pascallanger
c2577df6f7
Bayang telemetry : sending volt/4
...
Change for Taranis
2016-12-09 08:24:51 +01:00
pascallanger
36cb0fb4cd
Bad _config.h file pushed...
2016-12-08 15:11:06 +01:00
pascallanger
e4e909737c
CX10/Q2x2 protocol update
2016-12-07 19:16:09 +01:00
pascallanger
dfd8d0fa3d
Added: Bayang telemetry
...
Changed telemetry configuration and validation for AFHDS2A and HUBSAN
Added default Bayang telemetry from Silverxxx:
- Option=1 to activate telemetry (option=0 -> standard Bayang protocol)
- Value returned to the TX: RX RSSI, TX RSSI, A1=uncompensated battery
voltage, A2=compensated battery voltage
2016-12-06 22:30:48 +01:00
pascallanger
7d7ca11c81
Telemetry: volatile
2016-12-05 21:51:27 +01:00
pascallanger
8f0ecac842
Core: stop transmitting if serial or ppm signal disappears
2016-12-04 18:58:29 +01:00
pascallanger
54dd562d88
Flysky/CX20 fully reversed
2016-12-04 18:56:03 +01:00
pascallanger
c24f7a86d4
Flysky/CX20 reversed elevator channel
2016-12-02 20:28:47 +01:00
pascallanger
d6b4437664
Latest protocol file for ersky9X
...
To be placed on the SD Card.
2016-12-02 18:20:35 +01:00
pascallanger
3fa40b2303
Bayang: add sub_protocol H8S3D
...
Protocol: 14
Sub_protocol: 1
2016-12-02 10:19:42 +01:00
pascallanger
33d676e1fe
Core: option to reverse input channels
2016-12-01 22:30:27 +01:00
pascallanger
afb7af287b
Flysky->CX20: hopping frequency based on any TXID
2016-11-30 18:28:56 +01:00
pascallanger
d6291a4c47
Flysky/CX20 fix
2016-11-30 17:02:09 +01:00
pascallanger
7228b84bf8
Flysky CX20 mods
2016-11-30 12:18:39 +01:00
pascallanger
2dbf8ebb65
Flysky: typos...
2016-11-30 07:55:07 +01:00
pascallanger
2d90844239
Flysky: addition of sub_protocol CX20
...
sub_protocol=4
7 channels
supports bind and extended channels
Only 1 TXID supported for now
2016-11-29 22:30:13 +01:00
pascallanger
5edaa6ec29
SLT: fix
2016-11-25 22:44:17 +01:00
pascallanger
1c0ed2a2c1
Q222 some channels direction reverse
2016-11-25 11:44:32 +01:00
pascallanger
245d27ea71
CX10 channel modifications
2016-11-25 10:28:18 +01:00
pascallanger
f14d4b8ac3
SLT
2016-11-24 20:28:42 +01:00
pascallanger
fdc867b9d5
Q222
2016-11-24 20:22:52 +01:00
pascallanger
8e876d6a99
Q222: arming
2016-11-24 19:06:33 +01:00
pascallanger
c9de0b4cf2
Q2X2 protocol addition for Q222/Q242/Q282
...
Q2X2 protocol : 29
Sub-protocols:
- Q222 : 0
- Q242 : 1
- Q282 : 2
2016-11-23 21:56:00 +01:00
pascallanger
27b3a86155
SLT Vista format
2016-11-23 15:35:27 +01:00
pascallanger
683bdc838d
SLT
2016-11-18 16:51:52 +01:00
pascallanger
4f9f10ddf2
Core: blinking pattern for PPM signal detection
2016-11-18 16:51:52 +01:00
pascallanger
7c22110c96
SLT Fix?
2016-11-16 21:17:03 +00:00
pascallanger
6ad9fb8f27
AFHDS2A sub protocols and validation
2016-11-06 16:36:44 +01:00
pascallanger
4348f4b0d4
STM32: USART init changed
2016-11-06 16:34:40 +01:00
pascallanger
22529e28d8
Fixed compilation issue if telemetry is not enabled
2016-11-06 16:32:43 +01:00
pascallanger
aa52bcee8c
Apply J6Pro modifications from Vlad
2016-11-06 15:47:40 +01:00
Arne Schwabe
7840438bfc
Allow TX to request forwarding of FlySky telemetry data
2016-11-05 01:21:26 +01:00
pascallanger
f56ca6318a
STM32: align STM32 code with other platforms for tx_pause/tx_resume
2016-10-27 11:15:25 +02:00
pascallanger
909fb2eb2b
AFHDS2A: working version
...
- Wait for transmit completion before switching to RX (no more fixed
delays...)
- Verify if data has been received before processing it (better handling
of telemetry)
- Added TX_RSSI (along with the existing RX_RSSI)
Known issue: RX_RSSI value needs to be looked at. I'm seeing only values
between 157 (bad) and 196 (good). Is this normal for this protocol?
2016-10-26 13:51:54 +02:00
pascallanger
b2209eaad0
AFHDS2A fix
2016-10-24 23:14:42 +02:00
pascallanger
3a3a2ec76d
AFHDS2A
2016-10-22 13:36:07 +02:00
pascallanger
01ef79ac33
AFHDS2A again
2016-10-22 12:06:44 +02:00
pascallanger
f78e11057d
...
2016-10-21 19:57:48 +02:00
pascallanger
314ee96525
AFHDS2A: another trial
2016-10-21 19:39:59 +02:00
pascallanger
efc1223d45
AFHDS2A: again...
2016-10-21 18:37:27 +02:00
pascallanger
38d9aa4997
AFHDS2A: another trial...
2016-10-21 18:10:25 +02:00
pascallanger
42c7431416
AFHDS2A: changes
2016-10-21 10:55:55 +02:00
pascallanger
d1e40ee71c
AFHDS2A cosmetic changes
2016-10-20 22:55:50 +02:00
pascallanger
43169d8bab
AFHDS2A: few changes
2016-10-20 22:33:37 +02:00
pascallanger
8cbbb52b95
Fixed compilation issues due to AFHDS2A introduction
2016-10-20 21:55:02 +02:00
pascallanger
807a55fcdc
AFHDS2A: option value changed
...
Option value should be between 0 and 70 which gives a value between 50
and 400Hz (value in Hz = 50 + 5*option)
2016-10-20 21:21:10 +02:00