New Products Flash Sale
Jack Crossfire's blog View Details
Posted by Jack Crossfire | May 08, 2016 @ 04:23 PM | 2,371 Views
So the mane processor is an STM32F103C8 64K flash, 20K RAM, 72 Mhz, 48 pins. It breaks out single wire debug on pins 34, 37 for raw programming. It also breaks out 3.3V, GND to the programming header.

There's no distinguishing feature for the chips to detect which board they're on. It must be programmed in the bootloader or some initialization handshake.

MOSFETS are connected directly to GND & battery V+. They're some kind of motor controller packages with complementary MOSFETS.

switching regulator reduces battery to 5V
linear regulator reduces 5V to 3.3V
STM32 VDD comes from linear regulator
LMV358 VDD comes from linear regulator
hall effect VDD comes from linear regulator

Header entering yaw board:

RX/yaw PWM -> 100R to pin 43/UART1_RX/I2C1_SDA/TIM4_CH1
TX/pitch PWM -> 100R to pin 42/UART1_TX/I2C1_SCL/TIM4_CH2
Mode PWM -> directly to pin 41/TIM3_CH2

Header exiting yaw board:

100R to pin 21/UART3_TX/I2C2_SCL/TIM2_CH3
100R to pin 22/UART3_RX/I2C2_SDA/TIM2_CH4

Board to board wires are straight through. The boards communicate via UART at 2Mhz. Colors are reversed on the IMU wire but I2C connects to the MPU-6050 as expected. I2C goes at 1Mhz.

Hall effect sensor uses SPI. Clock speed is 561khz. Chip select goes low 1st. The STM32 sends a command in 16 bits, switches the SPI to input & reads the result in 16 bits. Chip select goes high last. Sequence repeats every 300us. Doesn't have an initialization...Continue Reading
Posted by Jack Crossfire | Apr 30, 2016 @ 06:10 PM | 3,133 Views
Future of Faster | The PUMA BeatBot (1 min 30 sec)

It only took 3 years, but MIT & NASA finally caught up with the blog. Their version of the pacing robot uses line following for navigation & they didn't seem to have solved the manual control problem, yet. The line following is based on IR leds with a video camera so it only works at night, on a track.

It won't be long until they discover line following is not worth as much as an ergonomic manual control.
Posted by Jack Crossfire | Apr 27, 2016 @ 12:43 PM | 2,592 Views
After 2 weeks of round the clock commuting & moving, the home network came up again. It was sheer brilliance for Comca$t to make every one of their rental modems a public hotspot & it's amazing AT&T never copied the idea. When the idea 1st came out, the internet screamed bloody murder. What would be the impact on performance for subscribers when their rented modem was shared with a user on a different account? Of course, it was more AT&T screaming bloody murder & the internet just doing what it was told.

In the fullness of time, the outcries disappeared like any dead celebrity meme & the sheer brilliance of the move arose. Despite the insane cost, most people still rent modems instead of buying their own for half the price. Every one of those millions of modems automatically pops up on every wifi enabled gadget, a gigantic window saying "XFinity". It's the biggest customer sponsored advertising blitz, ever.

It takes very forward thinking to get to an advertising blitz this extreme. It began when the wifi standards were ratified. Someone had to realize allowing a router to push a web page for logging in was a useful feature. The true power was in the standards process.

So when finally subscribing to Comca$t, after years of endless XFinity popups on every wifi device, the hotspots instantly worked. There was no need to buy a modem at all or wait for an installation kit in the mail. You could just use your neighbor's wifi & it even went up to 8 megabits. Not sure if the speed was throttled based on the account. Every modem automatically signed in.

