Discussion New Quadrocopter and Tricopter UAVP updated with GPS and more - UAVX!

[Danveal]

Originally Posted by jesolins

Hello Danilo,
Thanks for trying the UAVX with Holger ESC's. I'm sure Greg will have a quick fix for you and your Holger's after he has his morning coffee. The I2C was working on Ken's quad with previous gkeware, so be a bit patient for his response. Also you might want to try the GKE 16F876 version in our download area on your 16F876. Ken was flying I2c with that firmware as well.
Cheers,
Jim

Hi Jim,
thanks for your great reply, I just downloaded the GKE16F-HOL version that previously could not find.
Now in Italy is night. I will try tomorrow, I will update.

Ciao
Danilo

[gke]

Originally Posted by Danveal

Thanks for the development work you have done !!

I have some problems with the software UAVX and I2C HOLGER ESC

Compass, barometer and GPS are not installed.

In UAVPSet 3.0 I have chosen:
JR XP8103/R700 PPM (I have a Graupner MX16)
ADXRS610/300, Melexis90609
HolgerI2C

But the engines do not run.

With PWM ESC and appropriate parameters everything works.

If I change the 18F2620 pic with the 16f876 and load the old original software: Profi-Ufo-V315-CAM0-HOL-ADX300 everything works.

Thanks for any help, sorry for my bad english.

Regards, Danilo

Hi Danilo.

I do appreciate your very clear diagnosis.

First check you are not running a version that has DEBUG in the name as these versions have the motors disabled for safety.

Try the new version below. I do not have Holger's ESCs so we may need to try a few times .

If this fails can you check if the motors start using the old version of the 18F2620 code UAVP-V3.15.511gke-18F2620_16 20090716.zip which is visible again on the download site.

Greg

[foliage]

Is there a need to orient the compass board in a fix position with respect to the front on the UAVX. I have my board mounted in a different place on the main board. I read the note but there was no mention of any specific requirement regarding compass orientation. Should the board be set like in its original position. Since the GPS uses the compass, maybe there is need to know where is the front of the QUAD with respect to the north?
thanks.
Jack.

[jesolins]

Jack,
Yes the orientation is important but only when the GPS is used. Greg set up the firmware to adjust it to true north when it is mounted as in the manual. I had an earlier production version of the compass that was 180 degrees off from Greg's newer one. I ended up getting a couple of newer versions and they were the same as Greg's, so we a hopeful that most will be correct. Use the test firmware pull-down menu to first calibrate, then test the compass. If yours is correct, then the front will be true north. If it ends up being something else, let us know.
Cheers,
Jim

Originally Posted by foliage

Is there a need to orient the compass board in a fix position with respect to the front on the UAVX. I have my board mounted in a different place on the main board. I read the note but there was no mention of any specific requirement regarding compass orientation. Should the board be set like in its original position. Since the GPS uses the compass, maybe there is need to know where is the front of the QUAD with respect to the north?
thanks.
Jack.

[gke]

Originally Posted by jesolins

Jack,
Yes the orientation is important but only when the GPS is used. Greg set up the firmware to adjust it to true north when it is mounted as in the manual. I had an earlier production version of the compass that was 180 degrees off from Greg's newer one. I ended up getting a couple of newer versions and they were the same as Greg's, so we a hopeful that most will be correct. Use the test firmware pull-down menu to first calibrate, then test the compass. If yours is correct, then the front will be true north. If it ends up being something else, let us know.
Cheers,
Jim

Thanks. I have added some FAQs on the compass etc. to the relevant pages.

Greg

[Danveal]

Originally Posted by gke

Hi Danilo.

I do appreciate your very clear diagnosis.

First check you are not running a version that has DEBUG in the name as these versions have the motors disabled for safety.

Try the new version below. I do not have Holger's ESCs so we may need to try a few times .

If this fails can you check if the motors start using the old version of the 18F2620 code UAVP-V3.15.511gke-18F2620_16 20090716.zip which is visible again on the download site.

