timecop wrote:OK, so does manually sending something like "$PMTK251,115200*1F" to your gps dongle witih usb>serial converter switch it to 115200 baud mode? If you're getting data at 9600, there are two possibilities:

when using gps_type = 0 (raw nmea), you have to pre-configure the GPS to the gps_baudrate value first - there's no automatic way to set that, so that explains why no data at other baudrates with type = 0.

Yes, using a Sparkfun FTDI I can set the baudrate with $PMTK251 strings, set the refresh rate with $PMTK300 strings and I do get data back after.Also working is MiniGPS to set everything(only thing I can't do is store default settings to my liking, the module I received has flash write protected - how lucky can you get ....)

If you re-install the 115200 5hz firmware, you will get those settings installed, and also have opportunities to change the settings using Mini GPS. There are some firmware downloads on Eosbandi's gps site.

I have a Question about Telemetry,I have a Turnigy 9x with Frsky on its way and have found al the things i need to do to make Telemetry working from my Naze32.The FrSky converter from AbusMark (TC) is already mounted on.One thing is just not clear to me there was alot of info on the Telemetry on RCGroups but no direct answhere on the Voltage Meter.

Is the Naze able to send the Lipo Voltage (if connectect ofcource) to the Frsky unit?

And i realy want to experiment with GPS and i see alot of units passing but wich do you guys recommend to work with the Naze?

Battery voltage can be transmitted. Currently, it's not, but I'm going to add this real soon, because I already have some fixes queued for telemetry. FrSky LCD can view 2 sensors - the amp/voltage sensor which reports only one voltage and the "cell" split voltage, obviously I can't find individual cell voltage, so I'll be emulating the current/voltage sensor output.

The value is taken from VBAT sense on naze32 - so you'd have to connect that to your power distro/battery and configure vbatscale in cli until you are getting correct readings. default divider value should work though, to +- 0.2V or so.

Scotth72 wrote:If you re-install the 115200 5hz firmware, you will get those settings installed, and also have opportunities to change the settings using Mini GPS. There are some firmware downloads on Eosbandi's gps site.

I could probably to that. However I (and probably other MTK users) would much rather have the Naze send the needed settings to the unit on startupWould simplify matters a lot ..

I think I nailed the GPS stuff (for those who are getting a lock, at least) with latest commit.http://code.google.com/p/afrodevices/so ... tail?r=209Still haven't looked at MTK stuff or at people having trouble getting actual hardware to work - that is likely something about your config.

timecop wrote:Bootloader shorting shouldn't be necessary unless you killed the existing firmware, the proper/easy way is sending 'R' then doing flash load.

... hm: for serial / CLI I use hercules software. Entering ## to sende the # works fine, but R or RR never worked. Maybe I should enter #R to tranfer this R ?

I have a single R in one of the hex boxes at the bottom then all i have to do is press send.

RAY

thx ray ... but i could not flash after sending the R ... so I tried to replace the uart...dll and made a full system scan for it (Win 7)... and the search result was, that in Nicohd's great tool "Naze32 AIO" (win: http://www.rcgroups.com/forums/showthread.php?t=1667516 ) there is a stmloader (a command line version?) integrated in his GUI ... it works; .hex is selectable, says [updating 1-... s] in a button text while flashing ... this is perfect. So: solved.

@ GPS Task Force : ... after flashing r209 I saw, that there is a change in the GUI: now there is 'ANGLE' + 'HORIZON' ... and my 3 [ACC] toggles where not set after upgrading + loading the (old) config files ... so take care for ACC = HORIZON (I think [?]). What is ANGLE?

Attachments

Last edited by LeoWie on Sat Sep 08, 2012 6:51 pm, edited 1 time in total.

Also please make sure to 'defaults' in CLI after loading latest revision. I think I changed something in settings and maybe forgot to bump config struct version again - on 2 of my test models I got randomized channel MAP as a result, could be other side effects too. Better start off with 'defaults'

Test Report r209 Summary: ... it was a windy day (12+km/h ...) and Rabbit GPS on a Naze32 with Test r209 ... WORKS FINE.

... and more (sorry @ Rabbit): The Naze32 GPS Hold + Home (with a Rabbit GPS Module) is better than that from Rabbit FC ever was.I am ABSOLUTELY SURE in this point, because I have been testing at this location 50+ times with all my copters ... and 3 different Rabbits.

... and after 2 lipos something inside me began to trust in this GPS software + hardware configuration: there was no problem.

In the moment I can not say, if there should be adjustment in some GPS parameters (there was too much wind).But if there is wind like today I want the setting like it is.

I finally upgraded my archaic radios systems, added a Spektrum module to my 20 some odd year old JR PCM10. Planning on using the satellite RX. Where's a good place to pull 3.3 volts off the board to power the satellite?

LeoWie wrote:... and more (sorry @ Rabbit): The Naze32 GPS Hold + Home (with a Rabbit GPS Module) is better than that from Rabbit FC ever was.I am ABSOLUTELY SURE in this point, because I have been testing at this location 50+ times with all my copters.

... and after 2 lipos something inside me began to trust in this GPS software + hardware configuration: there was no problem.

In the moment I can not say, if there should be adjustment in some GPS parameters (there was too much wind).But if there is wind like today I want the setting like it is.

With a gps module connected should I expect the 'GPS' to be green in multiwiiconf (yellow arrow in pic) - I'm guessing not and that it's a case of waiting for a lock to see any confirmation within multiwiiconf that gps is working?

not sure if I've got the tx and rx the right way round and can't get a lock indoors...

Doesn't look like you're even connected in that pic, but yes, if GPS was detected (i.e. its receiving nmea/ubx/whatever data at the rate specified in settings) then GPS would be green and the NSEW compass mark would blink at the rate the data is coming (5Hz if it was configured as such). If you messed up rx/tx, if baudrate for gps_type=0 is wrong, etc, it wouldn't detect it and gpb box would be unlit.

No, no changes to MAP command. The channels are just skipped. You won't have AUX3+4It might not be so clear, but 1234 in map command is NOT the channel order, its the order of aux channels.The actual order is the way pins are connected.

I'm missing the obvious somewhere - please kick in the right direction...

First I've set my gps module via minigps software to 5Hz and 115200 and can see it outputting stuff:

Flashed the latest firmware, into cli to set all my usual settings + feature gps. Defaults of gps_type=0 & 115200. Save everything, unplug copter from pc.Power up quad (gps module powered by one of the f20a esc bec's). Plug in the usb, open the com port in multiwiiconf and the GPS isn't showing. So close port, disconnect and power everything down and swap tx/rx cable going from module to naze32. Power up, connect usb and open in multiwiiconf and still nothing. I've repeated this with gps_type = 2 and still nothing.

Am I missing a step somewhere or do I need to change the stuff being sent by the module?

Maiden + GPS test report:- Maiden Flight: was very good, just yaw's P maybe a little too high (had no time too change it on the field, ... too dark).- GPS test PWM receiver r212 development test-version: GPS Hold: workes fine, just a little param tuning to do (have to learn what params to change first ... makes circles / spirals closer to the desired point ~ o.k.).GPS Home: there is a bug I think: copter begins to turn to one side (left) and has some problems when crossing the point ... looks like copter gets confused data sometimes: wants to yaw ... had this 5+ times, 3 times I had 3 harder landings when testing GPS Home (remark: with a copter like this / < 200g I think we have to redefine the word 'crash' to 'falling down softly' or something like this: there was no damage, even no props. I think it's close to the point where the feather effect takes place). Possibly it has to do with the a little too high Yaw P(?) ... problem: it was a copter maiden + GPS test in one.Never a problem when GPS switched off ... and the new Baro / Height Hold works fine.

~~~ edit 2012-09-10 ~~~ Test report for r213: exactly like r212

Attachments

Last edited by LeoWie on Tue Sep 11, 2012 6:22 am, edited 17 times in total.

Just tried my MTK (FMP04 breakout from ohararp http://ohararp.com/products.html) which was pre-configured to 115200/10Hz output and it works with gps_type=0 (nmea). By "works" i mean compass blinks and serial data is incoming.

I see something on the flytron page about needing a hack for 3.3V operation, I wonder if that's related?It's pretty hard to have serial "not work" so I'm going to have to shrug this one off as 'user error' unless someone has better ideas.