@egunak95 wrote:

Airspeed sensor 4525D with PCA9306 Dual Bidirectional I2C Voltage

4525d to PCA9306.JPG3072×2304 627 KB

-Level Translator

Posts: 1

Participants: 1

Read full topic

@AndreyI wrote:

Hi!
Connect to Matek f405 Wing, RGB LED WS2812B. in 7 servo channel connected servo “VTailLeft”, in 8 servo channel connect WS2812B. As soon as I set the parameter SERVO 8_FUNCTION = 120, the LEDs start to work, but stops working 7 servo channel.
Is it a bug or a feature of f405?

Posts: 3

Participants: 2

Read full topic

@jace26 wrote:

So I just tried to play around with Plane 4.01 on a test bird and had an interesting issue. When I would switch from Manual (default mode) to Qstabilize the attitude displayed on MP would shift drastically from a zero roll, zero pitch (the actual orientation) to a nose-down 35deg, and wings level attitude. Switching back to the manual would revert the attitude to nose level. This was with the same parameters that I had on when using Plane 3.9.10, and a rollback to 3.9.10 showed this issue was not present under the same conditions. Any clue as to what might be happening here?

Posts: 1

Participants: 1

Read full topic

@KadaverJoe wrote:

Hi folks,
I upfloaded the new ArduPlane 4.0.1 firm.ware to my Pixhawk 4 and tried to fly some Auto-WP missions to create some orthophotos.
I have the problem that the camera feedback trigger via hotshoe does not work properly. So I did some trials with the camera hooked up on the bench. I armed plane and then took about 18 pictures with the “Trigger camera NOW” command.
After downloading the logfile I tried to use the geo ref images tool and loaded the correct log and photos. When I choose Trigger Message as source it shows less trigger messages than actual picures taken.

Before the fw upgrade I used ArduPlane 3.9.7 and it worked fine (at least I did two missions with roughly 1800 pictures each and it worked perfectly!). So I tried to downgrade to 3.9.7 again. Thing is that no log is created in the earlier fw versions anymore. I checked the “LOG_BACKEND_TYPE” and its set to 1 and the bitmask is 65535. @tridge: What could cause that problem?

Posts: 1

Participants: 1

Read full topic

@andree wrote:

Hi I need now the communities help.

I built a Peon 230 based copter with Kakute F7 AIO FC using Chibios and a NEO 6M GPS with integrated compass. My Radio is now the Taranis 9xD Plus with the X8R .

I went through the complete first installation process in setting and calibrating the copter completely and to my belief correctly.

The first problem, which led me to the second problem, I encountered was that the EKF remained red. Due to a poor satellite signal, so no arming. It did not mater which configuration I chose, I got max. 10 satellites the mean number was 7. Funny wise I got more satellites under my roof window inside than outside on the free field with blue sky. I read a post that with copter 3.6 there might be an issue in configuring the GPS. So I tried to step down to 3.5. I missed because I could only find the 3.6.2 version for the Kakute Board. This is currently my arducopter versionI have installed. Nevertheless it did not change anything! I now remained with the value 67 to get GPS+SBAS+GLONASS.
In order the to get a white EKF in the HUD I changed the EK2_GPS_Check from 31 to 3. So just NSats and HDop as preflight check.
The third Problem is that the compass deviates around +13° even after various calibrating sessions which I concluded always ok.

As I could not find a better situation I wanted nevertheless to check how it behaves when flying.

Big Mistake!!! I am currently printing all parts again, all!!!

Before the flight I checked how the copter behaved without props.

Quite aggressive reaction of the throttle in stabilised mode in Alt Hold the motors ran to my felling very stable with mid revs.

So I decided to go with props Alt_Hold.

Before the start I checked the gps with 7 satellites (I know poor).

In the middle position of the throttle the copter took off with some toilette bowling, but not very heavy. I put a little bit more throttle and then it flew away in the sky and did not react on the throttle position anymore.

With the climbing speed the copter showed I was very stressed, so I decided to cut off the motors. It fell, I then switched on the motors again. It recovered but went up again with the same speed. I did this 2 times then I crashed.

