Posts by roeger

Hi Jesse,

I'm not sure, if I understood your problem correct, but for the design you put here I would offer you this optimized Version:

1. From my understanding there is one buffer redundant and can be simply left out.

2. For the SelectROI you can as well use the H-Box I put there. In this H-Box all lines except for the one you spezified with Y_Offset are removed. Usually that is a more efficient way if you only need an ROI in Y direction since the Operator needs to take the X-direction in account as well and therefor needs more ressources.

In the modified File I put there you will have a second process with my modifications.

Does that help you or do you need something else?

Best regards,

Björn

Hi Mike,

there are two different concepts to work with our Framegrabber.

These are:

1. Applet (lets take it as an extention to the firmware)

2. Software SDK

The first one acts as an extention to the basic functions of the hardware. The second one focus on using features that are either implemented in our firmware or by the user in an applet.

As for the CL-Ser: That is an interface that is already avaiable in every CL-Framegrabber.

Each CL device needs a bit different handling. That's why there is a standard defining how to manage this different devices. So you don't need to implement a version on the low level but can use an already existing interface.

OK, that's for the theory.

As for the "how". There is an example in your Runtime installation:

%SISODIR5%\CameraLink\ClSer

You may look at this to get an idea how to handle serial comunication in CL.

Did that answer your question?

Best regards,

Björn

Hi Jesse,

since the design you try to build is for a marathon card I would suggest you use Vivado instead of ISE. Vivado will greatly reduce your design times, since it has a better optimisation posibility than ISE.

As for your question what to do if there is only ISE(e.g. for a Ironman Card):

You can try to reduce parallelist of LUT and ROM operator to maximum 2(if you need more you can split them into multiple instanzes). This will result in a bit more resources, but it will reduce the clocking in this operators to only use the normal clock. Otherwise it will use a 2x faster clock as well which might make routing more complicated.

I hope that helps a bit.

Best regards,

Björn

Hi Theo,

I have add you a pre-Version of the example for multi Encoder usage in VA. Currently there is a VA-File for

1. CL Full Gray with 4 encoders

2. CL Full Bayer with 6 encoders

3. CXP Gray using 4 encoders

I still didn't finish the CXP Color with 6 encoders(the design didn't fit) I still hope I can find a solution to get it squized in somehow. Anyway, in the Example.zip you will find the VA Files and the modified JpegCreator.h/C++ project.

I was limited with the upload for the jpeg-lib. You will need that one as well(it is included in the old example).

I hope that will help you get a starting point.

this is the Example:Example.zip

PS: I will add the docu and missing parts as soon as I find a way to get it small enough

best regards,

Björn

Hi Simon,

I use TCL for Applet generation. For that I created a folder with TCL scripts. When I run my base script I set the base folder to the folder the script is in and after that I run relatively from that path.

You can do that using this code in your main TCL-Script.

cd [file dirname [info script]]

after setting the path to the known folder can be done relativly using the cd command.For example if your image folder would be one folder up and than named image

cd ../image

I hope that helps you to archieve your goal.

best regards

Björn