Satya bro be careful with CF. They are not good for health. Wear mask.
http://www.protechcomposites.com/pages/Working-With-Carbon-Fiber.html

Hi satyagupta. Did you switch to carbon fiber arms as well? or only the central plate?

Vineet

Well Folks the inevitable finally happened!!!!!. Had my first major crash.  Major in the sense I actually caused physical damage to a boy!  Had to rush him to a hospital and 8 stitches later.......  Gosh.
My wife has banned me from flying on my rooftop.    It was entirely my fault.  Didn't know what this "Flying Blender" can do.  Very irresponsible of me. 
Damage to the Quad. 
1. Bent arms
2. 2 Broken props
3. A damaged esc.   
Well not at the cost of causing physical injury to anybody.   Please fly safe guys.  I am still yet to get over the trauma!!!!!  Will post a video soon

OMG sorry to hear that sir. Your son got hurt?

This is very sad, please guys be very careful about this, speciality when kids/minors are around. You should ask them to stay at a very safe distance and if they don't listen then its better to pack your bags for the session.

@dreamfly, I don't think posting the video is a good idea. One formal complain and the whole community could be done for good.

I understand bro, once i had my quad crashed over my wife (she was shooting it) she could not understand and the quad came down crashing over her. Good thing, that the props stopped spinning and she got a small cut on her finger but indeed it is very dangerous.

About kids you really cant do anything to keep them away, shout at them or anything but these awesome alien things (quads) get their attention, and they do crowd around it. This is what i used to do, fly at afternoon around 1-3 most of the kids are at home. Then i had a dog "pluto" he used to scare every kid that came close to quad, and kids used to get scared by pluto a lot lolz. So i used to take him while i go for flying.

I have heard this a lot, from my wife and mom. Every time i crash they are like dare you touch that thing again..

Jokes apart a physical injury to anyone is not good. Good thing is it was nothing major, and you took care of it. With these things even in RCG you will hear a lot "FLY WITH CARE AND HUGE RESPONSIBILITY"

On the other hand let me not post the video.  Well there is nothing gory in the video though.  It is just crashing against the wall that's all, but the broken props are the ones that caused the mishap when it fell on the boy which is not on the video.  Anyway  while flying this thingy please make sure you fly slow so that it can be controlled and Never try to show off your flying skills.  Thats when all things go wrong.  I guess lots of lessons to be learnt personally. Sorry about this guys.

Happens to even best of us, we all learn from it.

Hmm hope the boy is doing ok

Quick question - which mode is preferred for a beginner? + mode or x mode?

Actually + and x mode both are same. For Arial photography/FPV many prefer x more over +

Thanks Satya, will start with + mode and see how it goes.

I remember that was a good topic to argue upon on RCG in several threads. There are many various opinions regarding that. Ofcourse for AP/AV/FPV, 'X' mode is preferred, but I am using X-mode for normal flying also. I (and most others) fly outdoors and X-mode looks and flies great outdoors.

Vineet

Thanks, will give it a try

Today i tested my quad with KK2.0 on terrace at night. Test went smoothly, no damage. But default PI values are too high for non simonk flashed ESCs. It was 150 P on roll/pitch. As soon as throttle reached 50% it jumped in the air 4-5 feet which is i am sure not normal compare to my previous HK board, i landed it safely. Finally i have set mine at 40-50P roll/pitch and now performance is near to previous board. I will test again tomorrow as it's windy from past few days. I see lots of talk on RCG about advantages of using flashed escs. I am wondering but factory flashed simonk rapid escs are out.
http://www.rctimer.com/index.php?gOo=goods_details.dwt&goodsid=780&productname=
I am sure hobbyking will be next.

Yes, the default P gain is way to high. I was wondering why my quad wants to commit suicide when it leaves the ground. I have also lowered it to the 40-50 range.
BTW which pack are you using - I am hardly getting ~3 mins from a 2200 mAH.

Sir me too using 2200mAh battery. It gave me same 3-4 min time on HK board. Later i flew with that battery more than 20-30 times allmost daily at night don't know exact time but it was good but now it has gave up after so many recharge and discharge cycles. Yesterday i flew quad with KK2.0 but i see lots of difference.

