...

• check Pixel-Clock in lower right (should be green text)
• should auto-detect camera on software startup: board->attached camera→camerainformation
• image format->test pattern→ramp
• i/o controls→trigger mode was on (means waiting for trigger)
• advanced control→line sync source→internal line trigger
• linetriggermethodsetting use method1
• use CC1 trigger pulse pulse#1
• image buffer and roi → camera sensor and geometry setting → 8X-1Y
• image height (in Lines) changed to 1000
• frame grabber leds flashing green when things working
• can move camera back to factory settings
• restarting cam expert is faster than auto-detecting camera
• can select between stored different camera configurations (stored inside camera)
• all fields green in lower right of cam expert (pixel clocks (3) and line valid).  Pocl's red
• "board" section is the frame grabber.  everything else is camera related.
• "Device:" Xtiunm-CL_MX4_1 size options: are the server options.  we only want full mono.  "camera link_1" is the serial port (the latter is almost legacy)
• histogram option in upper right.  open it first (bug) then click "grab"
• camera information→power configuration set to factory setting.
• be careful with internal/external triggering
• frame-rate is for many lines
• what data gets is "focus dependent": depends on what is selected in menu in lower left, either frame grabber OR camera config is saved
  • we want file->preferences→NOframegrabberconfigfileonly (will also stores like the external/trigger setting).  and we need we need to set "focus"
  • two types of files: camera configuration file, and frame-grabber configuration. both files have same extension. (remember focus-dependent saving)
• path to ccs files: c:\programfiles\teledyneDalsa\sapera\camfiles\user
• File→Open Chrisb_test.ccf in above directory, I think

Restarting IOCs

(courtesy of Tyler Johnson)

...