Except of one antenna leg from the X8R and all the plastic nothing was damaged.

Could you please explain me what did I wrong? Is it a vibration, GPS or compass problem? The copter flew quite good with Betaflight.

I would be really grateful for your help. I put already so much time in this project I must get it going.

I will attach the log of the flight as well as the params file.

Thank you very much for your help in advance.

Kind regards,

Andreas

2019-12-06 11-43-30.tlog (212.4 KB) 2019-12-05.log.param (15.4 KB)

Posts: 2

Participants: 2

Read full topic

@anbello wrote:

It is the second time that this happen to me. The first time with a little 3inch with revo-mini so I have no log. The second time happened with a 5inch with Pixracer and so I have the log.

I did Autotune on the three axis, I tested both old and new PID in flight then I landed with Autotune On and disarmed. After this I saw on GCS (Tower on Android phone) the new PID, but after power off - power on I saw the old PID.

Using mavparms.py I could extract the parameters both from df log and from tlog. On the first I have old PID and on the second new PID.

I attach dataflash log, telemetry log, params extracted from dflog and params extracted from tlog.

I have to say that I was using Copter-4.0.0-rc2 with PR #11886 from @andyp1per applied cloned from here.

Posts: 6

Participants: 3

Read full topic

@TheTroll wrote:

Hello!
I’m using arduplane 4.0.1 and qgroundcontrol
Strange thing happened and I cannot find RSSI_CHANNEL parameter in parameters list.

Could you please advise how to configure rssi over sbus channel?

Thanks!

Posts: 2

Participants: 1

Read full topic

@hosein_gh wrote:

Hello everyone
Whats RSSI input doing in ardupilot ?
Is it just for showing in GCS? Or its involved in flight performance

Posts: 4

Participants: 3

Read full topic

@MickeM wrote:

Hi

One of the more time consuming parts when fiddleing with electronics is to find out the most obvious things like for the USB-port… do Data+ go to Data+ and Data- to Data-? Or Data+ to Data- and Data- to Data+? (I am connecting a USB-LED-module to the Carrier Board for a Cube 2.1, both have D+ and D-.)

Rx goes to Tx and Tx goes to Rx, I2C Data goes to I2C Data and I2C Clock goes to I2C Clock… that I know. But the above? Why dont write things like that on all pinouts, if it is known, I may wonder.

/MickeM

Posts: 2

Participants: 2

Read full topic

@dogangcr wrote:

Hi,

When I move stick for arm to f450 , there is no movement on the motor .When I connected via mission planner, armed and disarmed messages have seen on the home page.
Compass and radio calibration setting was done.
When I tried to esc calibration, esc calibration didnt do correctly…
I followed this tutorial https://ardupilot.org/copter/docs/esc-calibration.html and this video https://youtu.be/gYoknRObfOg.
3 beep sound didn’t come from esc. How can I solve this issue? When I plug the battery, apm start normally without 3 beep sound.(I have 3s battery btw.)

My setup:
f450 frame
apm 2.8 V.3.2.1
Sİmonk 30A esc
ready to sky rs 2212-920kv.
FLysky i6 mod 1

Posts: 2

Participants: 2

Read full topic

@voi9viper2 wrote:

I have been trying to get telemetry to work for literally months. I have tried everything I could find. A max3232 converter did not work. Several circuits I found on the internet did not work until I built the attached converter. It must be supplied with 5V. 3.3V does not work. 2n3904 transistors can be used instead of BC547s, but the pinout is reversed. I think the problem is the voltage levels needed by the r-xsr receiver, but it could also be the max232 mini converters I got from amazon. I got one out of 10 to work with my pixhawk FC. The circuit came from a german website, kudos to whoever designed it. !
frskyinvert|659x208

Posts: 1

Participants: 1

Read full topic

@voi9viper2 wrote:

My Wraith ESCs all work fine with my Pixhawk2, but I can’t get telemetry to work. I wired all the telemetry wires to Serial5’s RX pin, set BATT_MONITOR to 9. I’ve used SERVO_BLH_TEST to check all six ESCs, and they all pass. Is there anything I’m missing?

