Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 1.4 Version: 1.4 FrameWork SR2 | |||
| Release Date: Nov 09 1999 12:00AM | |||
Known Issues | |||
| Datalink values continue to be transmitted via Ethernet when inspection are off. | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| If you are using datalink across ethernet, the values will continue to be sent if you have play mode on but running of inspection off. This is not the case if you are sending values over the serial port. | |||
| Blob Softsensor changes preprocessing values when restoring product from the PC. | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| The size for step of preprocessing is incorrectly read in as 10 when restoring a blob generator softsensor from the PC. You must manually edit the step 2 preprocessing size value when you restore the product. | |||
| Blob Angle is reported from 0-180 degrees when principal axis (360 degree) is selected for angle calculation. | |||
| Status: Verified As Designed | Version Fixed: | ||
| The blob angle softsensor will report an angle between 0-180 if the blob is symetric due to the angle algorithm. | |||
| Very long input strings in the Datalink strings tab will cause the computer to lockup and proper values will not be output. | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| If an input string has been entered that results in a string being sent to the firmware that is longer than 200 char the user interface will lockup the next time the datalink box is opened. | |||
| Using Erosion, Open, or Close on a Blob Generator SoftSensor may cause boundary blobs to be counted. | |||
| Status: Open | Version Fixed: | ||
| 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 | |||
| Restoring Inspection Products may not restore all softsensors. | |||
| Status: Verified as Designed | Version Fixed: | ||
| 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. | |||
| Straightness is missing from an area-edge-line sensor in DataLink | |||
| Status: Verified Fixed | Version Fixed: 2.2 Release FrameWork | ||
| Copy from Display does not work all the time. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| Copy image from display does not work. This is a known problem with Service Release 1. | |||
| Copy Image to Display does not work all the time. | |||
| Status: Verified Fixed | Version Fixed: | ||
| Copy Image to Display does not work. This is a known problem with Service Release 1 that has been corrected in SR1a. | |||
| New or moved softsensors are not marked in the Sampled Image Display | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| New or moved softsensors are not marked on the image in the SID. This occurs with Service Release 1 when the real-time feedback is not enabled. A new image is not sent back to the user interface with the new softsensors marked. The softsensor marking w | |||
| SmartImage sensor sometimes continues taking images when real time feedback and inspections are off. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| After turning real-time feedback and inspections off, the smartimage sensor will continue to take images. This will be indicated by the strobe light continuing to flash. This has been fixed in Service Release 1a. | |||
| One long LED flash followed by three short ones. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| If unit has mismatched software and firmware the unit can display an unusual sequence of LED lights. One long green ready followed by three short green ready lights. This is accompanied with no serial or ethernet communications. Hyperterminal communica | |||
| Min Contrast setting for blob generator softsensor appears to switch. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| When the mininum contrast value is set, the value moves to the warn condition. | |||
| Long 1-D Barcodes can cause Series 600 to crash. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| There was a limitation of the number of edge crossing that could be handled in FrameWork 1.4 for 1-D barcodes. An overflow in the code would occur and the system would crash. This could potentially occur if percent of path contrast threshold is used for | |||
| Scale factor cannot reference the script softsensor's distance. | |||
| Status: Fixed | Version Fixed: 2.4 FrameWork Beta 17 | ||
| Some measurement and math softsensors cannot be used as a reference for a scale softsensor, even though they appear in the reference softsensor drop down list. | |||
| 1-D barcodes sometime pass with a blank image. | |||
| Status: Fixed | Version Fixed: | ||
| Some 1-D barcodes seem to pass when there is a blank background. | |||
| Access Correct Password can change with certain characters | |||
| Status: Verified Fixed | Version Fixed: 2.4 Beta 6 FrameWork | ||
| The following characters cannot be used in the following password positions. Position 1: u, x. Position 2: y, Position 7: r, Position8: s, Position 9: p, Position: 10: q, position 11:v. These characters in these particular position are ignored by FrameWork on subsequent powerup. Therefore, the password in altered. | |||
| Intermittent communication or cannot connect serial to system. | |||
| Status: Verified As Designed | Version Fixed: | ||
| 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 | |||
| Status: Reproduced | Version Fixed: | ||
| 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. | |||
| F8 does not bring up the histogram graph for a blob generator softsensor. | |||
| Status: Verified Fixed | Version Fixed: 2.2 Release FrameWork | ||
| The F8 button is used to open the primary graph of a SoftSensor. For the Blob Generator F8 should open the histogram graph. It does not. | |||
| Strange intensity softsensors brightness values in datalink. | |||
| Status: Verified As Designed | Version Fixed: | ||
| 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. | |||
| User Interface will not communicate with Series 600 over Ethernet. | |||
| Status: Verified as Designed | Version Fixed: | ||
| 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 | |||
| Image noise in a Series 600 image when image has saturation. | |||
| Status: Verified as Designed | Version Fixed: | ||
| 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. | |||
| Status: Verified as Designed | Version Fixed: | ||
| 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. | |||
| Template Pass and Warn parameter are not stored correctly when restoring the product file. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| When backing up a product which contains a template match softsensor, the PASS/WARN criteria for percent error is stored as 0% instead what is was set to in the DVT SmartImage sensor. | |||
| Template Only Softsensor are incorrectly duplicated. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| When duplicating a Template Only softsensor the template softsensor defaults to using segments. Since no search area is used with the Template Only softsensor, this should not effect the template match error result. | |||
| Moved off image failure when duplicating a Product which uses a Template Match Softsensor. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| When duplicating a product which has a Template Match Softsensor which references another softsensor for position, the template match softsensor will lose its position information. This causes template softsensor to fail and the result in the results tab | |||
| Template Softsensor does not reproduce zero on same learned image after powering system down. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1 | ||
| This is caused by the sequence in which you apply a relearning of a template softsensor. After relearning a template softsensor you should hit OK. | |||
| Memory allocation seen as failure cause for a Measure Across Area softsensor. | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| The Measure Across Area softsensor returns an incorrect failure code when no edges are found. It returns a Memory Allocation Error instead of a No Edges Found result. | |||
| Automatic Failed Image Capture saves too many images. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| The automatic failed image capture save whatever image is in the sample image display ever 1-2 seconds. This occurs whether it is a new image or not. If there is not a new image it will store the same image over and over. | |||
| The blob softsensor runs abnormally slow on a Series 600 when calculating the radius. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| The blob softsensor runs slow when calculating the angle using the furthest point method or if the radius parameter is checked. The code has been optimized in Service Release 1a. | |||
| Blob Radius parameter cannot be set above 200. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| The parameter to check to radius of a blob cannot be set above 200. This has been increased for larger radii in Service Release 1a. | |||
| Script softsensor can cause the SmartImage sensor to crash. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| A script softsensor can cause the system to crash if an "else if" statement is used without also using an "else" statement. This condition will cause the code to continue to loop infinitely. | |||
| Only a portion of the image appears when restoring an image for the PC. | |||
| Status: Verified as Designed | Version Fixed: | ||
| 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. | |||
| Scanning for 1-D barcodes does not appear to mark or work. | |||
| Status: Verified Fixed | Version Fixed: 1.4 Beta 6 FrameWork | ||
| The spacing is currently set at the scacing number minus one. Therefore, you must have at least a 2 pixel spacing for it to scan. This will be corrected in future versions. | |||
| System crashes on power-up when using a response function in datalink. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| If you save a product to flash with a response function, the smartimage sensor could crash on power up. This problem has been fixed in FrameWork Service Release 1.4 SR1a. | |||
| UPC barcode reader reads code but fails inspection in results table. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| There was a check sum error in the UPC code algorithm with effected codes which ended in the number 0. The code would be read but would fail inspections. This has been fixed in Service Release 1a. | |||
| Sampled Image Display is minimized on a 600 when running FrameWork 1.4. | |||
| Status: Verified as Designed | Version Fixed: 1.4 FrameWork SR1 | ||
| 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. | |||
| The warn and pass conditions for blob generator softsensor is checked and set to zero. | |||
| Status: Verified Fixed | Version Fixed: 1.4 FrameWork SR1a | ||
| When restoring a product with a blob generator softsensor from the PC, the warn or pass conditions way be checked and set to zero if either is initially set. (ie, if only the pass condition is checked and set to 10, when you restore the product from the | |||
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. | |||
| Gradient Threshold and Scale factor do not work in Datalink | |||
| Version Effected: 1.4 FrameWork SR2 | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| The Scale Factor and Gradient Threshold Parameters were not enabled for this version of FrameWork. | |||
| Very long input strings in the Datalink strings tab will cause the computer to lockup and proper values will not be output. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| If an input string has been entered that results in a string being sent to the firmware that is longer than 200 char the user interface will lockup the next time the datalink box is opened. | |||
| 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 | |||
| F8 does not bring up the histogram graph for a blob generator softsensor. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| The F8 button is used to open the primary graph of a SoftSensor. For the Blob Generator F8 should open the histogram graph. It does not. | |||
| 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. | |||
| Straightness is missing from an area-edge-line sensor in DataLink | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 2.2 Release FrameWork | Status: Verified Fixed | |
| 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. | |||
| Template Pass and Warn parameter are not stored correctly when restoring the product file. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| When backing up a product which contains a template match softsensor, the PASS/WARN criteria for percent error is stored as 0% instead what is was set to in the DVT SmartImage sensor. | |||
| Template Only Softsensor are incorrectly duplicated. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| When duplicating a Template Only softsensor the template softsensor defaults to using segments. Since no search area is used with the Template Only softsensor, this should not effect the template match error result. | |||
| Moved off image failure when duplicating a Product which uses a Template Match Softsensor. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| When duplicating a product which has a Template Match Softsensor which references another softsensor for position, the template match softsensor will lose its position information. This causes template softsensor to fail and the result in the results tab | |||
| Template Softsensor does not reproduce zero on same learned image after powering system down. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| This is caused by the sequence in which you apply a relearning of a template softsensor. After relearning a template softsensor you should hit OK. | |||
| Memory allocation seen as failure cause for a Measure Across Area softsensor. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| The Measure Across Area softsensor returns an incorrect failure code when no edges are found. It returns a Memory Allocation Error instead of a No Edges Found result. | |||
| Automatic Failed Image Capture saves too many images. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| The automatic failed image capture save whatever image is in the sample image display ever 1-2 seconds. This occurs whether it is a new image or not. If there is not a new image it will store the same image over and over. | |||
| Copy from Display does not work all the time. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| Copy image from display does not work. This is a known problem with Service Release 1. | |||
| Copy Image to Display does not work all the time. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Verified Fixed | |
| Copy Image to Display does not work. This is a known problem with Service Release 1 that has been corrected in SR1a. | |||
| New or moved softsensors are not marked in the Sampled Image Display | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| New or moved softsensors are not marked on the image in the SID. This occurs with Service Release 1 when the real-time feedback is not enabled. A new image is not sent back to the user interface with the new softsensors marked. The softsensor marking w | |||
| The blob softsensor runs abnormally slow on a Series 600 when calculating the radius. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| The blob softsensor runs slow when calculating the angle using the furthest point method or if the radius parameter is checked. The code has been optimized in Service Release 1a. | |||
| Blob Radius parameter cannot be set above 200. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| The parameter to check to radius of a blob cannot be set above 200. This has been increased for larger radii in Service Release 1a. | |||
| Script softsensor can cause the SmartImage sensor to crash. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| A script softsensor can cause the system to crash if an "else if" statement is used without also using an "else" statement. This condition will cause the code to continue to loop infinitely. | |||
| SmartImage sensor sometimes continues taking images when real time feedback and inspections are off. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| After turning real-time feedback and inspections off, the smartimage sensor will continue to take images. This will be indicated by the strobe light continuing to flash. This has been fixed in Service Release 1a. | |||
| Datalink values continue to be transmitted via Ethernet when inspection are off. | |||
| Version Effected: 1.4 FrameWork SR1a | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| If you are using datalink across ethernet, the values will continue to be sent if you have play mode on but running of inspection off. This is not the case if you are sending values over the serial port. | |||
| Blob Softsensor changes preprocessing values when restoring product from the PC. | |||
| Version Effected: 1.4 FrameWork SR1a | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| The size for step of preprocessing is incorrectly read in as 10 when restoring a blob generator softsensor from the PC. You must manually edit the step 2 preprocessing size value when you restore the product. | |||
| 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. | |||
| One long LED flash followed by three short ones. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| If unit has mismatched software and firmware the unit can display an unusual sequence of LED lights. One long green ready followed by three short green ready lights. This is accompanied with no serial or ethernet communications. Hyperterminal communica | |||
| Dynamic scale function in the Scale Softsensor does not work. | |||
| Version Effected: 1.4 Framework SR2 | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| When clicking on the dynamic function of the scale softsensor, the softsensor result status changes to fail and the scale calculations do not work. | |||
| 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. | |||
| Scanning for 1-D barcodes does not appear to mark or work. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 Beta 6 FrameWork | Status: Verified Fixed | |
| The spacing is currently set at the scacing number minus one. Therefore, you must have at least a 2 pixel spacing for it to scan. This will be corrected in future versions. | |||
| System crashes on power-up when using a response function in datalink. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| If you save a product to flash with a response function, the smartimage sensor could crash on power up. This problem has been fixed in FrameWork Service Release 1.4 SR1a. | |||
| Min Contrast setting for blob generator softsensor appears to switch. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1 | Status: Verified Fixed | |
| When the mininum contrast value is set, the value moves to the warn condition. | |||
| UPC barcode reader reads code but fails inspection in results table. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| There was a check sum error in the UPC code algorithm with effected codes which ended in the number 0. The code would be read but would fail inspections. This has been fixed in Service Release 1a. | |||
| Long 1-D Barcodes can cause Series 600 to crash. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| There was a limitation of the number of edge crossing that could be handled in FrameWork 1.4 for 1-D barcodes. An overflow in the code would occur and the system would crash. This could potentially occur if percent of path contrast threshold is used for | |||
| Scale factor cannot reference the script softsensor's distance. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 2.4 FrameWork Beta 17 | Status: Fixed | |
| Some measurement and math softsensors cannot be used as a reference for a scale softsensor, even though they appear in the reference softsensor drop down list. | |||
| 1-D barcodes sometime pass with a blank image. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: | Status: Fixed | |
| Some 1-D barcodes seem to pass when there is a blank background. | |||
| 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. | |||
| The warn and pass conditions for blob generator softsensor is checked and set to zero. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 1.4 FrameWork SR1a | Status: Verified Fixed | |
| When restoring a product with a blob generator softsensor from the PC, the warn or pass conditions way be checked and set to zero if either is initially set. (ie, if only the pass condition is checked and set to 10, when you restore the product from the | |||
| Access Correct Password can change with certain characters | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 2.4 Beta 6 FrameWork | Status: Verified Fixed | |
| The following characters cannot be used in the following password positions. Position 1: u, x. Position 2: y, Position 7: r, Position8: s, Position 9: p, Position: 10: q, position 11:v. These characters in these particular position are ignored by FrameWork on subsequent powerup. Therefore, the password in altered. | |||
| 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. | |||
Resolved Issues | |||
| 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 | ||
| The necessary fwk.cnt file is not installed when you run the FrameWork 1.3 installation program. | |||
| Advanced Measurement softsensor parameters can cause SmartImage sensor to intermittently crash. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 1.4 FrameWork | ||
| 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. | |||
| 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 | |||
