I just pulled out my CRIUS AIO Pro that has been put away for about a year now. It was working great before I put it up but now when I connect to Mission Planner the HUD shows it on it's side but it is sitting level on the floor. I have included a screenshot. Any ideas?

Edit: So I guess it is bricked for now anyway. Can't even get the status LEDs to light up now. Only the two behind them and the blue LED next to the USB. Tried burning the bootloader and apparently you can't do that with the USB port or an AVRISP v2 on the SPI pins.

There are no real identifying markings on the boards that have led me to much.

I'm only able to find limited information about the boards and how to hook them up. From what I've found from similar boards I put together this graphic. Hopefully someone familiar with this board can look at it and tell me if I am connecting things correctly and then maybe fill a few gaps.

Should the YAW motor be hooked to point A or B?

Where to hook point C "RX YAW channel"?

Do you seriously connect a 14v battery directly to the board or should there be a BEC?

Images

I have a set of 710KV T-Motors and 30A OPTO 600Mhz ESCs flashed with SimonK. I calibrated each individually. After completing calibration I hooked them up to my CRIUS. When applying throttle if I am very subtle in movement between 0 and about an 1/8 throttle I get some fluctuation in motor speed but once hitting that 1/8 of throttle it is full throttle and the remaining 7/8 there is no speed change. I have never seen this behavior and am unsure what would cause it. These are the first ESCs I have used with SimonK firmware so I am not sure if that may have something to do with it. Anyone have any ideas?

After my adventures with Flycam's naviboards and then destroying my MCFC I was going to just stick with what has worked for me being the kk1 and kk2 boards until I got a chance to pick up an APM2 but then I see the CRIUS AIO PRO which was cheaper than both APM and FC and the hardware looked rather promising. I decided it can't possibly be any worse than what I've been dealing with so I bought one. Right off upon opening and inspecting the board and accessories I was impressed. It was all clean and proper. I say this because all the FC products I purchased had a residue I assume from their PCB wash and some parts where shoddy at best but anyway this is about the CRIUS.

I soldered and wired everything up as per information in the manual. Yes there is a manual! A number of them actually. I opted for MegapirateNG for firmware. I set up my FS 9x to use my AIL and F. Mode switches to achieve the 6 flight modes though it would be nice being able to assign more. One of these days I would like to have at the source code for Mission Planner.

I just took it out for the maiden and all went rather well. No tuning yet. I found the elevator needed to be reversed in the TX. I am honestly not sure that it is intended to be reversed but I am only comfortable with pulling back on the elevator to return to me. "You know, pull up! pull up!" Takeoff and hover only inches off the ground with no serious ground effect. Pretty impressed with that. Motor response is very tight.

I just wanted to post a few pics. This is my x525 frame that I modified by bringing the motors in closer to the center. It did affect stability a bit but not much and it helped to protect the props while I was learning.

Here is my last frame from GLB. Last meaning I won't buy another from them. It was not the frame I ordered but I have had so many issues with them that I didn't want to bother trying to send it back. The TX in the picture is a FlySky FS-TH9X modded with the ER9X firmware using the usbASP programmer that came with a GLB blackboard knockoff. I added the FrSky DHT 2-way telemetry mod, replaced 2 junk factory pots and it now uses a 2200mAh S3 20C battery.