USB would be nice. Bluetooth is possible as well. It’s got much higher latency
(10ms), but not so much that well-written software cannot work. That makes the
physical fit easier, and also allow placing the android and the servo/control
model on opposite sides of a parachute compartment if that is beneficial.
On Jul 5, 2019, at 6:02 AM, Craig Fink
<webegood@xxxxxxxxx<mailto:webegood@xxxxxxxxx>> wrote:
Didn't watch the entire video so don't know exactly what you did, but it was
great. But, while sitting on the launch pad your flight software should be
integrating errors out of the accelerators while motionless, figure out where
gravity is, calibrating and aligning . After liftoff, the errors should be
integrated to re-trim the Thrust Vector through the C.G. so the Rocket fly's
straight instead of at an offset.
Have you thought about using an Android Phone for your On-Board Computer and
Sensors? It could reduce your overall mass of the individual components. Most
phones have a fairly complete suite of sensors including dual cameras, multiple
radios, 3-axis accelerometers, 3-axis gyroscope, 3-axis Magnetometer,
barometer, usb interface, fast multi-core processors... The phone would still
need an interface board (usb) to read (sensors) and write (commands) to the
rocket hardware.
https://source.android.com/devices/sensors/sensor-types
https://www.xda-developers.com/
On Thu, Jul 4, 2019 at 9:51 AM Joe Barnard
<joe@bps.space<mailto:joe@bps.space>> wrote:
Hey that’s mine! More luck than anything, the thrust curve matched the prop
mass loss really well. TVC setpoints were a little off which is why you see the
slide to the right.
Joe Barnard
https://bps.space<https://bps.space/>
On Wed, Jul 3, 2019 at 9:31 PM Craig Fink
<webegood@xxxxxxxxx<mailto:webegood@xxxxxxxxx>> wrote:
LOL, ......That's not Good....... That's great!
https://www.youtube.com/watch?v=s9aTd29t2dg&t=2542
--
Craig Fink
WeBeGood@xxxxxxxxx<mailto:WeBeGood@xxxxxxxxx>
--
Craig Fink
WeBeGood@xxxxxxxxx<mailto:WeBeGood@xxxxxxxxx>
