Recent Posts

Pages: 1 ... 8 9 [10]
91
General Discussion / Re: Revo Oplink (Using as Coordinator???)
« Last post by Johnatronecl on May 01, 2019, 03:19:30 pm »
Hi,
Quote
I'd like to connect the Revo to my transmitter and take ppm input. Anyone gotten something like this to work?

This is not supported at this time, may need some work to do changes into the code.

Would this require a significant change or addition? I would like to familiarize myself with the codebase (and hopefully contribute in the future), was thinking of using this as an introductory exercise.

Thanks
92
If someone has some CC3Ds that they think are good and some that they think are bad

The aforementioned "import uav settings over and over till all flash blocks are used" is a lengthy procedure because it kind of assumes that the problem is not with the CC3D hardware.  A simpler procedure (that assumes the CC3D is the problem) is:
- erase with CF
- use GCS to verify that it has default values
- make one change with GCS and save it
- reboot the CC3D and use GCS to see if the change is still there (and assuming it is)
- try to erase with GCS and it fails (prove with GCS that the "one change" setting is still "changed")
- try to erase with CF and it works (prove with GCS that the "one change" setting has gone back to default value)

If someone has some CC3Ds that they think are good and some that they think are bad then this test will work differently on the good ones than on the bad ones.  "Try to erase with GCS" will work with good ones and fail with bad ones.  That will prove that the problem is related to a difference in CC3Ds.

At this point, I am guessing that the flash chips in the "bad" CC3Ds (if it is the CC3Ds) need to be "erased longer".  As I recall you hold the chip erase signals active for a certain length of time.  The chips in these "bad" clones might need longer erasing.  The longer time could be the fault of the flash chips being not to spec, the flash chips having a new spec that needs to be coded into LP's erase flash code, or LP code that was not written to spec, but written to "this works".
93
General Discussion / Re: Revo Oplink (Using as Coordinator???)
« Last post by f5soh on May 01, 2019, 01:31:03 pm »
Hi,
Quote
I'd like to connect the Revo to my transmitter and take ppm input. Anyone gotten something like this to work?

This is not supported at this time, may need some work to do changes into the code.
94
Applications - FPV / Re: MinimOSD Display - strange capacity
« Last post by f5soh on May 01, 2019, 01:28:12 pm »
Hi,

If you want the energy consumed you need a current sensor.
Using a Revo the Voltage/Current sensor is usually connected to the Revo and give more space into the MinimOSD for extended features. (LP_All_From_Revo170818.hex firmware)
Your OSD shows the current, voltage and consumed mAh.

Firmware updates can be found here
95
Applications - FPV / MinimOSD Display - strange capacity
« Last post by gnumarco on May 01, 2019, 10:16:28 am »
Hi guys.
I finally managed to set up my MinimOSD, configured using the Revo in Combridge etc...
What I find strange is that where it should display the capacity (CA), it displays 25.02A (see attachment)...the battery is a 1800mA (not sure there are actually 25000 mA batteries for quads). So, I was thinking: is it possible that to get accurate capacity I need to have a current sensor?
My MinimOSD is only connected to the battery using the GND and Batt1 pins. Is this only used to get accurante voltage (I thought it would get voltage and current)?

Another concern: The number next to the "thunder array" symbol should be the battery percentage (or maybe I configured wrong...?). Why does is show the mAh consumption?

I did not upgrade any firmware, as I was not able to find any place to download it. Shall I update the firmware?

Thanks ofr your help!!
96
As I re-read my own post, I realized my frustration was shining through. That was not my intend.

Quote
- As far as I know there are no developers that have this problem.
Maybe devs don't work with chinese copies? Could be a combination of the right (wrong) hardware with 16.09 or specific settings.
Question: What type of craft do ppl with this problem have, heli, drone or fixed wing? I use my CC3D's in airplanes only (I'm a bad pilot). Maybe Devs (almost) never setup for fixed wing?

Quote
-If someone with the problem (that can fix it using CleanFlight) could document how to break it, perhaps like this, then a developer could possibly get it to break and we could understand it.
When I get CF running and if CF-Erase works, I'll try to break it again. Can take a while, I'm rebuilding our bathroom, so I'm pretty busy and often too damn tired after.

Quote
- The erase procedure must be followed exactly.
 
Done. Doesn't work.

Quote
- It sounds like it is a problem that started with 16.09, but  <cut>  I think I recall a user that went back to e.g. 15.xx still had the problem which fits with it being a problem with 15.xx all along.
Last shipment, I had 2 CC3D's that were 'blancs', so there never was a version 15 on them untill after the problem appeared.

I will try out the possible power issues. But all my other CC3D's (10-12pcs) work fine (on 1A USB ports).

I will try Linux. Have a PC running it. Never thought of running LP on it.