What prop and motor are you running Dharmik?

Sir i am using
MOTORS http://www.hobbyking.com/hobbyking/store/__5429__AX_2308N_1100kv_brushless_Micro_Motor.html
ESC http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=15202
And PROPS: 10x4.5
Here is video. HK V1 board

I think you have over propped your motor, i would not use anything more than 8x4 on it.
And please dont call me sir, i've not been knighted, yet

Yes sir so I have gemfan 8x4.5 props balanced and ready for new kk2. I bought them from rchobby addict last month.
Now I am flying in X mode. Here are some pics

Correction, I am getting close to 6:30 mins of flight time now from a 2200mAH pack.
Earlier, I hadn't setup the quad correctly. The nuts holding the props would become loose during the flight causing the motor to spin faster causing excess heat and current drain. Now, that i have loctited everything, its much better.

How does it flies sir with kk2.0? Please post video.

Hmm, it flies ok. I haven't been able to dial it in - will have to play around some more. Currently, I have set up at 30 P-gain and 5 I-gain. Rest settings are default. If I go more than 30 on the P-gain, then it starts to wobble (low frequency wobble).
Will try to take a video tomorrow.

Today i flashed one of damaged F-20A ESC with simonk firmware and it worked! So i will go further to flash my other ESCs soon. Here msg i got after flash. Fingers crossed
Flash the firmware from repository.

E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.exe -C E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.conf -p m8 -P usb -c usbasp -B 8 -e -U lfuse:r:E:\zzzzzzzzzzz\tmp\/lfuse.hex:r -U hfuse:r:E:\zzzzzzzzzzz\tmp\/hfuse.hex:r

avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x1e9307
avrdude.exe: erasing chip
avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: reading lfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "E:\zzzzzzzzzzz\tmp\/lfuse.hex"
avrdude.exe: reading hfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "E:\zzzzzzzzzzz\tmp\/hfuse.hex"

avrdude.exe done.  Thank you.


E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.exe -C E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.conf -p m8 -P usb -c usbasp -B 8 -e -U lfuse:w:46:m -U hfuse:w:202:m

avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x1e9307
avrdude.exe: erasing chip
avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: reading input file "46"
avrdude.exe: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude.exe: 1 bytes of lfuse written
avrdude.exe: verifying lfuse memory against 46:
avrdude.exe: load data lfuse data from input file 46:
avrdude.exe: input file 46 contains 1 bytes
avrdude.exe: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.02s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of lfuse verified
avrdude.exe: reading input file "202"
avrdude.exe: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude.exe: 1 bytes of hfuse written
avrdude.exe: verifying hfuse memory against 202:
avrdude.exe: load data hfuse data from input file 202:
avrdude.exe: input file 202 contains 1 bytes
avrdude.exe: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of hfuse verified

avrdude.exe done.  Thank you.

Flashing firmware from file.: E:\zzzzzzzzzzz\tmp\bs_nfet.hex

E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.exe -C E:\zzzzzzzzzzz\lib\avrdude\windows\avrdude.conf -p m8 -P usb -c usbasp -B 8 -e -U flash:w:E:\zzzzzzzzzzz\tmp\bs_nfet.hex:i

avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x1e9307
avrdude.exe: erasing chip
avrdude.exe: set SCK frequency to 93750 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: reading input file "E:\zzzzzzzzzzz\tmp\bs_nfet.hex"
avrdude.exe: writing flash (8192 bytes):

Writing | ################################################## | 100% 2.17s

avrdude.exe: 8192 bytes of flash written
avrdude.exe: verifying flash memory against E:\zzzzzzzzzzz\tmp\bs_nfet.hex:
avrdude.exe: load data flash data from input file E:\zzzzzzzzzzz\tmp\bs_nfet.hex:
avrdude.exe: input file E:\zzzzzzzzzzz\tmp\bs_nfet.hex contains 8192 bytes
avrdude.exe: reading on-chip flash data:

Reading | ################################################## | 100% 1.97s

avrdude.exe: verifying ...
avrdude.exe: 8192 bytes of flash verified

avrdude.exe done.  Thank you.
 

Good job!