- Posts: 5
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Protocol Mismatch after upgrading from v4 to V5
Protocol Mismatch after upgrading from v4 to V5
- SpriteyC
- Topic Author
- Offline
Less
More
19 Jan 2017 16:58 #58197
by SpriteyC
Protocol Mismatch after upgrading from v4 to V5 was created by SpriteyC
Hi there, I'm sure this is simple to fix, but I have a protocol mismatch now on Devo 7e boot up & I cant bind to any of my quads. Can anyone help me solve this issue please. PS I have both a7105 & nrf24l01 installed. Thanks in advance.
Protocol mismatch 0801f448 & 0801fbf0
Hardware.ini shows this
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
;button_types: trim-all, trim-(left|right)-(up|down|both)
;May occur more than once if necessary.
;extra-buttons=
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
; has_pa-cyrf6936 = 0
enable-a7105 = A14
has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
enable-nrf24l01 = A13
has_pa-nrf24l01 = 1
; enable-multimod = A13
Protocol mismatch 0801f448 & 0801fbf0
Hardware.ini shows this
;Only useful for transmitters with an after-market vibration motor
;enable-haptic=1
;
;switch_types: 3x2, 3x1, 2x2
extra-switches=3x2
;
;button_types: trim-all, trim-(left|right)-(up|down|both)
;May occur more than once if necessary.
;extra-buttons=
;
[modules]
; there is no need to enable the cyrf6936 module unless
; it is wired to an alternate port. It is Enabled automatically otherwise
; enable-cyrf6936 = B12
; has_pa-cyrf6936 = 0
enable-a7105 = A14
has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
enable-nrf24l01 = A13
has_pa-nrf24l01 = 1
; enable-multimod = A13
Please Log in or Create an account to join the conversation.
- SpriteyC
- Topic Author
- Offline
Less
More
- Posts: 5
19 Jan 2017 17:36 #58199
by SpriteyC
Replied by SpriteyC on topic Protocol Mismatch after upgrading from v4 to V5
No panic, I sorted it. I forgot the 'format disk' before copying the files over. Panic over (for me
Please Log in or Create an account to join the conversation.
- Thomas.Heiss
- Offline
Less
More
- Posts: 698
19 Jan 2017 20:10 #58208
by Thomas.Heiss
Replied by Thomas.Heiss on topic Protocol Mismatch after upgrading from v4 to V5
You also need to copy the protocol folder (files) on the 7E, don't forget them!
Please Log in or Create an account to join the conversation.
- SpriteyC
- Topic Author
- Offline
Less
More
- Posts: 5
20 Jan 2017 09:07 #58225
by SpriteyC
Replied by SpriteyC on topic Protocol Mismatch after upgrading from v4 to V5
Thanks Thomas, it came up saying about protocols, so i copied them over & bingo
Please Log in or Create an account to join the conversation.
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Protocol Mismatch after upgrading from v4 to V5
Time to create page: 0.029 seconds
- Home
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Protocol Mismatch after upgrading from v4 to V5