Quote
- I would bet that of the users that have this issue, all their CC3D's exhibit the issue.
 
Then you would loose that bet, because I have at least a dozen other CC3D's that work fine with either version of LP. The eldest at least for 6-7 yrs. All but one have been up/downgraded before.

Quote
- If someone with a broken CC3D would be willing to send it to a dev
Well, if I can't get it to work, it's not much use having it, so in principle I would be willing. Any capable (for this problem) dev in The Netherlands?

Strange thing: My board is recognized as CopterControl, but when fiddling with BL's, it didn't accept the CC-BL. I needed to use the CC3D-version

   
Quote
I read the Cleanflight-method, but can't get CF to work
This sounds important.  Try a different computer and different cable.  CF 1.10 should work.
Been there, done that. Using all proven cables and computer setup. It's just me. Tired, can't sleep -> Can't focus.

Thanks for thinking with me/us about this problem!
97
General Discussion / Revo Oplink (Using as Coordinator???)
« Last post by Johnatronecl on May 01, 2019, 08:52:26 am »
Hi,

Currently I have an oplink mini module, connected to my transmitter. The transmitter sends ppm to the oplink mini, which then connects to my Revo fc.

I have a spare Revo, I was wondering how to get it to work as a coordinator. I'd like to connect the Revo to my transmitter and take ppm input. Anyone gotten something like this to work?

I can get the two Revo boards to connect, one as coordinator and one as receiver. However, I can't get the Revo (coordinator) to take a ppm input.

98
General Discussion / Re: Setting up for first flight.
« Last post by TheOtherCliff on May 01, 2019, 03:02:48 am »
Yea, you can reduce your Output page Maxes on all motors to say 1500 or even 1300 if it's really wild and you want to tone it way down.

With a tightly tuned (PIDs as high as possible without oscillations) quad, doing this might cause oscillations, but not in most cases, especially with just a default tune.
99
There are a few problems with tracking this down.  The big most important ones:

- As far as I know there are no developers that have this problem.

- We don't have a simple set of instructions to recreate the issue starting with a completely erased CC3D.  I suspect that you could take two sets of "exported UAV settings", (defaults.uav and completelyinstalled.uav) and do Import UAV settings alternating one and the other several times over (with NO erases) until all the flash memory blocks were used.  Then it must be erased and maybe the LP erase would fail.  If someone with the problem (that can fix it using CleanFlight) could document how to break it, perhaps like this, then a developer could possibly get it to break and we could understand it.



Other important things that cloud the issue:

- The erase procedure must be followed exactly.  During the erase, the board looks locked up for over 20 seconds and you MUST NOT power it off till the SystemTime counter starts counting again so it might be a user error.

- It sounds like it is a problem that started with 16.09, but there are only a finite number of flash memory blocks.  Changing a setting or two only uses a small number of blocks.  Installing a new version uses a lot, so it would use them up sooner, making it look like the new version is the problem.  Successfully erasing settings makes the blocks all available again.  I think I recall a user that went back to e.g. 15.xx still had the problem which fits with it being a problem with 15.xx all along.

- It's possible that your USB port doesn't produce enough current or your long thin cable doesn't allow enough current.  It might be that adding power from your ESC/BEC after connecting USB,  but  before erasing, (or using a computer instead of a laptop, or a different laptop with better USB power) helps.

- It may be an issue that only happens on one OS and not another.  Most users have Windows OS.  I think firmware developers tend to use Linux; at least I do.

- I would bet that of the users that have this issue, all their CC3D's exhibit the issue.  I recall hearing some say that they had some good ones that later turned out to be "bad".  This implies either - that there is something about that user's setup that causes the issue - or that devs that can't recreate the issue just have never used all the flash blocks up (at least that may be true for me).

- If someone with a broken CC3D (won't erase with LP but will erase with CleanFlight) would be willing to send it to a dev to see if they can successfully erase it with LP, the answer would either be: yes and so the user setup has an issue (possibly not the user's fault, like doesn't work on Windows 10 Vxxxx) or no in which case the dev has a CC3D with the issue and can debug it.

- There are probably other factors that I forgot to mention while writing this.

Quote
I read the Cleanflight-method, but can't get CF to work
This sounds important.  Try a different computer and different cable.  CF 1.10 should work.
100
General Discussion / Re: Setting up for first flight.
« Last post by Stardaddyed on April 30, 2019, 01:59:45 pm »
That's what I thought, it happened so quick.  It was a nightmare.  The other thing I forgot to mention is that I designed the quad in eCal to be able to carry a camera on a gimble and a larger battery so as it is now it is very over powered.  Can I limit the amount of throttle I am allowed to apply?  Say 50% max. 

Also, I should have read your start guide BEFORE I fired the thing up!  Great write up and I probably violated every pointer.

Ed
Pages: 1 ... 8 9 [10]