EOSBandi wrote:The vendor ID which is set in the module. PA6B made by Global-Top, and they wrote the 1.9 firmware FMP04 made by FTech and they did not wrote any firmware
A1.5E is an NMEA only firmware.... the latest fw for your module is the 1.3-(v1.6) for binary mode. (it also made by Global-Top but did not check for vendor ID)
Is there a way to change the vendor id? Or maybe we can patch the firmware?
Hi ! Yes I know. Only with i2c-gps, and it will be fixed with the 2.2 release of the i2c-gps... BTW. 665M is usually more than LOS and flying without LOS is not legal in many countries.... EOS
EOSBandi wrote:I just committed some rework on the HMC5883L gain calibration (init). The code is based on Fabio's FreeIMU code and I think this is as good now as it could be on this platform. After some experimenting I decided to keep the current offset calibration method (MAG DANCE) since the ellipsoid to sphere method did not gave significantly better results, but added difficulty to the calibration process. I tested it but i would appriciate if somebody will took a look.
Hi EOSBandi,
I have tried this new solution but after set of calibration attempts I couldn't get linear values... e.g. if on north it shows 0 degree, for south it's ~165, but not 180 With old calibration non-linearity was max 3-5 degree for all directions...
Probably at my location ellipsoid much elongated and old calibration was closer... What do you think?
Hello can please help me someone to take my GPS Modul module"I2C PA6C GPS + LLC breakout board 3, 3/5V by Drotek" into operation? I read a lot of threats here, but I’m still unsuccessful. I’m using the flight control board"MultiWii 328 p flight controller w/FTDI & DSM2 port" from Hobbyking I get only I2C errors and no single satellite in the MultiWiiGui. If I connect the the GPS Modul with the FTDI and do not cross RX / TX by using some extra cables, I see 8 satellite with the "mini GPS tool V1. 7. 1" (I select115200 baud to access.) I tried to put the I2C_GPS_NAV on the GPS Modul by using the Arduino 1.01, but at the end of the transferring process I get the error “avrdude: stk500_getsync(): not in sync: resp=0x00” Before I do that, I had to open the solder bridge on the GPS Board. Beside this point I'm not shure if the step is realy nessesarry, because drotec postet at the description of the Board following:
"Bootloader and firmware of Atmega328 already flashed" "Firmware of GPS is configured with 115200 Baud and 10 Hz parameters"
In the config.h of the MultiWii 2.1 I did following changes:
EOSBandi wrote:I just committed some rework on the HMC5883L gain calibration (init). The code is based on Fabio's FreeIMU code and I think this is as good now as it could be on this platform. After some experimenting I decided to keep the current offset calibration method (MAG DANCE) since the ellipsoid to sphere method did not gave significantly better results, but added difficulty to the calibration process. I tested it but i would appriciate if somebody will took a look.
Hi EOSBandi,
I have tried this new solution but after set of calibration attempts I couldn't get linear values... e.g. if on north it shows 0 degree, for south it's ~165, but not 180 With old calibration non-linearity was max 3-5 degree for all directions...
Probably at my location ellipsoid much elongated and old calibration was closer... What do you think?
I have tried this new solution but after set of calibration attempts I couldn't get linear values... e.g. if on north it shows 0 degree, for south it's ~165, but not 180 With old calibration non-linearity was max 3-5 degree for all directions...
Probably at my location ellipsoid much elongated and old calibration was closer... What do you think?
thx- Alex
Did you set your magdeclination ? EOS
Of course! But in any case magdeclination set only linear correction, but I have talked about non-linearity, i.e. when rotating for 180 degree from any position you can get yaw-diff 160-165 degree instead of 180...
majoo wrote:Hello can please help me someone to take my GPS Modul module"I2C PA6C GPS + LLC breakout board 3, 3/5V by Drotek" into operation? I read a lot of threats here, but I’m still unsuccessful. I’m using the flight control board"MultiWii 328 p flight controller w/FTDI & DSM2 port" from Hobbyking I get only I2C errors and no single satellite in the MultiWiiGui. If I connect the the GPS Modul with the FTDI and do not cross RX / TX by using some extra cables, I see 8 satellite with the "mini GPS tool V1. 7. 1" (I select115200 baud to access.) I tried to put the I2C_GPS_NAV on the GPS Modul by using the Arduino 1.01, but at the end of the transferring process I get the error “avrdude: stk500_getsync(): not in sync: resp=0x00” Before I do that, I had to open the solder bridge on the GPS Board. Beside this point I'm not shure if the step is realy nessesarry, because drotec postet at the description of the Board following:
"Bootloader and firmware of Atmega328 already flashed" "Firmware of GPS is configured with 115200 Baud and 10 Hz parameters"
In the config.h of the MultiWii 2.1 I did following changes:
Neo360 wrote:Hi to all, anyone can ask me why my home arrow was always wrong?? And see the Home distance, when was at 652m the counter restart to 0m, was normal?
Neo360 wrote:Hi to all, anyone can ask me why my home arrow was always wrong?? And see the Home distance, when was at 652m the counter restart to 0m, was normal?
Hello EOS Bandi , do you know of anywhere else i can buy the i2c-nav boards other than RCTimer. I have bought 3 boards from them over the past 6 months and all three work for a while and then they blow (no light and then heating up). It has happened on 2 GPS units.
This last board that blew also blew my brand new Crius SE v2.0 on its way out on a brand new tri-copter build.
So i want to use i2cNav but dont want to blow any more hardware.
This Thread is sooo huge atm. i was a long time not up-to-date with MWii and GPS.
What is the actual best GPS to I²C solution? With MTK and 1.9 FW, or UBlox GPS?
I can flash a "poor mans" Arduino with the Code from EOSBandi and connect it to MWii. Okay, but im searching for an allinone GPS to I²C Board. This from RCTimer seems to be dead after a while, so i ask u, what another complete board is done? The Drotek Board has "only" a MTK Chip, i thought, UBlox is better, or?
And can plz somebody (maybe Alex) collect the whole actual information in the first thread? Im very confused about the informations, that are splitted in so many answers.
What i mean is: What is the actual solution, to get the best GPS System for Multiwii?
Hello Apoc, i am now going to try the All-in-one boards like this one, it is less to go wrong and one set of code . the GPS plugs straight in to the spare serial port. I have ordered one and will see how it goes. There are some other advantages to the i2c-nav board , but for general navigation maybe keep it simple is better.
you dont need the "Extend Board for AIO PRO FC" because that just allows you to update the quad copter's GPS waypoints using your laptop while its flying. for basic gps return to home and pos hold just get the basic GPS "u-Blox CN-06 GPS Receiver"
Deet wrote:For those looking for a reliable I2C GPS board, look at the one from multiwiicopter.com. It also has an external Mag sensor which helps with accuracy.
Yes pretty much plug and play, just pid tuning, even for someone(me) a week into my first Multi. Steep learning curve, but, flies great, just trying to get Baro and PH tuned with R 2.1
Hi I am a bit confused, at the moment i have two Navigatron V.2 from Flytron that works with AXN1.51_2722_3329_384.1151100.5 and I2C_GPS_NAV-v2.1rc2 on Atmega 328. Is this the last possibility for Navigatron V.2 or can improve ? Thanks in advance
Sorry if i'm out of context, but does anyone have a Fastrax iTrax comptatible GPS receiver that sends data to a Server via GPRS, so that you can use data to show GPS position and status in Google Maps?
Sharkcopter wrote:Hi I am a bit confused, at the moment i have two Navigatron V.2 from Flytron that works with AXN1.51_2722_3329_384.1151100.5 and I2C_GPS_NAV-v2.1rc2 on Atmega 328. Is this the last possibility for Navigatron V.2 or can improve ? Thanks in advance
You can update your GPS module firmware to AXN1.51_2776_3329_384.1151100.5_v19 and enable MTK_BINARY19... ATM this is the best that you can get from your hw.
Hi, would it be possible to use the i2c sonar (like SRF08) without slowing down the process? I have actually a navigatron and it's so hard to connect something on the unused inputs of 328.
Sharkcopter wrote:Hi I am a bit confused, at the moment i have two Navigatron V.2 from Flytron that works with AXN1.51_2722_3329_384.1151100.5 and I2C_GPS_NAV-v2.1rc2 on Atmega 328. Is this the last possibility for Navigatron V.2 or can improve ? Thanks in advance
You can update your GPS module firmware to AXN1.51_2776_3329_384.1151100.5_v19 and enable MTK_BINARY19... ATM this is the best that you can get from your hw.
Hi I wonder if someone can help me? Trying to get the best out of my Navigatron V.2 I managed to updates its firmware to AXN1.51_2776_3329_384.1151100.5_v19 ok! Thats the good news! The bad news is that when I use minigps it seems that it only communicates at 38400 I also noticed that the red led on the Navigatron starts flashing and then stops completely. Not daunted I uploaded I2CGPS - Inteligent GPS and NAV module for MultiWii by EOSBandi V2.1 to the Navigatron after #define GPS_SERIAL_SPEED 115200 and #define MTK were set.
On Multiwii r1315 I have done #define MTK_BINARY19 - result no fix! and Navigatron red led is off.
Ive tried to reflash the Navigatron back to how it was but can no longer flash it ? Can someone please help? Have i bricked my Navigatron? and why does it now only auto detect with minigps @ 38400 and no longer updates or reports its firmware version
Sharkcopter wrote:Hi I am a bit confused, at the moment i have two Navigatron V.2 from Flytron that works with AXN1.51_2722_3329_384.1151100.5 and I2C_GPS_NAV-v2.1rc2 on Atmega 328. Is this the last possibility for Navigatron V.2 or can improve ? Thanks in advance
You can update your GPS module firmware to AXN1.51_2776_3329_384.1151100.5_v19 and enable MTK_BINARY19... ATM this is the best that you can get from your hw.
Hi I wonder if someone can help me? Trying to get the best out of my Navigatron V.2 I managed to updates its firmware to AXN1.51_2776_3329_384.1151100.5_v19 ok! Thats the good news! The bad news is that when I use minigps it seems that it only communicates at 38400 I also noticed that the red led on the Navigatron starts flashing and then stops completely. Not daunted I uploaded I2CGPS - Inteligent GPS and NAV module for MultiWii by EOSBandi V2.1 to the Navigatron after #define GPS_SERIAL_SPEED 115200 and #define MTK were set.
On Multiwii r1315 I have done #define MTK_BINARY19 - result no fix! and Navigatron red led is off.
Ive tried to reflash the Navigatron back to how it was but can no longer flash it ? Can someone please help? Have i bricked my Navigatron? and why does it now only auto detect with minigps @ 38400 and no longer updates or reports its firmware version
Any help would be much appreciated thanks
Sorry all, I forgot to do blink sketch before using minigps again ! Now the Navigatron when query by minigps gives me AXN_1.51 2276 and communicates on 115200 So I guess the AXN1.51_2776_3329_384.1151100.5_v19 firmware is working fine -
With blink sketch on the Navigatron, the red led on the top of the Navigatron blinks until it aquires sats and then goes out - Is this correct?
My problem now is exactly which sketch to upload to the Flytron?
What to change on on the multiwii r1315/6 and flytron when I enable MTK_BINARY19 ?
Should be easy for someone - sorry to be so thick!
Sharkcopter wrote:Hi I am a bit confused, at the moment i have two Navigatron V.2 from Flytron that works with AXN1.51_2722_3329_384.1151100.5 and I2C_GPS_NAV-v2.1rc2 on Atmega 328. Is this the last possibility for Navigatron V.2 or can improve ? Thanks in advance
You can update your GPS module firmware to AXN1.51_2776_3329_384.1151100.5_v19 and enable MTK_BINARY19... ATM this is the best that you can get from your hw.
Having had a chance to get more familiar with the Navigatron V.2 from Flytron I do not think it will work when updated to AXN1.51_2776_3329_384.1151100.5_v19 it seems that SBAS is not properly set by minigps tool after down powering the Flytron SBAS is no longer set. With version AXN1.51_2722_3329_384.1151100.5 SBAS is set OK. Does anyone else find this?
vineetaquarius wrote:hi all this is the first time i am posting some thing on this forum , pardon me if i am over ruling this forum rule guys please help
i have been trying to make gps works now , with different baud setting , but no luck yet
now what is the correct baud rate and wiring please some body let me know who have got it worked
do i need ubox and ftdi also ? , i read some where that there is no need to set this gps as it is already configured.
ps : i am using v2 for both board and gps
please any body
I've got a similar issue with almost identical hardware. Set the GPS module via FTDI to 115200 and 10Hz, works fine with ucenter and gets a lock right away. When i plug into multiwiiconf, i can see the compass edge blinking indicating GPS frames are being received but it never acheives a lock when plugged into the copter. None of the GPS indicators in the GUI get any values. No blinking LEDS on FC either
Anyone have some pointers as to whats going on here? Im stumped!
Hardware is good and wiring seems ok as compass blinking but no lock ever. GPS module has had config saved to EEPROM and definately retains settings across power cycles as plug back into ucenter and get a fix right away.
Looks like a good'un as it has a built in EEPROM and I love how easy it will be to mount.
I'm planning on stripping back one of my MEGA based FCs and using a standalone compass BoB and try and find somewhere to mount it that is well away from interference.
I have some problems also getting my MTK gps from Navigatron v1 to work with Multiwii on AIO. I have the GPS module disconnected from the 328 chip and using it like a pure serial GPS. All the flashes work fine when tested with the Mini GPS tool. Tried DIY Drones v.1.6 and 1.9. Using TeraTerm I can connect and get data stream at 38400 speed. The data is in the following format: $GPGGA,182044.600,330x.xxxx,N,0965x.xxxx,W,1,7,1.09,173.8,M,-24.1,M,,*6C $GPGSA,A,3,21,18,15,29,22,26,09,,,,,,2.02,1.09,1.70*04 $GPRMC,182044.600,A,330x.xxxx,N,0965x.xxxx,W,0.00,138.85,190113,,,A*7A $GPVTG,138.85,T,,M,0.00,N,0.00,K,A*3A
The x-es are numbers actually.
In config.h I have Serial 2 set for 38400, GPS serial port 2 and GPS speed 38400 (which I believe doesn't matter, since we are not sending any params to the GPS module). I have only Tx from GPS connected. For GPS protocol selected is MTK_BINARY19 and the GPS module is flashed with the ver 1.9. Also tested with MegapirateNG on the same board and the GPS works and shows 3D fix, so the hardware looks fine. I ran out of ideas what is wrong other than somehow the MultiWii doesn't understand the data sent from the GPS. Can somebody with similar setup give me a hint what is wrong?
thebgrian wrote:I have some problems also getting my MTK gps from Navigatron v1 to work with Multiwii on AIO. I have the GPS module disconnected from the 328 chip and using it like a pure serial GPS. All the flashes work fine when tested with the Mini GPS tool. Tried DIY Drones v.1.6 and 1.9. Using TeraTerm I can connect and get data stream at 38400 speed. The data is in the following format: $GPGGA,182044.600,330x.xxxx,N,0965x.xxxx,W,1,7,1.09,173.8,M,-24.1,M,,*6C $GPGSA,A,3,21,18,15,29,22,26,09,,,,,,2.02,1.09,1.70*04 $GPRMC,182044.600,A,330x.xxxx,N,0965x.xxxx,W,0.00,138.85,190113,,,A*7A $GPVTG,138.85,T,,M,0.00,N,0.00,K,A*3A
The x-es are numbers actually.
In config.h I have Serial 2 set for 38400, GPS serial port 2 and GPS speed 38400 (which I believe doesn't matter, since we are not sending any params to the GPS module). I have only Tx from GPS connected. For GPS protocol selected is MTK_BINARY19 and the GPS module is flashed with the ver 1.9. Also tested with MegapirateNG on the same board and the GPS works and shows 3D fix, so the hardware looks fine. I ran out of ideas what is wrong other than somehow the MultiWii doesn't understand the data sent from the GPS. Can somebody with similar setup give me a hint what is wrong?
Wrong, the code initialise the GPS module, you need two way communication....
Thank you, EOSBandi Do I need to change the speed settings for Serial and GPS? Tried adding the other serial connection, but still no luck. I did it according to the instructions at conf.h
/* GPS using a SERIAL port only available on MEGA boards (this might be possible on 328 based boards in the future) if enabled, define here the Arduino Serial port number and the UART speed note: only the RX PIN is used, the GPS is not configured by multiwii the GPS must be configured to output GGA and RMC NMEA sentences (which is generally the default conf for most GPS devices) at least 5Hz update rate. uncomment the first line to select the GPS serial port of the arduino */
Noticed in the current dev version there ia now a #define UBLOX param in config.h - could this now be why the AIO pro is not acheiving a GPS fix? Im currently running stock 2.1 where no such option exists.
Is it worth flashing current dev or is something else causing my GPS headaches?
vineetaquarius wrote:hi all this is the first time i am posting some thing on this forum , pardon me if i am over ruling this forum rule guys please help
i have been trying to make gps works now , with different baud setting , but no luck yet
now what is the correct baud rate and wiring please some body let me know who have got it worked
do i need ubox and ftdi also ? , i read some where that there is no need to set this gps as it is already configured.
ps : i am using v2 for both board and gps
please any body
I've got a similar issue with almost identical hardware. Set the GPS module via FTDI to 115200 and 10Hz, works fine with ucenter and gets a lock right away. When i plug into multiwiiconf, i can see the compass edge blinking indicating GPS frames are being received but it never acheives a lock when plugged into the copter. None of the GPS indicators in the GUI get any values. No blinking LEDS on FC either
Anyone have some pointers as to whats going on here? Im stumped!
Hardware is good and wiring seems ok as compass blinking but no lock ever. GPS module has had config saved to EEPROM and definately retains settings across power cycles as plug back into ucenter and get a fix right away.
Any pointers greatly appreciated!
thankyou zerosignal ,ordered ftdi also can you check above my connections are ok for gps
The RcTimer u-blox GPS that you bought defaults to 9600 baud. the GPS config options need to be set to 9600.
I use the updated GPS code that EOSBandi wrote for 2.1 (Found on this forum). That code will connect at 9600 but then change the baud rate to 57600 with a 5Hz update.
Also make sure you're wired correctly. (Default Rctimer wiring is wrong for some boards)
Vineetaquarius, I think you're wired correctly. My wiring is the same using serial tx2/rx2. I think my problem is down to my version of multiwii perhaps. Im seeing the flashing compass in GUI but never pick up any sats or a fix. Using the wingui i can log out the GPS data to a file. Everything is 0 so i'm not sure multiwii is parsing the data from the GPS. With ucenter i get a lock in a couple of seconds even in my house
Mark_K wrote:The RcTimer u-blox GPS that you bought defaults to 9600 baud. the GPS config options need to be set to 9600.
I use the updated GPS code that EOSBandi wrote for 2.1 (Found on this forum). That code will connect at 9600 but then change the baud rate to 57600 with a 5Hz update.
Also make sure you're wired correctly. (Default Rctimer wiring is wrong for some boards)
Vcc -> 5v, Gnd -> Gnd, Tx -> Rx, Rx -> Tx
thanks mark
ok i have wired the same way you are telling rc to tx and tx to rx , but you see if you connect it to i2c port then you will have 1rx 1tx, 2rx 2tx, 3rx 3tx , which way to go , currently i have connected to gps rx to tx1 and gps tx to rx1 . is that right ?
second thing can you give me a link for the multiwii code 2.1 from eosbandi which you are talking about , or can you send to my mail vineet.aquarius@gmail.com , that would be very great full of you
zerosignal wrote:Vineetaquarius, I think you're wired correctly. My wiring is the same using serial tx2/rx2. I think my problem is down to my version of multiwii perhaps. Im seeing the flashing compass in GUI but never pick up any sats or a fix. Using the wingui i can log out the GPS data to a file. Everything is 0 so i'm not sure multiwii is parsing the data from the GPS. With ucenter i get a lock in a couple of seconds even in my house
Will let you know how i get on. Good luck!
see the above post of mark
he is saying something about a version which is working fine , i am waiting for the link of that version , you should also try that , i think it is probably some thing with the multii wii version
thebgrian wrote:I have some problems also getting my MTK gps from Navigatron v1 to work with Multiwii on AIO. I have the GPS module disconnected from the 328 chip and using it like a pure serial GPS. All the flashes work fine when tested with the Mini GPS tool. Tried DIY Drones v.1.6 and 1.9. Using TeraTerm I can connect and get data stream at 38400 speed. The data is in the following format: $GPGGA,182044.600,330x.xxxx,N,0965x.xxxx,W,1,7,1.09,173.8,M,-24.1,M,,*6C $GPGSA,A,3,21,18,15,29,22,26,09,,,,,,2.02,1.09,1.70*04 $GPRMC,182044.600,A,330x.xxxx,N,0965x.xxxx,W,0.00,138.85,190113,,,A*7A $GPVTG,138.85,T,,M,0.00,N,0.00,K,A*3A
The x-es are numbers actually.
In config.h I have Serial 2 set for 38400, GPS serial port 2 and GPS speed 38400 (which I believe doesn't matter, since we are not sending any params to the GPS module). I have only Tx from GPS connected. For GPS protocol selected is MTK_BINARY19 and the GPS module is flashed with the ver 1.9. Also tested with MegapirateNG on the same board and the GPS works and shows 3D fix, so the hardware looks fine. I ran out of ideas what is wrong other than somehow the MultiWii doesn't understand the data sent from the GPS. Can somebody with similar setup give me a hint what is wrong?
Wrong, the code initialise the GPS module, you need two way communication....
Got it finally. It is simple as expected. To have my GPS initialize I had to enable not only #define MTK_BINARY19 but also #define INIT_MTK_GPS. Pretty obvious right? So here are my GPS related settings for MTK ver 1.9 (it should be the same for 1.6) for AIO from Hobbyking/Crius:
#define SERIAL2_COM_SPEED 38400
#define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA #define GPS_BAUD 38400 #define MTK_BINARY19 #define INIT_MTK_GPS // initialize MTK GPS for using selected speed, 5Hz update rate and GGA & RMC sentence or binary settings
vineetaquarius wrote:ok i have wired the same way you are telling rc to tx and tx to rx , but you see if you connect it to i2c port then you will have 1rx 1tx, 2rx 2tx, 3rx 3tx , which way to go , currently i have connected to gps rx to tx1 and gps tx to rx1 . is that right ?
second thing can you give me a link for the multiwii code 2.1 from eosbandi which you are talking about , or can you send to my mail vineet.aquarius@gmail.com , that would be very great full of you
Mine is connected to serial port 2 so GPS_TX->RX2, GPS_RX->TX2 and I have these defines in my config.h in the GPS section : #define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA #define GPS_BAUD 57600 // It's starts as 9600 baud but then it is changed during initialization #define GPS_RATE 200 //200ms for 5hz #define UBLOX
And under GPS filtering I commented out the line below and added the next line after it: // #define GPS_FILTERING // add a 5 element moving average filter to GPS coordinates, helps eliminate gps noise but adds latency comment out to disable #define GPS_LEAD_FILTER
Hi Do I have to disable #define GPS_LEAD_FILTER in multiwii conf when I use i2c GPS ? In the newest version of i2c GPS there is GPS_LEAD_FILTER already.
vineetaquarius wrote:ok i have wired the same way you are telling rc to tx and tx to rx , but you see if you connect it to i2c port then you will have 1rx 1tx, 2rx 2tx, 3rx 3tx , which way to go , currently i have connected to gps rx to tx1 and gps tx to rx1 . is that right ?
second thing can you give me a link for the multiwii code 2.1 from eosbandi which you are talking about , or can you send to my mail vineet.aquarius@gmail.com , that would be very great full of you
Mine is connected to serial port 2 so GPS_TX->RX2, GPS_RX->TX2 and I have these defines in my config.h in the GPS section : #define GPS_SERIAL 2 // should be 2 for flyduino v2. It's the serial port number on arduino MEGA #define GPS_BAUD 57600 // It's starts as 9600 baud but then it is changed during initialization #define GPS_RATE 200 //200ms for 5hz #define UBLOX
And under GPS filtering I commented out the line below and added the next line after it: // #define GPS_FILTERING // add a 5 element moving average filter to GPS coordinates, helps eliminate gps noise but adds latency comment out to disable #define GPS_LEAD_FILTER
Correct. The above code works with the default 9600 baud rate. On each initialization, it changes the GPS speed from 9600 baud to 57600 baud (and the update rate to 5 hertz).
Mark_K wrote:Correct. The above code works with the default 9600 baud rate. On each initialization, it changes the GPS speed from 9600 baud to 57600 baud (and the update rate to 5 hertz).
i cannot find this code in config.h
#define GPS_RATE 200 //200ms for 5hz
should i write it like that only below baud rate .