MultiWii

doughboy

only 1 pulse is needed, and its based on pulse width multiples of 100us. I think this is more exact than the original reverse engineering based on frequency. I wrote a test sketch using timer0 interrupt for arduino UNO and sent GgBbRrZz in arduino serial monitor and these are the pulses captured by ...

doughboy

how about line 100 in MultiWii.ino? I think that is needed for GUI.

doughboy

as far as using interrupts, timer0 is available if using quad for promini (I only looked at promini code since I have atmega328). I think there is one counter left if you have a quad + servo for camera stab.
is the control signal based on frequency and not pulse width?

doughboy

I think for what you want to do (manual aim for camera), you need to have 8 channel RX to use aux3 and aux4 (assigned to potentiometers on your transmitter) to control camera aim manually. In order to do that with your FC, your RX must use PPM sum so all 8 channel RX data goes through one pin only (...

doughboy

compile error if SERVO_MIX_TILT enabled

I know this is dev branch, but please check more thoroughly before checking in.

doughboy

if inflight_calibration is enabled, compile failed.
I think Sensors.ino line 376 missed the update.

doughboy

I dd the merge and it works fine. I only have gyro+accel and my cycle time is around 2500-2600 only. Cycle time increased to 2800-2900 with pilot lamp. Does the cycle time get too high with more components like GPS, Baro, etc.?

doughboy

is this feature not in the main shared code?

I just got my pilot lamp. smaller than I expected

doughboy

I'd say it is the second developer's responsibility (and common courtesy) to credit where he copied the code/idea from, and not the repository owner. So don't blame Alexinparis

doughboy

g_serial = new Serial(this, portPos, 115200); to g_serial = new Serial(this, portPos, 111111,'N',8,2.0); remember, when you run into errors, you must reset the xbee by unplug/plugging the one on pc, and resetting the FC before you start your next test. make sure you changed the FC baud rate to 11111...

doughboy

The "never connect" is because the pin is either on (beep) or off (no beep). In other words, you can't hook a speaker directly to it, it's only an on/off switch which is exactly how my buzzer works. I'm pretty sure the never connect is due to the current load. it is a given the output is ...

doughboy

I think the atmega spec for the pin current output is total for all pins, and not for one pin. I can't remember exactly the value, but there is definitely a limit for sure. Like if it says 50ma output current on one pin, does not mean it can output 50ma on each of the 20 output pins. Besides, the mu...

doughboy

for those not familiar with Process, within the sketch folder you've got to create a <sketch>/libraries/controlP5/library/ folder and rename controlP5.jar_ to controlP5.jar I think I did that at first, then I realized there is an import library feature in the Processing IDE menu that will do all th...

doughboy

It may need refinement, I just got the code for rendering the circle working.

attached the source.
change starts at line 1130.

ignore the change in InitSerial to use 111111 8n2, I needed that change for my xbee connection.

doughboy

I modified the level indicator from this

to this

sample video
http://youtu.be/5XqmHboTDRo

doughboy

I get this error: avrdude: stk500_recv(): programmer is not responding you can get that error due to the DTR line is disconnected. - make sure the DTR line from FTDI is connected to RESET pin on the FC board FTDI connector. or the FC bootloader is gone. The DTR or reset is not needed for multiwii c...

doughboy

Excellent. That worked now. So the last bit of the puzzle. Can I use the USBAsp with the MultiWii Conf program as well? unfortunately, no. are you sure the ftdi is broken? unless you see physical damage like it got stepped on, I can't imagine it to not work. now perhaps when you were trying usbasp ...

doughboy

Doughboy, just for clarity, how are you connected the usbasp to the arduino? In other words, what pins etc. I used to use 6 single jumper wires to connect the +5,gnd,rst, mosi, miso, sck to the arduino. but I won an auction for one of these for $0.65 so have been using this since. https://encrypted...

doughboy

yes, you can ignore that. its just a warning and not an error. you just flashed successfully using usbasp! note that once you program using usbasp, your bootloader is gone. in order to use ftdi or usb again, you must select UNO as board, then select burn bootloader (with usbasp connection of course)...

doughboy

I use usbasp, but I built my FC board myself, but it should not be different from Crius or any atmega328 based FC board. in IDE, you selected board as UNO and programmer as USBAsp? If you selected USBAsp, it should not ask for a serial port. Another option is to add this entry to boards.txt file in ...

doughboy

we can use smaller bootloader m this link is for an atmega328 bootloader. so make sure you don't use this on leonardo. in fact, that info is old, because the optibootloader for the atmega328 is even half that at 512 bytes only. icsp programmer costs around $3-$4 on ebay. so there is no excuse not t...

doughboy

see my post here

viewtopic.php?f=18&t=2415&p=23592#p23592

doughboy

ok, after struggling with this over the weekend, I finally am able to get mutiwiiconf to work with xbee. only after skimming through a few of the thousands of posts on digi forum, I learned that there are two ways to get xbee to work at 115200. first is to set the host to use 111111 baud rate, secon...

doughboy

the 64 bit GUI does not work because rxtx serial library only works in 32-bit mode. If you do a search, someone built a 64 bit version of the library. I have not tried this, but it may work if you replace the rxtx dll with the 64 bit version.

doughboy

I found this post
http://forums.digi.com/support/forum/vi ... 7255#21770

apparently, xbee transmission problem at 115200 is not a new issue. you find tons of post in digi forum about this.
from the article, the best solution is to use 111111 baud rate. I tried that and result was not any better. I'll try that again. then I'll try using 2 stop bits.

doughboy

if the leonardo works the same way as the UNO or promini, you can program via ICSP and get the full 32k. you lose your bootloader though, and you always have to program via ICSP unless you reburn the bootloader.

doughboy

I know this is a little off-topic but it seems very interesting: m it is still related and confirms what I said. you need to write your own program or modify the way the mw gui use of serial commands. I'm sure mw gui was designed without xbee in mind, and that is fine. right now, the way it is code...

doughboy

only the 32bit gui works. of course nobody will tell you that and just let you find out for yourself, just like everything else with multiwii

doughboy

ok, xbee connection works at 9600 with wingui, I have not tested any baud rate in between. you can see there are a few packet errors, and win gui seems to be able to recover. processing gui still does not work at 9600, I'm pretty sure due to the way it sends all the commands in series. http://i1193....

doughboy

in order to work with xbee, either the gui must be enhanced to support it by slowing down the requests, or you need to write your own client to do that. the serial LCD used for configuration and telementry don't have this problem, as they only deal with smaller packets of data. I will test hooking u...

doughboy

I have confirmed the problem is due to the gui requesting too many bytes at once than the xbee can handle. I did a loopback test on xbee and it works on 128 bytes at a time, I tried 256 and it times out. the gui sends a series of commands at a time, instead of doing request-response-request-response...

doughboy

I monitored the signal on the xbee/FC side, and I can see the initial request/response exchange was perfect. But starting with the first command of the next set of request, the FC received an invalid command 22. the capture below shows FC received a command 22, and responded with error unknown code ...

doughboy

You will know it is working when the ARM light blinks and if you have a buzzer, it will beep when complete.

doughboy

Or if you move, simply press the reset button. Or use sticks to calibrate gyro with throttle at lower left and pitch at min (the stick combination for v2.1). The calibration takes about 1 second.

doughboy

I'm trying to get a baseline timing of the signals using a logic analyzer. signal coming from FC is 93.5us per character http://i1193.photobucket.com/albums/aa352/jerrysy/quad/fromFC_zpscc03526f.jpg signal coming from PC is 86.75us per character http://i1193.photobucket.com/albums/aa352/jerrysy/quad...

doughboy

The APC220 works transparently on current Multiwii here. Just set the APC220 to the max. Baudrate (56000) via its software config tool and modify Multiwii Serial0 Baud to the same rate... I can get MWii to run Perfect with APC220 @57600 and MultiWiiWinGUI. But only partial with the Processing Gui! ...

doughboy

I undid all my changes and ran the program and this is the error I am getting invalid checksum for command 240: 96 expected, got 224 <240 30> {150302315030238545128161571112812820845142080701010040250100128128128} [224] ––U-€€€-PF d(úd€€€ invalid checksum for command 113: 207 expected, g...

doughboy

It works probably due to using the lower baud rate. I'll try to lower the xbee baud rate.

kaik, I take it you change the multiwii gui baud rate to 56000 also right? can you describe how you changed the baud rate? it is hard coded in the program to 115200.

doughboy

that calculation is for the UART prescaler. If you substitue baud 115200 and f_Cpu 16000000, you get 16 (using integer calculation). the standard calculation is (((F_CPU) / 8UL / (baud)) -1UL) which gives you a prescale value of 16. Now I know for a fact in Aeroquad, they use baud rate of 111111 to ...

doughboy

ok, I studied the multiwii code a little bit, and it uses its own home rolled uart code. this static void inline SerialOpen(uint8_t port, uint32_t baud) { uint8_t h = ((F_CPU / 4 / baud -1) / 2) >> 8; uint8_t l = ((F_CPU / 4 / baud -1) / 2); I think is incompatible with xbee. the standard arduino li...

doughboy

What is m328? Or do you mean atmega328

doughboy

I'm going to venture a guess that the base or reference gyro and acc orientation has something to do with how it is oriented in Wii motion plus and nunchuck. I agree that at first glance it makes no sense, I think someone should document this reference axis oreintation in the wiki. This will clearly...

doughboy

it must be a multiwii software thing that causes all this orientation mismatch

according to 6050 data sheet, the gyro and acc axis is the same

doughboy

to make things more confusing, the 6050 chip contains both gyro and acc, yet their orientation is opposite! #if defined(GY_521) #define MPU6050 #define ACC_ORIENTATION(X, Y, Z) {accADC[ROLL] = -X; accADC[PITCH] = -Y; accADC[YAW] = Z;} #define GYRO_ORIENTATION(X, Y, Z) {gyroADC[ROLL] = Y; gyroADC[PIT...

doughboy

Look, you can arm your copters anyway you want. As long as I can disable it. I have to say personal preferences should be kept out of the main code. After all, this is open source and anyone can check out and customize the heck out of the code to suit one's preference. But we can already disable ar...

doughboy

fiendie wrote:Look, you can arm your copters anyway you want. As long as I can disable it.

I have to say personal preferences should be kept out of the main code. After all, this is open source and anyone can check out and customize the heck out of the code to suit one's preference.

doughboy

I won't say it's useless, but it is definitely redundant. I think it is used in in flight acc calibration right? Which I think you wrote? I think if space (resources) is considered a premium, I would not mind if the arm option is just completely removed. You can still do in flight acc calibration vi...

doughboy

I don't know why they use 3.85v as the default, as it does not make sense. the resistor divider is 51k and 33k, so total resistance is 84k. if battery is 12.6v, then A3 pin should get 12.6 x 33/84 = 4.95v. the default value in config.h should work fine, you will need to change only if you are using ...

doughboy

thats a great link. did you actially get 3.85 volt on middle of resistor divider? I did not know of this vbat calculator, but the voltage reading shown on the gui is exactly my actual battery voltage. and my mid point voltage (on pin A3) is closer to 5v (I think 4.96). anyway, just try that vBatvalu...

doughboy

lol. I think programming to nimh for that micro quad makes more sense since it uses 2s battery and I think users experienced one motor shutting down due to this hence they advise to change to nimh. I doubt it is the case for this thread, since OP uses 3s battery. simonk, if I am not mistaken, omitte...

Search found 252 matches