Originally Posted by godwisper

most probably its the gps unit thats faulty as when I connect to ucenter even if I see data at 115200 I dont get any satellite fix... the wire connecting the antenna had gone off and had asked a friend to resolder it back....can it be that it got damaged ?

Hi, sorry to say, but the soldering looks really bad. I broke the antenna connector off at my board too. It is not so easy to solder it correctly again, since it is surface mounted. But there must be an other problem too, otherwise it should communicate with u-center....

It communicates with ucentre...its just doesnt get a fix as if there is no signal. Now its either I did solder on different points the antenna or else something else....

Originally Posted by godwisper

It communicates with ucentre...its just doesnt get a fix as if there is no signal. Now its either I did solder on different points the antenna or else something else....

Did you try it outside?

Yes I did

I might order another one but to which points does the antenna wire connect too ?

Bought the SE Flight Control Board V1.0 + IC2 board and the GPS module on a whim from RCtimer. Thanks to this great thread and directions I was able to get the GPS up only moments after opening the package!



Sadly I believe this was probably the easy part..

Everytime I receive I2C errors (showing error number 26 now).
I´m using firmware v2.1 on Crius Multiwii v1.0

My GPS configuration:

UBLOX with 38400 baud rate...soldering pin 13 /14.
I2C updated with the lasted version - v2.1.

May you help me? How can I fix it?

Originally Posted by JackinFtLaud

Bought the SE Flight Control Board V1.0 + IC2 board and the GPS module on a whim from RCtimer. Thanks to this great thread and directions I was able to get the GPS up only moments after opening the package!



Sadly I believe this was probably the easy part..

Originally Posted by QUENAZ

Everytime I receive I2C errors (showing error number 26 now).

May you help me? How can I fix it?

26 errors in what time? If it is not counting up continosly, it`s not fine, but it should works in principle. I seem to have some i2c errors at startup. The counter often shows errors....

Originally Posted by QUENAZ

Everytime I receive I2C errors (showing error number 26 now).
I´m using firmware v2.1 on Crius Multiwii v1.0

My GPS configuration:

UBLOX with 38400 baud rate...soldering pin 13 /14.
I2C updated with the lasted version - v2.1.

May you help me? How can I fix it?

I only get IC2 errors when the IC2-GPS board is not plugged into the Multiwii board. Otherwise it stays at 0 as you can see in the screen shot. It was running for a while when I took that. Perhaps you have a bad connection or a damaged connector on one of the two boards?

Hello everyone and pm1.
I use the board CRIUS SE V1.0 with GPS-NAV and GPS uBlox.
I soldered pins.
I uploaded the new firmware for the card NAV.
I configured correctly the file gps.ino (for pids) and the parameters related to the config.h gps even hit the magnetic declination (and others) in config.h.
I did the calibration mag.
The led in the NAV blinks 3x indicating positioning 3D and the software MultiWiiConf show location and from about 10 satellites.
But anyway, I tried with several PIDs and does not hold position. Tried with pids standards and was increasing and then decreasing, gps hold woks inverse, on acc only is better.
Tried with mag mag on and then off and the result are the same.
The baro is disable.
It simply does not work.

See the video

Quadcopter MultiWii 2.1 GPS Hold Failed (1 min 25 sec)

In this video I try 3 times, when I say "GPS on" I move the switch for GPS Hold and wait, when it goes away I disable "GPS OFF".

Please someone help me.

Thank you very much (sorry by English)

Great thread. I'm sure with this instruction in this thread I will have it working in no time. I am a little stuck however.

I have had the Crius multiwii running 2.0. I just got my ftdi programer and had no problems doing the multiwii upgrade with the fc to 2.1.

Problem: I added pins to the Crius I2c board and plugged it in and it seems to communicate appropriately, however when I upload the sketch it just stalls during the upload. Arduino program never errors, just shows uploading, and the fdti and i2c board blink. Like its flashing ok, but never finishes.

Byte wise it seems to be about half of what multiwii 2.1 is so I don't think it should take all that long.

Any guidance? I have worked thru other flashing issues in the past, but this is new to me. I have tried changing boards in the Arduino prog too.


Thanks

Walking away and coming back later apprently helped. I had the ftdi plugged in backwards. I thought I checked it a few times before. I have since been able to flash the Ic2 board.

One of the reasons I have no posts is because I can usually find what I need by searching around. I'm usually just a lurker.

Anyways, Great group!

Thanks!

Scott

I got a lot of I2C errors.... i updated the 2 a version

If i disable #define I2C_GPS in config.h the errors are gone...

I didn't soldering the 14 + 15 pins. If i do that wil the i2c errors maybe gone?

The GPS it self is working i got afix within 40 seconds....

Originally Posted by mast3rwurm

I got a lot of I2C errors.... i updated the 2 a version

If i disable #define I2C_GPS in config.h the errors are gone...

I didn't soldering the 14 + 15 pins. If i do that wil the i2c errors maybe gone?

The GPS it self is working i got afix within 40 seconds....

If you get i2c errors, the connection between fc and i2c board is not ok. Did you connect +/+ rx/tx tx/rx -/- ?

This problem has nothing to do with the gps module!

- how does the i2c board blink?
- which fc you are using?

Originally Posted by Ébeo

Tried with mag mag on and then off and the result are the same.

Check, if mag orientation is ok. check, if the copter in the gui follows exactly the direction of the copter!