When the wired modem finally arrived, it required jumping through an activation hoop. After this, the wifi hotspots no longer worked. It seems they only allow use of the hotspots before activating your modem. Then, they require upgrading your plan, yet another marketing move based on human fear of denial.
Posted by Jack Crossfire | Apr 22, 2016 @ 05:25 PM | 2,676 Views
There have been so many man rated quad copters, EDF powered hoverboards, mini helicopters, that only go 5 minutes, can't get above ground effect, or never got finished, the Flyboard looked like more of the same when in fact it was different. The key is to consider too this day, the smallest flying machine that actually works is the original hydrogen peroxide jet pack. It goes 30 seconds.

The Flyboard is the 1st to be at least as compact as the jet pack, but go much longer than 30 seconds. It uses 4 hobby size jet engines at $10,000 each. The fuel is in a back pack with a hose going down the pilot's leg. If the fuel line gets kinked, he loses $40,000 & dies.

The remote control only controls thrust. The pilot leans to control direction. It probably has foot switches, but his feet are rigidly mounted. There could be a trick involved in rigid foot mounting, yet allowing enough motion to provide user input.

Hobby jets probably have enough response to stabilize it by varying engine thrust. There's no thrust vectoring or reaction control thrusters. 2 red EDFs on the sides counter the torque of the jets & provide yaw.

There's nothing in it which couldn't have been done 10 years ago, except for coming up with the money. Borrowing $40,000 was once equivalent to borrowing $400,000 today.
Posted by Jack Crossfire | Apr 19, 2016 @ 11:04 PM | 3,028 Views
To not feel so bummed about the home made copters of years ago being stressful & difficult to keep out of harm's way, it's time to start compiling Neistat's quad copter crashes & tribulations.

boat crash:

loss of signal:

bridge crash:

So basically, despite years of multiplying valuations & redundancies, even the most foolproof quad copter still isn't much more foolproof than the old days. The attempts at obstacle avoidance by sonar & IR obviously haven't translated into anything meaningful. Neistat explained that he gets away with flying by having 4 quad copters & chewing them up.

He explained that he was getting all the selfie shots by semi autonomous control, not by any dedicated feature:

Ergonomics were probably the biggest factor in doing it manually. Given the amount of flight time & length of the final shot he gets, it's probably too cumbersome to set up a "cable cam" , waypoints, "leash cam", or geofence.

Still suprising he has to carry all that gear. There would be no way he could use a 3DR copter because they're too big. The Phantom is just small enough.

Ground vehicles have no worries. They can precisely navigate the city streets. Combining their single handed controller with a quad copter would be the ultimate selfie system, 10 minutes at a time.

The videos of the Phantom 4 at low altitude do look rock solid precise. It uses sonar for altitude & dual cameras for optical flow, but also fuses that with the accelerometer.
Posted by Jack Crossfire | Apr 13, 2016 @ 08:54 PM | 3,196 Views
The amount of soot appears related to the amount of time the surface spent at ambient temperature, so the gradations in soot can show the amount of LOX left in the tank during each re-entry burn. 33% of the total LOX capacity was required for recovery. Of the 33%, finer gradations show the 1st & 2nd re-entry burns with 15% left over for the landing burn. The line dividing black from white would be the edge of the common bulkhead, since there is no intertank section to provide a smooth gradient.
Posted by Jack Crossfire | Apr 09, 2016 @ 08:14 PM | 2,732 Views
Managed to get the USB->serial dongle working in VirtualBox, since it's a ttyUSB instead of a ttyACM. The problem is the gimbal has to be turned on after the firmware update tool is already listening. The firmware update tool waits for a start code so it can force it into bootloader mode. PWM did indeed have to be off. TX came from the pitch PWM. RX went into the yaw PWM.

So the Feiyu turned out to already have 1.14, the latest firmware. That left waiting for another firmware update in the future or programming it from scratch. Feiyu already discontinued the mini 3D, so another update is unlikely.

Tearing it down revealed a bewildering nest of miniaturized boards which would have to be reverse engineered. The same board is replicated for each motor. There is only 1 IMU.

Next, we have an MV358 op amp, given away by some RC pairs next to it. It probably amplifies a signal from a chip marked only 01281000, undoubtedly a hall effect sensor despite the lack of any Goog results. It's directly under a magnet on each motor which serves no purpose other than giving the motor's orientation. These magnets are circular polarized to give a varying field for each position.