Posts: 1

Participants: 1

Read full topic

@Filipe_Januario wrote:

Hi,

I’m new here and I’m also new on drone world.
I’m trying to connect and configure my ardupilot module and I downloaded APM Planner v2.0.24 for windows.

I Install and run software but when I go to Initial Setup / Install Firmware, I select the ArduCopter (I’ll configure it for F450) and on CLI it apears the message “APM planner flash button clicked without any HTTP links!”

I’ve already tryed with v2.0.27 for windows but it’s even worse (don’t show the devices buttons to select wich on I want to configure for).

I’m running W10 on a MS Surface Pro. Can please anyone help me?

Thank you

Posts: 3

Participants: 3

Read full topic

@ChrisOlson wrote:

So I have never been all that happy with the heli throttle controls in ArduPilot. We improved it a lot, especially for pistons and turbines, in 3.6 and 4.0. But there is still room for improvement.

So I’ll highlight the changes here:

• The old RSC object is deprecated and replaced with a Throttle control library. Governor and throttle curve moved to a calculate_autothrottle() function. Logic for both single and twin-engine helicopters. Logic for Manual/AutoThrottle controls.
• Governor is re-designed and operated by on/off switch instead of automatic. This was done for commercial-grade helicopters to manually disengage the governor in the event the speed sensor partially fails and causes erratic governor operation
• There is no “throttle modes” you can select like RC Passthru, ESC Setpoint, etc… The throttle control system has been replaced with a Manual/AutoThrottle system like full-size aircraft autopilots use
• There is no longer any “motor interlock” or “throttle hold”. That is transparent in the design of the control
• Fully supports twin-engine helicopters with dual channel Manual and FADEC-style AutoThrottle controls. Including individual engine runups, split-needle checks, in-flight shutdown and securing of a problem engine while continuing powered flight on the operating engine
• Allows for in-flight restart of an inoperative engine, independent of the operating engine, if the engine is electric start (or electric motor)
• Allows shutdown and restart of piston or turbine engines for refueling, without disarming the flight control
• Since ground idle is controlled by the RC radio instead of the flight control, allows for multiple ground idle speeds to be set for starting/warmup of piston engines using Ecotrons Electronic Fuel Injection. And advancing the throttle to 100% for the Ecotrons ECU to “learn” the 100%, 0% and ground idle throttle positions prior to engine start. This start sequence has to performed on every cold start with a Ecotrons EFI

It is obviously heavily slanted towards piston and turbine power and provides no advantages for electric helicopters. It was not developed for ArduPilot. It was developed because the existing controls in ArduPilot are not able to start the engines in some helicopters I’m testing. Nor does ArduPilot have support for twin-engine.

It is based on the fact that there is legacy cruft in the code (IMO) to do things that a RC radio is much more adept at doing. And the RC radio is an integral part of the entire system.

• Like the ESC Setpoint. Totally not needed. Just set a flat throttle curve or set the throttle percentage sent to the control with your RC radio
• Want “idleups” because your Castle ESC supports it? Set your throttle curve to 100% and use a three-position switch to set the throttle control channel output to off, Idle1, Idle2.
• Need a low idle/fast idle for piston engine starting/warmup? Set a three-position switch to move your throttle channel from fuel cutoff, low idle, fast idle - while still enjoying the advantages of the AutoThrottle with governor. Many people aren’t even flying with a ground station anymore with telemetry to the RC. If you need to adjust your engine idle speed can do it in in the RC radio - don’t need a ground station computer for that.

Bill and I (mostly me) talked about a potential RSC overhaul for heli for about the last year. This is a demo of my “vision” of how it should work, the concept derived from how full-size aircraft AutoThrottle systems work.

Posts: 1

Participants: 1

Read full topic

@seth_poh wrote:

Hi all,

I was trying to run a simple mission where the vehicle takes off to an altitude of 5 m and fly to the next waypoint and perform loiter unlimited.

However I observed that the altitude of the vehicle seems to be off. I estimated it to be about 2.5 m rather than the programmed 5 m. I have included the logs and the mission here:

But the baro and gps altitude seem to be correct.

