Hi all, Does anyone have a link to a glossary list of all the voice commands / data feedback / errors that the Graupner transmitters can give and what each one is referring to? Thanks.
This is the closest I found after a quick search: http://www.mkmanual.com/graupner-mx-20#TOC-Voice-output There may be other information sources. Andy.
Hi Andy, Thanks ... But ... What i'm looking for are some of the possible commands that the transmitter could provide at startup. There are 2 or three I get before starting the motors ..for the life of me I can't remember them. The bird is on the bench at the moment getting a BL repaired. So I'm trying to stock up on valuable info / resources ... I saw that link but not what I was looking for. Will keep trawling. When I find it, I'll be sure to post it here!
OK, IMHO Andy J-L isn't the only guy with forensic skills on this site. I dusted off my long-forsaken geek skills and took a look at the .VDF files that contain the voice messages. It seems there is a list of them, and they're sent over the downlink as text (that's quaint), and a table is created in the Graupner corresponding to voice prompts. Here's the list that I created. I have no idea how many of these are actually represented in the voice files, and what the conditions are for them to be spoken. But I would guess that there's a corresponding table somewhere in the MK source code. I'm not feeling adventurous, so I'll leave that up to somebody else. So here we go...stand by for a Very Long Posting. +01.BEEP_START+02.BEEP_SETUP+03_BEEP_TIMER_GO+04.BEEP_CLKBEEP3+05.BEEP_CLKBEEP2+06.BEEP_CLKBEEP1+07.BEEP_CLKHIGH+08.BEEP_CLKSEC+09.BEEP_TRMCEN+10.BEEP_TRMMOVE+11.BEEP_JOG_VALUE+12.BEEP_JOG_VALUE+13.EEP_JOG_INCMOV+14.BEEP_JOG_DECMO+15.BEEP_JOG_UP+16.BEEP_JOG_DN+17.BEEP_WARNING+18.BEEP_POWERDOWN+19.BEEP_JOG_KEY+20_302_error_cali+21_303_error_rece+22_304_error_data+23_305_error_navi+24_310_error+25_306_error_comp+26_307_error_sens+27_308_error_gps+28_309_error_moto+29_329_max_temp+30_313_altitude_r+31_312_waypoint_r+32_311_next_waypo+33_316_landing+34_318_GPS_fix+35_301_undervolta+36_319_GPS_hold+37_320_GPS_home+38_321_GPS_off+39_17.BEEP_WARNIN+40_300_Mikrokopte+41_wCapacity+42_324_carefree_o+43_314_calibrate+44_328_max_range+45_wMaxAltitude+46_wAltDown1+47_wAltDown2+48_wAltDown3+49_wAltDown4+50_wAltDown5+51_wAltUp1+52_wAltUp2+53_wAltUp3+54_wAltUp4+55_wAltUp5+56_wCurALT_20m+57_Mikrokopter_of+58_Altitude_on+59_Altitude_off+60_wCurALT_100m+61_323_carefree_o+62_327_down+63_326_up+64_325_hold+65_322_GPS_on+66_317_follow+67_315_take_off+68_wReceiver+69_Mikrokopter_wP+70_0_eTxVolt+70_eModelTime+71_eBatteryTime+72_eStopwatch+73_eRunTime+74_eTimer1+75_eTimer2+76_eTimer3+77_eLapTime+78_eCountdown+79_eUpTimer+80_eCurrent+81_eServoTemperat+82_eServoPosDiv+83_eServoCurrent+84_eRcvVolt+85_eRcvTemp+86_eRcvStrength+87_eRcvLowVolt+88_eVoltCell1+89_eVoltCell2+90_eVoltCell3+91_eVoltCell4+92_eVoltCell5+93_eVoltCell6+94_eVoltCell7+95_eVoltCell8+96_eVoltCell9+97_eVoltCell10+98_eVoltCell11+99_eVoltCell12+100_eVoltCell13+101_eVoltCell14+102_eSensor1Volt+103_eSensor2Volt+104_eSensor1Temp+105_eSensor2Temp+106_eFuel+107_eAltitude+108_eMaxAltitude+109_eMinAltitude+110_eRPM+111_ePowerVolt+112_ePowerCurr+113_eSpeed+114_eDistance+115_eDirection+116_eAltDifferenc+219_uPoint+220_uVolt+221_uAmpere+222_uDecibel+223_uMiliseconds+224_uDegree+225_uPercent+226_uRPM+227_uMeter+228_uMinus+229_uPlus+230_uKilometer+231_uMeterPerSec+232_uMeterPer3Sec+233_uMeterPer10Se+234_uKilometerPer+235_uOclock+236_uMiliAh+237_uMiliLiter+238_uMinutes+240_uSeconds+241_uHour+242_eMotorrun+243_eFlighttime+244_eFrametime+245_eclk1+246_eclk2+247_eclk3+248_Number_of_sat+249_Compass_dir+250_home_directio
huh .... nice one! Forensic skills noted! I'll filter through those and try make sense of them! Much appreciated.
How do you feel about using Understand to look at C code, Steve? Need someone else who can dig into MK code! Andy.
I'm not sure how useful I'd be. It's been 10 years easily since I've done that. But what the heck...it's all in English, right? Oh, wait... What do I need to do to get access to the code? Do they use subversion?
I always was a "start with grep, then set a few breakpoints in the debugger" kind of hacker. Not easy to do when your copter's hovering above your head, I guess.
Yeah. Subversion. http://svn.mikrokopter.de/ The thing I've not yet been able to find (although had to give up looking for owing to lack of time) is where the MK Tool Read/Write are handled -- does setting ParamSet to, say, 3, in MK Tool achieve the same effect as making ParamSet 3 active (left stick -> 10:30, right stick to noon)? Better brush up on your German (or your Google translate!) Andy.
My brother speaks German, but not C. And as a Jewish man, German kinda rubs me the wrong way, if you know what I mean.
Hmm. I think what my assistant did was just select the entire folder just using a web browser and drag it....something counter-intuitive, I know. Let me find out what he did. Andy.