hey guys just wondering if someone can help me out i fly a cinestar 8 with mk when i turn it on and calibrate it gives me 5 beeps 3 normal ones and 2 fast ones, its not normal not sure what it means? then if i turn the copter on some of the engines dont turn on! they are different engines every time. if somenone has any idea of what could be happing please let me know chris bragg Chris Bragg Costa Rica
Can you connect up with MK Tool to either the Navigation Control Board or the Flight Control Board and verify on the Easy Setup window two things: 1. Above the "Help" button on the bottom of the page, there should be a number in a box just to the right an up/down arrow. What number is there? It should be three. 2. Also, just above that, for the Mixer-SETUP, it should be Octo2. Do you see that there. Thanks Andy.
Andy, thanks for the help, just found out that my recever changed to jetti by it own, once i changed that i got telemetry and all engines are working but my recevier indicates magnet error 22, what does this mean or what could this happen. thanks chris
Andy, just verifed what you told me the numeber over the help button is 5 should i changed it to 3 an i do have octo 2 thanks
Hi Chris: Check here for error codes: http://www.mikrokopter.de/ucwiki/en/ErrorCodes#A22_.22ERR:_Magnet_Error.22 (Might want to bookmark it as you'll be going back!) You need to do a compass calibration. http://www.quadrocopter.com/feed_detail.asp?id=200 (I'd suggest you are a bit further away from cars and metal railings than Casey was in the video, but what do I know? ) You have parameter set 5 select. You need to select "Beginner" parameter set 3, so select 3 in that window and "Write" the configuration back to the copter. Andy.
hey andy, thanks for the help i did all you said and it worked fine but after one flight igot a different error this time it is 17: I2c fc bl ctrl not sure what this means maybe you can help me out thanks chris
Per the link in Andy's post: 17 "ERR: FC I2C" Cause: the I2C communication to the BL-Ctrls is disturbed Solution: check supply of the BL-Ctrls check I2C-cables (mixed C and D?) check addresses of the BL-Ctrls disconnect single BL-Ctrls to find one defective Josh
Chris: Yeah, you can expect to see some of these I2C errors on each flight. Initially they're caused as the boards are initializing. But it's OK as long as you don't see them occurring during the flight -- the number should stay constant. Andy.
josh , thanks for the help my board is completly in red and my engines dont start so not sure what to check
I would check the molex connector from the FC to the PDB. Try unplugging and plugging back in and see if that fixes it. Josh
Can you clarify what you mean by "my board is completely in red" please Chris? The Flight Control board? The BL-Controls on the PDB (are they all red)? Thanks Andy.