49 Best AnkuLua: Game automation Alternatives Apps for Android Devices. More informationhttp://ankulua.boar. So faraway-PINC INC あてもない道ばかりを フラフラ歩いていた今ドコを目指して 何をして良いのかも-君が好きなあの曲.

Talking about Makefile. Can a change be made so that it generates a.bin file as well? I'm using the stm ruindows tool to load that only likes.bin files. Editing the local copy is bad as I don't want version conflicts on each tree update.

I know It can be generated manually easily but I confess I'm lazy. If you are using eclipse odev: 2 possibilities: Project properties/Setting/ARM Sourcery.Create Flash Image/Out ->choose binary or Project properties/Setting/Build steps/Post build steps ->include here the command to generate bin file. I have no error here. Please post output. The biggest problem with the accels is vibration, no matter the frame, no matter how well you have the props balanced.

And some ADXL345's are better than others. Here is some accel telemetry. This data is with the accels oversampled at 1 kHz, averaged for use at 100 Hz, and run thru a 4th order low pass filter.

It's not too bad looking. You can see when the system is armed, when it takes off, and when it lands very clearly. The second chart is attitude estimated by a kalman filter. The roll and pitch values are good, the heading estimate needs a little work.

Igonore the large heading spikes as I was flying with the quad pointed almost due south and you are seeing the +/-180 degree transistion. The attitudes are estimated at 500 Hz and corrected (with the above accel data) at 100 Hz. This telemetry was output at 100 Hz. Getting away from single sample sensor data and using oversampling looks to offer some improvement with these inexpensive sensors. The work getting to this point is described over in the baseFlightPlus thread for those interested. It's still a work in progress, but it's looking very promising.

Hi John, I was going to email you today but this may build on what you are getting. I have added a pre-filter to my simplest filter schemes. The idea is that you slew limit the input signal to the maximum rate of change that is permissible (or should be possible) for a given filter bandwidth before applying it to the filter proper. This seems to work quite well on my testing so far.

In some senses looks like clamping diodes on old radio gear but in this case it is floating of course. For all of the classical filters you get 'smearing' of noise spikes over many samples. I have tried several firmware revisons and have optimized each to the best of my ability. With my FreeFlight board, it isn't possible to get a solid level mode. I'm at the point where I need to go back to basics and focus on my frame rather than firmware.

Pm1's firmwares (including the latest) worked the best on my (suspect) setup and eliminated the druken sailor effect, replacing it with a drift in a single, random direction. The last revison held the best. I tried the r183 baseflight last and drunken sailor is present, despite optimizing PID and trying different loop times. I want to provide some context for my previous posts in this thread. My frame is a relatively large scratch-built spider quad. It is 730mm (fairly symmetrical X), motor to motor is ~520mm, AUW (inc. 3S 4000mAH lipo) is 1130g.

It uses cheap Turnigy 2213N outrunners and RC Timer 10x4.5 props. The props are balanced.

The motors are currently tilted at ~10 degrees (for yaw authority). The frame is light ply and the arms are made from 1/2' window screen framing with pine inserts. The flight controller is hard mounted on nylon standoffs. It uses RC Timer 30A ESCs flashed with simonk 06-01 tgy.hex.

Before I go any further with firmware, I want to spend some time tweaking the frame to tighten up tolerances and eliminate vibrations. I am going to lessen the motor tilt, maybe eliminate it (according to an expert, too much tilt may induce wobbles that may affect the ACC). With all the firmwares, gyro mode is really terrific. It's only level mode that is underwhelming.

My application is sport FPV, so smoothness is most important. I'm honestly very satisfied with it in gyro mode for my application, but just want to optimize it some more. I also have some Sunnkysky 980kv motors and GWS 3-blade props coming. Once I get the frame optimized, I'll revisit firmware.

Thanks for your efforts in tweaking the ACC code. I just think it's time for me to do my part and clean up my frame work before I can do a fair assessment of the hardware and firmware performance. I really didn't like the level mode when increasing loop time.

Which is why I pushed r183 back out with looptime and acc_lpf to old defaults. With acc_lpf at 100 acc influence was really sluggish and would visibly tilt the copter in opposite direction after long forward flight or during turns etc. Back to looptime of 0 (no limit) and acc_lpf of 4, its back to 'normal' weak leveling that stays out of the way and just keeps the copter level while allowing flying fast forward at a large angle without worrying about it winding back up at the turn or in general getting in the way.

