Motors won't start by tx but have full control over them in mk tools. Just added GPS and navi. I have disabled them both and have connected straight to fc with mk tools. No errors. I calibrate and then do engine start and nothing happens. Any thoughts??
HI Devin Let's start with some simple stuff first. So you are saying that everything was working until you wired the nav and GPS? Are you saying that they are not even wired to the flight control board or that they are wired but disabled in the software? If you have them wired up do you have the check box checked that says you have to have a SD card in the navigation card on startup? Have you checked to make sure the receiver is still bound to the transmitter? I would also verify that your Channels 1-4 are working correctly in the channels tab. Make sure they are responding correctly as you move the sticks.
Hi Dave, Thanks for speed response! I had everything working fine....added gps and navi and had everything working yesterday, (motors would start and stop and cine would repond to basic commands but it was raining so didnt fly) ....have flown just manually without gps for last 9 months ....tried to start up today... no luck.... so i disconnected wires to gps and navi and disabled gps in mk tools. All my channels work according to mk tools. no boxes are checked. Am able to calibrate gyros and acc but cant go to next stage of motor start
oh to add.... I have the new ff motor control set with IC2....all works. All motors work under mk tools
Normally the simple stuff that I know of that prevents start ups would consist of: 1. SD card not in Navigation SD card slot or it pops out of the SD card slot by accident. 2. No GPS fix 3. ACC not calibrated 4. Gyros not calibrated 5. Receiver becomes unbound 6. TX channels become uncalibrated preventing the left stick to hit -100 and -100 to trigger start electronically. 7. Compass not calibrated #1, #2, and #7 shouldn't apply to you if you don't have the nav/gps wired up. I assume you checked your battery and tried another one? You could reinstall the firmware on the flight control board if you run out of ideas to try but somethings telling that there could be something with the I2C converter that could prevent this if something with it is not absolutely right? Gary would know and I'm sure he will chime in.
HI, Everything has been checked that can be checked.... Yea I just upgraded to latest version of fc and i wonder if it is not compatible with I2C conertor.....have to do some searching
Devin: Just to test your theory, try downgrading back to the previous version and see if the problem goes away. It's a bit irritating to have to do, but it would be proof positive -- that said, I believe Gary's on version 2.0 (which beta'd as 0.91j if my memory serves me correctly). Andy.
I would be shocked if 2.0 was the issue because Gary's been flying the Beta for a while and 2.0 is essentially the Beta.
Likely the motors don't start as the default is the 2 stick method for safety reasons. Left stick to lower right, then right stick to lower left. Outlined in the 2.0 instructions. Also as Dave points out depending on your configuration values may not start if you don't have the minimum GPS sats.
Hmmm didnt know there was a new stick method ....now just to find instructions..... Here they are for quick reference: http://www.mikrokopter.de/ucwiki/Fi...gabe_des_Kanals_bei_den_wichtigsten_Schaltern
VERY unwise to load a new firmware without reading and fully understanding the update notes!!! All sorts of nastiness could have happened.
Howard: Lesson Learned....first time updating....so didnt know protocal Was able to upgrade fc to 2.0 but now can not get a connection with NAvi board....any suggestions.....even tried downgrading back to earlier versions and no luck.....so fruastrated
Devin it's a good idea before an upgrade to do screen shots of every MKTool screen. You will find with the updates it's not like a computer update. Many of the settings will get reset to default value and unless you check every screen against your last known good configuration you may get an unhappy surprise on the next flight. Also carefully read through and check off each of the changes that are included on the wiki instructions. Slow and methodical and check it more than one time.
The other option you can consider as a possible alternative to Gary's suggestion (and I'd recommend this only for those with geek in their heart), is to save the current settings using MK Tool. This creates a file of type .mkp -- but it's just a plain ASCII text file so you can read with with Wordpad, etc. It just stores all of the settings in sections that correspond to each of the screens. You can even use Microsoft Word's "compare documents" feature to compare your previous saved settings to your currently saved settings to you can see what's changed. Note that occasionally MK will alter the contents of the .mkp file so resist the temptation to bring forward your previous settings by loading the previously saved .mkp file. Bad Things can happen. That's why, for example you'll see a warning like this: Compatibility Note: the challel numbers were changed - Do not load saved settings from older version with the KopterTool! See http://mikrokopter.de/ucwiki/en/Firmware-2.00 Also note that there are five independent parameter sets for MK Tool. Most people work with only Setting #3. But if you use more than #3, then you need to set all five correctly to bring them forward to the new version. Andy.
Andy is absolutely correct, at least if you are a computer geek . I am much simpler and strongly believe that a picture is worth 1000 words especially if I have to read them in something as archaic and so 70's DOS like, you do know what DOS is (Dinosaur Operating System), as Wordpad in ASCII. Seriously Andy we are in a new millennium where we have gotten rid of green screens and eye shades
MS-DOS is the first known computer virus. It started life as Q-DOS (Quick and Dirty Operating System). Actually a picture is worth several thousands of words of memory. As for the American Standard Code for Information Interchange (ASCII), yeah, I'm afraid it is archaic. People really should be using Unicode, but what can you do, eh? But Gary's right. The data in the .mkp file is a bit hard to understand [Setup]Name=EasyIniVersion=4GlobalConfig=107GlobalConfig2=34GlobalConfig3=81[Channels]Nick=3Roll=2Gas=1Gier=4Poti_1=7Poti_2=6Poti_3=5Poti_4=8Poti_5=9Poti_6=10Poti_7=11Poti_8=12Receiver=6MotorSafetySwitch=0[Stick]Nick_Roll-P=6Nick_Roll-D=10Gier-P=4ExternalControl=0[Altitude]Setpoint=255MinGas=30P=20Barometric-D=40Z-ACC-Effect=30Gain=15HoverVariation=1GPS_Z=0StickNeutralPoint=0MaxAltitude=150 ::