MityCAM Vision Cameras: Supporthttp://support.criticallink.com/redmine/http://support.criticallink.com/redmine/redmine/favicon.ico?16338348402021-12-15T14:38:36ZCritical Link Support
Redmine Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6153#message-61532021-12-15T14:38:36ZJonathan Cormierjcormier@criticallink.com
<p>Glad you got it figured out</p> Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6152#message-61522021-12-14T23:06:55ZMaurizio von Flotow
<p>Final follow up on this issue:</p>
<p>Spyder is fine! <br />I just needed to restart Spyder to force it to update its environment variables (since I updated the PATH after I had originally opened Spyder).</p> Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6151#message-61512021-12-14T22:52:09ZMaurizio von Flotow
<p>It seems as though this issue is linked to using Anaconda's Spyder IDE. <br />If I run the file from Pycharm or directly from a command line (or in this case: "Anaconda Prompt"), the program complete successfully.</p>
<p>I was able to pick up on the minor instruction typo when originally implementing and did correctly set my path variable. So unfortunately that was not the issue for me.</p>
<p>Thanks for the help.</p> Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6150#message-61502021-12-14T22:16:10ZJonathan Cormierjcormier@criticallink.com
<p>Found an issue with the snap.py and instructions: The viewer installation path changed from "Gentle Viewer" to "GenTL Viewer" so they needed to be updated. Update instructions on wiki and uploaded an updated snap.py. Also fixed the deprecation warnings as well.</p>
<pre>
(gentl_37) C:\Users\jcormier\Documents>python snap.py
None
2021-12-14 16:51:24,983 - harvesters - INFO - Added c:\Program Files\Critical Link LLC\GenTL Viewer\bin\GenTL.dll to the CTI file list.
2021-12-14 16:51:24,984 - harvesters - INFO - Discarded the device information list.
2021-12-14 16:51:24,992 - harvesters - INFO - Initialized GenTL Producer, c:\Program Files\Critical Link LLC\GenTL Viewer\bin\GenTL.dll.
2021-12-14 16:51:24,994 - harvesters - INFO - Opened System module, criticallink/gentl.dll.
2021-12-14 16:51:24,995 - harvesters - INFO - Opened Interface module, Simulated.
2021-12-14 16:51:25,008 - harvesters - INFO - Opened Interface module, U3V.
2021-12-14 16:51:25,141 - harvesters - INFO - Updated the device information list.
Found 0 devices
[]
No devices found
2021-12-14 16:51:25,145 - harvesters - INFO - Started resetting the Harvester object.
2021-12-14 16:51:25,146 - harvesters - INFO - Removed the all CTI file from the list.
2021-12-14 16:51:25,147 - harvesters - INFO - Discarded the device information list.
2021-12-14 16:51:25,148 - harvesters - INFO - Closed Interface module, Simulated.
2021-12-14 16:51:25,150 - harvesters - INFO - Closed Interface module, U3V.
2021-12-14 16:51:25,151 - harvesters - INFO - Closed System module, criticallink/gentl.dll.
2021-12-14 16:51:25,154 - harvesters - INFO - Closed c:\Program Files\Critical Link LLC\GenTL Viewer\bin\GenTL.dll.
2021-12-14 16:51:25,156 - harvesters - INFO - Completed resetting the Harvester object.
</pre>
<p>Tried using the sim camera but it looks like it's not going to work with harvesters right now. Seems like harvesters doesn't like the XML path we are returning.<br /><pre>
(gentl_37) C:\Users\jcormier\Documents>set SIMCAM_XML_FILE=C:\Users\jcormier\Documents\sim_camera.xml
(gentl_37) C:\Users\jcormier\Documents>python snap.py
...
2021-12-14 16:59:15,070 - harvesters - WARNING - Failed to open xml file /C:/Users/jcormier/Documents/sim_camera.xml. : RuntimeException thrown (file 'XmlParser.cpp',
line 157)
Traceback (most recent call last):
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 2313, in _get_port_connected_node_map
node_map.load_xml_from_zip_file(file_path)
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\genicam\genapi.py", line 2010, in load_xml_from_zip_file
return _genapi.NodeMap_load_xml_from_zip_file(self, ZipFileName)
_genapi.RuntimeException: File open failed in ParseXmlFile. Filename = '/C:/Users/jcormier/Documents/sim_camera.xml' : RuntimeException thrown (file 'XmlParser.cpp', line 131)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 2316, in _get_port_connected_node_map
node_map.load_xml_from_file(file_path)
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\genicam\genapi.py", line 2004, in load_xml_from_file
return _genapi.NodeMap_load_xml_from_file(self, FileName)
_genapi.RuntimeException: Failed to open xml file /C:/Users/jcormier/Documents/sim_camera.xml. : RuntimeException thrown (file 'XmlParser.cpp', line 157)
Traceback (most recent call last):
File "snap.py", line 41, in <module>
ia = h.create_image_acquirer(list_index=0)
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 3383, in create_image_acquirer
file_dict=file_dict, do_clean_up=self._do_clean_up
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 1772, in __init__
file_dict=self._file_dict, do_clean_up=self._do_clean_up)
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 2327, in _get_port_connected_node_map
self._remove_intermediate_file(file_path)
File "C:\Users\jcormier\.conda\envs\gentl_37\lib\site-packages\harvesters\core.py", line 2342, in _remove_intermediate_file
os.remove(file_path)
OSError: [WinError 123] The filename, directory name, or volume label syntax is incorrect: '/C:/Users/jcormier/Documents/sim_camera.xml'
</pre></p> Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6149#message-61492021-12-14T21:43:39ZMaurizio von Flotow
<p>GenTL Viewer: 2.4.5<br />Python: 3.8.5<br />Harvester: 1.3.2</p> Support: RE: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/6147?r=6148#message-61482021-12-14T21:12:04ZJonathan Cormierjcormier@criticallink.com
<p>The dll file takes place of a cti file. Can you share what version of the GenTL viewer you are using? And the python version as well as the version of harvesters?</p> Support: Unable to extract CTI from DLLhttp://support.criticallink.com/redmine/boards/21/topics/61472021-12-14T21:09:06ZMaurizio von Flotow
<p>I am trying to set up a Python project to communicate with a MityCAM-35MMFHDXS Evaluation Kit using Harvester, as outlined here: <a class="external" href="https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Using_Python_With_Critical_Link_GenTL_Producer">https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Using_Python_With_Critical_Link_GenTL_Producer</a>. <br />I made minimal modifications to the example snap.py (to match my GenTL Viewer directory).</p>
<p>---> Note that the camera has been ordered but has not yet shipped/arrived, so this is all preliminary work. <--</p>
<p>--<br />Issue<br />--<br />When I call the harvester function "add_cti_file" or "add_file" with the 'GenTL Viewer\bin\GenTL.dll', harvester complains with the following error: "GenTL exception: Failed to load CTI file; The specified module could not be found."</p>
<p>--<br />Attempts to fix:<br />--<br /> -Add "GenTL Viewer\bin\" directory to PATH<br /> -Download 'sim_camera.xml' and create the corresponding environment variable, as suggested here: <a class="external" href="https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Running_the_GenTL_producer_in_simulated_mode">https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Running_the_GenTL_producer_in_simulated_mode</a></p>
<p>--<br />Questions:<br />--<br />Is the .cti file bundled into this GenTL.dll file? <br />Does a standalone .cti file exist from Critical Link?<br />Is a camera required for this .cti file to be generated by the GenTL.dll file?</p>
<p>-Maurizio</p> Support: RE: MityCam B2521 CAL / WCAL commandshttp://support.criticallink.com/redmine/boards/21/topics/6059?r=6061#message-60612021-03-16T16:29:06ZKyle McKinney
<p>I think knowing that they are not applied in the uncorrected modes is sufficient. What about CDS? Are there any differences in how that functions between the modes? Basically I am attempting to get as RAW and uncorrected data as possible.</p>
<p>Thanks,<br />Kyle</p> Support: MityCam B2521 CAL / WCAL commandshttp://support.criticallink.com/redmine/boards/21/topics/6059?r=6060#message-60602021-03-16T14:47:10ZMichael Williamson
<p>Hi Kyle,</p>
<p>You can operate the sensor without calibration gain or offset data set<br />using the SGAN command.</p>
<p><SGAN 3> is high gain only (no corrections)<br /><SGAN 4> is low gain only (no corrections)<br /><SGAN 5> is combined high / low gain (no corrections)</p>
<p>If you want to replace the files with the default files prior to<br />corrections, you will need to use the USB 2.0 port (which presents and<br />RNDIS interface as described in section 13 of the user manual) and use a<br />program such as winscp to replace the calibration data with default data.<br />Let me know if you need help with that.</p>
<p>-Mike</p>
<p>On Tue, Mar 16, 2021 at 10:03 AM <<a class="email" href="mailto:redmine@criticallink.com">redmine@criticallink.com</a>> wrote:</p> Support: MityCam B2521 CAL / WCAL commandshttp://support.criticallink.com/redmine/boards/21/topics/60592021-03-16T14:02:58ZKyle McKinney
<p>Is it possible to remove/reset (set to zero) the calibration coefficients that are set by running the CAL and WCAL commands? Is there a way to figure out what they are set to?</p>
<p>Thanks,<br />Kyle</p> Support: RE: MityCAM-120MXS 12bit two least significant bits always 0http://support.criticallink.com/redmine/boards/21/topics/6001?r=6003#message-60032020-05-05T16:33:10ZDoug MacEwen
<p>Good to know! No problem, I just wanted to make sure I wasn't missing something. Thanks!</p>
<p>On May 5 2020, at 9:31 am, <a class="email" href="mailto:redmine@criticallink.com">redmine@criticallink.com</a> wrote:</p>
<blockquote>
</blockquote> Support: RE: MityCAM-120MXS 12bit two least significant bits always 0http://support.criticallink.com/redmine/boards/21/topics/6001?r=6002#message-60022020-05-05T16:31:10ZMichael Williamson
<p>Hi Doug,</p>
<p>The 120 MP Canon sensor is really a 10 bit sensor, but the MityCAM camera framework does not support 10 bit-per-pixel output packing at this time, so we packed the 10 bits into a 12 bit word with a left shift so that a full scale signal would result in a full scale output on the display. The bottom two bits will be zero.</p>
<p>I am sorry for the confusion.</p>
<p>-Mike</p> Support: MityCAM-120MXS 12bit two least significant bits always 0http://support.criticallink.com/redmine/boards/21/topics/60012020-05-05T16:28:10ZDoug MacEwen
<p>Hello,</p>
<p>I have been working with the MityCAM-120MXS in with the BayerRG12p pixel format (over USB) and noticed that the pixel values increment by 4. I dug around a little and it appears that the two least significant bits are never used, essentially making the output 10bit. I checked my implementation against the GenTL viewer provided by Critical Link and noticed that the pixel values increment by 4 there as well.</p>
<p>I was hoping that you could provide some guidance on whether this is expected behavior, I miss configured the camera, or if (and how) I should file a bug report. Let me know if there is any more information I can provide.</p>
<p>Thank you!<br />Doug</p> Support: RE: Mity Viewer Crashinghttp://support.criticallink.com/redmine/boards/21/topics/5861?r=5864#message-58642019-10-16T15:51:35ZKiel Trotter
<p>One issue was the Windows 10 driver. I think that is now understood.</p>
<p>The other issue is the dropping of images. This is the standard REBS camera. I start up the Viewer (Version 2.6.8) with the following under “Help – About CCDisp Viewer”</p>
<p>Model: S7031-1007<br />S/N: 1171<br />Mfg: Hamamatsu<br />Rows:128<br />Cols:1024<br />FPGA: 7.02<br />DSP: 6.15</p>
<p>I set the camera to Continuous update, 1 Clear Cycle. I set the mode to binning and load in a file that bins rows 4 to 124. The issue is most present at 10ms exposure time (Shortest Frame Interval box is checked, Frame rate is 21ms) and seems to not be present for exposures > 100ms. When I click Start Capture, the binned spectra is observed. After a bit (was < 1minute, now after several minutes of running) I start to see errors pop up in the lower left hand corner.</p>
<p>WARNING Image queue backup ... dropped 3 images. pushed = 2520, popped = 1693</p>
<p>As time goes by (still continuously running) the # of dropped images keeps going up. Eventually, the software freezes and has to be restarted.</p> Support: RE: Mity Viewer Crashinghttp://support.criticallink.com/redmine/boards/21/topics/5861?r=5863#message-58632019-10-14T22:08:27ZJaime Wilkiejwilkie@criticallink.com
<p>Hi Kiel,</p>
<p>In addition, can you let us know how you are imaging the camera? Area Readout vs Binning? What timing settings are you using when the software crashes, i.e. exposure time and frame interval time? Do you have the "Shortest Frame Interval Possible" box checked off?</p>
<p>Thanks,<br />Jaime</p> Support: RE: Mity Viewer Crashinghttp://support.criticallink.com/redmine/boards/21/topics/5861?r=5862#message-58622019-10-14T20:22:49ZMike Fiorenza
<p>Hi Kiel,</p>
<p>I do not recall seeing the issues that you are describing. I will set up a camera and try to reproduce this here.<br />Are you saying that if you boot the camera (using default settings) and set to continuous capture, the viewer will eventually crash after X amount of dropped images?</p>
<p>When you say you're using the latest version of the software, are you referring to the MityViewer or the camera software? Or both?</p> Support: Mity Viewer Crashinghttp://support.criticallink.com/redmine/boards/21/topics/58612019-10-14T17:52:48ZKiel Trotter
<p>Hello, We have a MITY Viewer application hooked up to a camera, Model S7031-1007. It will drop images during the run that increase in number until the entire application crashed. Any know issues like this. We are currently on the latest version of software. Thank you.</p> Support: RE: 12-bit Pixel Format using Python Harvesterhttp://support.criticallink.com/redmine/boards/21/topics/5841?r=5844#message-58442019-07-09T20:05:10ZMichael Williamson
<p>You might post to the chat/gitter room or open a ticket on the github site<br />for the harverster stuff:</p>
<p><a class="external" href="https://github.com/genicam/harvesters">https://github.com/genicam/harvesters</a></p>
<p>The project owner is very good about supporting this stuff. I suspect this<br />is likely a problem in the harvester layer.</p>
<p>-Mike</p>
<p>On Tue, Jul 9, 2019 at 4:03 PM <<a class="email" href="mailto:redmine@criticallink.com">redmine@criticallink.com</a>> wrote:</p> Support: RE: 12-bit Pixel Format using Python Harvesterhttp://support.criticallink.com/redmine/boards/21/topics/5841?r=5843#message-58432019-07-09T20:03:08ZWill Van Hyning
<p>The packed formats don't appear on the HTML page (which I'm unsure why that is) but they are listed in pfnc.py . I have tried including 'from harvesters.util.pfnc import mono_packed_location_formats' at the beginning of the script but it still gives me the same attribute error.</p> Support: RE: 12-bit Pixel Format using Python Harvesterhttp://support.criticallink.com/redmine/boards/21/topics/5841?r=5842#message-58422019-07-09T19:52:37ZMichael Williamson
<p>I was looking at this page, which has an example, but it looks like it was for 8 bit as well....</p>
<p><a class="external" href="https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Using_Python_With_Critical_Link_GenTL_Producer">https://support.criticallink.com/redmine/projects/gentl_apps/wiki/Using_Python_With_Critical_Link_GenTL_Producer</a></p>
<p>When time permits, we'll look at testing with 12 bit mode here with python + harversters.</p>
<p>It looks like the version of havesters you are using doesn't appear to support the Mono12p and Bayer12p (according to the list of supported formats in the data section on the HTML page).</p>
<p>It might be worth asking the question with the harvester developer, they may not support the "packed" formats. Mono12p and Mono12 are packed differently, according to the Pixel Format Naming Convention documents.</p>
<p>-Mike</p> Support: 12-bit Pixel Format using Python Harvesterhttp://support.criticallink.com/redmine/boards/21/topics/58412019-07-09T18:31:52ZWill Van Hyning
<p>Hello,</p>
<p>I have been trying to interface to the MityCam-C50000 using python and the harvesters library, and have been having trouble getting 12-bit data. When requesting the data from the payload component, I get an Attribute error stating: 'NoneType' object has no attribute 'data'. This happens when the PixelFormat.value is set equal to either 'Mono12p' or 'BayerBG12p'. If the PixelFormat.value is set to either 'Mono8' or 'BayerBG8', the program works as expected. I've attached an HTML document which was generated using pydoc which I have been using to understand the way the harvester module is setup.<br />Thank you for your support.</p>
<p>-Will</p> Support: RE: MityCam-2521FTS-CM-C-S fails to boothttp://support.criticallink.com/redmine/boards/21/topics/5587?r=5784#message-57842019-01-31T12:36:55ZMichael Williamson
<p>I assume you have resolve this problem with our product team, but if you have not, if the power supply light is blinking, then the camera must be somehow damaged and would need repair.</p> Support: RE: Sending commands to MityCAM-C8000 by USBhttp://support.criticallink.com/redmine/boards/21/topics/5368?r=5783#message-57832019-01-31T12:35:38ZMichael Williamson
<p>There is also a DLL for the USB 2.0 interface if you want to write a C or C++ application. Let me know if this is still of interest.</p> Support: RE: Sending commands to MityCAM-C8000 by USBhttp://support.criticallink.com/redmine/boards/21/topics/5368?r=5782#message-57822019-01-31T12:34:51ZMichael Williamson
<p>I am sorry this is so late.</p>
<p>You can get camera link cables from many vendors, such as <a href="http://www.pureformancecables.com/products.asp?catid=2&scatid=2" class="external">Pureformance</a></p>
<p>You will also need a Camera Link Frame Grabber to use the Camera Link interface.</p>
<p>The <a class="wiki-page" href="http://support.criticallink.com/redmine/projects/mityvision/wiki/Supported_Framegrabbers_CMV8000">Supported Framegrabbers CMV8000</a> lists the frame grabbers we have tested.</p>
<p>-Mike</p> Support: MityCam-2521FTS-CM-C-S fails to boothttp://support.criticallink.com/redmine/boards/21/topics/55872018-01-19T01:39:58ZAldo Apponi
<p>The serial number for our camera is S/N 673</p>
<p>We have been using this camera more or less non-stop for probably 2 years now and this is the first time I have observed this issue.</p>
<p>The camera powers on, fan runs for a few seconds, then it shuts off and a blinking yellow light can be seen through the fan housing near the top of the board. I even imagined that I smelled something at the time, but I might have been imagining it.</p>
<p>The light on the power supply blinks at the same rate as the yellow light, which seems to me that the board is using all the power supply can give it.</p>
<p>I tried to start the camera a couple of times after the first time it failed. It seemed to get a bit further along the second time--I nearly was able to complete the initialization over cameralink. The third time, it quickly failed. I did not try a fourth time.</p>
<p>It appears to me that something might be damaged in the unit.</p> Support: Sending commands to MityCAM-C8000 by USBhttp://support.criticallink.com/redmine/boards/21/topics/53682017-07-14T15:15:20ZAlessandro Maragno
<p>Hello,<br />I'm evaluating a CMOSIS CMV8000 image sensor, into the context of the project I'm working on. I received your MityCAM-C8000 after purchasing the evaluation kit. I made the setup and started taking familiarity to the kit by MityViewer (1.4.4 v), but now I need to write some script to automate the test procedures. After taking a look to the documentation on this wiki, I realize that I can send commands to the camera only by the CamlinkPanel application (1.2.0 v) by CameraLink Interface. When I received the kit, it didn't came with a CameraLink cable, and I don't know if it may be a standard interface only by the pins described into the "Interface Description for MityCAM - C8000 Camera link Interface" document. After a look around, I haven't found any cable with the same interface to link the kit to my host pc.<br />Stating this, I was wondering if there's a way to communicate and give commands to the MityCAM by USB connection, or what type of cable I need to link it to my host pc by CameraLink Interface.</p>
<p>Thank you very much for support.</p>
<p>Alessandro</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5121#message-51212016-12-02T07:53:13ZJeffrey Myersjmyers@criticallink.com
<p>Anton,</p>
<p>The dark calibration would have been cleared when you reflashed the SD card. For best performance, you should set the clock to your desired rate, then run the calibration command with the sensor darkened. The calibration values will persist between reboots (so it only needs to be done once for your chosen clock setting).</p>
<p>You can force the camera to calibrate by calling "CLCISCalibrate()." The light on the back will blink a couple times. When it goes back to solid green (and stays solid green for at least 2 seconds), the calibration is finished.</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5120#message-51202016-12-02T05:19:42ZAnton Bakulevab@carsdevices.com
<p>Update. It return non zero images only for exposures bigger than 6 sec.<br />With exposures in interval 6.01 - 6.1 sec images are partially zero (lower part of image). More exposure - less zero valued part.<br />The same issue on 80MHz also.</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5119#message-51192016-12-02T03:07:34ZAnton Bakulevab@carsdevices.com
<p>Jeffrey,</p>
<p>Thank you for your reply. I've upgraded a firmware successfully. Now it reports the following:<br /><pre>
Build Info jenkins-MityCAM-B1910_Release-41 - 41 40-000065-4-RC4
Camera Part Number 80-000719
Sensor Part Type CIS1910_GRAYSCALE
Sensor Board Revision 80-000723RC-1
SoC IO Board Revision 80-000623RC-3
IO Board Revision 80-000624RC-2
Serial Number 1
FPGA version QSYSID/DATE = 0x00010003 / Wed Aug 10 15:10:42 UTC 2016
ARM APP MD5SUM 0aa607a4f67787c58a56a589b964d11b
Linux Linux mitysom-5csx 3.12.0 #1 SMP Wed Aug 10 11:53:54 EDT 2016 armv7l GNU/Linux
</pre><br />But the camera still reports a 283MHz clock after cold reboot. And returns zero valued images after resetiing clock to 40MHz.<br />Could you write how I could diagnose and fix the issue?</p> Support: RE: There is no eth0 device in 40-000065-4 release firmwarehttp://support.criticallink.com/redmine/boards/21/topics/5116?r=5118#message-51182016-12-02T03:01:58ZAnton Bakulevab@carsdevices.com
<p>Jeffrey,</p>
<p>Thank you. Yes, this instructions fixes the problem. Now my MityCam works well by eth0.</p> Support: RE: There is no eth0 device in 40-000065-4 release firmwarehttp://support.criticallink.com/redmine/boards/21/topics/5116?r=5117#message-51172016-12-01T07:56:21ZJeffrey Myersjmyers@criticallink.com
<p>Anton,</p>
<p>I sent you an email with instructions on reconfiguring the camera.</p> Support: There is no eth0 device in 40-000065-4 release firmwarehttp://support.criticallink.com/redmine/boards/21/topics/51162016-12-01T04:44:12ZAnton Bakulevab@carsdevices.com
<p>Hello,</p>
<p>I've installed a 40-000065-4 release firmware from [[<a class="external" href="https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware">https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware</a>]] (by the way, file name is MityCAM_B1910-40-000064-4_soc_camera.img.zip, not a MityCAM_B1910-40-000065-4_soc_camera.img.zip) and got a message about eth0 device error while booting:<br /><pre>
EXT3-fs (mmcblk0p2): using internal journal
Starting Bootlog daemon: bootlogd.
Configuring network interfaces... eth0: ERROR while getting interface flags: No such device
SIOCADDRT: Network is unreachable
Starting rpcbind daemon...NET: Registered protocol family 10
IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
done.
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
</pre></p>
<p>in 40-000065-2 release firmware there was no such a problem:<br /><pre>
EXT3-fs (mmcblk0p2): using internal journal
Starting Bootlog daemon: bootlogd.
Populating dev cache
Configuring network interfaces... eth0: device MAC address 00:50:c2:11:22:33
udhcpc (v1.21.1) started
Sending discover...
libphy: stmmac-0:03 - Link is Up - 1000/Full
Sending discover...
Sending discover...
No lease, failing
SIOCADDRT: Network is unreachable
Starting rpcbind daemon...NET: Registered protocol family 10
IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
done.
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
</pre></p>
<p>Please, write how could I fix it?</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5113#message-51132016-11-29T07:40:55ZAnton Bakulevab@carsdevices.com
<p>Thank you.<br />Yes, it's fully enclosed camera that was re-flashed several months ago in this post? [[<a class="external" href="https://support.criticallink.com/redmine/boards/21/topics/4794">https://support.criticallink.com/redmine/boards/21/topics/4794</a>]]<br />Ok. I'll update a firmware.</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5112#message-51122016-11-29T07:29:03ZJeffrey Myersjmyers@criticallink.com
<p>Anton Bakulev wrote:</p>
<blockquote>
<p>I've tried to set clock rate to 40MHz but images acquired after that is zero valued. Did you tried this approach on your site?</p>
</blockquote>
<p>The MityViewer uses this approach to adjust the clock when changing between rolling and global shutter (it explicitly sets the clock to 200MHz for rolling shutter and 80MHz for global shutter). What is the serial number camera you are using? What version firmware do you have on the camera? Do you have fully enclosed cameras or just a board stack? Is the sensor a scientific or standard package sensor?</p>
<p>Is this the same camera that was re-flashed several months ago in this post? <a class="external" href="https://support.criticallink.com/redmine/boards/21/topics/4794">https://support.criticallink.com/redmine/boards/21/topics/4794</a></p>
<p>It looks like your firmware is older and needs to be updated: <a class="external" href="https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware">https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware</a></p>
<blockquote>
<p>Also I've found that defailt clock rate is 283Mhz. Such a value was received after hard reboot of MityCam.</p>
</blockquote>
<p>Depending on the type of camera setup you have (full camera vs. just boards), this may be correct. There is also a known issue regarding the reported clock frequency (see the firmware page above).</p>
<p>The clock is incorrectly reported as 283 in the case of a fully enclosed camera. Fully enclosed cameras are capped at 200MHz while the board set can be clocked up to 283MHz.</p>
<blockquote>
<p>And I see that not all clock rate values can be set. For example, when I've tried to set 50MHz the result of CLGetParameter was 0MHz.<br />What values of clock rate is valid list?</p>
</blockquote>
With the latest firmware, the clock can be set arbitrarily and the firmware will round up to the nearest appropriate clock. Assuming you have a fully enclosed camera, here are the valid clocks:
<ul>
<li>200</li>
<li>108</li>
<li>80</li>
<li>54</li>
<li>40</li>
<li>30</li>
</ul> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5111#message-51112016-11-29T05:42:39ZAnton Bakulevab@carsdevices.com
<p>I've tried to set clock rate to 40MHz but images acquired after that is zero valued. Did you tried this approach on your site?<br />Also I've found that defailt clock rate is 283Mhz. Such a value was received after hard reboot of MityCam.<br />And I see that not all clock rate values can be set. For example, when I've tried to set 50MHz the result of CLGetParameter was 0MHz.<br />What values of clock rate is valid list?</p> Support: RE: Gain regulation for high and low gain channels in MityCam-CIS1910http://support.criticallink.com/redmine/boards/21/topics/5106?r=5107#message-51072016-11-28T11:05:52ZMichael Williamson
<p>We currently do not support altering the gain settings in the camera. For rolling they are fixed to x1 / x30 in combined mode, for global they are x1 / x10 in combined mode.</p>
<p>This could be added, but it is not available in the current firmware or DLL API.</p>
<p>-Mike</p> Support: Gain regulation for high and low gain channels in MityCam-CIS1910http://support.criticallink.com/redmine/boards/21/topics/51062016-11-28T10:53:46ZAnton Bakulevab@carsdevices.com
<p>There is an ability to switch low gain channel from x1 to x3 and high gain from x10 to x30 in CIS1910 sensor. Could you, please, write how to do this in MityCam-CIS1910 by API calls?</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5105#message-51052016-11-28T10:31:56ZJeffrey Myersjmyers@criticallink.com
<p>Anton Bakulev wrote:</p>
<blockquote>
<p>Could you write also is it possible to change clock speed by MityViewer app?</p>
</blockquote>
<p>Unfortunately, there is currently no GUI interface for changing the clock speed.</p>
<blockquote>
<p>Also could you write a full structure definition tsCisParamSCLKRate ?<br />I could not find it in <a class="external" href="https://support.criticallink.com/rm_embedded/mityccd/clcamiface/clcamiface_8h.html">https://support.criticallink.com/rm_embedded/mityccd/clcamiface/clcamiface_8h.html</a> documentation.<br />Or I should search it in some other place?</p>
</blockquote>
<p>This is a fairly recent addition and it looks like the header hasn't been included in the installer package for MityViewer yet. I've attached it here.</p> Support: RE: Maximum values for HighGain, LowGain and Combined modes for MityCAM-CIS1910http://support.criticallink.com/redmine/boards/21/topics/5101?r=5104#message-51042016-11-28T09:18:45ZMichael Williamson
<p>I do not see a specification for the ADC converters to be 12 bit, only 11 bit. Can you please provide me a reference spec version and paragraph that indicates 12 bits?</p>
<p>There is a DOUT [ 11 ] pin, but that is only a flag that indicates a multiplexor value (the high gain data output can be used to multiplex high gain outputs and low gain outputs based on the the ADC value in the high gain channel, see section "2.3 Sensor Data"). Is this what you are looking at for 12 bits? The ADCs are only 11 bits.</p>
<p>With 2047 maximum values, the theoretical maximum combined value is:</p>
<p>2047+30*2047 = 63457.</p>
<p>However, full well is actually a little lower than the maximum ADC count in the low gain channel and is also sensitivy to the VTX2_NEG voltage level (which controls anti-blooming), so you may not reach all the way up to that level.</p>
<p>At a 1.7 DN/e- spec'd level with >= 33000 e- of full well spec, you may see a maximum combined count that is closer to ~55,000 counts on various pixels (that is the maximum low gain value at x1 setting will be 0.055 * 33000, or 1815 maximum value unscaled instead of 2047).</p>
<p>-Mike</p>
<p>-Mike</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5103#message-51032016-11-28T08:55:03ZAnton Bakulevab@carsdevices.com
<p>Also could you write a full structure definition tsCisParamSCLKRate ?<br />I could not find it in <a class="external" href="https://support.criticallink.com/rm_embedded/mityccd/clcamiface/clcamiface_8h.html">https://support.criticallink.com/rm_embedded/mityccd/clcamiface/clcamiface_8h.html</a> documentation.<br />Or I should search it in some other place?</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5102#message-51022016-11-28T08:48:56ZAnton Bakulevab@carsdevices.com
<p>Thank you for an explanation and a part of code. <br />Could you write also is it possible to change clock speed by MityViewer app?</p> Support: Maximum values for HighGain, LowGain and Combined modes for MityCAM-CIS1910http://support.criticallink.com/redmine/boards/21/topics/51012016-11-28T08:44:15ZAnton Bakulevab@carsdevices.com
<p>I tested maximum values in images acquired from MityCAM-CIS1910 and got that <br />for HighGain and LowGain there is 2047<br />for Combined mode there is 61380</p>
<p>2047 is 11111111111 (11bits)<br />61380 is 1110111111000100 (16bits)</p>
<p>According to CIS1910 specification it should be 12bit values in HighGain and LowGain modes and full 16bits in Combined mode.<br />Why there is so strange values in MityCam ?</p> Support: RE: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/5099?r=5100#message-51002016-11-28T07:50:53ZJeffrey Myersjmyers@criticallink.com
<p>When using the clcamiface API or MityViewer, you need to set the frame interval to something greater than the desired exposure time. If the frame interval is shorter than the requested exposure time, the camera will reduce exposure to fit in that frame interval time. The maximum frame interval time for the default clock is ~3.2 seconds.</p>
<hr />
<p>The CIS1910 with the default clock has a maximum exposure of ~3.2 seconds.</p>
<p>Depending on your camera's firmware version, you can set the clock to 40MHz for longer exposures:<br /><pre>
tsCisParamSCLKRate sr;
sr.mnSCLK_MHz = 40;
CLSetParameter(mnCamHandle, CISPARAM_SCLK_RATE, &sr, sizeof(sr)); // Sets the sensor clock speed to 40MHz
</pre></p>
<p>With a 40MHz clock, the camera will support up to ~16 seconds of exposure/frame interval.</p> Support: Acquiring images from MityCam CIS1910 with exposures grater than 1 sechttp://support.criticallink.com/redmine/boards/21/topics/50992016-11-28T02:56:48ZAnton Bakulevab@carsdevices.com
<p>I'm trying to acquire images from MityCam CIS1910 by using clcamiface API or by using MityViewer and I don't see a difference in images with exposures greater than 1 sec while using API and greater than 3 sec while using MityViwer. It seems that maximum exposure is 1 sec while using API and 3 sec while using MityViwer. Could you explain me what I'm doing wrong? Is it possible to acquire images with long exposures from MityCam CIS1910? I'm interested in exposures about 10 sec or even greater .<br />Could you provide me an example of API command sequences for acquiring images with exposure 10 sec?<br />My sequence is the following:<br /> CameraHandle = CLOpenENetCamera(strIpAddress, 19200);<br /> if (CameraHandle >= 0) {<br /> int RowStart = 0, ColStart = 0, NRows = 0, NCols = 0;<br /> CLGetCCDArea(CameraHandle, ref RowStart, ref ColStart, ref NRows, ref NCols);<br /> CLCISSetShutterMode(CameraHandle, teCISShutterMode.eeRollingShutter);<br /> CLCISSelectChannel(CameraHandle, teCISChannelConfig.eeCombined);<br /> CLCISClearCalibration(CameraHandle);<br /> CLOverrideImageTimout(CameraHandle, -1);<br /> CLSetExposure(CameraHandle, (long)(10.0 * 1000.0F));<br /> CLClearCCD(CameraHandle, 1, 0);<br /> CLWaitCompletion(CameraHandle, (int)(10.0 * 1000.0F + 10000.0F));<br /> CLReadCCDArea(CameraHandle, buffer, 1, 1);<br /> CLWaitCompletion(CameraHandle, (int)(10.0 * 1000.0F + 10000.0F));<br /> // reads a content fo a buffer and shows an image from it.<br /> }</p> Support: RE: Dump of camera sd cardhttp://support.criticallink.com/redmine/boards/21/topics/4794?r=4795#message-47952016-04-25T06:57:23ZAnton Bakulevab@carsdevices.com
<p>Thank you. I already solved the poblem.<br />1. There is necessary to download 40-000065-2_soc_camera.img.zip file from <a class="external" href="https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware">https://support.criticallink.com/redmine/projects/mityvision/wiki/MityCAM-B1910_Firmware</a> and unzip soc_camera.img and soc_camera.img.md5sum from it.<br />2. Check md5sum for soc_camera.img and write it with Win32DiskImager, for example, to extracted from MityCam mini sd card.<br />3. Insert mini sd card into MityCam and load it.<br />4. Connect by ssh to MityCam and install a soc_camera-1.0-2.mitysom_5csx.rpm from /home/root/</p> Support: Dump of camera sd cardhttp://support.criticallink.com/redmine/boards/21/topics/47942016-04-25T05:55:12ZAnton Bakulevab@carsdevices.com
<p>Hello,</p>
<p>Could you advice me where could I get an image of CIS1910 MityCam sd card? <br />I leaved my camera plugged in local network and it seems that somebody made a bad joke. Today I saw that mmc0 contains no files:<br />MitySOM-5CSx # ext2ls mmc 0<br /><DIR> 1024 .<br /><DIR> 1024 ..<br /><DIR> 12288 lost+found<br />MitySOM-5CSx #</p> Support: RE: IO port pinout diagramhttp://support.criticallink.com/redmine/boards/21/topics/4743?r=4745#message-47452016-04-11T07:57:46ZAnton Bakulevab@carsdevices.com
<p>Thank, you. It's really there. <img src="/redmine/plugin_assets/redmine_wiki_extensions/images/smile.png" alt=":)"></p> Support: RE: IO port pinout diagramhttp://support.criticallink.com/redmine/boards/21/topics/4743?r=4744#message-47442016-04-11T07:17:07ZMichael Williamson
<p>Did you check the datasheet, Figure 7 and table 5? Or is there something else that you need that is not there?</p>
<p><a class="external" href="http://www.criticallink.com/wp-content/uploads/2014/01/MityCAM-B1910F-Datasheet.pdf">http://www.criticallink.com/wp-content/uploads/2014/01/MityCAM-B1910F-Datasheet.pdf</a></p>
<p>-Mike</p> Support: IO port pinout diagramhttp://support.criticallink.com/redmine/boards/21/topics/47432016-04-11T06:48:28ZAnton Bakulevab@carsdevices.com
<p>Could you provide an IO port pinout diagram for CIS1910 MityCam? I have failed finding it in manuals.</p> Support: RE: Sources of clcamiface.dllhttp://support.criticallink.com/redmine/boards/21/topics/4722?r=4731#message-47312016-04-06T15:27:00ZAnton Bakulevab@carsdevices.com
<p>Mike,</p>
<p>Thank you for trying to fit our needs. I thinking to implement algorithm in embedded Linux user space ARM code prior to transmission via Ethernet. FPGA part of code is not needed. Yes I am familiar with Linux BSP. I'll be waiting for results of your discussion with management. Previously I wrote Omar that we have a plan to produce our spectrometers with your camera boards and currently developing the technology on MityCam.</p>
<p>-- SY, Anton.</p> Support: RE: Sources of clcamiface.dllhttp://support.criticallink.com/redmine/boards/21/topics/4722?r=4729#message-47292016-04-06T14:46:31ZMichael Williamson
<p>Hello,</p>
<p>I need to speak with management here as to how best to satisfy your needs. We have ported the DLL and the MityViewer application to linux (it is still being tested, some functions did not port cleanly, most did). The source code for that is easier to export. For the internal camera firmware, there is embedded ARM linux control code as well as FPGA VHDL. Were you thinking of impelmenting algorithms in the ARM prior to transmission via ethernet, or implementing algorithms in the FPGA. The project files for this code are a little more involved and will require a linux build platform (typically we provide a VM with the necessary tools). I am assuming you are comfortable with a linux based development environment?</p>
<p>In addition we are also in the process of releasing GigE compliant firmware (that sits alongside the MityViewer protocol). Would this be preferred?</p>
<p>-Mike</p> Support: RE: Sources of clcamiface.dllhttp://support.criticallink.com/redmine/boards/21/topics/4722?r=4725#message-47252016-04-06T12:29:45ZAnton Bakulevab@carsdevices.com
<p>Mike,</p>
<p>Thank you for your answer. I'm needed to add some spectrometer calibration commands for uploading and downloading it by clcamiface API. Also there is a question of some image processing on MityCam side (clean distortions from image). And finally we plan to add our Linux spectroscopic application in addition to Windows that uses clcamiface API.</p> Support: RE: Sources of clcamiface.dllhttp://support.criticallink.com/redmine/boards/21/topics/4722?r=4724#message-47242016-04-06T12:11:46ZMichael Williamson
<p>Hello Anton,</p>
<p>We don't normally provide the sources for the embedded firmware or for the DLL. However, the DLL can be used without MityViewer (it is a C library API) for Windows and is documented <a href="https://support.criticallink.com/rm_embedded/mityccd/clcamiface/clcamiface_8h.html" class="external">here</a>. The requried header files and libraries for linking both a 32 bit and 64 bit application are provided in the MityViewer installation package.</p>
<p>Are you targeting another operating system? What modifications do you require below the DLL level?</p>
<p>-Mike</p> Support: Sources of clcamiface.dllhttp://support.criticallink.com/redmine/boards/21/topics/47222016-04-06T12:05:07ZAnton Bakulevab@carsdevices.com
<p>Hello Mike,</p>
<p>I'm using MityCAM-B1910FTS-GM-C (Gigabit, Mono, Compact) for our spectrometer development and there is a need to modify process of receiving data from MityCam to PC by API (instead of MityViewer). Would you be so kind to give me a sources of soc_camera-1.0-2.mitysom_5csx.rpm that communicates on MityCam side and clcamiface.dll that communicates on PC side in order to bring some modifications needed in our case?</p>
<p>-- SY, Anton</p> Support: RE: Source Code for Camera Link Control Panel http://support.criticallink.com/redmine/boards/21/topics/4284?r=4721#message-47212016-04-06T11:50:24ZAnton Bakulevab@carsdevices.com
<p>Mike,<br />Great thank you for so quick answer!<br />Also would you be kind enought to give a sources of clcamiface in order to connect each other? soc_camera and PC.</p> Support: RE: Source Code for Camera Link Control Panel http://support.criticallink.com/redmine/boards/21/topics/4284?r=4720#message-47202016-04-06T11:43:19ZMichael Williamson
<p>I am ataching the source files for version 1.3.</p>
<p>This is a Qt project, and you will need the <a href="https://sourceforge.net/projects/clallserial" class="external">clallserial</a> library as well to build the application.</p>
<p>Pretty much it uses the text API as described in the relevate camera link APIs (see the main wiki page for links to each camera).</p>
<p>-Mike</p> Support: RE: Source Code for Camera Link Control Panel http://support.criticallink.com/redmine/boards/21/topics/4284?r=4719#message-47192016-04-06T11:32:29ZAnton Bakulevab@carsdevices.com
<p>up. <br />Is anybody answers here a questions?<br />I have the same question.</p> Support: RE: top and bottom half sensor temphttp://support.criticallink.com/redmine/boards/21/topics/4332?r=4334#message-43342015-01-19T15:38:26ZKyle McKinneykyle.a.mckinney@aero.org
<p>Ok great thanks! Just wanted to double check.</p> Support: RE: top and bottom half sensor temphttp://support.criticallink.com/redmine/boards/21/topics/4332?r=4333#message-43332015-01-19T15:16:20ZMichael Williamson
<p>Hi Kyle,</p>
<p>This is why we use an external thermistor attached to the sensor for temperature reporting. We have observed quite a bit of variance in the VPTAT voltages from chip to chip wrt temperature.</p>
<p>Each half of the 2521 sensor requires a factory level calibration and lookup that BAE has not provided. We don't have an easy way to measure the voltages from VPTAT and create lookup table based on temperature at factory. The values we are dumping assume a curve that is only an approximation. I would use the thermistor sensor temperature for monitoring sensor temperature, or if you want to develop your own lookups from the measured voltages that would also work.</p>
<p>We did some initial measurements of the halves as well as case, and you are right, there should not be a large difference between the top and bottom halves.</p>
<p>-Mike</p> Support: top and bottom half sensor temphttp://support.criticallink.com/redmine/boards/21/topics/43322015-01-19T15:10:51ZKyle McKinneykyle.a.mckinney@aero.org
<p>I have noticed that there is a big temp difference between the top and bottom half of the sensor.</p>
<p>Example:</p>
<p>Vptat_Top: 2.12863V : 35.3651C</p>
<p>Vptat_Bot: 2.16838V : 44.065C</p>
<p>I took a look at the sensor with a thermal camera and did not see a difference in temp between the two halves. <br />I assume the difference is cause artificially by the devices used to measure each half being slightly different?<br />The difference is seen even right when the camera is turned on after having ample time off for the two halves<br />to equalize.</p> Support: RE: High/Low gain mode using 8bpp-12bpphttp://support.criticallink.com/redmine/boards/21/topics/4283?r=4305#message-43052015-01-08T10:41:20ZKyle McKinneykyle.a.mckinney@aero.org
<p>Mike, is there a similar bias in the 8bit and 12bit modes? <br />If so what is it?<br />Does 12bit pack into 11bits in those modes?</p> Support: RE: High/Low gain mode issue using 16bpphttp://support.criticallink.com/redmine/boards/21/topics/4283?r=4288#message-42882014-12-30T13:11:40ZKyle McKinneykyle.a.mckinney@aero.org
<p>Ah, ok well that explains it! No problem, just good to know what is happening. <br />Thanks.</p>
<p>Kyle</p> Support: RE: High/Low gain mode issue using 16bpphttp://support.criticallink.com/redmine/boards/21/topics/4283?r=4287#message-42872014-12-30T12:50:53ZMichael Williamson
<p>There is a 20 count bias in the data. It's a bug in the mode you are using.</p>
<p>During calibrated high/low gain blending (normal operation), there is a 20 count bias added (digitally) to each of the channels prior to the blending.</p>
<p>The uncalibrated single channel modes you are using do not disable the 20 count bias. It should.</p>
<p>Subtract 20 counts to get the raw data. We will fix this issue in a future firmware release.</p>
<p>I am sorry for the inconvenience.</p>
<p>-Mike</p> Support: RE: High/Low gain mode issue using 16bpphttp://support.criticallink.com/redmine/boards/21/topics/4283?r=4286#message-42862014-12-30T12:38:51ZKyle McKinneykyle.a.mckinney@aero.org
<p>I use MATLAB to look at and process the data. Knowing that the data is packed into the lower 11 helps answers my question. <br />Using only 11bits should produce a maximum pixel value of 2047 but I am getting pixel values that peak at 2067. Is this <br />supposed to happen?</p> Support: RE: High/Low gain mode issue using 16bpphttp://support.criticallink.com/redmine/boards/21/topics/4283?r=4285#message-42852014-12-29T08:04:53ZMichael Williamson
<p>Hi Kyle,</p>
<p>Are you using XCAP (the epix frame grabber) or MityViewer to look at the data?</p>
<p>When you switch to single channel, all of the data scaling is removed and the data is packed into the lower 11 bits of the 16 bit word.</p>
<p>Quite often the data scaling presented by XCAP (and Mityviewer, depending on how you set it up) is trying to linearly map 16 bits of data to the 8 bits on the screen, and so all but 3 bits are chopped in the display and it looks black. The images are there (if you save them and open them in ImageJ or if you take the isolated image and scale it in MityViewer) but, the data is jammed into the LSBs of the pixel.</p>
<p>For a single image buffer in XCAP, you can shift the 11 bits of data in each pixel to the MSB:</p>
<p>- Ensure the capture is in "Unlive" <br />- Snap an image<br />- From the PIXCI View window --> Modify menu<br /> - Arithmetic<br /> - Bit Shift Left; Shift Bits set to 4 (or 5)<br /> - Hit apply</p>
<p>Let me know if this helps at all.</p>
<p>-Mike</p> Support: Source Code for Camera Link Control Panel http://support.criticallink.com/redmine/boards/21/topics/42842014-12-23T16:51:03ZKyle McKinneykyle.a.mckinney@aero.org
<p>Would it be possible to get the code behind this program? <br />I would like to be able to include the functionality of talking <br />to the camera in the software I use to collect imagery.</p> Support: High/Low gain mode issue using 16bpphttp://support.criticallink.com/redmine/boards/21/topics/42832014-12-23T16:47:04ZKyle McKinneykyle.a.mckinney@aero.org
<p>I am having issues using 16bit mode with any gain mode other than combine. <br />Data is transmitted but no matter the light level I get darkness. As I<br />change the light level the overall average pixel value does change so<br />something is happening, just nothing meaningful.</p> Support: RE: Pixel Clock B2521http://support.criticallink.com/redmine/boards/21/topics/4262?r=4265#message-42652014-11-21T16:23:43ZKyle McKinneykyle.a.mckinney@aero.org
<p>Yes I think it is time to upgrade the FG. Thanks for all the help.</p>
<p>Kyle</p> Support: RE: Pixel Clock B2521http://support.criticallink.com/redmine/boards/21/topics/4262?r=4264#message-42642014-11-21T16:20:27ZMichael Williamson
<p>Hi Kyle,</p>
<p>At the moment, the camera link serializer / pixel clock is fixed at 85 MHz. We would need to make you a custom FPGA image to drop the PLL rate down from 85 to 60. I need to see how complex that would be and get back to you.</p>
<p>It might be quicker to use an EPIX card, which we have qualified at the 85 MHz rate.</p>
<p>-Mike</p> Support: RE: B2521 Raw Order and Pixel Packing BASE modehttp://support.criticallink.com/redmine/boards/21/topics/4259?r=4263#message-42632014-11-21T15:44:29ZKyle McKinneykyle.a.mckinney@aero.org
<p>Alrighty, thank you.</p> Support: Pixel Clock B2521http://support.criticallink.com/redmine/boards/21/topics/42622014-11-21T15:44:01ZKyle McKinneykyle.a.mckinney@aero.org
<p>So I finally figure out the problem, my frame grabber can only handle a 60Mhz pixel clock. Is it possible to lower the pixel clock from 85 to 60?</p>
<p>Thanks,<br />Kyle</p> Support: RE: B2521 Raw Order and Pixel Packing BASE modehttp://support.criticallink.com/redmine/boards/21/topics/4259?r=4260#message-42602014-11-17T16:00:58ZMichael Williamson
<p>Yes, currently base mode works the same in terms of readout order.</p>
<p>It would be possible to add a new mode in firmware to support psuedo single port readouts to support a standard raster order at the cost of reduced framerate (which for base mode probably wouldn't matter), but such a mode is currently not available / planned.</p>
<p>Contact your MityCAM-B2521 rep for more information.</p>
<p>-Mike</p> Support: B2521 Raw Order and Pixel Packing BASE modehttp://support.criticallink.com/redmine/boards/21/topics/42592014-11-17T15:57:30ZKyle McKinneykyle.a.mckinney@aero.org
<p>Does BASE mode work similar to 10-Tap mode seen here:<br /><a class="external" href="https://support.criticallink.com/redmine/projects/mityvision/wiki/B2521_Raw_Order_and_Pixel_Packing">https://support.criticallink.com/redmine/projects/mityvision/wiki/B2521_Raw_Order_and_Pixel_Packing</a></p> Support: Welcome to the MityCAM Support Forumshttp://support.criticallink.com/redmine/boards/21/topics/42512014-11-11T11:41:10ZAlexander Blockalex.block@criticallink.com
<p>Thank you for visiting our MityCAM support forums.</p>
<p>Please feel free to post regarding any of our MityCAM products here. Please include the following so our engineering team, whom monitors these forums, can assist you quickly:</p>
<ul>
<li>Camera Model Number</li>
<li>Image Capture Mode/Device (Cameralink, ethernet, USB, etc.)</li>
<li>Image viewer application and version (MityViewer, EPIX, National Instruments, etc.)</li>
<li>Detailed background of the issue and current behaviors</li>
</ul>
<p>With that information and more our team will be happy to assist you with your MityCAM product(s).</p>