🚀 go-pugleaf

In article <SCHULTZ.92Jul21200306@halley.est.3m.com> schultz@halley.est.3m.com (John C. Schultz) writes:
>
>The software may or may not be worthwhile.  MAXWARE was generally considered
>worthless because of bugs although some companies (Innovision perhaps?) fixed
>the bugs and got proprietary versions working.  IMAGEFLOW is apparently much
>better but I have no first hand experience with that.  We made our own
>environment for interactively programming the earlier boards as did most of
>the people using the early Datacube hardware.

Imageflow is pretty nice (though admittedly I don't have experience
with any comparable packages).  Takes a bit of time to learn the
programming model, but once you do it's pretty easy to control the
hardware.

>The biggest conceptual problem with the MAXVIDEO cards is that timing is
>EVERYTHING.  Programming is OK, but you have to get the timing correct so that
>the two desired pixels arrive at the adder (or whatever) at the same 10ns
>increment relative to the RS170 H and V timing.  The easiest way with the
>older boards such as you have is to simply make a function which allows you
>interactive control of the delay lines and FRAMESTORE precess.  Then adjust
>these interactively to get what you want.

Fortunately, Imageflow eliminates all of this.  You just tell it how
to connect the pipelines using dqConnect() calls and the like, and
then "arm" and "fire" the pipeline.  It takes care of setting up all
delays, gateway parameters, etc.

Paul


-- 
Niven's Law #14:   There exist minds that think as well as you do, but
                   differently.
Niven's Corollary: The gene-tampered turkey you're talking to isn't
                   necessarily one of them.