The links above seem to be to websites in Chinese. Can someone please tell me where to see an English version, or how to change what I am seeing to English if that’s an option.
Sorry, we are trying to create English instructions
—Original—
Can you give me your email?
Yes, sent it to you via PM.
Hi I reported that the mRo v21. is not flyable when in loiter mode. rc-2 chibiOS but flies realy nice in RC-1 nuttx. If you get a chance can you look at this for me. " I donate when i can" in the video below shows the craft working well in Nuttx sorry for the OT “https://www.facebook.com/485789568436939/videos/651634608519100/”
For a direct comparison, could you post dataflash logs of flying rc2 with ChibiOS and rc2 with NuttX, preferably one after the other?
We expect them to fly the same, apart from ChibiOS having improving timing accuracy
Cheers, Tridge
Thank you, odd, looks like i getting a timeout when uploading any new firmware I been reflashing a lot. Here is the link to the Chibios log as of a few days ago: Dropbox - File Deleted - Simplify your life
and here is the link to the nutxx 3.6-rc1: Dropbox - File Deleted - Simplify your life
@Quadzilla Those two logs use quite different parameters, different PIDs, different accel-cal, different compass-cal and detects different sensors. Are you sure its the same frame?
For a comparison test like this I need two logs flown back-to-back with exactly the same parameters. Don’t do any calibration between them.
Cheers, Tridge
1 Like
Bummer I thought i was sending back to back logs can be hard keep track! I will remake them for RC-3
For everyone who has a development test PixHackV5, please be careful to check compass orientation with the latest firmware. I have made changes to which I2C bus is considered internal to match the production hardware, and that means the development boards are now incorrect.
Please check that COMPASS_EXTERN2 is set to 0. You may find it gets detected as 1 with the new firmware. This will affect boards that are not oriented in the normal orientation.
Also, I have now added separate builds for the CUAVv5 board type. They will appear in the download directory shortly.
1 Like
Why we always need IO Processor? Main Processor has enough IO port , I think it’s redundant for us.
For folks doing dev builds the waf configure command is now:
./waf configure --board CUAVv5
Can anyone summarize what the standard Arducopter firmware support is with this CUAV V5. Can it be loaded on this autopilot or does it still require a special CHIBIOS procedure ? If so, is the CHIBIOS install documented somewhere ?
Thanks
1 Like
It does not require anything special. The CUAV Pixhack V5 is now in the automatic builds: You automatically get the ChibiOS RTOS by simply downloading the firmware from here:
http://firmware.ardupilot.org/Copter/latest/
I was only referring to folks doing development builds for the V5 controller, which I do 2-3 times a day to test different things. End users can simply use the pre-built firmware.
1 Like
thx. What is the difference between the two files? (i assume a firmware version supporting blHeli ?)
arducopter.hex
arducopter_with_bl.hex
Your assumption would be the same as mine, as I don’t know for sure what the “with-bl” is all about.
_bl is with the bootloader. after flashed once you don’t need it again.
1 Like
I just got my Pixhack V5 and connected to MissionPlanner. It was not showing the right parameters so, I figured I would flash the latest firmware. Now, I cannot get the USB port to be recognized. It say setting up PX4 FMU v5x and then fails with USB not recognized. Any help would be greatly appreciated. BTW: Windows 10.
Maybe try something here?
Thanks - I had to switch to Linux to recover the board.
Unfortunately, after getting it to boot up, I have 2 dead USARTs and the GPS port does not appear to be working either.
Does anyone know how to get support/warranty replacement/repair from CUAV?
Or, even get in touch with them?