101 replies to this topic

[CrispyCargo]

spackletoe, on 17 August 2011 - 06:58 PM, said:

Sorry if I missed this, but in the Mac version, is there something that might be causing my sticks to be pinned top left?  Using 8-14's version, I see this:

Screen shot 2011-08-17 at 11.56.51 AM.JPG

I got the same issue as well. I just assumed it wasn't supported on the MAC side. It works perfectly on my PC.

[harpia]

I'm finding it difficult to set up the newly acquired Copter Control and my Evo9 2.4Ghz
I'm following exactly the video " first episode of OpenPilot TV" but after finish all setting up and shut down the Control Copter and turn on again the Copter Control, a series of beeps sound  there's, like no radio signal (PWM).
My setup is this:
- Windows XP
- Multiplex Evo9 2.4Ghz TX
- RX 7 channels (PWM)
- 4 motors 2835 Jdrones
- 4 20 Amp ESC Jdrones
- 2200 Amp Battery



I'm following these steps:
1 - Download and Run the openlot GCS (http://wiki.openpilo...20e-install.exe)
2 - Plug the USB cable into the PC
3 - Firmware tab, click Rescue
4 - Plug USB cable on Copter Control,Ok
5 - Firmware and boot ok
6 - I go to the Configuration tab.
7 - Set all the steps to Quadricopter X version, imputs, etc..
8 - Set all outputs, flight mode, etc.
9 - Calibrate motors, Save all and unplug USB cable.

10- After, I turn on TX first and after the Copter control, there is an uninterrupted series of beeps giving the impression that there is no RX radio signal in Copter Control.

To make sure that it is a problem of my RX, I unplug the RX Copter Control and the same thing happens, ie, an uninterrupted series of short beeps.
I have other controllers multicopters (Ardupilot and DJI) which run perfectly with my Radio Multiplex Evo9 and the same RX.
It could be CC incompatible with the Multiplex Evo M-Link 2.4GHz?

See the video

[AlPackin]

harpia, on 31 December 2011 - 10:42 PM, said:

I'm finding it difficult to set up the newly acquired Copter Control and my Evo9 2.4Ghz

Could you please attach you UAV Settings file here so we could look at it

File>>Export UAV Settings

[harpia]

Hi Alpackin
Here are the  UAV Settings file.

Attached Files

•  UAVSettings.uav   8.62K   18 downloads

[PT_Dreamer]

You have your arming settings set to "always disarmed".

[AlPackin]

You have mismatched GCS and firmware versions.  Your GCS is 814 and I'm not sure what your FW is but it is different.  Download and install the latest release of both.
http://wiki.openpilo...tware+Downloads

if your CC board is from the latest batch it has 819 fw installed so you would just have to update your GCS to 819

[harpia]

Hi

My board is latest batch.
I installed version 819 fw did not work.
Everything works perfectly on the PC configuration phase, except for motors that are not connected by security, but when disconnected from the PC and turn on the CC Quadricopter happens in the same result, continuous beeps as seen in the video above.

Edson

Edited by harpia, 01 January 2012 - 06:38 PM.

[AlPackin]

you have 819 firmware but 814 GCS.  As I recall that mismatch will not allow the mixer settings to save correctly and the ESCs will continue to beep
This line from your UAV Settings shows the mismatch and that your GSC version is 814


<!DOCTYPE UAVSettings>
<settings>
    <versionInfo>
        <Embedded gitcommittag="39fcc5bd" fwtag="next" cpuSerial="52ff6d064882565313362087"/>
        <GCS revision="next:2f7f920e 20110814 14:25"/>

Just update your GCS to 819 and you should be ok.

[harpia]

I downloaded and installed this file http://wiki.openpilo...e=1315330486000 Is not this the most current version of the GCS and the firmware in a single installation file?

I installed everything again and redid the whole configuration of the CC, Firmware and calibrate motors. It's not working, the beeps continue without stopping.
I took the CC and installed my Arducopter board (to make sure it would have no problems with the ESC and receiver) with the same motors, ESC and the same receiver and everything worked perfectly with Arducopter board.
I removed Arducopter and installed  the  Copter Control and redid it again, did not work.
It would not be incompatible my Windows XP in Portuguese with the GCS? I changed my regional settings to U.S. English but still did not work.

Attached Files

•  UAVSettings.uav   8.91K   10 downloads
•  Print_Sc.JPG   97.75K   27 downloads

[AlPackin]

that's better, your versions now are equal.  You have your output update rates set to 50 hz, set them to 400 hz (outputs 1-3 and 4).  Then run the ESC throttle calibration described at the bottom of this page.  Remove all props and follow the sequence exactly as far as when to connect the battery
http://wiki.openpilo...t Configuration

[harpia]

Dear AIPackim

After  ESC calibrate everything is working perfectly.

Thank you.

[AlPackin]

very good, you're welcome

[c2po]

I think the thread title needs to be changed to "Very old firmware! Do not use this build"

[AlPackin]

it is a bit dated, new stuff coming soon

[Berkely]

c2po, on 02 January 2012 - 01:51 AM, said:

I think the thread title needs to be changed to "Very old firmware! Do not use this build"

But that's still a stable tested build & firmware, nothing wrong with it. I agree that the newer version has a lot improvements but basically the "flying behavior" of the aircraft shouldn't change.

[c2po]

Berkely, on 02 January 2012 - 06:26 PM, said:

But that's still a stable tested build & firmware, nothing wrong with it. I agree that the newer version has a lot improvements but basically the "flying behavior" of the aircraft shouldn't change.

Maybe there's nothing wrong with it but just count the number of threads when people received CC board with 0819 firmware, then installed this 0810 GCS and then had all kind of problems caused by mismatch of a firmware and GCS, and that particular version doesn't warn you about a mismatch.

My opinion is if all boards are shipped with the latest public release 0819 then all other versions should be hidden/removed to avoid that kind of confusion. 20110810 build is incompatible with some of the 20110819 UAVOblects, that thing alone is the reason good enough to take it down.

For programmers and techie people it is easy to spot that 20110819 version is newer that 20110810 which is actually a date of a release, but for average user it is not. They see "New Firmware!" title and download it and it takes days to troubleshoot the problem why settings are not saved or mixers are zero, etc., because no one is specifying the versions they use, nor they are attaching a file with settings.

[Spydmobile]

All valid points that seem to illustrate a need for a dedicated approach to advertising the latest firmware to both avoid the problems and for simple common sense ease of navigation. Not sure what we should do about it, but changing the title is a good start.
F

[jbkappirossi]

hi guys, i got a question about the new FW 201.

I've just upgraded from 819 and noticed a differents in gyro handeling.
Where as 819 smoothly stabelizes the quad. 201 almost yanks it back in place... can someone explane what that is?

With bolth FW's i've left the KI Kp setting at default.

[peabody124]

I'll be honest all of the versions should fly the same with the same settings.  Best guess is that you didn't migrate one of the settings identically.  Since you specify the stabi settings are the same (I would really double check that though) what about the mixer gains?  Do you have before/after .xml files for us to compare?

[jbkappirossi]

nope, i didn't save anything. I just remembered my settings.

I wil flash 819 back and look if i can find a difference. Cant test it any more though.
201 made me ramp the quad into the wal with huge prop los. one cracked and 2 completely destroyed.
But i wil make some screenshot from the setting and overlook it again.
And if i can't find it, I ques i'll go back to 819, wich work for me.
I'm stil a beginner so i dont know every thing you mean just yet.
By mixer, you mean the KI and KP settings?
And where ore how can i get a xml file? ore is that the same as a UAV file?

thanks

Edited by jbkappirossi, 05 March 2012 - 10:17 PM.