@111123 wrote:
Hello,
i am trying to configure how to mount an external IMU to pixhawk 2.4.8,because the internal one has a very big error and in combination with the GPS error the position of the vehicle is way of track.
First of all is it possible to do it?
If it is do i have to program it to feed the data in a certain way, or is there a more automated way?
Thank you in advance.
Posts: 4
Participants: 4
@Oliverl96 wrote:
Hello,
My first ArduPilot helicopter build is coming to an end, but Im concerned about a few things regarding the build. As visible in the photos I have mounted the RC antennas as well as the FPV video antenna for optimal signal. What I dont know though is if this is a terrible idea that will vibrate and mess with the FC way to much. Another result of all this weight on the tail is that the heli is tail heavy and requires about 250-300 grams of added weight on top of the battery for it to balance around the main shaft.
Any input would be much appreciated.
/Oliver
Posts: 1
Participants: 1
@tj272004 wrote:
I’m currently attempting to build a drone using the DALRC Rocket 4 in 1 ESC Engine and my APM. I’m new to this field and had some questions about wiring the ESC to the APM. The ESC comes with 4 1-pin motor wires, a 1-pin Curr wire, a 1-pin 5V wire, and a 2 pin GND and VCC cable. I was wondering where I plug them into the APM.
Posts: 4
Participants: 2
@ShrimpWang wrote:
Pull up the latest code from git and compile it using vs2019
Posts: 1
Participants: 1
@wicked1 wrote:
I’m using crossfire, and now w/ rc2, I get constant GCS failsafes. I get them at times when I have not lost telemetry. The signal hasn’t changed, my MP screen is still updating.
FYI, the telemetry signal level is always detected quite low when using crossfire… About 20% is actually the max. It has something to do w/ Crossfire not sending as many packets (or frames or something) as MP is expecting… but it has always been this way.Does " continue-in-pilot-mode" let me keep flying manually, even if there is a failsafe? If so, that would be good for GCS, but not for RC.
Posts: 1
Participants: 1
@Oeble_Huygen wrote:
Hi , Im in the middle of a project.
I have a Joystick working perfectly all modes buttons ect. But i would like to control my Gimbal with the D-Pad on the joystick. The D-pad is recognized as axis 6 and axis 7 in Qgroundcontrol . How do i couple the axis 6/7 to RC/Servo 10 and 11 on the Pixhawk ( these are connected to the Gimbal and working with Radio control )?.
Posts: 1
Participants: 1
@Yaman_Aggarwal wrote:
The throttle, yaw and roll sticks are not being calibrated while only the pitch stick is being calibrated. Please can anyone tell why this is happening.
Posts: 1
Participants: 1
@jace26 wrote:
The other day just prior to launch on an auto mission, while the aircraft was armed and on the ground the GCS showed and verbalized an uncommanded disarm followed shortly by an (also) uncommanded arm. We looked at the tlog and it did show this happening, but the DF log did not show it. A closer look at the tlog again shows a disarm for less than a second:
Never saw this before, and haven’t seen it sense, but the guess is a bad packet? comic ray flipped a bit?
looks similar to this post from some years ago over on copter:
Posts: 1
Participants: 1
@sdeal3 wrote:
(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Posts: 1
Participants: 1
@sdeal3 wrote:
I have been successful uploading the firmware to a Pixhawk 4 using ./waf and connecting to Mission Planner. Now I was following the tutorial on the wiki explaining how to build an example library and I haven’t been able to get that to work right
I run the commands in a windows linux terminal:
$ ./waf configure --board=Pixhawk4
$ ./waf build --target examples/INS_generic --uploadand the build seems to execute successfully and ends with the output
Build commands will be stored in build/Pixhawk4/compile_commands.json
‘build’ finished successfully (3m39.033s)However, when I try to connect to a serial terminal on PuTTY (COM9, 57600) to view the output it fails to connect. I have also tried mavproxy with the command
$ mavproxy.py --master=/dev/ttyS1 --baudrate 57600 --setup
and the output that I get is
Connect /dev/ttyS1 source_system=255
Log Directory:
Telemetry log: mav.tlogand no other output, not the output of the library that I was expecting. Additionally, in case its relevant, when I try to run
$ mavproxy.py --master=/dev/ttyS1
I get the output
Connect /dev/ttyS1 source_system=255
Log Directory:
Telemetry log: mav.tlog
Waiting for heartbeat from /dev/ttyS1
MAV> link 1 downMAV>
Doesn’t seem like that is working either. Any ideas what I am doing wrong? Thanks
Posts: 1
Participants: 1
@hwurzburg wrote:
Quadplane moved into a new realm with the additon of QACRO in 4.0…
the Convergence will never be a mini-quad…but its still fun…PID defaults need a bit of tuning…but acrobatics and gate-racing is certainly a possibility now…
Posts: 1
Participants: 1
@Leonardthall wrote:
I am starting this thread for people to propose a default parameter set for sub 250 sized aircraft. This should make it much easier for small multirotors to be set up using ArduPilot.
I would like as many people as possible to post what they believe is the important parameters to change to get good performance from this class of multirotor.
Posts: 1
Participants: 1
@Mirko_Zhou wrote:
Dear community,
I’m using the Sik telemetry to connect my rover with the Mission Planner.
Inside of the room, it works perfectly fine. However, when I do the field test outside under the sun in a sunny day, sometimes the telemetry will stop working suddenly and the connection will be also interrupted. So is it because all the telemetry has the same problem and I should avoid drive my vehicle under the sun ? Or I need to purchase a better telemetry that can work under the sun ?
Posts: 3
Participants: 2
@banjing wrote:
Hi experts, i would like to ask for your help please if will this kind of Obstacle avoidance sensor works for my Pixhawk 2.4.8? If yes, how to configure? I didn’t see much online about this sensor.
Posts: 3
Participants: 2
@brunoolivieri wrote:
Topic: Support for Travel to Ardupilot Unconference 2020
Proposal type: Hardware [ ] , Software [ ] , Other [X] : Travel Expenses
Description: I would like to attend at the ArduPilot Unconference 2020. I believe it would be an incredible opportunity to interact and strengthen communication with the development team. It is even better as, by 2020, there will be a day that focuses on documentation, and this has been the area I have been trying to help.
Unfortunately, I cannot afford the cost of this long and expensive trip at this opportunity.
I am requesting support to cover the costs of flights (BSB->CBR, (35h to 46h hours of Economy class)), and accommodation for the pre-unconference meet-up, and accommodation for the unconference itself. The quoted value below includes accommodation at the proposed hotel for the conference.
Many thanks in advance,
Bruno Olivieri
Planned amount $$ (USD): $2900.00
(2.1k for the flight and .8k for accommodation)
Estimated time for completion: Mar 2020
Posts: 1
Participants: 1
@kevin1lin wrote:
Hi all,
We would like to use the “Point Camera Here” function is Mission planner to the camera. The gimbal camera system needs to be controlled with the computer due to its unique communication protocol that is incompatible with Pixhawk. Here is how every components are connected in our setup:
MP <-> Pixhawk <-> Companion computer <-> gimbal camera
I looked into how “Point Camera Here” works. MP will issue an MAV_CMD_DO_SET_ROI to Pixhawk. My problem is that I’m not able to forward the command to the companion computer. I could get the DIGICAM_CONTROL (“Trigger camera NOW” in MP) command to the computer though.
Is it possible to get make this setup work? Thanks.
Posts: 1
Participants: 1
@banjing wrote:
Hi Experts, I created a drone for mission purposes using Pixhawk 2.4.8 and ArduCopter 3.6.7. I use SJ6 Legend Camera for triggering photos and video, and use FlySky for switching between Photo and Video, and it works, When switch to Photo, i autocamtically take photo every 5 seconds. When switch to Video it capture video footage.
My concern is, i want to use DO_DIGICAM_CONTROL so that it will take photo everytime i called in in every waypoint. So, i started the mission, switch it to Video to record the place. This is my mission commands: In my undertstanding It should capture on every waypoint right? but it didnt.
Posts: 1
Participants: 1
@xingxing wrote:
QGroundcontrol can’t retrieve full set ofparameter after connect to plane .it can be use to upload flight plan and see the plane position etc,but the FC parameters can’t be change via QGC,we have to bring anoter laptop computer for changeing parameters ,It’s very inconvenient. the mission planner works fine with this plane.
I have create an Draft in QGC page of this forum but don’t receive any information,please go to
https://discuss.ardupilot.org/t/the-qground-control-cant-received-full-set-of-parameters/48773?u=xingxingsome one said it’s in the noisy connection,the high lost rate will indeed triger this message,but my friends have the same problem in another flight area with the same hardware,so i’m not sure if this problem is due to firware.
my hareware :minitalon,F405 wing installed arduplane3.9.9 firmware,ULRS(Ultimate long range system).
the main problem maybe is the ULRS,because if i use 3DR telemetry ,the QGC works fine,
any recommendation about this problem ?thanks
Posts: 1
Participants: 1
@Airpig wrote:
Not sure what exactly happened, this is my first time with an X2.1 in the Plane. Armed, throttled up and when I threw it sharply rolled then nose dived about 10 feet off the ground.
Internal Compass was off turned off at the time.
Nano Talon AUGW ~668g (that may have been the issue)
mRo X2.1-17N
mRo Neo-M8N Dual Compass
Titan Power 3S 3.5mAhJust throwing it out there until I can take a look this weekend.
Posts: 1
Participants: 1
@Roi.15 wrote:
As seen with the video above, the lower end of the throttle curve seems normal but as soon as it reaches this ~10% curve range the drone starts to jump and do this spin.
- I thought it was getting caught on an edge so I changed the surface of launch
- I calibrated the ESCs through the transmitter procedure.
- I made sure the motors are spinning the correct direction: top left is CW, top right CCW, bottom left CCW, bottom right CW. I also made sure that the props are the correct ones.
I also had to switch two wires on 2 motors to get the direction correct.
When I was trying to calibrate the ESCs I was changing the RC values a little bit (I thought that was the min and max range of throttle) I’m not sure if that might have resulted in the problem?Thanks!
Posts: 1
Participants: 1
