Originally Posted by Multor

i really hate this. mpng crius just wants to wobble to death

what is imax D: can someone please please please help me

any one with 1000kv 1045 setup in there in a 450 frame or 550 i cant trust my camera on this stabilization huhuhu please someone help

It sounds like your gains are too high, maybe Stabilize gains as NDw says, have your tried lowering them?

Have a look at "koolkiwikat's" last post HERE

Originally Posted by KevinBuckley70

Thanks for that - I'll work through them.

Regarding connecting a cabled USB socket directly to the broken PCB, I believe the important connections are as shown below?

OK - I appear to have connectivity back to the USB controller chip & no shorts.

And plugging a USB cable into the tail powers the board OK. But the PC isn't responding to it.

Does anyone know what the pad representing pin-4 (ID) is supposed to be connected to? It doesn't appear to be connected to anything on the Crius.

According to the spec. for USB, the pinout for micro-B is:

1 VBUS Red +5 V
2 D− White Data −
3 D+ Green Data +
4 ID (No colour)
5 GND Black Ground

EDIT: BTW: I know pins 2 & 3 are the wrong way around - I tried it both ways

Originally Posted by nebstress

It sounds like your gains are too high, maybe Stabilize gains as NDw says, have your tried lowering them?

Have a look at "koolkiwikat's" last post HERE

i did both rate and stabilize from 1-7 and at rate 0-.400


edit: i tried 180 imax from 20 and now its good but its sliding around really badly and sometimes it just shoots up to one direction for no reason.

on MY crius multiwii SE board it works fine, all my esc are calibrated parallely.

Originally Posted by KevinBuckley70

OK - I appear to have connectivity back to the USB controller chip & no shorts.

And plugging a USB cable into the tail powers the board OK. But the PC isn't responding to it.

Does anyone know what the pad representing pin-4 (ID) is supposed to be connected to? It doesn't appear to be connected to anything on the Crius.

According to the spec. for USB, the pinout for micro-B is:

1 VBUS Red +5 V
2 D− White Data −
3 D+ Green Data +
4 ID (No colour)
5 GND Black Ground

EDIT: BTW: I know pins 2 & 3 are the wrong way around - I tried it both ways

i think this will help you out
http://www.cpkb.org/wiki/Micro-USB_pinout
just visualize it imagine* you have the female version and lay the orientations down in your board.

edit: oops i just read thoroughly tru your post. get your usb cord plug it in your broken female micro connector and see the continuities of your missing pin 4.

Originally Posted by Multor

i think this will help you out
http://www.cpkb.org/wiki/Micro-USB_pinout
just visualize it imagine* you have the female version and lay the orientations down in your board.

edit: oops i just read thoroughly tru your post. get your usb cord plug it in your broken female micro connector and see the continuities of your missing pin 4.

Thanks. That's how I have wired it. I know the orientation is correct because when I plug in the USB, the board powers up. So +5 & Gnd are in the right places. And you can see from the photograph the D+ & D- pads which are tracked to the controller chip.

But for some reason, the PC can't see it.

Can some one please explain how to get voltage sensor working I'm pretty sure it's pin a0 I can configure it and then test it with a battery and the volts change when I connect it to battery but it's not an accurate reading. I have tried the power from the ubec and a esc but the voltage on both don't seem to drop as the battery drains. I'm using mega pirate r4. I'm trying to get the battery reading correct in the mission planner osd.

Originally Posted by nebstress

It hooks up the same way as the V1, TX to RX2 & RX to TX2:

Thanks! That did the trick, GPS is now working and locked on.

Originally Posted by nebstress

That is very strange, it looks like the throttle is being pumped, as long as all your settings are correct I would double check/re-run the ESC's throttle calibration & try sticking the CRIUS AIOP just on the white foam without the velco, sometimes too much vibration dampening will cause even more problems.

I will try that, Im pretty sure I did all my throttle calibrations. Did 3 with a programming card, and one by radio because the card stopped working.

Originally Posted by NDw

I'd try just getting it a few feet off the ground and see if it sorts itself out.

I'm using the same frame but nvr tried the multiwii firmware. The megapirate defaults work really well with it.

I played with the settings a bit and got it to hover at about 2 feet. But it only will hover for like 10-15 seconds. Then one side will cut out and dip and it crashes to the ground.

[QUOTE=scribble007;22787480]I will try that, Im pretty sure I did all my throttle calibrations. Did 3 with a programming card, and one by radio because the card stopped working.

Throttle cant be calibrated with a card, the TX must be used. Hence the word "calibrate"

Chris

Oh, Oops
I miss spoke (typed)
I used the card to make all settings identical (cut off, timing ect)
And I used a y-harness to do the throttle calibration 2 at a time.
Ill try again one at a time tonight. Im also trying to fab that CD holder Board suspending rubber band mount I saw on here. Forgot who made it.

I've read through this entire thread to learn more about the board, and there are questions that were completely skipped through regarding the GPS...

who knows what is a better module to use with the AIO?

these seem to be what the majority is using:
U-blox NEO-6M
U-blox LEA-6H
MediaTek MT3329
MediaTek MT3339

anyone?

Originally Posted by nomand

I've read through this entire thread to learn more about the board, and there are questions that were completely skipped through regarding the GPS...

who knows what is a better module to use with the AIO?

these seem to be what the majority is using:
U-blox NEO-6M
U-blox LEA-6H
MediaTek MT3329
MediaTek MT3339

anyone?

I would suggest MT3339

I have a U_blox NEO-6M ... with 6.02 firmware, if anybody knows how to upgrade the firmware to 7.03 I will appreciate, on ublox site apparently NEO firmware is not even available ...

As a followup to an earlier request for help thanks everyone. In the sketch I did see how to set or know what the ftdi port speed is. For MPNG can someone fill me in. I'm trying to get the BT working.

Hi,

I've been trying to get in touch with rctimer via email, does anyone know how to reach them? I've tried sales@rctimer.com and rctimer@gmail.com, are there any others? Thanks!

I saw earlier in the thread some back-and-forth about the Crius LCD not working properly with MultiWii 2.0 and above. I'm having some problems getting my LCD to work, and wondered if anyone had some solutions (other than soldering an ISP header to the LCD board and reflashing the firmware).

I'm using MultiWii 2.1 with a Crius SE 2.0, and the Crius LCD flashes "SERIAL LCD V1.03" on power-up.

Has anyone managed to get this working using LCD_SERIAL3W , or is there something else I'm missing?