Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 2 Version: 2.0.1 Release FrameWork | |||
| Release Date: Apr 21 2000 12:00AM | |||
New Features | |||
| FrameWork User Interface | |||
| Version Added: 2.0.1 Release FrameWork | |||
| Numerous aspects of the user interface have been enhanced in FrameWork 2.0. A Result Panel has been added to make the Result Table and SoftSensor graphs more visible. The SoftSensor threshold can be changed on the Result Panel graph. Modeless dialog boxes allow easier navigation. A ctrl-click allows the user to zoom in and out of the image display while drawing SoftSensors. | |||
| SmartImage Sensor Emulator | |||
| Version Added: 2.0.1 Release FrameWork | |||
| The Emulator allows you to run FrameWork without connecting to a SmartImage Sensor camera. This mode allows for off-line Product development, debugging, and general education. | |||
| OCR SoftSensor | |||
| Version Added: 2.0.1 Release FrameWork | |||
| BETA software. DVT is evaluating optical character recognition software to be included in future FrameWork versions. Implemented in the FrameWork 2.0 Emulator is an OCR SoftSensor. This tool is for testing and evaluation purposes. This Beta SoftSensor is made available by an ini setting. | |||
| ObjectFind SoftSensors | |||
| Version Added: 2.0.1 Release FrameWork | |||
| This new category of SoftSensor is an enhanced position-finding tool. Object Find SoftSensors learn the shape of your part, then seek out instances of that shape in later images. It finds objects through 360 rotation and through varied lighting conditions. | |||
| Fanuc Communications Driver | |||
| Version Added: 2.0.1 Release FrameWork | |||
| This new driver implements Fanuc’s Sensor Interface protocol over a serial connection. This works with RJ-2 and RJ-3 controllers. For more information, please download the Fanuc Integration note from the Support/ Download area of the DVT website. | |||
| Motoman Communications Driver | |||
| Version Added: 2.0.1 Release FrameWork | |||
| This new driver allows the DVT hardware to communicate with a Motoman XRC controller. Data can be sent to the Motoman registers via the serial connection. For more information, please download the Motoman Integration note from the Support/ Download area of the DVT website. | |||
| Undo/Redo Functions | |||
| Version Added: 2.0.1 Release FrameWork | |||
| The Edit menu (new in FrameWork 2.0) now includes an Undo and Redo command. In addition, on the Expanded Toolbar, there are buttons for Undo and Redo. | |||
| Background Scripting | |||
| Version Added: 2.0.1 Release FrameWork | |||
| Background Scripting in FrameWork 2.0 allows the user to run a script independent of inspections. | |||
Known Issues | |||
Other | |||
| FrameWork UI looses communication when long output pulse widths are used. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Reproduced | |
| A dialog box is displayed that states "Communications has been lost with the SmartImage sensor, would you like to disable communications". The status/ready LED light is constantly off. This is typically caused by having an output pulse width larger than your time between triggers. | |||
| Using Erosion, Open, or Close on a Blob Generator SoftSensor may cause boundary blobs to be counted. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Open | |
| Boundary blobs being counted when count boundary blobs is disabled. When performing preprocessing on a blob generator tool, any preprocessing involving erosion (erosion, open, and close) will cause the boundary pixels to be eliminated, therefore causin | |||
| If a Blob Selector SoftSensor is being used as a Locator, the position check box in the softsensors parameter page must be enabled | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified As Designed | |
| When referencing a Blob Selector SoftSensor for position, the softsensor fails and the results table failure mode is indicated as "Position Failed" If the position check box in the Blob Selector SoftSensor is not enabled, then there is no correct posit | |||
| Restoring Inspection Products may not restore all softsensors. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Verified as Designed | |
| A message stating "Not all softsensors parameters were correctly transferred to the SmartImage Sensor" or some of the softsensors are not restored for a product. DVT Product files are not properly restored when the Product ID is already used by another product. | |||
| Outputs seem to be not available when using a multiplexer and the toggle output. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified As Designed | |
| The toggle digital output toggles after each head instead of when the outputs are available. | |||
| A dialog box is displayed that states "Communications has been lost with the SmartImage sensor, would you like to disable communications". The busy LED light is constantly on and ready LED light is constantly off. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Open | |
| Communications with the SmartImage sensor appears to stop due to an overtaxing of the SmartImage sensors processor. The usually occurs when inspections are running internal trigger at full speed and there is a long output pulse width is defined. | |||
| Memory allocation is indicated in the results table for a small circular softsensor. A small circle or arc is drawn incorrectly in the sampled image display. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Open | |
| When drawing a small circle or arc less than 7 pixels in diameter, there are not enough points to approximate the circle. This causes a memory allocation error in the firmware which causes the system to eventually run out of memory causing the system to fail. | |||
| "Cannot reference own outputs" shows up when compling script tools. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified as Designed | |
| When writing a script, the outputs of the script softsensor cannot be referenced. They can only be set. | |||
| Strange intensity softsensors brightness values in datalink. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | Status: Verified As Designed | |
| The brightness value for an intensity softsensors used in datalink is % below threshold. This is actual the % darkness scaled by 100. So a brightness of 32.56% would be 6744. | |||
| When referencing subpixel position of a Blob Selector SoftSensor, the wrong position can sometimes be used without warning. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified as Designed | |
| The wrong position of a blob selector softsensor is sometime sent to the coordinate transformation softsensor when more than one blob is sent from a generator blob tool to a selector blob tool. This occurs because the first blob is always the upper most blob. | |||
| "Error executing Script" is generated in the compiler results of the script. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified as Designed | |
| The script tool itself is not recognized in the script until you hit apply, since new SoftSensors are only created when you hit apply or OK. However, once you hit apply or OK, the SoftSensor will start being used for inspection purposes. | |||
| Coordinate Transformation softsensor generated incorrect values when referencing a Blob Selector SoftSensor. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified as Designed | |
| The position and angle check boxes in the Blob Selector SoftSensor parameters page must be enabled, otherwise no position is calculated and there is no correct position to reference. | |||
| The feature size parameter appear to change on the user. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified as Designed | |
| The minimum feature size must be less than the maximum feature size, if this is reversed the two values are automatically switched without notifying the user. | |||
| User Interface will not communicate with Series 600 over Ethernet. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | Status: Verified as Designed | |
| You cannot communicate with a different SmartImage sensor with the same IP address. This includes if you are connected directly to one Series 600 then disconnect it and connect to another Series 600 with the same IP address. Reason: each ethernet device | |||
| The SmartImage sensor fails inspections, however the SID and results table passes. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified As Designed | |
| This is related to a timing issue caused by incorrect system setup. If you go to the Ssytem Inspection Statistics graph you will see missed inspections and/or resource conflicts. Check areas related to timing: Delay after trigger, inspection period, output pulse width. | |||
| Image noise in a Series 600 image when image has saturation. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | Status: Verified as Designed | |
| This occurs when the image has saturation area and antiblooming is enabled. You will see slight intensity variation in the saturated area. The area will the variation will not change from image to image. This is caused by a combination of antiblooming and sensor gain. | |||
| Creating a power up System Status output by inverting the polarity. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | Status: Verified as Designed | |
| You can create a System Status output by inverting the polarity of an output on the I/O parameters page. Therefore, the output is only active when the system is powered up in FrameWork. If the system is turned off or in diagnostic mode, the output will not be active. You can also create a power up bit using a background script. | |||
| Only a portion of the image appears when restoring an image for the PC. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | Status: Verified as Designed | |
| Only a portion of a full image will appear when an image is restored from the PC when the Series 600 is first powered up. This occurs because the image buffers have not yet been initialized. Before restoring images from the PC, you should first start real time feadback. | |||
| Blob Angle is reported from 0-180 degrees when principal axis (360 degree) is selected for angle calculation. | |||
| Version Effected: 1.4 FrameWork SR1a | Version Fixed: | Status: Verified As Designed | |
| The blob angle softsensor will report an angle between 0-180 if the blob is symetric due to the angle algorithm. | |||
| Sampled Image Display is minimized on a 600 when running FrameWork 1.4. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1 | Status: Verified as Designed | |
| Newer Series 600 systems contain a new FPGA chip for imaging. This chip requires different firmware code. You have downloaded FrameWork 1.4 and you must instead download FrameWork 1.4 SR1a. | |||
| Incorrect position location given by measure across area softsensors | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.2 Beta 9 FrameWork | Status: Verified Fixed | |
| The position given in datalink and script for a measure across area softsensor is incorrect when using the mean, median, min, or max distance advanced parameter. The value that is reported is the distance value added to the x-axis. | |||
| Blob Selector stops reporting blobs | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| After creating a Blob Generator and Selector, if the Generator SoftSensor is moved on the SID, applied to the new position, and then the Undo button is checked, the Selector will no longer report any Blobs being found. | |||
| Intermittent communication or cannot connect serial to system. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Verified As Designed | |
| You may be getting noise on the serial port. This can be checked by using Hyperterminal which is installed with Windows. The default serial communication setting are 38400-8-N-1-NO FLOW. Hold down the Enter key of the PC, you should recieve question marks ? back from the SmartImage sensor. If you get any other characters, you are getting noise on your serial line. Check to make sure you are using a fully populated, 6 conductor serial cable and not a 4 conductor cable. | |||
| Output Timing/Inspection Termination Issue | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Reproduced | |
| If Outputs are configured for "Immediately, but within X ms after trigger", there is an issue with the termination of the inspection. The internal clock is reviewed after each SoftSensor has finished executing to determine the inspection time. If there is a SoftSensor that takes a long time to execute (non-optimized OCR failure), and it starts inspecting just prior to the Output time-out, the timer is not polled again until after SoftSensor has finished inspecting. This is an issue if there is a new triger coming just after the timer times out - you will end up with a resource conflict. | |||
| Some data from dialog not transferred when OK is selected. | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.3 Beta 10 FrameWork | Status: Fixed | |
| Script Non-Conversion of Byte to Long | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: | Status: Not-Reproduced-R&D | |
| System cannot convert Byte to Long - Error states can't convert type "B" to type "J". | |||
| Segmentation would not be performed correctly when fixed, percent path contrast, or percent reference thresholding set. | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.4 Beta 6 FrameWork | Status: Verified Fixed | |
| Setting a threshold value that would result in a threshold of 80% or more would cause no objects to be segmented by the OCR routines. | |||
Confusion Points | |||
| Intensity values sent by Datalink and used by Script SoftSensors do not appear to be correct. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | ||
| Intensity values used in the Script SoftSensor and in Data Link are Integer values between 0 and 10000. These values are actually the percent darkness scaled by 100 in order to achieve an integer value. | |||
| Template does not find correct template on same image. | |||
| Version Effected: 1.4 Beta 5 FrameWork | Version Fixed: | ||
| Sometimes the template matching will find the wrong match even on the same image after the first learn. This is a function of the way template matching is implimented. This indicates the most interesting feature of the template is being confused by another feature. | |||
| Noise character are seen on the Hyperterminal over the serial port. | |||
| Version Effected: 1.4 Beta 6 FrameWork | Version Fixed: | ||
| Depending on the environmental conditions, you may get noise over the serial line which does not allow you to communicate with the Series 600 or download firmware. This noise can often be suppressed by connecting the grnd pin on the RS-422 port. This pi | |||
| Too many active users connections dialog when connecting to Series 600 | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | ||
| FrameWork only allows one active FrameWork session with the Series 600 in order to eliminate confusion between who has control over the FrameWork session. Another person may be connected to the system already. Our communications with the system was lost | |||
| Template percent error appears incorrect when using dark or light pixels only. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | ||
| Using the Template SoftSensor, when dark or light pixels only are selected, the percent error is calculated over all pixels contained within the SoftSensor, not just the light or dark pixels respectively. | |||
| Image appears to be blurry at very low exposure times. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | ||
| The image can appear blurry at very low exposure times (<0.1 ms) when you are using continuous illumination. At low exposure times, the shifting time of the image used by the electronic shutter becomes a greater percent of the exposure time. The streaki | |||
| Image in the SID appears to be grainy or blurry. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | ||
| The image in the sampled image dispay appears to be grainy. This is caused by the computer settings only using 63 grayscales when the computer is set up for a high resolution disply. The gray scaled image of FrameWork is best displayed on the computer with 256 Grey Scale. | |||
| Warning on digital inputs for product selection may be misleading. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: | ||
| A warning comes up when the digital product ID is set to a number greater than 16 which states numbers greater than 16 are not supported ditigally. However, you can add or delete digital inputs for product selection. This warning should be more generic. | |||
| Cannot communicate serially between the 600 and IA Motion Controller | |||
| Version Effected: 1.4 Beta 12 FrameWork | Version Fixed: | ||
| The reason for this problem is that the BlackBox RS422-RS232 converter is powered with the signals from the RS232 side 9-pin interface, specifically from pin 4(DTR). IA requires use of a Selnet port (6 pin straight plastic connector). This connector onl | |||
