Camera woes

cam76.jpg
After a lot of fussing, finally got an 802.11 association.

ap02.png

That was a lot of work.  Nothing changed.  With 1 dongle, it only associates by doing iwlist manually, then iwconfig.  With another dongle, it usually gets it with just the iwconfig command.  The STM32 USB is still putting out a huge number of errors.  The way iwconfig probes is always generating an error URB.
It turned out none of the current routers send beacons at all.  What the kernel reports as beacons are really the responses to the last PROBE request.  

STM32 bugs continued to torment.  This time, the transmit operation ended up requiring multiple 64 byte packets.  The demo showed multiple packets of 512  bytes.  The receive operation allows any size buffer.

Also not in the demo, between transmit operations, you need a polling loop which waits for the urb status to not equal IDLE.  Not equalling IDLE actually means it is idle.  No receive or transmit operation can occur until the urb is not IDLE.  Of course, the urb status is always IDLE before the 1st send request.
Those discoveries got Marcy 2 networking to stop locking up.

Networking got to the minimum level for a camera test.  It does 0-800kbit/sec with lots of packet loss.  This is using the ground station to send beacons & the aircraft to send 1024 bytes per beacon, all UDP, just like the final product.  It would be much more complicated to have the aircraft send continuously.  There isn't enough memory or latency tolerance to use TCP.

The 802.11 auth, assoc, & UDP packet generation are just good enough to work, even with the USB packet loss.  The ARP table & DHCP is still manual.  The hope is moving ahead will show more aspects of the latest USB problem.

Power consumption is a real problem.  The DPAK LM317 starts smoking during 800kbit transmission, with no camera.  A simple camera board obviously requires a lot of power hardware.

marcy2_16.jpg



The board & camera were finally mated.   Because Vdd appears in the same place on 3 of the corners, pin 1 ended up soldered wrong, which resulted in a hot air heating.


cam75.jpg



That melted it.  Eventually heat it from behind & got it to fall off.  The focus ring is now welded into place.  The 1st pictures will be blurry, but hopefully good enough to characterize the rolling shutter.

This was the only part that only got 1 order, due to lack of money.  This shows how the actual cost is much higher than the BOM.

Like any lens, it's not attached by much, & trying to turn a melted focus ring only rips off the lens.

cam76.jpg




cam77.jpg



Definitely some evidence of the focus ring melting all the way through.


cam78.jpg

cam79.jpg


The problem with these cameras is not the sensor as much as getting a sensor & lens combination in that size.  Sensors are abundant.  Could even use a CCD sensor & be done with warping, if the lens materialized.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Developer

    Nice.  I had a lot of problem getting a lens + holder working for the optical flow.  Of course you're going right down to doing the actual image processing on your CPU which I'm sure will be very tricky.  good luck.

This reply was deleted.