The same firmware probably runs on each board, relying on the placement of jumper resistors to know which board it is. Communication between the boards, how to change the firmware with the existing bootloader, how to control the motors are all the great tasks. It would have been a lot easier if they just allowed configuring the product.
Posted by Jack Crossfire | Apr 09, 2016 @ 02:45 AM | 3,013 Views

Another small step forward. Landing at sea increases the amount of mass which can be launched on a reusable rocket. Still up to the voters & government to determine when humans will finally be able ride it. Their 1st launch of a human is entirely dependant on your continued support of the CCDEV program. The human mission to low earth orbit would be the easiest to recover the booster from, the baseline mission for the reusable system.

You would think there would be competition between customers to be the 1st to pay for a used rocket. It would be quite a publicity boost. The 1st is going to be the one in Wikipedia for all time or at least as long as it keeps raising donations.
Posted by Jack Crossfire | Apr 07, 2016 @ 03:05 PM | 2,814 Views
Current usage with camera recording at 8.4V:

0.85A with motors not deflected
2.3A with all 3 motors fully deflected

The old pro doesn't work without battery. There's no point in using the power supply umbilical unless you're previewing video. Even then, the power lead should be desoldered. It's easier to use the pro battery in its included spot than carry around an extra gimbal battery.

A dummy battery could go in the pro that would trick it into working without a battery. It probably just needs to see 4.2V on a pin, but no spare battery exists to sacrifice.

Current usage without powering camera at 8.4V:

0.25A with motors not deflected
1A with all 3 motors fully deflected

When powering the camera, a converter reduces current usage for higher voltages. Without powering the camera, the current rises slightly for higher voltages, but with no increase in torque. Minimum current is always 0.25A. The torque seems just high enough, but could go higher without burning out the motors.

Motor control is quite a bit more robust than past gimbals. There's no skipping or studdering. It's like it has encoders giving it motor position, but it doesn't. It's using gyros attached to all 3 motors to gleam phase in addition to orientation. It seems to have an algorithm change which invokes the gyro based encoding when the angles get offset beyond a certain amount. This allows it to recenter instead of studdering.

It was deemed good enough to hard code the mode & speed in...Continue Reading
Posted by Jack Crossfire | Apr 04, 2016 @ 12:39 PM | 2,243 Views
The 1st assembly of the Feiyu was disappointing. It wasn't as transportable as hoped, but it was more compact than keeping the shock absorbers. Wires hung out everywhere, but the assembly can probably be wrapped. The aluminum arms are going to bend over time. The bolts need reinforcing tubes. There's not enough clearance from the handle to easily turn an allen wrench. The pins for calibrating the horizon need to be flush on the handle.

The power switch managed to stick on by reflowing the hot glue after gluing it on. Reflowing hot glue by blasting it with the heat gun after initially tacking it has been effective at sticking difficult parts.

The power switch was deemed necessary because the Feiyu has to be powered on in the orientation it's going to stabilize in, but it's a fragile arrangement with lots of wires. A quick test should reveal if the power switch is necessary or if the battery plug, a MOSFET with delay, a tact button, or app button for enabling the Feiyu can do the job.

It was decided to remove the 2 pots for mode & speed. Those are better controlled over bluetooth app. The voltage regulator needs to be replaced by a 3.3V & bluetooth connected to the debugging port. Need to measure the power consumption of bluetooth.
Posted by Jack Crossfire | Mar 27, 2016 @ 05:34 PM | 2,582 Views
After multiple credit card rejections & alerts, the bang good transaction went through. 4 days later, the goods arrived with a bang. The quest for a handle began.

1st, it needs another control board to generate roll, pitch, & mode PWM signals. The PWM generator is required whether it's on a handle or a vehicle.
Only 6 signals go in: power, GND, roll, pitch, mode, video There is a 0.176V diode on the shock absorber board to protect against reverse voltage.

