LibrePilot Forum
Development => Hardware => Topic started by: mazevx on December 08, 2015, 10:54:35 pm
-
Hello, just found this one named Revolution Mini at goodluckbuy...
http://www.goodluckbuy.com/openpilot-mini-cc3d-revolution-flight-controller-stm32-32bit-processor-.html
Did you know about that?
If yes im sorry!
-
I think one of the devs was thinking about buying one of those. It is a Revo, but in a smaller package.
I worry that it might not have Revo telemetry even though it says "preserves all the functions and interfaces of the standard one (Revo)". Maybe it does though. It would be sweet.
Anybody bought one and received it and can comment on telemetry and everything else about this? :)
-
I have one in the mail. I'll report back when it arrives.
-
I found what looks like the same thing on eBay http://www.ebay.com/itm/Openpilot-CC3D-Revolution-Mini-Nano-Flight-controller/331727888080 that has more details.
If it is the same one it's a revo without the oplink but with an added connector to connect an external oplink without using the main or flexi ports. You can see the connectors on the goodluckbuy site's picture. PWM out on the left, the PWM inputs and usb on the top, the new 7 pin oplink connector on the right, and the sonar, flexi, and main on the bottom. I cheated and looked at the picture with labels in the eBay auction. :)
-
Looking at that I'm not sure how that (the eBay one) would work with a standard oplink. The new connector has 7 pins and there are 7 signals on the revo between the cpu and the rfm22b. VCC, gnd, sdo, sdi, sck, nsel, and nirq. But running them out to a connector wouldn't do any good with a standard oplink. You'd need a custom stripped external modem with just the rfm22b and antenna connector in it. Without custom firmware on the "revo" it wouldn't know how to talk to a standard oplink that's not on either the main or flexi port.
It'll be interesting to see just what Brian gets.
edit: found it, goodluckbuy sells an oplink with the 7 pin connector http://www.goodluckbuy.com/oplink-433mhz-mini-air-and-ground-station-telemetry-transmit-system-for-mini-cc3d-revo-flight-controller.html They sell two different variations of the oplink, one "mini-air" with the 7 pin connector and one "mini-ground" that looks like the one we normally use.
-
That was the conclusion that we came to as well. You could likely use an RFM22B breakout board for the OPLink portion, or even solder directly to the module if you really want something small and light, but you're also going to need a 3.3V regulator.
-
Order placed. Curious to test on a micro racer :)
-
Well damn. A few days ago I ordered one of those oplink pairs hoping the air one was a real oplink and not just an rfm22b.
I will report when I get it.
-
Im on the way to buy one but they say that it takes 10-20 days for delivery, just have to be patient again... And then maybe another week stuck in german customs...
A guy in our german forum says its well done with soldering and works good.
-
Just placed my order at banggood, same thing but little bit cheaper and trusted seller... Faster delivery also.
Im curious about the quality
-
Just found these out on Banggood which seems to have one of the better prices right now on it.
Here is board only 41.60 USD
http://www.banggood.com/OpenPilot-Mini-CC3D-Revolution-Flight-Controller-For-FPV-Multicopter-5g-p-1018903.html
And here in a kit with OPLink mini + air + gps + OP OSD 81,49 USD
http://www.banggood.com/CC3D-Revolution-Mini-Combo-OP-Flight-Controller-OPLINK-Radio-Telemetry-GPS-OSD-Power-Distribution-Board-p-1019051.html
-
This one looks interesting as well:
http://www.banggood.com/FPV-Revolution-Mini-Flight-Controller-STM32F4-Processor-Embeded-433Mhz-Digital-Telemeter-Radio-p-1021357.html
-
Brian, that is interesting, the cpu chip they say is the one from the full size revo, not the small one. And it apparently has an oplink on it. I've always wondered why the revo nano wasn't designed with one on it. But look at the connectors, they're five pin, not our standard four pin ones. I wonder what the pinouts are.
-
I'm wondering that same thing. It looks like a pair of them is the flexi-io port, which is 10 pins on the Revo, so that makes sense, but it doesn't make sense for the other ports. Maybe they added an extra ground?
In any case, I ordered one to see what it's like.
I'm also curious about the exact size. I'm estimating that it's about 20x30mm, but it could be a bit bigger. In any case, it's very small for a full Revo, especially with full 0.1" headers.
-
Whats about the CPU? Did I miss something? Thought they all have same CPU and flash specs?
-
Looks weird how they got rid of the servo header pins for a jst connector instead... Id rather use a standard Revo instead seeing that the uhf modem is built-in on the underside and that fact that it's plug-n-play regarding mounting (30x30) this clone Mini Revo Plus a the OPLink modem in those plastic cases looks as if it takes up much more space then simply 1 full sized Revo.
-
Im glad that they got rid of the servo headers. Its always anoying wenn they solder straight servo headers and you have to put them all out... I like flat copters, so its a personal choice!
-
I received the "Revolution Mini" today, and so far so good.
It is exactly the same size as the OPLink Mini clone that I have, and it worked well right out of the box. I also flashed the latest LP firmware on it, and it works great.
If you don't need/want the OPLink modem, I think this might be a good and very small FC.
-
Im glad that they got rid of the servo headers. Its always anoying wenn they solder straight servo headers and you have to put them all out... I like flat copters, so its a personal choice!
Those are so easy to get out with a hot air its not even a joke lol... They use solder paste on the header pins so they all come loose within seconds all at once.
-
Im glad that they got rid of the servo headers. Its always anoying wenn they solder straight servo headers and you have to put them all out... I like flat copters, so its a personal choice!
Those are so easy to get out with a hot air its not even a joke lol... They use solder paste on the header pins so they all come loose within seconds all at once.
Are you serious? Im good at soldering its part of my daily work, but the last one i soldered of was like fighting a cat...even with our professionel equipment had to pull out every single pin... But ok...Bad luck
-
Has anyone tried altitude hold with this board? Is it usefull or needed to cover the baro with foam like on the other FCs?
-
Has anyone tried altitude hold with this board? Is it usefull or needed to cover the baro with foam like on the other FCs?
There is no rule I think, depends how your baro behave. You should check in GCS how much it jumps etc.. Also depends on location of the board, type of case etc.. Best is to test and then try what works best for you. Probably each foam is different. I havent tried those boards yet, so I cant say anything about their hardware quality though. If baro does not work, just return it. Also baro needs time to warm up and stabilize so you cant expect to have it working first minute of flight. How big the noise should be is posted somewhere in another thread;)
-
You should protect the baro sensor from light, the case is semi transparent.
Case should almost protect sensor from wind.
See also this page:
https://librepilot.atlassian.net/wiki/display/LPDOC/Altitude+Hold
-
Thank you for your answer, i will cover it with dark open cell foam... Better to be on the safe side.
Baro works well on the table inside the house, its quiet and doesnt jump around.
The wiki is not available...for me...as most of the time :-(
-
The wiki is not available...for me...as most of the time :-(
Wiki is always up here... strange.
-
Mine comes with foam on baro sensor. The altitude hold is very good.
-
In model aircraft, baro always needs open cell foam covering it. Also needs to be covered to keep light out. Light can change the altitude by several meters if you rotate yaw so light hits it or doesn't hit it.
There are other things you can use too. Wad of cotton held on with tape, etc.
-
So hows this board working for everyone? Im interested who plans to support them.I just want a f4 tiny cheap board. I dont even need a baro and mag ( alt and pos hold are boring)
just lemme get the speed ;)
-
The board is performing very well. Even mag and baro ;-)
Im sure its better than cc3d feels very direkt
-
Hey, could someone post some pictures of the oplink Air pcb?
I am trying to work out how to build one from rf22 module, but there seems to be very little information on it... so far i cant really find even its pinout.
-
Hi all,
Can anyone who's bought/used one of these mini setups so far comment on the GPS performance? Mostly position hold and RTL?
I've been using APM and am probably a bit spoiled with regards to autonomous functions. I've become interested in seeing how small a quad I can build, and the mini seems perfect for this. But I wonder as to how well that tiny little GPS receiver works, and of the general performance of GPS assisted modes in the firmware.
Thanks in advance.
-
Hi, welcome
The key for a good setup is external mag, mandatory for a mini sized quad.
Small Gps do not have Mag but for 3$ a small I2c mag can be added.
Next release should allow additional support for i2c mag or Naza Gps/Mag.
Laurent
-
Ok, thanks. So assuming I use an external mag, those little GPS units would do a reasonably good job? My main interest is just RTL and position hold, and even then I'm fine if they're just in the ballpark so to speak.
If I'd need to use a larger GPS, then the attraction of the mini board is somewhat reduced and I'd probably just go for the full size Revolution w/telem radio integrated - gain some size in the FC, but eliminate the need to carry a separate radio makes it a wash.
And on that mini board (common on Banggood), it has two ports, main and flexi, so I assume those could be used for the GPS and a mag, once the firmware supports it?
I'd love to see how small I could make a quad that still retains GPS functionality.
-
Those small Gps uses a one chip neo7 like, small patch antenna and no LNA or filtering.
Current Next (dev branch) already support i2C mag.
Connect GPS to MainPort and I2C to flexi port, on Revo still one serial port on Flexi_IO (receiver port) for OSD use.
-
Wrote a long post of my experience of this FC.
But forum in logg was timed out. All text lost.
But in short. I like this one. The board is of good manufacturing standard.
Ony thing I did mod. Was the foam that was compressed against the case and the baro.
I did cut it in half with a scalpel knife.
Have tested alt. hold a few times. Workes very well on my Tarot Robocat 250.
Even in quite windy conditions.
First flight was with generic 250 settings. But carful calibrations.
Flies well with minor adjustments to roll/pich/yaw rotations/deg.sec´s.
No adjustments to pID´s so far. No vibrations or other problems.
Adds a few pics of the unit with the case dissasembled.
Is there a plan to add this unit to the wiki manal?
-
Ah. pics to large.
New downscaled ones here.
-
Is there a plan to add this unit to the wiki manal?
No plans.
Sorry but we only describe original hardware in Wiki.
-
Is there a plan to add this unit to the wiki manal?
No plans.
Sorry but we only describe original hardware in Wiki.
Ok, can understand that. :)
So the next qestion is..
Is there going to be any LP original hardware?
-
Currently designing new hardware is very low priority.
Need something new ?
-
Not really!
But new developments are always intresting. :)
-
Maybe the Revo could get updated to a newer MPU-9250 sensor?
(maybe I could also help with the hardware...)
-
Why do you want to replace the existing sensor with a MPU-9250? What new capabilities will that give your new board that the current revo doesn't have?
Those are the kind of questions that need to be answered before designing and supporting a new board. What new capabilities does it have? How is it significantly better than the existing boards?
-
No need to reinvent the wheel : Revo + MPU9250 + spare ports = Sparky2
-
Just saying...
-
Oh!
Blackbox would be a nice addition!
The possibility to logg flights and sensors. Whith out the need of oplink.
Maby there already is a "revo" clone that has all funktions. ?
BLHeli or oneshot pass trgogh flashing would be nice to!
-
Theoretically an SD card could be connected via SPI that is found on the RC input connector on both Revo and Nano (but not on the sparky 2).
But it'll probably be at least a couple of releases before LP devs start considering designing new hardware (might I be wrong...?)
-
Blackbox would be a nice addition!
The possibility to logg flights and sensors. Whith out the need of oplink.
Maby there already is a "revo" clone that has all funktions. ?
BLHeli or oneshot pass trgogh flashing would be nice to!
Those are both software or firmware changes, not hardware.
Blackbox is cleanflight's modified version of openlog. There's an open issue requesting support for openlog, https://librepilot.atlassian.net/browse/LP-95 it's waiting for a developer to adopt the issue and program it.
The ESC pass through has also been proposed, https://librepilot.atlassian.net/browse/LP-250 and is waiting for someone to program it.
-
Blackbox would be a nice addition!
The possibility to logg flights and sensors. Whith out the need of oplink.
Maby there already is a "revo" clone that has all funktions. ?
BLHeli or oneshot pass trgogh flashing would be nice to!
Those are both software or firmware changes, not hardware.
Blackbox is cleanflight's modified version of openlog. There's an open issue requesting support for openlog, https://librepilot.atlassian.net/browse/LP-95 it's waiting for a developer to adopt the issue and program it.
The ESC pass through has also been proposed, https://librepilot.atlassian.net/browse/LP-250 and is waiting for someone to program it.
Ah!
But if I understand it correct. There is need for a memory chip or memory card on the FC boards?
ESC pass through sounds promising. I wish I had the coding skills needed.
Last time I did anything was in the late 80´s ;D Remember building controllers for LUXOR ABC 80 computers. Old stuff already then.
Some coding Mecman controllers for automation ect.
We had those 5" soft floppydisk as storage for basic programs. I my memory dosent fail. IBM AT 285 was the hottest and newest PC back then.. Ok.. It was a while ago.. ;D
-
...But if I understand it correct. There is need for a memory chip or memory card on the FC boards?
...We had those 5" soft floppydisk as storage for basic programs...
No, blackbox is an external board with a micro sd card on it. No chips on the FC are required, just one of the serial ports. The board is actually a SparkFun openlog https://www.sparkfun.com/products/13712 cleanflight just modified the SparkFun firmware a little. The board is about 15mm x 20mm.
I started way before the 5 1/4" floppies, the first computer I built in 1975 used an audio cassette for program storage and had a huge amount of ram, 2 thousand bytes. :) After that we had 8" floppies followed by single sided single density 5 1/4" floppies that had a huge capacity, 89 thousand bytes. :)
-
...But if I understand it correct. There is need for a memory chip or memory card on the FC boards?
...We had those 5" soft floppydisk as storage for basic programs...
No, blackbox is an external board with a micro sd card on it. No chips on the FC are required, just one of the serial ports. The board is actually a SparkFun openlog https://www.sparkfun.com/products/13712 cleanflight just modified the SparkFun firmware a little. The board is about 15mm x 20mm.
I started way before the 5 1/4" floppies, the first computer I built in 1975 used an audio cassette for program storage and had a huge amount of ram, 2 thousand bytes. :) After that we had 8" floppies followed by single sided single density 5 1/4" floppies that had a huge capacity, 89 thousand bytes. :)
TY for the info! Learning new stuff every day. :)
So, not stealing the tread. But, then you remember ZX Spectrum. Atari and Commodore..
Adjusting azimut on tape storage stations.. :)
-
Hi! I bought a similar controller from Hobbyking, because I want use with Raceflight firmware. I succesfully update the firmware to Raceflight, but the board can't see the receiver neither ppm, neither pwm mode. I tried with other receiver too, without success. I tried the f4 optimized betaflight version without success too... Otherwise the board working, without problems... (certainly I set receiver type on configuration tab)
I'd like return to open or librepilot, but if I tried update, seemingly succesful, but can't connect to GCS, and I hear periodic "disconnect" tone from PC. On board the blue led nearly constant lighting with little breaks...
I tried update the bootloader, but cannot connect...
What doing wrong?
Thanks for help! Istvan from Hungary
-
Try DFU recovery:
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+DFU
Edit: you need some soldering for SBL pads
-
First I thank you for the fast reply. I tried flashing three times, but no luck...
Certainly raceflight working... (without receiver :( )
here is the batch file's display:
-
Raceflight should not be anymore inside your Revo after you flashed entire flash.
Try Upgrade&Erase:
- Disconnect board
- Hit Upgrade&Erase button
- Connect board
- Wait until board remain connected.
-
"Raceflight should not be anymore inside your Revo after you flashed entire flash."
Certainly I flashed raceflight after I can't connect to librepilot.
I think this board defected, I tried upload+erase option, nothing changed...
Thanks for help, next time I can't buy untested hardware, like this...
-
What happens with Upgrade&Erase ? Works as expected ?
If yes, try flashing manually the resurrect firmware that boot and format flash memory:
From this thread:
https://forum.librepilot.org/index.php?topic=208.msg1329#msg1329
Download this file:
https://forum.librepilot.org/index.php?action=dlattach;topic=208.0;attach=1180
Emergency Rescue Procedure:
Flash and run the resurrection firmware:
- Run the GCS
- Unplug the board from power and USB.
- Go to the firmware tab in the GCS and press the Rescue button.
- Plug the board into USB.
- GCS recognizes the board in a few seconds.
- Press the "Open" button to navigate to and select the correct resurrection firmware opfw file that you downloaded.
- Press the Flash button to write the currently built firmware.
- It will start in a few seconds. First it will erase, then it will write (flash) the firmware.
- When the flash is done, press the Boot button which will cause the resurrection firmware to run
- Let it run for 30 seconds at least. On Sparky2, I see blue and green LEDs for 10 seconds, then just green for another 10 seconds, then the board boots normally (LEDs do the normal operation colors). You might also see just 20 seconds of green followed by normal operation LEDs.
-
What happens with Upgrade&Erase ? Works as expected ?
If yes, try flashing manually the resurrect firmware that boot and format flash memory:
From this thread:
https://forum.librepilot.org/index.php?topic=208.msg1329#msg1329
Download this file:
https://forum.librepilot.org/index.php?action=dlattach;topic=208.0;attach=1180
Emergency Rescue Procedure:
Flash and run the resurrection firmware:
- Run the GCS
- Unplug the board from power and USB.
- Go to the firmware tab in the GCS and press the Rescue button.
- Plug the board into USB.
- GCS recognizes the board in a few seconds.
- Press the "Open" button to navigate to and select the correct resurrection firmware opfw file that you downloaded.
- Press the Flash button to write the currently built firmware.
- It will start in a few seconds. First it will erase, then it will write (flash) the firmware.
- When the flash is done, press the Boot button which will cause the resurrection firmware to run
- Let it run for 30 seconds at least. On Sparky2, I see blue and green LEDs for 10 seconds, then just green for another 10 seconds, then the board boots normally (LEDs do the normal operation colors). You might also see just 20 seconds of green followed by normal operation LEDs.
I flashed firmware, what you recommend!
I think, I took a step forward, because the board' leds flashing (green and blue too), but have another problem, I can' connect to GCS... If I pull down connections menu, I can't set the com port, only two options hava, what I attached...
-
After you run the resurrect you need to reflash the normal firmware.
- Disconnect board
- Hit Upgrade&Erase button
- Connect board
- Wait until board remain connected.
-
Half success! The GCS is connecting, but the board still not detected the receiver...
But I can make a film with problem and send to hobbyking...
Thanks for patience and many many help!
Sincerely: Istvan
-
Post pictures how you connected the Receiver and the config file you use.
File > Export UAV settings
-
I put the third pin the ppm signal from openlrs receiver and configured the controller receiving ppm signal.
-
In your config file still the receiver port configured as PWM input, should be set to PPM, look in Hardware tab.
Remember all changes inside Hardware tab need a reboot.
Did you setup your OpenLRS receiver for PPM output ?
Remember also the PPM input is 12 channels max for Revo.
You can easilly monitor the receiver activity, go to System tab and search for ReceiverActivity Uavo.
More easy for debugging.
(https://forum.librepilot.org/index.php?action=dlattach;topic=394.0;attach=2813)
-
In your config file still the receiver port configured as PWM input, should be set to PPM, look in Hardware tab.
Remember all changes inside Hardware tab need a reboot.
Did you setup your OpenLRS receiver for PPM output ?
Remember also the PPM input is 12 channels max for Revo.
You can easilly monitor the receiver activity, go to System tab and search for ReceiverActivity Uavo.
More easy for debugging.
(https://forum.librepilot.org/index.php?action=dlattach;topic=394.0;attach=2813)
Total success!!!
The board is working, and sense the receiver's signal.
A BIG-BIG thanks for help and patience.
Yours sincerely: Istvan
-
The oplink air port on a revo mini, is this just a serial port connecting the revo mini to the oplink mini air? In other words if you have a revo mini and don't use the oplink port can it be used for other items (OSD, GPS, etc )
Ben
-
Cannot be used for OSD or other accessories. Just his "Oplink Air"
-
What kind of port is it?
-
It's for their oplink air. They took the RFM22b radio module off the bottom of the revo, ran the wires that went to it to a connector, and put the RFM22b in a separate case. Unless you're writing your own firmware for the controller it can't be used for anything else. It should have power, ground, and 5 of the processor's pins related to SPI. Most of them are shared with the flash memory chip.
-
Hi, any idea why Sonar port is disabled in HW Settings tab, and how can I enable it? I need it for voltage divider.
-
yes, disabled in HW tab.
For sensor setup, take a look here:
https://librepilot.atlassian.net/wiki/display/LPDOC/Configure+a+Current-Voltage+sensor
-
Thanks a lot! I see how to activate now:
1 - Connect the board to your computer and got to the System tab in your GCS
2 - Browse the first part (Settings) and find the HwSettings UAVObject
3 - Enable the Battery module : OptionalModules > Battery > Enable
4 - Set the analog input pins for voltage and current :
ADCRouting > adc0 > BatteryCurrent
ADCRouting > adc1 > BatteryVoltage
-
Exactly, like explained in wiki page. Congrats :)
Be sure you do not over voltage the inputs, Revo Mini do not have ESD protections.
-
I'll do my best! :) Thanks for the tip!
-
Hi everyone.
I need little help.
I am trying to use a FM800 MINI FASST RX. It is S-BUS&CPPM only with the Revo mini.
Can the revo still work with CPPM? That is what I set it to.
I tried to run the quad after using the libre pilot but one motor wont run and the others stutter.
I all so could not get my switch to activate in libre pilot and just skipped it.
I have it 5v reg.
The RX is blinking fast, so that's suppose to be CPPM mode. I am just now wondering if it saved it? Could revo mini still kind of wrok in S-BUS mode?
I know this may sound all bad, but I wont give up. Thanks
-
Green led flashing fast mean Sbus i think.
Seems this need to push again the button to go back to solid Red for save and power cycle the receiver.
All boards support PPM and S.Bus input (MainPort) at least.
(https://forum.librepilot.org/index.php?action=dlattach;topic=394.0;attach=3731)
I tried to run the quad after using the libre pilot but one motor wont run and the others stutter.
Another issue maybe...
I all so could not get my switch to activate in libre pilot and just skipped it.
This means all previous stick while following the radio wizard works ?
If yes, you may need to declare your switch for one chanel output in your radio.
Please note CC3D and Revo are two different boards, "Revolution" is just a Chinese marketing name.
-
Green led flashing fast mean Sbus i think.
I will check
Seems this need to push again the button to go back to solid Red for save and power cycle the receiver.
Got it
All boards support PPM and S.Bus input (MainPort) at least.
I just found out S-B is digital and CPPM is analog, I will switch to S-B;
This means all previous stick while following the radio wizard works ?
yes they worked.
If yes, you may need to declare your switch for one chanel output in your radio.
I need to find out how to activate the switch.
Please note CC3D and Revo are two different boards, "Revolution" is just a Chinese marketing name.
Got it. I have the Revo mini black case. My friend has the CC3D yellow case.
So I think as you said, I have it in S-B mode.
So I need to back and recognize it in librepilot as S-B instead of CPPM/PPM. As it is, it is seeing it as CPPM/PPM.
-
That not a case color, yellow or black.
CC3D is one board, and Revo another board.
Two different boards, with different capabilities. Simply not the same.
If your stick are recognized, there is no issue with your input.
PPM or Sbus works or not. Cannot be a issue with half working input.
Check your radio for switch/channel output.
SBus need the receiver connected to the MainPort
-
That not a case color, yellow or black.
CC3D is one board, and Revo another board.
Two different boards, with different capabilities. Simply not the same.
Got it f5soh, Thank you. I put a picture of the one I have on my last post, mini revo.
If your stick are recognized, there is no issue with your input.
PPM or Sbus works or not. Cannot be a issue with half working input.
I thought so. I will also switch mode librepilot to S-BUS, because its in PPM mode and the RX is in as you said, in S-B mode. I hope this is it.
Check your radio for switch/channel output.
I need to find out how to activate the switch futaba 18SZ
SBus need the receiver connected to the MainPort
It is
-
If you have a Futaba 18SZ i hope you can activate a switch :D
-
I thought I had a bad esc, but I cheeked it on channel 2 and it worked. so there must be a problem with the first channel in the controller.
Can selecting The wrong modulation cause this? PPM/S-BUSS
I need to send the controller in for repair.
Where do you send them too?
-
...I need to send the controller in for repair.
Where do you send them too?
You'd have to contact whoever you purchased it from and see if they'll replace it. Anything else the parts and labor would be more than the price of a new board.
-
Thank you hwk.
I thought I had a bad esc, but I cheeked it on channel 2 and it worked. so there must be a problem with the first channel in the controller.
Can selecting The wrong modulation cause this? PPM/S-BUSS
-
Old thread, but generally not.
You problem could be incorrectly set output type (PwmSync / OneShot / etc), bad ESC, bad motor, bad connector, bad FC output. Move things around to find what is the bad thing. Bad FC output can be worked around by moving ESC connector to a different output, and changing from 1-1 2-2 3-3 4-4 x-x to x-x 2-2 3-3 4-4 5-1 (I forget exactly what it looks like).
-
Somewhat off topic, but does anyone know what the UART 6 tx pin might be?
Is the oplink breakout actually an UART?
-
UART6 Tx (BF) is FlexiIO-pin5 because they removed the pin3 and pin4 in RevoMini, should be FlexiIO-pin7 in normal Revo board.
https://librepilot.atlassian.net/wiki/display/LPDOC/Revolution+Configuration#RevolutionConfiguration-FlexiIOpinOut/Functions