Greg

Hello Greg,
I am glad to speak with you, your work on the UAVP and UAVX software is fantastic.
I tried the UAVX version that you have attached but the engine still not running.
Then I loaded the: UAVP-V3.15.511gke-18F2620_16-ADX300-HOL version, same result, I have the green light but the engine not running.

Finally I changed the pic with 16F and uploaded the GKE version: Profi-Ufo-B3_1-V3_15m3-ADX300-HOL.
I have the green light, and the engines are working properly with Holger I2C ESC

Regards,
Danilo

[gke]

Originally Posted by Danveal

Hello Greg,
I am glad to speak with you, your work on the UAVP and UAVX software is fantastic.
I tried the UAVX version that you have attached but the engine still not running.
Then I loaded the: UAVP-V3.15.511gke-18F2620_16-ADX300-HOL version, same result, I have the green light but the engine not running.

Finally I changed the pic with 16F and uploaded the GKE version: Profi-Ufo-B3_1-V3_15m3-ADX300-HOL.
I have the green light, and the engines are working properly with Holger I2C ESC

Regards,
Danilo

Thanks Danilo,

I will need to work through the problem step by step in the morning when I am properly awake - it is getting late here now.

It may be a problem between UAVPSet and UAVX with passing the ESC type. It will be a simple correction - once I find it

Greg

[dleroi]

Originally Posted by gke

It may be a problem between UAVPSet and UAVX with passing the ESC type. It will be a simple correction - once I find it

Greg and Danilo,

Just a thought - if your programmer software will read the eeprom (PicKit2 and EPICwin do), you can compare what's there with what you entered in UAVPSet to see if the problem lies within UAVPSet.

Cheers,
Don

[Danveal]

Originally Posted by dleroi

Greg and Danilo,

Just a thought - if your programmer software will read the eeprom (PicKit2 and EPICwin do), you can compare what's there with what you entered in UAVPSet to see if the problem lies within UAVPSet.

Cheers,
Don

HI,
I have the PicKit2, I can read and report. What are the eeprom locations and correct values?

[jesolins]

@Danilo,
Reposted from UAVP forum.
Your English is fine
What mode is your TX? Did you check the appropriate box in the UAVPset V3.0? What are your channel assignments on your Graupner MX16 TX? Greg will be up in a couple of hours.
@Ken,
You did not have these issues with 16F and your I2c, no? ...Or did you swap ESC positions?
Cheers,
Jim

Originally Posted by Danveal

Today I spent several hours to get it to work but unfortunately without success.
In UAVX does not work
In pic 16F engines work, with testsoftware-hol each HOLGER I2C ESC are recognized in the correct position and address
However, during testing I discovered that when you move the stick of roll to the left, the back engine is activated instead of the right engine

When active the stick of nick forward the right motor is activated instead of the back motor.
The other 2 commands and motors work properly.
I tried to change the back controller with the right controller against the official istruction and the axes of the nick and roll work but the uavp is uncontrollable.
The radio channels are set correctly
In my opinion there is a problem with the flight software on uavp hol version or some incompatibility with the latest versions of holger esc. I have tried on holger esc version 1.2
On the 16F pic I tried both versions 3.14-3.15 that the GKE. All with the same result
Sorry for my bad english
Regards
Danilo

[kb6mcc]

Originally Posted by jesolins

@Danilo,
Reposted from UAVP forum.
Your English is fine
What mode is your TX? Did you check the appropriate box in the UAVPset V3.0? What are your channel assignments on your Graupner MX16 TX? Greg will be up in a couple of hours.
@Ken,
You did not have these issues with 16F and your I2c, no? ...Or did you swap ESC positions?
Cheers,
Jim

Hi Jim, I don't have any i2c ESC problem with the GKE 3.15m on 16F or 18F. I will test the UAVX with i2c later.

[gke]

Originally Posted by kb6mcc

Hi Jim, I don't have any i2c ESC problem with the GKE 3.15m on 16F or 18F. I will test the UAVX with i2c later.

