Ticket iMAGE S | Ticket AVT | Problem Description | Camera Model | FW Version | Status on the field | iMAGE S comment | Feedback AVT |
1009 | 117202 | Incomplete frames, even when a single frame is triggered | Manta, and Alviums USB (2050m and 500m) - Probably directly not related a specific model | up to FW 10 | Solved with FW Update to 12. Handled with workaround (new frames request when incomplete frame occurs) | Likely influenced by the specifc USB Chipset, reducing the Throughput limit strongly reduces the rate of Incomplete frames | Fixed from FW12 |
354 | Asynch. acquisition with SW Trigger, wrong image when throughput limit is not frame rate's multiple. FW 7 | Alvium 1800 U - 2050m (alleged to affect all Rolling Shutter sensors) | 7 | Solved with FW Update to 12. If FW update is not allowed: handled with workround (Freerun at fixed frame rate instead of SW Trigger used. Frame rate set to multiple of the timing imposed by the throughput limit) | Fixed from FW12 | ||
1184 | 117202 | Image artifacts when ROI size and offset are set for the first time, with ReverseY enabled | Alvium 1800 U-2050m | 12 | Solved with FW update to 13. If FW update is not allowed: handled with workaround - set ReverseY first and then set the ROI settings. Or set ROI in two steps | Fixed from FW13 | |
1184 | 120438 | While in Single Frame, if a new Exposure Time is set, the camera starts to acquire continuously in freerun. | Alvium 1800 U-500m | 12 | Solved Previously handled with workaround - Stop the camera before modifying exposure time | Fixed in FW 13.01 | |
1184 | 120348 | Acquisition in SingleFrame: when exposure time is pretty long (>=500ms). After some single frames have been acquired. A brigther one is acquired. Then grabbing any further single frame gets a -13 error. The camera needs a Reset. | Alvium 1800 U-500m | 12 | Solved | Fixed in FW 13.01 | |
1184 | 120348 | Acquistion in SingleFrame: after the above issue occurs, further frames acquisition are denied. Error code -13 is reported. The camera needs a Reset | Alvium 1800 U-500m | 12 | Solved | Fixed in FW 13.01 | |
1184 | 120348 | Acquisition in SingleFrame: is Start/Stop grab is done too fast (i.e. before the frame is completed), a -13 error is returned. The camera needs a Reset | Alvium 1800 U-500m | 12 | Open | Camera behaviour | |
1280 | 121770 | If gain is modified with too large excursion the new setting has no effect on the image intensity. Nevertheless that, gain's feature is updated correctly. | Alvium 1800 U-500m (exposures >=100ms) | 11/12 | Handled with workaround - Change gain gradually with smaller steps | Fixed with FW 13.1 | |
122257 | With Async. acquisition and trigger mode, if exposure time is modified just before providing a new SW trigger. The camera is not able to return a frame. A delay equal to the frame time must be waited before commanding a new frame. Camera needs to discard a dummy frame after exposure change, before accepting a new one. | Alvium 1800 U-2050 Alvium 1800 U-500 | any | Open | Intrinsic property of Rolling Shutter sensors, some improvements could come with FW14 and Sony sensors. | ||
| 764 | 114611 | With more than one camera, disconnection and acquisition problems happening randomly on one or more cameras. | Alvium 1800 U-240 | 10/11/12/13 | Solved | Tested almost everything, from SW to cables, from acquisition interface to PC mainboard. Nothing solved. PCB replacing solved | |
| - | - | Sometime, especially with Intel's USB Chipset, the camera is recognised as USB2 device | Alvium USB3 | 10/11/12/13 | - | To test problems at camera's USB interface, a fallback FW has been provided previously, fallback FW is attached | |
988 | DPC map not correct, AVT's DPC tool cannot manage > 1000 defect points. So with high resolution sensors it is not able to handle a custom DPC map properly. Also DPC algorithm seems to be improved | Alvium 2460c | Any | Open - custom creation of DPC map. For instance with Halcon | Likely will take very long time to be addressed | AVT's DPC tool to be improved. Still to be done. | |
| - | 1983 | Wrong white balance when operating with trigger mode | Alvium 1240c e 2050c | 13.01.794391f9 | Open - to be fixed in next FW release | It is due to wrong management of read out with red and blue pixels | To be fixed in next FW release |