* before protocol name, will not bind...

More
24 Feb 2016 00:02 - 24 Feb 2016 00:04 #43529 by grnd flyr
* before protocol name, will not bind... was created by grnd flyr
Installed A7105 & Nrf modules in a 7E, double checked all connections but get no binding and it has a * before the Hubsan4 name. Also won't do anything when clicking Re-init. Have double checked the correct A13 & A14 are assigned to TMS/TCK in the hardware ini file. Flummoxed with out a clue what to try/do next... any ideas? Attached a pic but don't know if it'll help or not... appreciate all ideas guys. Frustrated...



edit... forgot to say that I'm using latest nightly: deviation-emu_devo7e-v4.0.1-667678f
Last edit: 24 Feb 2016 00:04 by grnd flyr.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 00:15 - 24 Feb 2016 00:15 #43531 by Arnold
Replied by Arnold on topic * before protocol name, will not bind...
That file you refer to, "deviation-emu_devo7e-v4.0.1-667678f" is not for installation on your transmitter. That is an emulator file that installs on your PC to emulate the behavior of a transmitter when examining an .ini file.
Try installing the version of that file without the "emu" part.

Too many hobbies & too many Devos!
Who knows where the time goes?
Last edit: 24 Feb 2016 00:15 by Arnold.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 00:22 #43532 by grnd flyr
Replied by grnd flyr on topic * before protocol name, will not bind...
Sorry, I didn't copy over the deviation-emu_devo7e-v4.0.1-667678f.exe & libportaudio-2.dll file, just: filesystem/devo7e files from the deviation-emu_devo7e-v4.0.1-667678f.zip file.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 02:12 #43534 by grnd flyr
Replied by grnd flyr on topic * before protocol name, will not bind...
Ok, think I'm gonna stop for the night, before I hurt myself or my poor 7E... :evil:

However...
In tx.ini, is:

[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=1
has_pa-a7105=1
enable-cc2500=None
has_pa-cc2500=0
enable-nrf24l01=1
has_pa-nrf24l01=1

...if I change: enable-a7105=1

to: enable-a7105=B13 (thinking 13 & 14 from hardware ini file)

I get the following message: Bad/missing protocol modules

BUT!!! there is no * before Hubsan4. Now, if I try to Re-init, the button finally works, BUT!!! I get the same "Bad/missing protocol modules" message.

...snarg...

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 02:54 - 24 Feb 2016 02:55 #43536 by mwm
If you really did what it sounds like you did, you're lucky the transmitter isn't crashing. You needed to instill the dfu file from the zip file with a DFuse tool (not the STM one), them copy the rest of the files over in USB mode. Unless you've done a really odd hardware install, the enable line values are A13 and A14. The * in front of the protocol name means the module isn't enabled.

If you haven't read them yet, read the installation section of the user manual in the menu on the left. Use the direct link, as that had been updated recently but is still correct for 4.0.1. Ditto for the module installation documents found on the "Links" page in the menu. Pay particular attention to the differences between installing modules for use with the the release version vs the nightly build.

Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.

My remotely piloted vehicle ("drone") is a yacht.
Last edit: 24 Feb 2016 02:55 by mwm.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 05:09 #43542 by grnd flyr
Replied by grnd flyr on topic * before protocol name, will not bind...
...but the rest of the story ends well... Thanks for the info mwm. For some reason I thought that after flashing with Deviation, you just needed to copy the files over from then on. Anyway, used the DFuse tool again and now both new modules are recognized but the CYRF is not with a warning about it being missing when I first turn it on. The Hubsan X4 & JJRC 1000 fly much better now, so like I said, all ended well. Thanks again.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 05:11 - 24 Feb 2016 05:23 #43543 by RedSleds
Replied by RedSleds on topic * before protocol name, will not bind...
Your hardware ini should look like this

[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 = 1
enable-a7105 = A13
has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
enable-nrf24l01 = A14
has_pa-nrf24l01 = 1
; enable-multimod = A13

You can edit out the commented out lines if you want to, so it would look like this:

[modules]
enable-a7105 = A13
has_pa-a7105 = 1
enable-nrf24l01 = A14
has_pa-nrf24l01 = 1

Do not use notepad, it will not maintain proper format. Use notepad++ for editing.

You may have to swap the A13 and A14 around, depending on which module you connected to TMS, and which one you connected to TCK. The one connected to TMS needs to be A13, and the one connected to TCK needs to be A14.

See this page for full description >>> bitbucket.org/PhracturedBlue/deviation/wiki/Enabling_modules

DEVO 10 - Multi-module with nRF24L01 +PA +LNA, A7105 +PA, & CC2500 +PA +LNA transceivers.
Nightly Build: v4.0.1-548bbf5 (6/9/2015)
Last edit: 24 Feb 2016 05:23 by RedSleds.

Please Log in or Create an account to join the conversation.

More
24 Feb 2016 15:31 #43557 by grnd flyr
Replied by grnd flyr on topic * before protocol name, will not bind...
Thanks RedSleds, I haven't looked it up yet but with the DEVO-S-Mod module instead of the stock CYRF module I should still keep it at?:

[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 = 1

instead of:

[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 = 1

since DEVO-S-Mod module = range mod?

...still getting the missing CYRF module warning at startup. A7105 & Nrf are just peachy tho... :)

Thanks again

Please Log in or Create an account to join the conversation.

Time to create page: 0.044 seconds
Powered by Kunena Forum