Hello Volodymyr! On Tue, 13 Feb 2001, Volodymyr Babin wrote: > > Hello Matthias ! > > Unfortunatelly I don't have access for this machine at present moment, > but I'll send all logs from itifg_g.o to You as fast as possible (during > this week I hope). Camera configuration file I've attached to this > message. Hmm, the config file seems ok. I have put the attached file into the release tree. The only things I have changed is the resolution to 1280x1024 (the other lines should be blank!?) and the line miss value to No_LineMiss_Mode (the expirience says - this works better). > I have a couple bit more interesting questions. I've started implementing > AM-STD-RGB support in itifg-0.7.1 framework. I've read in the hardware > manual that I can access all AM registers after loading FPGA data. > I've looked how this is done for PCDig in itifg and in amrgb-patch. > The question is: is size of FPGA array variable (for fixed board) or > not (from PCDig sources follows that "not", but from amrgb-patch - that > "yes") ? Documentation say nothing about this (just suggest use ITEX > library). I'm asking about this becouse I've seen already existing types > and itifg_t structure members related to PCDig FPGA programming and > it would be nice (if this possible of course) to re-use them for AM-RGB. I have implemeted my PCDIG fpga download code AFTER the code for the RGB was written. It would be VERY nice, if you can reuse this framework also for the RGB!!! I know only, that the byte value is fixed for the PCDIG, and I have it implemented this way to keep is easy. You can feel free to extend the interface to mach your requirements. Do you have to convert the *.exo files for the RGB also?? (please see convert.c) > Next question is : itifg_t structure has flag `fpga_ok', it can be reused > for AM-RGB, but in many places of the itifg sources I've seen a macro > IS_PCDIG followed by some checks related to fpga in this case. What > You think about macro like NEED_FPGA (IS_PCDIG || IS_AMRGB) ? Yes, this is exactly the right way! Please remark: If detecting and ICPCI I hardwire iti->fpga_ok to TRUE (itifgAux.c, line 837). You have to make this module dependend. > And the last (for now ;)) question : could You point me to some > resources about FPGA programing? Urggg... I have only a look at the windows code and have it rewritten. No further expiriences! If the RGB also uses ORCA's, you should visit Lucent's web side directly or have a look at the attached pdf. > With the best regards, > Vova. > matthias ------------------------------------------------------------------------------- GOM mbH Tel.: ++49 531/3804-330 Gesellschaft fuer optische Messtechnik Fax.: ++49 531/3804-333 Rebenring 33 Mail: M.Stein@gom.com 38106 Braunschweig GERMANY http://www.gom.com -------------------------------------------------------------------------------
Attachment:
orca.pdf
Description: Adobe PDF document
#
# Example Configuration File for AM-DIG Module
# Camera: Basler A113
#
# Volodymyr Babin 02/01
#
[ICP:0] # Board 0
[AM-DIG] # Module AM-DIG
[CameraPort:0] # Camera 0
Camera_Name = "Basler A113 fps:? (8bit)"
Horizontal_Active = 1280
Horizontal_Offset = 0
Vertical_Active = 1024
Vertical_Offset = 0
NonInterlaced
NonInterleaved_Pixels
Area_Scan
LEN_Wide
No_LineMiss_Mode
FIFO_Reset_Mode
Pixel_Size_8
CCLK_36.00MHz
CCLK_Div2
ExtSync_Mode = FreeRun
EXSCLK_14.32_Div2048
EXSync_Counter_Enable
EXSCLK_CounterPreset = 1700
Trigger_Gen_Disable
Trigger_Source = External
Xillix_Mode_Disable
Camera_Mode = 0
PRI_Active_Low
AM_OutputA = Low_Byte
AM_OutputB = Low_Byte
AM_OutputC = Low_Byte
PCLK_NoInvert
LEN_NoInvert
FEN_NoInvert
FLD_NoInvert
EXSYNC_Pulse_Active_High