I am wondering anyone here experienced this and have solved this issue.

Thank you.

Posts: 1

Participants: 1

Read full topic

@deofdix wrote:

Hello. I need your help. My drone flies over corn fields at a speed of 8-10 m / s, and I would like to improve height control with lidar / sonar. Can I connect two lidars / sonars in a downward direction? How will the pixhawk height be considered (one priority or average), or can it be done using arduino (get both values and send the average to the FS). Many thanks.
P.S. what is the best firmware for these purposes 3.6 or 4.0

Posts: 1

Participants: 1

Read full topic

@OldGazer wrote:

Yesterday I installed a MAUCH HS series 100A current sensor. I have a Tarot 650 Sport frame. FC is a Pixhawk 2.4.6 running the latest stable AC firmware.

The previous sensor was the ubiquitous 3Dr style rated for 6S and 90 Amps.

The MAUCH sensor is mounted between the rail mounted battery tray and the lower frame plate.

Pixhawk is mounted on a vibration damper mount that is attached to the top plate. The Pixhawk is approximately 50mm above the current sensor.

The M8N GPS/compass puck is mounted on a fiberglass canopy. The GPS puck is approximately 85mm above the MAUCH sensor.

I am using a Taranis X9E running Flight Deck telemetry

Prior to installing the MAUCH I have had NO issues with either compass. I did a test flight this morning and after about 5 minutes or so of hovering I switched from Stabilize to Loiter and shortly there after my radio started “pinging”. I glanced down at the display and saw “EKF2 IMU1 ground mag anomaly, and EKF2 IMU1 switching to Compass 1.”

12/8/2019 Data Flash Log (.bin)

Posts: 5

Participants: 2

Read full topic

@Maayan_Fish wrote:

hey guys,
My quad is at my room, so there is no GPS fix. however, it still arms.
I went to configuration and ticked this setting
Standard Params -> Arm Checks -> GPS lock

I dont understand why my quad did arm. There is clearly something wrong here.
this is the log file:
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = GOOD - No MAG data, unable to test mag_field interference
Test: Dupe Log Data = GOOD -
Test: Empty = FAIL - Empty log? Throttle never above 20%
Test: Event/Failsafe = GOOD -
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = UNKNOWN - No IMU log data
Test: Motor Balance = UNKNOWN -
Test: NaNs = GOOD -
Test: OpticalFlow = FAIL - ‘FLOW_FXSCALER’ not found
Test: Parameters = GOOD -
Test: PM = UNKNOWN - No PM log data
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = GOOD -

does anyone have any idea ?
A few days ago it did not arm, which is what I expected as I saw the failures in the log.
Now for no apparent reason, nothing has changed and it does arm.

Posts: 2

Participants: 2

Read full topic

@wicked1 wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@rmackay9 wrote:

Copter-3.6.12-rc1 has been released for beta testing. The changes are in the ReleaseNotes and copied below. The upgrade from 3.6.11 should be painless, no re-calibrations or tuning should be required.

This release has two fixes:

1. Fix ChibiOS I2C DMA error
2. COMPASS_SCALE param to allow manual correction of compass scaling

The first fix resolves a rare case where the flight controller could lock up if there was excessive noise on I2C bus. We have one report of this happening from a core developer who accidentally connected a serial sensor to an I2C port.

The second issue allows users to work around a compass scaling issue with the Hex Here2 GPS/compass unit. The Here2 compass unit’s scaling is off by about 17% meaning setting COMPASS_SCALING = 1.17 should improve accuracy. The accuracy can be checked before and after this change by:

• fly the vehicle in any mode but ensure the flight includes chaning the vehicle’s heading
• download the dataflash log and check the NKF4.SM values which are the compass’s “innovations” (the difference between the expected values and actual values). Lower is better so hopefully Here2 users will see lower values after setting the COMPASS_SCALING value to 1.17.

Note: we can only run a single beta at a time so Copter-4.0.0 beta testing is suspended for about a week. We will be releasing Copter-4.0.0-rc3 by next monday (Dec 16th).

Posts: 3

Participants: 2

Read full topic