That's actually pretty interesting to hear, 100 might mean you have more of them than the Apertus folks have produced. Last I checked they had shipped like 25 of them.
What industry was this product targeted at?
In the photos it looks like you have the power and main boards. It looks like the PCI-E (Physical not electrical) connector may have been removed from the main board?
I'm assuming then the project would have been streaming the video over ethernet.
Almost all correct
We had ~150 PCB sets made, have the wherewithal to make at least 100 camera modules, probably more.
My employer is in the "precision agriculture via aerial imagery" industry via multi-spectral analysis. We developed a system that uses 3 such Axiom-Beta variants with different wavelength filters in each one (and a Nikon D800 DSLR for the human-friendly images), along with an Odroid UX4 to capture single frames from the 3 Beta-variant cameras over Ethernet, and store on USB3-connected Flash. Along with a bunch of supporting software and hardware to glue it all together, and integrate into an existing airborne system currently based on DSLRs. A combo of market and funding constraints mean we need to put further development on hold for a while :-(. But either way, if we iterate on this design, it probably won't be based on 3 discrete cameras, and more likely on a higher resolution sensor too (i.e. CMV50k).
So what you see in those 2 photos is:
- MicroZed (7020) with 16GB µSDcard
- standard Apertus Power PCB (v0.25)
- standard Apertus SensorIF PCB (v0.18 r1.3)
- inbetween the 2 Apertus PCBs is our adaptation of the Apertus 'Main' PCB. Basically I ditched the 'west' CPLD which was all about streaming video out, we didn't need it. Kept the 'east' CPLD, but rearranged things a little. At that stage Apertus had no HDL for that CPLD (other than to wire-thru a SPI bus from MicroZed PL through to Cmosis Sensor), so we developed our own CPLD code that met that MicroZed SPI bus with a SPI-slave, and then i/f that via Wishbone to a SPI-master (to the Sensor), and 2 or 3 I2C-Masters to i/f to the EEPROM & TempSensor chips. Not a pretty design, and if I had my 'druthers, it would've ditched both CPLDs all together, but at the time we wanted to maintain as much compatibility with Apertus's codebase as possible. That was a year ago, and we've since re-written a lot of that stuff, as well as our own application-level code.
'Reminds me - we had intended to hand over that CPLD code to Apertus. Not sure if they've already coded their own, which they'd intended to be a pair of LVDS lines to/from the Zynq with an embedded clock. We stuck with the single 4-line SPIbus implementation, because we didn't need much speed just to control the sensor & read from a couple of I2C peripherals. I'll make a note to check where they're up to there and offer it to them.
So as a single-frame camera (not video),
at least a 1 frame / second rate is easily viable. We currently have 3 Betas sending 1 frame as low as every 2.0 seconds to the Odroid XU4 via NFS over Ethernet without going to too much trouble, and I think the bottleneck there is the Flash write-speed anyway, so even faster is quite likely possible. We put quite a lot of time into optimising the frame-buffer read-out for either raw or pgm image format, down to about 200ms (i think it used to be over 2s), and with flexible region-of-interest options too.
If this 'complete camera modules' idea has legs, it might behoove us to have a bunch of original Apertus Main PCBs made, to restore all that functionality & s/w compatibility. It'll depend on the potential user's application...
The bigger problem with the Axiom is so far they have been busy with color science, and there is no onboard recording method yet.
Don't hold your breath for the latter, I don't even think it's on their roadmap - Beta is intended purely for an external HDMI/DP/SDI-connected recorder, at least as far as motion video is concerned.
As for the former, well, you can't rush perfection.
Folks that would pay more than just the cost of the parts, would probably be looking for a more complete system than what the Axiom has produced at this point.
Recently, there are more tech tinkerers in the industry, and more open source projects are becoming interesting to a point.
The major problem for a product would be something like the Blackmagic Design URSA, it uses the CMV12000, and is a complete ready to run camera produced by a company with a known history in the industry. And it sells for 3k USD, the Axiom beta project dev kit was 3k EUR. On the industrial side there is the JAI SP-12000M-CXP4 that was $4500 or so last I checked out.
As pointed out in this thread, I think there are some folks with the interest and expertise to take a module like this and integrate it into a useful application or tinker with as a learning tool.
But for the most part I think they are not the people that could justify spending 3-5k on it.
That's essentially the spot I'm in on my project, I would have liked to work with the larger CMV12000 but the cost pushed me down to the CMV2000.
If I could have set up the CMV12000 and support parts minus the FPGA/CPU board for under 1K it would have been a no brainer, at 3k it gets to be an expensive experiment.
For now the CMV2000 has taught me quite a bit, eventually I'll work on moving up to the CMV12000
Don't look now, but Axiom have just clarified their "path from dev-kit to production camera" in a blog post last week, and the dev-kit (i.e. no case, just the PCB stack & sensor) is now EUR$3990 for new sign-ups (only EUR$2100 if you backed the October 2014 Indiegogo campaign), and the full-pretty-case product is to be EUR$5990.
Obviously there's a certain market being aimed at with Apertus' dev-kit offering, as there would be for our hypothetical camera module. And the 'Beta II' in its pretty case is something else entirely...
I'm not quite ready to put a price on our camera module PCB stack with CMV12k mono sensor, but I suspect we'd be under half of Apertus' new asking price.
Anthony.