If people want silly nose-level hovering, I guess the current solution is high acc_lpf, high loop time, and whatever PID changes related to that. I fly on: all defaults except pitch/roll P at 6 (esc32/flashed esc), and pitch/roll/yaw rates at 0.6 and rc-rate at 1.0. This works fine for me on all my. Why does anyone fly around in level mode? Perhaps for slow, transitional flying, but for sport flying, fly in acro. Leave level mode for leveling and position hold.

This board flies so damn well in acro! Why can't we get level mode to actually work? To LEVEL, without drift? The Tarduinos can do it.

R182 comes very, very close. If you want to have level mode as a backup for mistakes, why not set up a mix in your tx that when your cyclic stick is centered, aux 1is on and set it to turn on level. As you move your sticks past a certain point, it turns aux 1 off, putting you in gyro mode. There is also code floating around in the MW forum about doing this for you. That way level mode could be tuned to actually level, and you could fly around with gyros with the safety of level mode. Finally, after a few weeks goodluckbuy shipped out my kcopter board. Yodot Rar Repair Keygen Photoshop on this page. Installing baseflight was a breeze, and it was a matter of replacing boards to get it airborne.

Using default pid values gave me a very stable quad in gyro mode, acc mode needs some attention and mag just did weird stuff. One question though, I usually fly in gyro mode only and die trying to fly like warthox, this board however seemed to lower my throttle input A LOT.

I found myself giving full throttle most of the time to get it climb. On KK board, the very same quad shot up like a rocket. Is there some setting for accro mode so I can do loops and other fun stuff? Good Day All I question about the 'RC Live feed' that are both shown in Naze32 GUI and MultiWii_dev GUI. Are the numbers shown there approximate, or should one accept them as fairly accurate, give or take afew usec's for jitter and tx resolution??? I'm using DX7 with a spektrum satellite, and have set tx throws and menu sub trims and get fairly consistent numbers with my Saleae Logic 8, and have take taken it as close as I can to 1000 usec & 2000 usec. But when I look at the numbers in RClive in the GUI's, the GUI numbers appear a little short of the edge.

Lower edge:- 1071 in Gui's 1005 with Saleae Logic Upper edge:- 1918 in Gui's 1995 in Saleae Logic MidRC is a match. I've attached screen captures of Saleae Logic. I think I have an accelerator mode setup that works for my purposes: 2) if flying in any direction, enabling level mode will level out the quad; 2) it doesn't do anything weird (like wobbling then going off in a random direction). It doesn't fly in ACC all that well (it resists inputs), but I don't want to use ACC mode for anything but FPV emergencies anyway. Gyro mode works beautifully in all the firmware revisions I've tried and that's the mode I'll be sport FPV flying in. Here's what worked for me: 1) pm1's r181 'b' 2) acc_lpf_factor=4, gyro_cmpf_factor=2000 I did try r183, but it brought back a lot of the drunken sailor characteristics and I couldn't dial it out with looptime (1000, then 3000) or acc_lpf_factor (100). I did tweak my frame a bit: 1) I found that my CoG was 1cm too far back.

2) I removed the 10 degree tilt on the motors 3) I soft mounted the FF FC on foam (was hard mounted on nylon standoffs). 4) I added a 150g weight to the front to stand in for the GoPro and vTx I'm very happy with the flight characteristics and satisfied with the ACC mode.

I think I have an accelerator mode setup that works for my purposes: 2) if flying in any direction, enabling level mode will level out the quad; 2) it doesn't do anything weird (like wobbling then going off in a random direction). It doesn't fly in ACC all that well (it resists inputs), but I don't want to use ACC mode for anything but FPV emergencies anyway. Gyro mode works beautifully in all the firmware revisions I've tried and that's the mode I'll be sport FPV flying in.

Here's what worked for me: 1) pm1's r181 'b' 2) acc_lpf_factor=4, gyro_cmpf_factor=2000 I did try r183, but it brought back a lot of the drunken sailor characteristics and I couldn't dial it out with looptime (1000, then 3000) or acc_lpf_factor (100). I did tweak my frame a bit: 1) I found that my CoG was 1cm too far back. 2) I removed the 10 degree tilt on the motors 3) I soft mounted the FF FC on foam (was hard mounted on nylon standoffs). 4) I added a 150g weight to the front to stand in for the GoPro and vTx I'm very happy with the flight characteristics and satisfied with the ACC mode. Calvin Hi martinic Here's what worked for me: 1) pm1's based on r182 2) acc_lpf_factor=100 no test with 4, gyro_cmpf_factor=1000 test with 2000 no difference for me 3) looptime 5000.