The USB connector on it is overkill. It really takes a standard UART TX & RX signal on the same pins as the roll & pitch, so it can't be programmed when the PWM source is running. The 5V from the USB connector is floating, so it needs to be powered from the PWM generator while no PWM is being generated.

The original plan was to remove the enclosure & bolt the handle directly onto the motor. The problem is a control board is bolted to the enclosure, which is bolted onto the motor. You can't remove the enclosure without removing the control board. Hacking the board to operate outside the enclosure would prevent the original shock absorbing board from being used. It also uses high speed I2C to communicate with control boards attached to all 3 motors & the IMU. That won't work outside the enclosure. There aren't any bolts long enough to go through an outside plate, the enclosure, board & motor.

The shock absorbing board can be removed, yielding a much more compact setup suitable for a...Continue Reading
Posted by Jack Crossfire | Mar 26, 2016 @ 02:09 AM | 2,606 Views
WE'RE MOVING!!! (10 min 54 sec)

Romantic Night (10 min 10 sec)
...Continue Reading
Posted by Jack Crossfire | Mar 20, 2016 @ 04:43 PM | 2,848 Views
Posted by Jack Crossfire | Mar 18, 2016 @ 11:19 PM | 3,195 Views
Washington DC Timelapse run (7 min 33 sec)

After making that, a better stabilization system became a lot more desirable. So basically, the brushless gimbal made 3 years ago ended up too big & cumbersome to be useful for most running videos or traveling. There's no way without the power of Chinese manufacturing to miniaturize it. Either that or the cost would be more than a commercial version.

In the future, 360 cams will replace all brushless gimbals, but there is currently no incentive for anyone to make a 360 cam work like a brushless gimbal when it's cheaper to borrow money. There might be a way to hack it. Years ago, there was an attempt to use a phone's internal IMU to stabilize the video from its own camera. The problem was they had to use an off the shelf phone & only the software APIs included. The focal length was too long to give enough overscanning area. The IMU wasn't fast enough to track fast movements. It only worked if the API gave time stamps which could synchronize the video with the IMU data.

The new idea would be capturing IMU data externally from the camera & synchronizing it by reading the VSYNC pulses from the sensor. New cameras may not have an exposed VSYNC signal. It's not likely the clocks would stay synchronized tightly enough to pull it off.

The raw IMU deltas would be recorded on the microcontroller's flash. They would generate offsets for Cinelerra's motion tracker. They would have to be exactly synchronized...Continue Reading
Posted by Jack Crossfire | Mar 06, 2016 @ 07:42 PM | 2,802 Views
Air Hogs took another swing at the spin copter game again with the Hoverblade. It looked a lot more like a monocopter than their previous efforts, but once again, it just had up & down control.

Spin Master Air Hogs 360 Hoverblade Unboxing (13 min 15 sec)

The lone gootube video of it showed a bad horizontal oscillation. It's almost like they tried a monocopter, but after getting nowhere with it, went back to the standard vertically controlled spinner.

While somewhat surprising no-one has ever commercialized Marcy 1, miniaturizing it enough to make it practical for the toy market might be too difficult. The motor size might be the limiting factor. There may not be materials strong yet light enough to achieve the same slow motion in a smaller size.
Posted by Jack Crossfire | Mar 05, 2016 @ 08:51 PM | 3,170 Views
It was the 1st computer a fake test pilot could afford by his own doing. There will never be another 1st.

It was a monster for its day. 200 whole megahertz. 512 k of "cache". Surely it would open up serious audio reverb, all done in the "cache". The cache was physically the same as the DRAM in those days. It was just addressed faster, but all the memory had to be accessed through another chip. What a joy to finally have a living breathing UNIX workstation that would never crash, with someone else paying the electric bill. It finally crashed when the heatsink filled with dust.

