Hi Randy, thanks for the looking at the log. Yes it is an external compass (Radiolink TS 100 mini that has QMC5883L chip). So the driver was detected correctly I think.
Unfortunately I have no idea of what I could check further, I have two TS100 units, both not working on Chibios. And works not very good on NuttX, having strange peaks I’ve described in Compass stop working but remains healthy
I’ve disabled all the peripheral devices to avoid interferences but that did not solved the issue.
I will also check on v3.5.
@rmackay9 here’s a new log with the compass calibrated, I was just hovering. The EKF Mag innovations are all zero as I reported in another thread. Could this be to do with using the compass with the large offsets? It seemed to go away when I excluded the external compass.
Cannot get Mavlink telemetry to work on any of the serial ports. Using the Matek 405CTR Tried UART3 (Serial1) and UART1 (Serial3) neither work selecting protocol 1 and Baud 57. If I flash with Arduplane using same serial parameters it works fine and the crossfire picks up all the telemtrey. Is this a bug? Thanks,
BATT FAILSAFE - I could not find the options for BATT_FS anymore. The parameters are available on the full parameters list (MP), but it´s blank at the tab Mandatory Hardware - Fail Safe configuration. I am still able to define the voltage and mA limits, but not the ACTION. The Radio_FS is OK.
PHLD_BRAKE_ANGLE & PHLD_BRAKE_RATE seems to be ignored. I have tried high values, but the behavior did not change at all. The drone brakes very slowly after release the sticks (in PosHold). It drift about 3 to 4 meters before stop. DZ and TRIM were checked and are accordingly.
Hi all
I upgrade my small 250 quad to 3.6.0-r12 from 3.5.7
I performed autotune but. I notice problem when copter is in loiter mode and I try yaw copter rise and down. ( 2-4 m)
Did anyone notice a similar problem https://drive.google.com/open?id=1VYxvUQr4PM3NhYYmnWs5UzzinO-3ykjV
I had problems similar to this, setting INS_ACCEL_FILTER and PSC_ACCELZ_FILTER to higher values fixed it for me (I am using 40). It could also be a baro problen, but I guess if 3.5.7 works fine then maybe not.
I noticed this weird interaction in my Pixhack v3 running 3.6.0-rc12, where it seems to be overheating, or something cause after a flight, i touched it and it was so hot, it almost burned my finger. Is that normal? Or am i just being weird?
I have a question.
Might be something I simply never noticed before…but thought I would ask.
so I have my new build on the bench. Transmitter is powered off.
I plug a battery into the quad and I hear mission planner express the different calibrations and such as the machine readies itself.
Finally is says Pre Arm Hardware Safety Switch…wait a minute my tx is still off. Should it not be concerned there is no RC in. It does say throttle below failsafe. If I hit the safety switch it all messages clear and I am ready to go…well sort of…the tx is off so it’s not going to arm.
Oh and the other odd thing is I have a Solid green status led…which the literature says is your good to go GPS acquired. No way that is right, I am in the basement with an hdop of 100.
Is this normal…is it just that i never noticed before
It’s a quirk. Until we see an RC receiver we don’t ever consider it
“bad” for the purposes of the SYS_STATUS mavlink message. This is on
purpose - possibly for RC-less flying (which some people do, relying on
channel-overrides or simply using guided modes.
Looked at the log. The temperature “jumps” because the log is not being recorded while the drone is disarmed, but the temperature keeps increasing. In the Mission Planner log viewer, you can use the “Use Time” checkbox to see that the temperature just increases slowly the whole time, even while disarmed.
I am not familiar with the Pixhack, but certainly 80C is too hot. Is it exposed to direct sunlight? Does it still heat up a lot if you leave it inside?
Thanks Peter Baker…that makes sense.
The only thing then that I am confused about is the LED colour then, but perhaps thats a change thats not been documented yet. Things change so fast around here it’s hard to keep track.