I have had all the ESCs previously calibrated. And set the maxthrottle value to 2000 in CLI. Change the board into a different frame/motor setup, lowered P values, but still, when i give full throttle, the quad only climbs slowly.

I don't think its a max throttle issue, the motors seem to spin up higher if i keep throttle up for longer. Any other ideas? You had the esc calibrated for the kk board which does not take into account that you need 1000-2000 throws on your sticks for mw. What do your stick throws show in the gui? You need to treat this as a multiwii setup and follow the setup procedure for that, so get your throws to 1000-1500-2000 in the mw gui then re-calibrate the escs for those values. I redid the test with 183 using exactly the same settings as I had with pm1s r181 'B' version and I do indeed get the same acceptable level mode behavior.

Glad I can run with the most recent baseflight dev version. Gyro_cmpf_factor = 1000 (max. Allowed under r183) looptime = 5000 acc_lpf_factor = 100 Screen shot from the GUI showing all values is attached. ACC is now good (for leveling out and staying put, it fights flying). The ALT hold isn't working for me yet. I get strong vertical oscillations with any P from 8.6 to 2.0.

Unrelated, but what does alt_hold_throttle_neutral do? Had foam on it all along, but maybe it could be sheltered better from light. There is a cover over the FC. Dropping the ALT P to 1.8, leaving I at 0.010 and changing D to 10 did the trick. No oscillations and holds pretty darned well. The level + altitude hold will be great in an emergency if I lose video. Gyro/acro mode is very nice - a huge upgrade from my KK 5.5 blackboard!

Now to install my FPV gear and then work on replacing the KK board on my FPV tricopter with the new KK2! But first I need to go mow the lawn - ugh! You had the esc calibrated for the kk board which does not take into account that you need 1000-2000 throws on your sticks for mw.

What do your stick throws show in the gui? You need to treat this as a multiwii setup and follow the setup procedure for that, so get your throws to 1000-1500-2000 in the mw gui then re-calibrate the escs for those values. My sticks already show 1001-2031 edit: just to be sure, i limited the throw to 2000 and recalibrated the ESCs but it didn't make a difference.

I then put the board on yet another frame and it is now working good 'I think' b/c I never flew it before, but it certainly has no lack of power. Could it be a vibration problem? Techstream Software Cracking. Just came back from the first field test. It flies good, have to work on the mag, but not sure if i ever use it anyway, at least in this quad. Have some questions and am not sure if they belong here or in the MWC thread. Trimming the ACC is: disarmed board, full throttle, use sticks to trim? How do i get more aggressive controls?

Loops and rolls are taking too long, I am used to flying the KK board in acro mode which throws the quad arround on the spot. I am not 100% sure about the firmware, is it a port of MWC for the STM32 platform and all manuals of MWC can be used, or has TC only made it compatible to the MWC GUI but its a complete new codebase under the hood?

I think they have 3 levels of battery out while I only have one, and mine was longer before. Need to fix it, will put on TODO list.

Flew 6 batt packs with new firmware (trying to get it working in the same way as pm1 firmware - still no way) - and i think, batt warning is ok, no need to fix it. Yes, it does it in different way, but sound level is approx the same, just instead of non-stop beeping, you get beep series. Once flew below 9V (was far away from me, my mistake - no need to fly so far away with almost empty pack) - i still heard warning. So, at least for me - this feature is working as expected. Just do a diff of r181 and pm1's source, you will see its like 4 lines of actual changes, then compare same location in latest baseflight, you will see same changes.

There's no technical explanation to why it would be different. Im not complaining, just added this short note about batt. And i believe, that all changes we're ported, so something must have changed with my frame. Didn't crashed, so dunno what's different, but will find anyway (yes, all bolts checked, etc). Oh, and the problem - much bigger 'vertical drift' with the same throttle curve, not horizontal.

I mean, quad/hex still floating up/down (without baro) at the same throttle value. As i do not have ideas - why - i will keep checking (maybe reflash back to check if it will fly 1:1 with older firmware) and return later;-). Finally, I have listen the Tricopter, special Hex and vtail users.:-) I modded the android Configurator to be able to choose unified Pitch/roll Pid settings or not. Update to the play market minutes ago (so it would take some hours to be really upped) or you can fetch the zip in my blog. Version is 1.42. PhalanX send me an email, I will send you the.apk file directly if you have problems with the.zip or cannot access play.google market. I cannot upload to rcgroups because.apk files are forbidden as attachment.

Kelly Clarkson's 'Love So Soft' Hits No.