Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 1.3 Version: 1.3 FrameWork | |||
| Release Date: Mar 23 1999 12:00AM | |||
Known Issues | |||
Other | |||
| Average Intensity values shift every time Apply is entered. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| Within the Blob Selector tool's Parameters tab check the Avg. Intensity box and enter a value for either the min. or max. (other than the defaults). Press Apply. The values will shift by a fractional amount. Repeated applications of Apply will each cause | |||
| When saving products to PC the Data Link strings are sometimes left out | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| When the product is saved to the PC the data link strings for some or all products are not saved. This has been traced to the UI not having successfully read the data when querying product parameters. | |||
| Changing to the datalink driver will switch to the driver and then not accept any commands or send any output. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| After changing to datalink, you could not change back to the system terminal driver to initiate FrameWork or System Terminal commands. This has been fixed. The *T- system command changes the datalink terminal back to the system terminal mode. You can then use the #Tb and #Tt command to permanently set the port to system terminal. This is all handled automatically by FrameWork now. | |||
| Terminal times out while connecting to a system with many products. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| After loading the attached *.dvt file to an 800 the FrameWork UI will not be able to reconnect. Everything works fine loading the product file but the problem appears after the UI has disconnected from the system and tries to reconnect. | |||
| 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. | |||
| Terminal window for datalink is not wide enough for long outputs. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| 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 | |||
| The y axis label for the Roundness graph for precision measurement softsensors indicates roundness is pixels even if it is scaled. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| Axis on roundness graph mistakenly states roundness is in pixel when the value is scaled. When scaling a precision circle fit softsensor, the roundness measurement as well as the radius are scaled. However, the roundness graph's y axis label is mistak | |||
| 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. | |||
| Strange datalink values show up in the terminal window. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| If the sensor is failing when a parameter entry is created for it the type is changed to 'character' regardless of the default type. | |||
| Memory allocation error in the results table for measurement softsensor. Funky random shut down of system after a period of time. May cause system to crash and LED lights on 800 to alternately flash. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| The Measure Across Area and Area Edge SoftSensors in the Precision Measurement toolbox will cause a memory allocation error if any of the advanced measurement settings are seleced besides line fit. Memory allocation will show up in the results table as a | |||
| 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. | |||
| Datalink strings seem to disappear or be wrong when product files are restored from the PC. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| The datalink string are sometimes missing due to the fact that the information is not queried from the smartimage sensor. To make the data current on the userinterface, each product can be reselected. This ensures all the data is correct. | |||
| Communications locks up when starting up the user interface when a large number of product files is present on the system. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| Communications locks up when starting up the user interface when a large number of product files is present on the system. | |||
| "Error executing Script" is generated in the script softsensors when referencing NumbBlobs. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Fixed | |
| The new Script Math SoftSensor cannot reference the parameter NumBlobs of a SoftSensor in a script file. An error executing script will be generated by the compiler in the script tab dialog. | |||
| No information is seen in a pixel graph or gradient graph for the new segmented find circle arc softsensor. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| The segmented arc softsensor graphs sometimes shows strange information. This is due to the fact that the softsensor graphs the information for the edge scan located at the 3 o'clock position. If there is no edge there, then the graph contains no data. | |||
| Product and/or softsensors start failing without cause. The threshold of a softsensor seems to have changed without cause. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| FrameWork 1.3 allows the threshold of a softsensor to be changed directly on a graph on the desktop by clicking on the appropriate threshold value. This was done to make it easier to set a threshold value. However, since a single mouse click changes the | |||
| Numbers formatted as ASCII characters are not output for Datalink. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3 FrameWork | Status: Verified Fixed | |
| In datalink it is documented that values can be formatted as a character. This should give an equivalent ASCII character when it is applicable. However, this formatting was not implemented in FrameWork 1.3. | |||
| Invalid Param shows up in the sample display for datalink and Invalid Format shows up in the terminal window. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1 Release FrameWork | Status: Verified Fixed | |
| The gradient threshold for datalink has not been implemented in FrameWork 1.3. | |||
| Invalid Parameter shows up in the terminal window for datalink. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| The scale factor should not be shown as a valid parameter under individual measurement softsensors. | |||
| Boundary blobs are counted when count boundary blobs is disabled. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| Boundary blobs are counted even when count boundary blobs are disabled | |||
| String data cannot be viewed in the terminal window of DataLink | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified Fixed | |
| The terminal window is not size properly to match the string length before wrapping to the next line. | |||
| "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. | |||
| 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. | |||
| A script tool gets a "syntax error" on the line which has a <> (not equal) operator on it. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| The not equal operator does not work in the Script SoftSensor and it causes a syntax error. | |||
| The intensity parameter setting shifts by a fractional amount when the apply or ok buttons are pressed. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| The intensity parameters are rounded incorrectly when they are sent to the processor. Therefore, each time the apply button or the ok button is pressed in the blob softsensor, the parameters change by a fractional amount. | |||
| The roundness value for the find circle or segmented arc softsensor is missing from datalink | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.3B24 FrameWork | Status: Verified Fixed | |
| The roundness value does not show up in the drop-down in the string tab for the datalink. | |||
| "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. | |||
| Axis on roundness graph mistakenly states roundness is in pixel when the value is scaled. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: | Status: Verified Fixed | |
| When scaling a precision circle fit softsensor, the roundness measurement as well as the radius are scaled. However, the roundness graph's y axis label is mistaken labeled still as in pixels when the value is actually scaled correctly. | |||
| 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. | |||
| F8 does not bring up the histogram graph for a blob generator softsensor. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| When you have the blob generator selected F8 brings up the Pass/Warn/Fail graph instead of the histogram graph. | |||
| The Table of Contents file does not show up for the Help file in FrameWork 1.3 | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.4 Beta 5 FrameWork | Status: Verified Fixed | |
| The necessary fwk.cnt file is not installed when you run the FrameWork 1.3 installation program. | |||
| 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. | |||
| Advanced Measurement softsensor parameters can cause SmartImage sensor to intermittently crash. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.4 FrameWork | Status: Verified Fixed | |
| Some advanced measurement softsensor setting can cause the smartimage sensor to crash due to a divide by zero. This will occur if no edges are found on a measure across area softsensor on a black image with mean distance selected on the advanced paramete | |||
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. | |||