Excellent - thanks very much Ken.

Which version of the I2C ESCs do you have?

If UAVX is checks out as well then we have a problem with Danilo's new ESCs maybe in the firmware/addressing.

Can also you confirm for (Jim and Danilo) that your ESCs are connected in the normal pattern:

K1- Front
K2- Left
K3 -Right
K4 -Back

I will wait for your test results on UAVX before changing anything in the software.

In the mean time I will check the MK software to see whether Holger has changed the addressing convention.

Greg

[Danveal]

Originally Posted by jesolins

@Danilo,
Reposted from UAVP forum.
Your English is fine
What mode is your TX? Did you check the appropriate box in the UAVPset V3.0? What are your channel assignments on your Graupner MX16 TX? Greg will be up in a couple of hours.
Jim

Hi Jim,
My tx is in mode 2.
The channel assignments are :Graupner/JR modes (K1=Throttle, K2=Roll, K3=Pitch, K4=Yaw) and in UAVPset3.0 I chose JR XP8103/R700 PPM.

But there are some strange things:
- when i check mode 1 or mode 2 in UAVPset3.0, in TX/RX setup windows the channel and the function of the stick is the same (eg. Thtottle always to the left despite the check on the mode 1)

- with the same TX EPA setting, in 18F2620-511gke and UAVPset 2.5 the range of the trhottle is 20 to 200 while in UAVX soft and UAVPset 3.0 the throtle range is approximately 8 to 90.
With 18F260-511gke software and PWM ESC's everything works fine, watch the first test flight.

http://www.vimeo.com/6086779

After this, I broke a PWM esc and I did not have time to try the UAVX version with the PWM ESC configuration

[Danveal]

Originally Posted by gke

Excellent - thanks very much Ken.

Which version of the I2C ESCs do you have?

If UAVX is checks out as well then we have a problem with Danilo's new ESCs maybe in the firmware/addressing.

Can also you confirm for (Jim and Danilo) that your ESCs are connected in the normal pattern:

K1- Front
K2- Left
K3 -Right
K4 -Back

I will wait for your test results on UAVX before changing anything in the software.

In the mean time I will check the MK software to see whether Holger has changed the addressing convention.

Greg

Hi Greg,
in I2C mode, the I2C bus is made only from PIN 1 (K2) and PIN1 (K3).
The YGE I2C must be addressed through the testsoftware while HOLGER esc must be addressed through the pad on the card.
With the testsoftware-hol (servo test command ) you can verify that HOLGER ESC are properly addressed.

[13brv3]

Originally Posted by gke

In the mean time I will check the MK software to see whether Holger has changed the addressing convention.

Greg

Hi Greg,

The Holger addresses haven't exactly changed, but there are more of them now. The version 1.0 BL-Ctrl boards had addresses coded in software for motors 1-4. The version 1.1, and 1.2 BL-Ctrls have solder jumpers that can select 1-4, so the software just looks at the jumpers. Now that they allow up to 12 motors, they have 3 versions of software. The normal version looks at the jumpers, and addresses them as 1-4. The "5-8" version uses the jumpers to select 5-8, and I'm pretty sure you can figure out what the 9-12 version does :-)

Actual addresses are.
// Motor number 1 (Front) is 29 hex or 41 decimal
// Motor number 2 (Rear) is 2A hex or 42 decimal
// Motor number 3 (Right) is 2B hex or 43 decimal
// Motor number 4 (Left) is 2C hex or 44 decimal
// Motor number 5 is 2D hex or 45 decimal
// Motor number 6 is 2E hex or 46 decimal
// Motor number 7 is 2F hex or 47 decimal
// Motor number 8 is 30 hex or 48 decimal
// Motor number 9 is 31 hex or 49 decimal
// Motor number 10 is 32 hex or 50 decimal
// Motor number 11 is 33 hex or 51 decimal
// Motor number 12 is 34 hex or 52 decimal

Cheers,
Rusty (still haven't gotten around to the UAVX)