- Posts: 4402
Devo7e work
- PhracturedBlue
-
Topic Author
- Offline
Less
More
01 Apr 2013 16:31 #8369
by PhracturedBlue
Replied by PhracturedBlue on topic Devo7e work
you may be able to resolve this by changing the scan-order of reading the analog inputs. That's how I resolved the interference between the battery and stick on the devo12. I never found a good reason for it, but I think the analog circuits on the Devo12 are not very well isolated leading to cross-coupling. It being intermittent is weird though. Maybe overheating, or low battery, or some particulate inside your transmitter case.
Please Log in or Create an account to join the conversation.
- cmpang
-
- Offline
Less
More
- Posts: 296
01 Apr 2013 17:18 #8374
by cmpang
I am a hardware guy.. and experience show that is a very great concern. Should there be inadequate isolation, interferrene can chime in at any moment making too big a surprise to the pilot to suffer ...
I also run R/C boats and a boating session usually goes about 1.5 to 2 hours. There were once or twice that I found after a session that my timer only shown for 40 or 50 minutes.. that may be a sign that the timers was reset by something that I was not aware ..
I am now busy setting up my Devo10 so I have something to fly.. until then, I might go to the route of soldering the wiring direct from the stick pot to the CPU pins to see if that works..
Replied by cmpang on topic Devo7e work
PhracturedBlue wrote: ... I never found a good reason for it, but I think the analog circuits on the Devo12 are not very well isolated leading to cross-coupling......
I am a hardware guy.. and experience show that is a very great concern. Should there be inadequate isolation, interferrene can chime in at any moment making too big a surprise to the pilot to suffer ...
I also run R/C boats and a boating session usually goes about 1.5 to 2 hours. There were once or twice that I found after a session that my timer only shown for 40 or 50 minutes.. that may be a sign that the timers was reset by something that I was not aware ..
I am now busy setting up my Devo10 so I have something to fly.. until then, I might go to the route of soldering the wiring direct from the stick pot to the CPU pins to see if that works..
Please Log in or Create an account to join the conversation.
- RandMental
-
- Offline
Less
More
- Posts: 521
01 Apr 2013 19:42 #8397
by RandMental
Replied by RandMental on topic Devo7e work
The default tx_ini of the current nightly build for a new installation is:
current_model=1
mode=2
[modules]
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
Should enable-cyrf6936 = B12 not always be enabled for the default Devo7e (No Mods)?
I assume has_pa-cyrf6936 = 0 be set to 1 if you have done the diode mod to enable the PA?
current_model=1
mode=2
[modules]
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
Should enable-cyrf6936 = B12 not always be enabled for the default Devo7e (No Mods)?
I assume has_pa-cyrf6936 = 0 be set to 1 if you have done the diode mod to enable the PA?
Please Log in or Create an account to join the conversation.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4402
01 Apr 2013 20:05 #8402
by PhracturedBlue
Replied by PhracturedBlue on topic Devo7e work
the devo defaults to always having a cyrf6936 at B12 so it is not necessary to enable this.
And yes, if you have the diode mod, you should change the has_pa value to '1'
And yes, if you have the diode mod, you should change the has_pa value to '1'
Please Log in or Create an account to join the conversation.
- RandMental
-
- Offline
Less
More
- Posts: 521
01 Apr 2013 20:19 - 01 Apr 2013 20:31 #8403
by RandMental
Replied by RandMental on topic Devo7e work
Hi Guys
I have spend a few hours now trying to get Deviation on my 7e. I have no problems on my Devo8s to load and run Deviation.
Loaded the latest nightly or one that I build locally for Devo7e, same results...
I loaded the DFU, formatted the drive, load the directories under the Filesystem Directory and copy the Protocols directory to the root, and changed tx.ini for the diode mod.
The screen however only shows a block (see below) and after a few seconds the backlight turns off. I went back to the Walkera firmware and all works as it should. Again back to the Deviation, same result.
Am I missing anything on the Devo7e upgrade to Deviation?
EDIT: below also now the errors.txt for today's nightly build, plus the required elf files, just in case
I have spend a few hours now trying to get Deviation on my 7e. I have no problems on my Devo8s to load and run Deviation.
Loaded the latest nightly or one that I build locally for Devo7e, same results...
I loaded the DFU, formatted the drive, load the directories under the Filesystem Directory and copy the Protocols directory to the root, and changed tx.ini for the diode mod.
The screen however only shows a block (see below) and after a few seconds the backlight turns off. I went back to the Walkera firmware and all works as it should. Again back to the Deviation, same result.
Am I missing anything on the Devo7e upgrade to Deviation?
EDIT: below also now the errors.txt for today's nightly build, plus the required elf files, just in case
Last edit: 01 Apr 2013 20:31 by RandMental.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
-
- Offline
Less
More
- Posts: 4402
01 Apr 2013 22:22 #8410
by PhracturedBlue
Replied by PhracturedBlue on topic Devo7e work
I need the elf file that came with the firmware (devo7e.elf). You only provided the elf files for the protocol modules, which isn't sufficient. Generally what you see is a little weird. the dialog box you see doesn't look like deviation dialog (which should have 2 parallel lines in the corners.
what you'd normally see if there was no filesystem. the little bars at the bottom look somewhat like the trims but the bounding rectangle is missing. I think it crashed before finishing the display (though in that case it should go into a reboot loop. You errors.txt does appear to contain a crash log though. If you provide the devo7e.elf with it I can debug further.
what you'd normally see if there was no filesystem. the little bars at the bottom look somewhat like the trims but the bounding rectangle is missing. I think it crashed before finishing the display (though in that case it should go into a reboot loop. You errors.txt does appear to contain a crash log though. If you provide the devo7e.elf with it I can debug further.
Please Log in or Create an account to join the conversation.
- farad
-
- Offline
Less
More
- Posts: 11
02 Apr 2013 00:33 #8413
by farad
I had the nightly 7e filesystem but I replaced it with the devo 10 filesystem and that fixed the issue.
Replied by farad on topic Devo7e work
sbstnp wrote:
farad wrote: I tried the most current nightly build and I can't see the graphs on any screen.
Replace the filesystem too.
I had the nightly 7e filesystem but I replaced it with the devo 10 filesystem and that fixed the issue.
Please Log in or Create an account to join the conversation.
- RandMental
-
- Offline
Less
More
- Posts: 521
02 Apr 2013 10:41 #8424
by RandMental
Thanks Farad, will try it this evening, perhaps it could fix my issues as well
Replied by RandMental on topic Devo7e work
farad wrote: I had the nightly 7e filesystem but I replaced it with the devo 10 filesystem and that fixed the issue.
Thanks Farad, will try it this evening, perhaps it could fix my issues as well
Please Log in or Create an account to join the conversation.
- RandMental
-
- Offline
Less
More
- Posts: 521
02 Apr 2013 17:02 #8432
by RandMental
Replied by RandMental on topic Devo7e work
NOTICE
We have confirmed the Devo 7e File System is not correctly generated in the current nightly builds or when built from the current source files. PB is working on it.
In the mean time the workaround is to load the Deviation for the 7e as normal per the manual, but copy the Devo10 file system directories, excluding the languages directory. Do not use the Devo 7e file system. Remember to copy the Protocol directory from the 7e build to the root directory as well.
We have confirmed the Devo 7e File System is not correctly generated in the current nightly builds or when built from the current source files. PB is working on it.
In the mean time the workaround is to load the Deviation for the 7e as normal per the manual, but copy the Devo10 file system directories, excluding the languages directory. Do not use the Devo 7e file system. Remember to copy the Protocol directory from the 7e build to the root directory as well.
Please Log in or Create an account to join the conversation.
- RandMental
-
- Offline
Less
More
- Posts: 521
02 Apr 2013 17:42 - 02 Apr 2013 18:01 #8433
by RandMental
Replied by RandMental on topic Devo7e work
Hi all
When changing protocols on the 7e and I switch between Flysky, DSM2/X etc, I can see the RF profile changes on a Spectrum analyser.
However, when switching back to either the Devo or Wk2801 protocol and selecting bind, there is no RF output from the TX. I then have to switch the TX off and on, before there is RF from the TX in those 2 protocols.
Can any one check if they get the same, on my side it is repeatable.
I have a XL7105-D03 installed, done the RF Power mod and the Firmware is the latest source/nightly build.
I have this issue logged as #311 on bitbucket, just in case.
EDIT: I have confirmed there is the same problem with this build on the Devo8s.
When changing protocols on the 7e and I switch between Flysky, DSM2/X etc, I can see the RF profile changes on a Spectrum analyser.
However, when switching back to either the Devo or Wk2801 protocol and selecting bind, there is no RF output from the TX. I then have to switch the TX off and on, before there is RF from the TX in those 2 protocols.
Can any one check if they get the same, on my side it is repeatable.
I have a XL7105-D03 installed, done the RF Power mod and the Firmware is the latest source/nightly build.
I have this issue logged as #311 on bitbucket, just in case.
EDIT: I have confirmed there is the same problem with this build on the Devo8s.
Last edit: 02 Apr 2013 18:01 by RandMental.
Please Log in or Create an account to join the conversation.
- dehalo
-
- Offline
Less
More
- Posts: 35
05 Apr 2013 16:44 #8583
by dehalo
Replied by dehalo on topic Devo7e work
Is the option to set transmitter power gone?
I only have the unchangeable option "default" in all protocols.
Devo3.0.0 7E &emu10
I only have the unchangeable option "default" in all protocols.
Devo3.0.0 7E &emu10
Please Log in or Create an account to join the conversation.
- sbstnp
-
- Offline
Less
More
- Posts: 649
05 Apr 2013 16:53 #8584
by sbstnp
7E defaults to max power now.
Devo 10 + 4in1
Spektrum Dx9
FrSky Taranis + TBS Crossfire
Replied by sbstnp on topic Devo7e work
dehalo wrote: Is the option to set transmitter power gone?
I only have the unchangeable option "default" in all protocols.
Devo3.0.0 7E &emu10
7E defaults to max power now.
Devo 10 + 4in1
FrSky Taranis + TBS Crossfire
Please Log in or Create an account to join the conversation.
- dehalo
-
- Offline
Less
More
- Posts: 35
05 Apr 2013 17:07 #8585
by dehalo
Max as default my be OK, but why can't it be changed?
And the Devo10 emu has "default" only
Replied by dehalo on topic Devo7e work
My 7E has the diode mode so the tx power setting would be helpful.sbstnp wrote:
dehalo wrote: Is the option to set transmitter power gone?
I only have the unchangeable option "default" in all protocols.
Devo3.0.0 7E &emu10
7E defaults to max power now.
Max as default my be OK, but why can't it be changed?
And the Devo10 emu has "default" only
Please Log in or Create an account to join the conversation.
- FDR
-
- Offline
05 Apr 2013 17:23 #8586
by FDR
Replied by FDR on topic Devo7e work
Then you should change the has_pa-cyrf6936 value in your tx.ini's modules section to 1:
[modules]
has_pa-cyrf6936 = 1Please Log in or Create an account to join the conversation.
- dehalo
-
- Offline
Less
More
- Posts: 35
05 Apr 2013 18:08 #8588
by dehalo
Replied by dehalo on topic Devo7e work
thanx
Please Log in or Create an account to join the conversation.
- eggma
-
- Offline
Less
More
- Posts: 4
10 Apr 2013 18:49 #8832
by eggma
Replied by eggma on topic Devo7e work
Hi
I've been following this topic for the last little while. Thanks to deviation, I know that the Devo7e can now fly blade nano cpx. Question: would it work for a brushless mod nano cpx?
Thanks
I've been following this topic for the last little while. Thanks to deviation, I know that the Devo7e can now fly blade nano cpx. Question: would it work for a brushless mod nano cpx?
Thanks
Please Log in or Create an account to join the conversation.
- rbe2012
-
- Offline
- So much to do, so little time...
Less
More
- Posts: 1433
10 Apr 2013 18:55 #8833
by rbe2012
Replied by rbe2012 on topic Devo7e work
I see no reason why it should not. The brushless motors are controlled by the same signal (only the driver is different).
I have an Nano CPx and a mCP x BL and can fly both with the same config.
I have an Nano CPx and a mCP x BL and can fly both with the same config.
Please Log in or Create an account to join the conversation.
- Joshua
-
- Offline
10 Apr 2013 19:19 #8836
by Joshua
Replied by Joshua on topic Devo7e work
I have a brushless Nano,and it works fine with deviation.
Ciao, Bernd
Ciao, Bernd
Please Log in or Create an account to join the conversation.
- eggma
-
- Offline
Less
More
- Posts: 4
10 Apr 2013 20:10 #8838
by eggma
Replied by eggma on topic Devo7e work
Good to know. Thank you everyone for your response. I'll sit tight to wait for my Devo7e instead of getting a Programmable Spektrum....
Please Log in or Create an account to join the conversation.
- RoGuE_StreaK
-
- Offline
Less
More
- Posts: 486
11 Apr 2013 22:26 #8873
by RoGuE_StreaK
Replied by RoGuE_StreaK on topic Devo7e work
What's changed in the emulator setup? I've downloaded the three 7E zips, extracted them as per my previous emu setup, and get the USB symbol only; pressing Enter then gives random graphics. I've tried rearranging the file locations all over the place, but still no go.
I've tried searching around and going through the release notes, manual etc but can't find anything.
Here's a snippet of what I get
I've tried searching around and going through the release notes, manual etc but can't find anything.
Here's a snippet of what I get
Brightness: 1
Wait Release
Released
Wait Press (pressed Enter here)
Pressed
Pressed
Wait Release
Released
Failed to parse Model file: models/model1.ini
Brightness: 5
Contrast: 5
Couldn't open font file: media/.fon
ERROR: Could not read media/sound.ini
etcPlease Log in or Create an account to join the conversation.
Time to create page: 0.116 seconds
-
Home
-
Forum
-
Development
-
Development
- Devo7e work