The problem is it has erroneous oscillations above 0.5m, as the bank angle influences the detected movement more. Tried downsampling the readings to 10Hz. That did nothing. Tried throwing out readings of quality 0 like autoquad does. That did nothing.
Time for another stab at the raw data like autoquad does. The PX4flow must not do very good bank cancellation.
So the phone returned from LG untouched. They didn't accept payment or try to repair it. None of the damage they reported was there. They probably can't really repair it, but either replace it or make up any excuse they can to do nothing at all.
Tried again to restore it by soaking the touch panel in water. Maybe it would dissolve salt from a gasket that was interfering with the sensor. Then tried scraping salt from the frame. It still didn't work.
This phone is now sold for $100 on Virgin. They have better plans, using the obsolete Sprint network. The obsolete Sprint network is still better than T-Mobile, which offers no data for under $40.
The parts could be used for a repair or the extra $5 could be paid for a Sprint plan. It would not be viable to pay for an unlocking code to stay on T-Mobile. Assuming no design changes, the mane board can be swapped.
Pretty good & frustrating demo of what the PX4flow can do. The obvious advantages are: large airframe, large propellers, lots of ground detail. Surprised the banking didn't throw off the optical flow. He used a unified kalman filter & did significant processing of the raw optical flow data.
Next, we have him recording a flight by walking around with the aircraft & playing it back. The next step would be copying parts of autoquad. It's probably what arducopter based its kalman filter on.
Decent pot arrangement. The trick is lots of hot glue & wood. A wheel would be better than a stick for steering.
Another iteration with production wood. Unfortunately, the steering stick has a finite number of gluings. There was no other way to attach it than with a giant blob of glue. The throttle stick wants to angle away from the camera, which would require a heavier piece of wood.
The buck converter was most efficient at 120Hz. It peaked at 9V 2.3A. To make that, it consumed 12V 2A for 82% efficiency.
The nominal use is 7.5V 1.5A. Lacking a real dummy load, it produced 7.5V 1.9A by consuming 12V 1.7A for 70% efficiency. The MOSFET still heated up over 75C. The efficiency was probably overstated because the load resistance was not accurately known.
The dropout voltage at nominal use was 3V. It's a much worse dropout voltage than an LM317. A pair of LM317's with a big heat sink would do the job in much less space. They have a 2.5V dropout voltage & heat to below 50C while providing 8V 1.7A.
A linear regulator would be 62% efficient. The circuit is definitely not the most ideal, probably owing to the MOSFET being extremely slow. The Castle 10A BEC can do a whole lot better in a lot less space, but this is the age of spare parts.
Would consider the lack of efficiency, weight of the inductor, size of the circuit & dropout voltage deal breakers for the buck converter.
It's a problem as old as time, we all encountered eventually. Now that the venture capitalists have latched on to wearable computing, it's a problem we have to face, whether or not it's any more solvable.
Today's problem is proportional steering & throttle with 1 hand. It begins by tearing down a picco Z controller for sticks. It would be ideal, since it was rugged & used single axis sticks. There's no chance the 8 year old controller would ever be used again.
It's probably equivalent to where it was in Sep 2013. The rate of rate gyro feedback seems to have stabilized it, slightly. The barometer is disabled, giving it tighter but more twitchy altitude. The buster was a new manual control interface. That brought out a lot of deficiencies that don't come out in a waypoint playback.
After all the work copying the DCM, came to the conclusion that the DCM is worthless, indoors. Consider that the equilibrium is perfectly level, indoors. The only nonzero angles are from IMU drift. If it turns, the DCM is going to swap the roll & pitch angles, when in fact the roll & pitch should be unchanged since they're from drift in the copter frame.
The DCM is best suited for outdoors, where wind causes a real nonzero equilibrium. So everything needed to be reverted to the straight integration, with all the gyro biasing & floating point added to those routines.
For some flights, the IMU doesn't drift. For others, it drifts.
The Chinese fartbags once again stick it to the poor people of the world. The blog recalls that the LCD wasn't cracked & there certainly wasn't any of the damage listed. The problem was the touch sensor, which wasn't listed, & discoloration of the backlight, which didn't have to be fixed.
Just because the Chinese are the only people in the world who can make phones & the only ones who can invent things, they treat the rest of the world like snot. The Americans get poorer & the rich move on to the stars. That's how humans have always lived.
So the PX4flow issue ended up being the UART overflowing. The floating point conversion must have slowed it way down. IMU drift still seems within limits. There are a few more UART routines to optimize for the higher latency, a few more glitch crashes.
After all that floating point rewriting, DCM conversion, & IMU hacking, the result was still pretty bad. Optical flow is still a sloppy method, especially outside the 1m fixed focus of the PX4flow.
It would scream if it had an autofocus based on the altitude data, but there's still no way to make a long macro lens with autofocus down to a price.
Getting the video feed on Qgroundcontrol requires disconnecting the PX4flow from all other power sources except USB. Official Linux support for Qgroundcontrol seems to be gone. It's just Mac & Win, unless you want to make your own port.
The PX4flow is indeed broken. The camera works. The altitude readings work. The flow compensated readings are garbage. Moving it around a lot gets useful flow compensated readings to start showing. It reverts to garbage after a certain amount of time below a certain amount of movement.
The gyros would have to be broken, but no mems gyro has ever died. Some of it could be the UART dropping characters. The raw readings are quite erratic around startup & engine arming time.
After a full day, the electronics were transferred to a new airframe with new motors & new propellers. The IMU drift, as it was known, was no more. So the motors should be considered gone after 1 crash.
There was 1 phase in the development where it was spontaneously getting thrusted into the floor by 2 motors going to full throttle. That might have done it.
The autopilot is now non functional. The PX4flow might be damaged. There was another reflex to put the sonar on foam, which probably doesn't work, either.
After a 2 day process, an outboard IMU was fabricated.
A magic switch was installed to switch the UART between debug & IMU input. The bootloader started in 115200, then the mane firmware switched to 230400 for the IMU. That supported 1050 full readouts per second.
Hard mounting the electronics made all 3 axes drift for the 1st time. So the next strategy was to get as many axes stabilized as possible, then use an offboard gyro for the 1 remaning axis.
Returning to nearly the original battery mounting still resulted in drift in 2 axes. Also tried the hardware lowpass filter setting & increasing the full scale range.
That left going back to a very large offboard IMU in a heavily padded case.
Finally added feedback for the rate of the rate gyros that all the commercial quad copters seem to have. They call rate of rate feedback "stabilization P", while the rate feedback is "stabilization I". The feedback for angle & trim are the "self leveling P & I". A total of 4 terms are required.
It didn't have any obvious impact. The weight of the PX4flow is degrading the flight characteristics.
So the pondering about cubesats was lame, but now there is a new idea. Get a cubesat to photograph a spy satellite up close. It can't be very far from happening.
The mane spy satellite of interest is USA 224. It's in a sun synchronous polar orbit that passes over Baghdad at noon. It's low enough for a cubesat to reach. It can only be seen from the ground in Australia. It is believed to be a shortened hubble space telescope which can be approximated by chopping off hubble's instrument section.
Another spy satellite worth visiting is USA-223, the largest satellite in orbit.
It has a 100m dish. It's in a geosynchronous orbit over the middle east. A cubesat would have a hard time reaching that orbit.