It didn't take long after mastering its audio capabilities for video to arrive. 1st came playback of 320x240 MPEGs. Then came recording 320x240 at 4fps or 640x480 at 1fps. Still didn't know enough about video compression to get the most out of it, but it was a new world. There will never be another new world in video or audio. The new world nowadays is the physical world.

You can't afford to keep a lot of the stuff you once had, especially with rent heading for a 3 handle. After 19 years of waiting for some kind of embedded repurposing that would never come, it was time to put it down. It might have actually had some use, right until 10 years ago when the Gumstix arrived. By 2014, the CPU heatsink was repurposed for the contact lens agitator. In 2015, the last of the PCI video cards was discarded, so it would never run again.
Posted by Jack Crossfire | Mar 04, 2016 @ 11:21 PM | 2,984 Views
7m15s mile (8 min 4 sec)

Snagged a 7m15s mile from the Ruckus. The image stabilization had its 1st material improvement in 18 years. There were previous attempts, but nothing which gave a net improvement. Now, much higher resolution can be stabilized in translation & rotation in much less time. This one took only 3 hours on the Macbook. On the dinosaur PC, it took 5 hours. Previously, the dinosaur PC was slightly faster than the Macbook.

The mane focus was using mipmaps instead of the full resolution image. The original algorithm stressed memory access while the new algorithm stresses the cache more. It shows the Macbook may have slower memory bandwidth, but faster cores. Memory may only be slowed down by the virtual machine.

There's still no solution to rotation drifting. Stabilizing a flipped video showed it's not a rounding error.

Then came the reality that using the vehicle as a pacer over a full 2 miles resulted in a slower total time than running without it, because of all the flips & navigation through mobs. The vehicle still allows higher speeds when maneuvering isn't required. Surprising how much a phone screen scratches after many slides on the pavement.

Steering oscillation remaned pretty bad. Steering was also too slow to respond, symptomatic of high D constants to overcome the oscillation. These factors made it very hard to navigate obstacles.
Posted by Jack Crossfire | Mar 01, 2016 @ 11:33 PM | 2,975 Views
After roughly 110 miles & 2 months, the SPMS401 died. While disappointingly short lived, the failure was software induced. When full time heading hold arrived, it made the steering build up when sitting still. After drifting far enough, the servo saver jammed well within the servo's range & the motor stalled. That's what happened when it was left powered on the bench after a successful drive. It worked until the end, but the next day, the servo was fried.

It was another case of software costing money & a servo saver destroying a servo. Ideally, the heading hold would time out after 30 seconds of no throttle. Replaced the SPMS401 with a Futaba S3102. While it didn't fit the servo saver, it worked fine with a standard horn. The standard horn didn't jam in the servo's entire range. Pity the fool who bought a replacement SPMS 401. It's a standard micro servo.
Posted by Jack Crossfire | Feb 27, 2016 @ 07:41 PM | 3,261 Views
In the search for a way to power 2 19V devices from 1 brick, it was finally time to tear one down. It was possible to get in by prying the enclosure apart, rather than grinding through it. There was a minimal amount of adhesive. Helas, there was not enough room inside the enclosure to solder a 2nd wire. The best way to split the output was not to break it open.

What was discovered was it doesn't require a macbook to turn on. It's off with no load. It outputs 17V when provided a load. An ESC was enough. The Accucell 8150 was enough. When powering the laptop, the laptop embeds data on the power line which causes the brick to adjust voltage depending on the load. A high CPU load makes it output up to 19V. A low CPU load makes it output 17V. This allowed Apple to get a constant voltage to the laptop through the minimum wire guage. Without the laptop on 1 end, it outputs 17V with the least load, sagging to 16V with increasing load.

It wouldn't be able to power the Accucell & laptop during full CPU usage. That would make it go above the Accucell's voltage limit to keep the laptop even. It also has very little reserve at full CPU usage. Any significant power usage makes it turn off.

Didn't document the powerline data chips because that wasn't the focus of the day. Being able to power a 19V fan & laptop from 1 brick is a huge savings in luggage.