Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 2.4 Version: 2.4.6 FrameWork Release | |||
| Release Date: Dec 13 2002 12:00AM | |||
New Features | |||
| Emulator Support for Color and HiRes Images | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| The emulator now supports the different image formats that will be used in the Legend Series. The emulator now supports 640x480 color, 1280x1024 grayscale and 1280x1024 color images. To utilize the different imaging formats choose the proper emulator system. | |||
| Faster image updating in the Sampled Image Display | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| The Sampled Image Display (SID) utilizes pixel interpolation for faster image updating. This produces a 2-3 times faster image update. This feature can be turned off using an ini setting. | |||
| FOV Balancing function for non-uniform lighting | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| A new image pre-processing function has been added which compensates for non-uniform lighting. This function is present in the image parameters dialog. To utilize it, perform the FOV balancing on a white sheet of paper. It will remember the relative intensities and it will adjust everything in the ROI to the highest pixel value. It will then use this for subsequent images. | |||
| Ethernet Terminal Controller added | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| A Ethernet Terminal Controller was added to the I/O menu. This allows the user to setup different Ethernet configurations for communications via Ethernet with different devices. The use can set the system up as either a TCPIP server or client. They can also set the Ethernet port to communicate on and the type of communications driver to use on the port. | |||
| EthernetIP Communications Driver | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| The EthernetIP communications protocol has been added to FrameWork. This is a new open Ethernet protocol used by Allen Bradley and Rockwell Automation. See attached document for details. | |||
| added Digital I/O Control Functions in Script. | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| Functions were added to the Background script to allow for better control of the background script. The two event trigger functions that were added were WaitOnInput and WaitOnAnyInputInGroup | |||
| Added an Image object for the Background Script. | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| An image object was added to the background script which allows control of image acquisition functions and methods associated with images. These would allow for the image preprocessing and image reinspecting with different products. The methods associated with the image object are Image, Acquire, Inspect and Save. The fields associated with the image object are ID, Handle, ExposureTime, AntiBloomingEnabled, IlluminationEnabled, AntiBloomingLevel, RCPW, CCDHead, Gain, DigitizationRate, X0,X1,Y0, and Y1. Preprocessing include threshold, negate, map, erode, dilate, filter, subtract, and add. | |||
| New Communication Objects added to Background Script. | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| Communications Objects were added to the background script to allow for control of the serial, ethernet, and Modbus. These allow for better control of information and also provide the ability for individual to make their own custom communication drivers. | |||
| Template Matching improvements | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| Several new options are features were added to Template Match to make it most robust and faster. These include added thresholding methods, the ability to disregard both light and dark edge pixels, calculation of error in individual segment for increased sensitivity, and post-processing of the error pixels. In addition, the non-scanning template match softsensor runs about twice as fast. | |||
| Improvements in Barcode reading. | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| Gradient-based edge detection and subpixel edge measurements were added to the 1D barcode reader. In addition, the Start/Stop code detection and location for Code 128, UPC, Semi BC412 and PDF417 provide for reading even when the quiet zone is not present. | |||
| Barcode grading | |||
| Version Added: 2.4 FrameWork Beta 8 | |||
| Barcode grading for Code 128 and UPC has been added to the firmware using the ANSI X3.182-1990 (R1995) standard. The grading detects poor contrast, defects, bar width variations and improper barcodes. A very uniform light at 670 nm with a 2 in FOV should be used. Grading using the ISO/IEC 15416 2000 standard may be done at a later date. The grading of Interleaved 2 of 5, Code 39, Codabar and PDF 417 are also a possibility. | |||
| Color SoftSensor added to FrameWork | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| A new Color softsensor has been added to FrameWork. This allows for the monitoring of colors or shades of gray. It feedback either the most dominate color or how far you are from your ideal color. It can take into account highlighted areas caused by spectular reflection or overall changes in intensity know as a matte line. Learned colors can be referenced from other softsensors to provide specific color filter for increased contrast. | |||
| Segmentation SoftSensor added to FrameWork | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| The segmentation softsensor uses fuzzy logic to identify objects and patterns. It is primarily used with color systems but can also be valuable when using a greyscale system. Distinct segments in the field of view are identified automatically. They are subsequentially looked for in future images. The segmentation softsensor can be thought of as a hybrid between a blob, template, and objectfind softsensors. | |||
| Processing Domain tab added to all SoftSensors on a Color SmartImage sensor. | |||
| Version Added: 2.4 Beta 4 FrameWork | |||
| A Processing domain tab was added to all the softsensors which also for a different method of thresholding an image. It is equivilent to adding a dynamic color filter to the camera to produce a grayscale image which the softsensors can process. Using the Processing domain, you can choose red, blue or green, or you can import a color learned by a color softsensor. | |||
| Wrong Code Digital Output | |||
| Version Added: 2.4 FrameWork Beta 10 | |||
| A new output has been added to the system that works in conjunction with the 1D barcode sensors. The new output shows up in the Output Function list as 'Wrong Code'. The output will automatically be activated if a 1D Barcode sensor fails due to not matching the desired code. | |||
| New AutoDetect features | |||
| Version Added: 2.4 FrameWork Beta 11 | |||
| New features have been added to the 1D Barcode AutoDetect setting. They can be found in the Advanced dialog accessible from the Parameters tab. The three possible settings are 1) Set to Barcode Type upon read -- This is the same behavior as before where the barcode type is set to the first type successfully read. 2) Always stay in AutoDetect mode -- The sensor will always stay in AutoDetect mode even after a successful read. 3) AutoDetect upon Digital Relearn -- During normal operation the barcode type is set to the first successful type read. However, when a Digital Relearn input is encountered the barcode type is reset to AutoDetect. | |||
| Added comprehensive Shortcut keys to the new framework 2.4 beta 12 | |||
| Version Added: 2.4 FrameWork Beta 12 | |||
| Short keys Description Ctrl+Alt+B Opens background script dialog Ctrl+C Opens image sequence configure dialog Ctrl+Alt+D Opens DataLink Dialog Ctrl+Alt+E Opens Modbus Transfer Dialog Ctrl+Alt+M Opens Ethernet terminal transfer dialog Ctrl+Alt+O Opens Connection dialog Ctrl+Alt+P Opens product dialog Ctrl+S Starts RTF Ctrl+O Stops RTF Hot keys F5 Start RTF F4 Stops RTF F9 Opens IO Diagnostics/Paramters F11 Starts inspections F3 Mode for 1/4 resolution/full resolution image transfer The RTF can be started and stopped even when the focus is on a dialog. | |||
| Allow system level parameters to be loaded as groups and also ask for deleting modbus master, ethernet terminals and background scripts before loading. | |||
| Version Added: 2.4 FrameWork Beta 12 | |||
| Dialog box to allow system level parameters to be loaded as groups. The dialog has got check boxes to determine which system groups to load (Access State, IO , terminal Specs). Depending on whether there are modbus master, ethernet terminals or background scripts already running or present, the user has the options of deleting these and load the new list. | |||
| Button in Product parameters to save all products and Delete All products. Asks the user for confirmation. | |||
| Version Added: 2.4 FrameWork Beta 12 | |||
| Added buttons to Delete all products and Save All products. The user if prompted by a yes/no messagebox when these buttons are pressed. There is also a short cut key for storing all products(F10). | |||
| The Digital I/O parameters tab has been changed | |||
| Version Added: 2.4 FrameWork Beta 10 | |||
| The layout has been changed to use drop lists in a manner first introduced in the SmartReader. Inputs and Outputs are all listed in the same drop list indicated by a prefix. Digital I/O can no longer be configured as both an Input and an Output. | |||
| Intensity Softsensor now has an output for actual number of pixels counted. | |||
| Version Added: 2.4 Release FrameWork | |||
| Intensity Softsensor now has an output for actual number of pixels counted. The pixel count can be referenced from a script sensor using the "PixelCount" output. The total number of pixel examined by the softsensor is available using the "TotalPixelCount" output. | |||
| TotalPixelCount and PixelCount outputs added to Intensity tool. | |||
| Version Added: 2.4 Release FrameWork | |||
| TotalPixelCount and PixelCount outputs added to Intensity tool, and can be referenced by a script sensor. | |||
| Reflectance Calibration added to framework | |||
| Version Added: 2.5 FrameWork Beta 12 | |||
| With this new feature the camera is calibrated against a known standard. This normalizes (to the standard) the reflectance computed by the following softsensors: 1-D ANSI barcode grading, Color monitoring, Segmentation. With this feature, ANSI barcode grading reflectance values would be accurate. If calibration was performed on 2 color cameras with the same target, the two cameras would matched. You can learn a color in one camera with color monitoring and save the product then load it into the other. This feature does not affect Pixel Counting. | |||
Known Issues | |||
| Color Sensor does not recognize change in Position Referencs Selection. | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| If you change the selection of the Position Reference only, the system does not enable the apply button. | |||
| Color Sensor does not fail when the Sensor that it references fails. | |||
| Status: Fixed | Version Fixed: | ||
| When the position referenced sensor fails, the referencing Color Sensor will pass (no information is displayed in the results table, but the result says pass). | |||
| GetImageID() output incorrect values | |||
| Status: Verified Fixed | Version Fixed: 2.4.1 FrameWork Release | ||
| The GetImageID() script function outputs a -1 instead of the image ID. | |||
| Threshold incorrect shown in Gradient Graph when using an intensity threshold for Measurement | |||
| Status: Reproduced | Version Fixed: | ||
| When using an intensity threshold on a Measurement SoftSensor, the red threshold line is still displayed in the Gradient Graph. | |||
| Manual will not allow printing. | |||
| Status: Verified Fixed | Version Fixed: | ||
| The manuals included in the FrameWork 2.4 installation and SmartReader 1.2 installation files were originally configured with a password for printing. | |||
| Help Files not found. | |||
| Status: Verified Fixed | Version Fixed: 2.4 Release FrameWork | ||
| Using early versions of FrameWork 2.4 installation program, the line UseHtmlHelp=1 was not added to the FWK.ini file on Windows 98 and Windows 2000 systems. To get the help files to work, add the line UseHtmlHelp=1 in the [Settings] section of the fwk.ini file. (For SmartReader 1.2, add it to the smartreader.ini file) This is corrected in the current FrameWork 2.4 installation file on the downloads page. | |||
| Partial Image window script parameters incorrectly documented | |||
| Status: New | Version Fixed: | ||
| The window properties of a script image object is incorrectly documented in the script reference guide and help files for FrameWork 2.4. The documents state the window properties as X0,Y0, X1, Y1. They should state X1, Y1, X2, Y2. | |||
| Modbus Master is not support yet on the Series 540, 542C, 544 and 544C. | |||
| Status: Verified Fixed | Version Fixed: 2.4.1 FrameWork Release | ||
| The new high speed processor using in the 54x family of products requires additional code to be written to support Modbus Master transfers. Modbus Mastering is not affected on Series 500 and 600 systems for FrameWork 2.4. | |||
| RegisterWriteShort script function cannot be used to write to odd register values for 54x systems. | |||
| Status: Verified Fixed | Version Fixed: 2.4.1 FrameWork Release | ||
| The new higher speed processor used in the 540, 542C, 544, and 544C requires new code development to support Short data types writes to odd register values. DVT will address this in the Beta version. | |||
| charAt() command is not documented as it has been implemented. | |||
| Status: Reproduced | Version Fixed: | ||
| The documentation states that this function returns a character at a given position in a string. The function actually returns the ASCII number for the character. | |||
| Modbus Objects crash/lock up the camera. | |||
| Status: Reproduced | Version Fixed: | ||
| Using the Modbus Objects (MBtransfer and MBTransfer) in the background script will cause the system to lock up. This behavior was seen on 530 and 630 systems. | |||
| Anti-Blooming button grayed in Series 544. | |||
| Status: Verified As Designed | Version Fixed: | ||
| Anti-blooming is not supported in the Series 544. | |||
| Barcode SoftSensor locks system when no code present | |||
| Status: Fixed | Version Fixed: 2.5 FrameWork Beta 12 | ||
| The barcode softsensor seems to cause the system to crash when there is no contrast under the softsensor. | |||
| Referencing Segmentation softsensor does not work | |||
| Status: Fixed | Version Fixed: | ||
| The problem shows up when a positioning softsensor is used to position a segmentation sensor. The position of the found segments are not relative to the positioning softsensor and relative segmentation fails. Workaround: Use "Reference Segment" of the segmentation softsensor for positioning rather than another sensor. | |||
| Template Details always goes back to Medium detail | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| Switching the Template Detail in the advanced parameters does not change the value. It always goes back to the Medium Detail setting. | |||
| Enabling Matte Line on a Color causes zero colors to be detected | |||
| Status: Fixed | Version Fixed: | ||
| When enabling the matte line on a color softsensor, the color softsensor failed to find any colors. This is caused by file write protection on the computer. This does not happen for Windows 98 or if you are logged in as an administrator on your computer. | |||
| Socket Object doesn't allow connection to itself. | |||
| Status: Reproduced | Version Fixed: | ||
| The background socket object does not allow a client connection to itself. The following code was used. The code does work if connecting to a different system/IP address. Socket sock; int Result; Byte out[] = new byte[3]; Byte in[] = new byte[3]; out[1]=1; out[2]=2; out[3]=3; sock = Socket(); Result = sock.Connect("192.168.1.34", 5000); //Result = sock.Connect("192.168.1.34", 5003); //Result = sock.Connect("127.0.0.1", 5000); DebugPrint("Result1="+Result); Result = sock.Send(out); Result = sock.Recv(in); Result = sock.Close(); | |||
| SoftSensor Parameters available in Script are missing in help file | |||
| Status: Reproduced | Version Fixed: | ||
| The softsensors parameters that are available to a script softsensor are not shown in the tree view under scripting in the help files. | |||
| Socket Constructor for background script not documented in help file. | |||
| Status: Reproduced | Version Fixed: | ||
| The socket() constructor in not documented in the 2.4 help files. The Socket() function must be called before using the connect() function. ie Socket sock; sock=Socket(); Result=sock.Connect("192.168.1.34",5001); | |||
| Images missing in the DeviceNet Communications Help File | |||
| Status: Reproduced | Version Fixed: | ||
| Several of the image from the DeviceNet SmartLink manual are missing in the help files. | |||
| Reading noise with code 128 reader causes system to hang. | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| Reading noise with code 128 reader causes system to hang. You can still connect (telnet) to a system, but you are no longer able to run inspections. | |||
| Barcode reader does not fail with "Minimum Contrast" even if it is configured so if it is able to read the barcode. | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| Set the "Min contrast" pass condition to that above the image contrast. The sensor will pass if the barcode is readable. | |||
| Invalid memory access exception when writing a float or double to a DVT register on a 54X system. | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| Write a floating point number, preferrably a double, to an unaligned register address. | |||
| Ethernet to Serial Converter document refers to old software. | |||
| Status: In Progress | Version Fixed: | ||
| The Moxa Ethernet to Serial Converter document for part number CON-ET2 is written for an older version of NPort Express. It is written for Version 1.01 instead of 1.02 and some of the menus have changed. The Raw Mode setting is set in the OpMode menu instead of the serverConfig menu. | |||
| Documentation of Reserved Registers is incorrect | |||
| Status: Reproduced | Version Fixed: | ||
| The integration note Using DVT Registers to Monitor and Change the State of Virtual IO has two errors in the bit table. The DVT register numbers should be reversed. That is, 10 and 11 should be reversed. Also, The Template/Digital Relearn input should be in bit location 1 of Modbus register 4 where the Dis.Run mode is. | |||
| Setting Gateway causes SmartImage Sensor to disappear from Network Neighborhood | |||
| Status: Fixed | Version Fixed: 2.4.2 FrameWork Release | ||
| When an ethernet gateway is set for a SmartImage sensor, the sensor will not appear in the Network Neighborhood after cycling power on the SmartImage sensor. | |||
| DoubleToString is incorrectly documented in the online help file. | |||
| Status: Reproduced | Version Fixed: | ||
| DoubleToString should be listed as a global function instead of a method. The correct way to use it is: str = DoubleToString(num,dec); where str is the target string, num is the double or float to be converted, and dec is the number of places to the right of the decimal that should be displayed. | |||
| IP address from the ethernet address dialog is being incorrectly parsed. | |||
| Status: Fixed | Version Fixed: 2.5 FrameWork Beta 5 | ||
| IP address entered as 192.168.000.013 is being parsed as 192.168.0.11. | |||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. | |||
| Status: Fixed | Version Fixed: 2.4.3 FrameWork Release | ||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. The number displayed on the result table is negative and it doesn't change when the edge position changes. This was confirmed on a 540 system, but would not occur on the emulator. | |||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. | |||
| Status: Fixed | Version Fixed: 2.4.3 FrameWork Release | ||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. The number displayed on the result table is negative and it doesn't change when the edge position changes. This was confirmed on a 540 system, but would not occur on the emulator. | |||
| Blob Angle defaults to 90 degrees on a 544 emulator | |||
| Status: Fixed | Version Fixed: 2.4.3 FrameWork Release | ||
| When using a blob selector to compute the angle for a blob, the blob angle always outputs 90 degrees. This happens on a 544 emulator but not on a 540 emulator. | |||
| Blob Angle defaults to 90 degrees on a 544 emulator | |||
| Status: Fixed | Version Fixed: 2.4.3 FrameWork Release | ||
| When using a blob selector to compute the angle for a blob, the blob angle always outputs 90 degrees. This happens on a 544 emulator but not on a 540 emulator. | |||
| Leaving Script Debug window open when disconnecting from system can crash UI | |||
| Status: Fixed | Version Fixed: 2.4.5 FrameWork Release | ||
| Leave the script debug output window open and disconnect from camera (or emulator). Then try and close the dialog that is left open. UI crashes. | |||
| Using Percent of Reference Intensities do not allow you to reference two different softsensors. | |||
| Status: Verified Fixed | Version Fixed: 2.4.4 FrameWork Release | ||
| When using the percent of reference intensities as a thresholding method, only one softsensor can be referenced. If two softsensors are reference then the softsensor used in the high reference gets copied to the low reference. | |||
| Active checkbox does not deactivate the color pixel counting softsensor | |||
| Status: Verified As Designed | Version Fixed: | ||
| When the active checkbox on the general tab of a softsensor is unchecked, the softsensor should not be processed during the inspection. This behavior does not occur in the color softsensor. ---------------- The active checkbox works the same on all sensors. It just prevents the sensor failing result to fail the product. DVT | |||
| FrameWork 2.4.3 cannot load into a 530 System while FrameWork 2.4.2 is running | |||
| Status: Reproduced | Version Fixed: | ||
| FrameWork 2.4.3 (Service Release 3) cannot load on top of FrameWork 2.4.2. The firmware is loaded onto the camera but the Status light remains off and the Result light is illuminated green. The system will not show up in the NetWork neighborhood. This has only been verfied to occur in the Series 530 systems. To Load FrameWork 2.4.3 into these systems, first place the system in Diagnostics, change the IP address to a valid one and load the firmware. | |||
| Background script dialog too small, Close and Help Buttons are hidden. | |||
| Status: Fixed | Version Fixed: 2.5 FrameWork Beta 10 | ||
| When the background script dialog is open, there are scroll bars on the left side. You must scroll down to view the close and help buttons. | |||
| % below threshold reports a four-digit integer rather than a number in the range 0-100 | |||
| Status: Verified As Designed | Version Fixed: | ||
| Number reported by the % below threshold in an intensity SoftSensor is a four-digit integer instead of a number from 0 to 100 percent. The value returned is 0 to 100 scaled by 100 to have 2 decimal places of accuracy. DVT | |||
| DebugPrint not working well | |||
| Status: Fixed | Version Fixed: 2.4.4 FrameWork Release | ||
| When Fwk 2.4.3 is connected to a system (not emulator) the DebugPrint statement will print "NULL" unless consecutive DebugPrint statements are used, in that case, only the last statement prints "NULL" | |||
| Blob sensor crashes the camera when positioned exactly at the edge of the image. | |||
| Status: Fixed | Version Fixed: 2.4.4 FrameWork Release | ||
| Draw blob sensor exactly at the edge of the image. | |||
| FOV Balance not working on partial image captures | |||
| Status: Fixed | Version Fixed: 2.5 FrameWork Beta 5 | ||
| Framwork 2.4 does not support partial image captues. 2.4 Release 2+ prevents the camera from crashing but still does not perform the FOV Balance. 2.5 Does support partial image captures | |||
| Threshold in template match using reference intensities. | |||
| Status: Verified Fixed | Version Fixed: 2.4.4 FrameWork Release | ||
| When using reference intensities for computing threshold in the template match tool, reopening reference dialog results in high reference is selected both as low and high reference. If no change is made the tool though uses the initially selected low intensity reference and therefore the function of it is allright. ---------------------- This is not related to template match. Any sensor using reference intensity thresholding had this problem. It had been fixed in 2.4.4 DVT | |||
| Potential crash on partial window image captures | |||
| Status: Fixed | Version Fixed: 2.5 FrameWork Beta 13 | ||
| There is a potential for 542C, 544 and 544C cameras to crash when partial window image capture is used. | |||
| Inspect function in script gets called in play mode. | |||
| Status: Fixed | Version Fixed: | ||
| The Inspect function appears to be called by the system during the playback inspection, since the system continues to take inspections even after the running of inspections is disabled. | |||
| ObjectFind learns and marks the SoftSensor perimeter as part of the Object | |||
| Status: Reproduced | Version Fixed: | ||
| The ObjectFinds perimeter is treated as part of the object and its edges it found. | |||
| Color space Delta E cmc(l:c) ratio not set properly | |||
| Status: New | Version Fixed: 2.6 FrameWork Beta 2 | ||
| cmc(l:c) ratio was (0:0) it was changed to (2:1) | |||
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. | |||
| The script tool will not initially recognize itself when setting parameters associated with it. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| "Error executing Script" is generated in the complier results of the script Description: The script tool itself is not recognized in the script until you hit apply, since new new SoftSensors are only created when you hit apply or OK. However, once yo | |||
| 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. | |||
| Script Position and Angle Referencing | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | Status: Open | |
| Issue in both Code and Documentation: The PointX and PointY values do not work when used as outputs for position references in the Script SoftSensor. PositionX and PositionY work, but are no longer available in the dropdown parameters list. Additionally, the angle must be referenced as Position.ThetaX and Position.ThetaY in order to be referenced, and they are calculated as ThetaX = COS Angle *16384 and ThetaY = SIN Angle * 16384 where SIN Angle and COS Angle are in radians. | |||
| 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. | |||
| My laptop computer doesn't communicate with the SmartImage sensors when laptop is undocked. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| This can be cause by the computers power saving setting which may turn off the PCMCIA ethernet card when it is running off of the battery. Use winipcfg (win98) or ipconfig (win NT) to determine the true status of your card. | |||
| User Guide and Script manual do not open properly from the help menu. | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | Status: New | |
| When installing the FrameWork software from the Virtual Tour CD, the links to the FrameWork manual and the Script reference do not work properly. | |||
| Min and max intensity incorrectly in the blob softsensor when using fixed thresholding | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| Min and max intensity are always shown as 0 and 100 respectively when a fixed threshold is used in a blob generator softsensor. Also, the contrast is always at 100. | |||
| 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. | |||
| Script - Old syntax is used in the FWK help files. | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | Status: Reproduced | |
| When using the help files in FWK, the examples for Script are in the old syntax. | |||
| 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". | |||
| Scripts execute slowly with Win 95/98/ME | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | Status: Reproduced | |
| When running lengthly scripts in the Emulator woth Windows 95/95/ME operating systems the execution can take a very long time. | |||
| User Outputs and Script Outputs do not maintain state during Inspection | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: | Status: Reproduced | |
| When Maintain Output Result is checked and the User Outputs are defined, the respective output will go low during the inspection. Furthermore, the state of the output should not change at all, due to the inspection result staying the same. The User Outputs are all set low during the Product Inspection. | |||
| Cannot manipulate the PASS output through Script | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: | Status: Reproduced | |
| Cannot manipulate the PASS result output through Script. | |||
| Background script editing changes appear to not be saved | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 11 | Status: Open | |
| If a background script is running, the user is allowed to go into a script and edit it. However, upon exiting the script the changes are lost. | |||
| RegisterReadLong always returns a zero. | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| The RegisterReadLong function will return a zero even when the contents of the registers are non zero. RegisterWriteLong appears to work properly. | |||
| Color Sensor does not recognize change in Position Referencs Selection. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| If you change the selection of the Position Reference only, the system does not enable the apply button. | |||
| Color Sensor does not fail when the Sensor that it references fails. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Fixed | |
| When the position referenced sensor fails, the referencing Color Sensor will pass (no information is displayed in the results table, but the result says pass). | |||
| GetImageID() output incorrect values | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.1 FrameWork Release | Status: Verified Fixed | |
| The GetImageID() script function outputs a -1 instead of the image ID. | |||
| Threshold incorrect shown in Gradient Graph when using an intensity threshold for Measurement | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| When using an intensity threshold on a Measurement SoftSensor, the red threshold line is still displayed in the Gradient Graph. | |||
| Manual will not allow printing. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Verified Fixed | |
| The manuals included in the FrameWork 2.4 installation and SmartReader 1.2 installation files were originally configured with a password for printing. | |||
| Help Files not found. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4 Release FrameWork | Status: Verified Fixed | |
| Using early versions of FrameWork 2.4 installation program, the line UseHtmlHelp=1 was not added to the FWK.ini file on Windows 98 and Windows 2000 systems. To get the help files to work, add the line UseHtmlHelp=1 in the [Settings] section of the fwk.ini file. (For SmartReader 1.2, add it to the smartreader.ini file) This is corrected in the current FrameWork 2.4 installation file on the downloads page. | |||
| Partial Image window script parameters incorrectly documented | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: New | |
| The window properties of a script image object is incorrectly documented in the script reference guide and help files for FrameWork 2.4. The documents state the window properties as X0,Y0, X1, Y1. They should state X1, Y1, X2, Y2. | |||
| Modbus Master is not support yet on the Series 540, 542C, 544 and 544C. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.1 FrameWork Release | Status: Verified Fixed | |
| The new high speed processor using in the 54x family of products requires additional code to be written to support Modbus Master transfers. Modbus Mastering is not affected on Series 500 and 600 systems for FrameWork 2.4. | |||
| RegisterWriteShort script function cannot be used to write to odd register values for 54x systems. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.1 FrameWork Release | Status: Verified Fixed | |
| The new higher speed processor used in the 540, 542C, 544, and 544C requires new code development to support Short data types writes to odd register values. DVT will address this in the Beta version. | |||
| charAt() command is not documented as it has been implemented. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The documentation states that this function returns a character at a given position in a string. The function actually returns the ASCII number for the character. | |||
| Modbus Objects crash/lock up the camera. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| Using the Modbus Objects (MBtransfer and MBTransfer) in the background script will cause the system to lock up. This behavior was seen on 530 and 630 systems. | |||
| Anti-Blooming button grayed in Series 544. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| Anti-blooming is not supported in the Series 544. | |||
| Barcode SoftSensor locks system when no code present | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.5 FrameWork Beta 12 | Status: Fixed | |
| The barcode softsensor seems to cause the system to crash when there is no contrast under the softsensor. | |||
| Referencing Segmentation softsensor does not work | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Fixed | |
| The problem shows up when a positioning softsensor is used to position a segmentation sensor. The position of the found segments are not relative to the positioning softsensor and relative segmentation fails. Workaround: Use "Reference Segment" of the segmentation softsensor for positioning rather than another sensor. | |||
| Template Details always goes back to Medium detail | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| Switching the Template Detail in the advanced parameters does not change the value. It always goes back to the Medium Detail setting. | |||
| Enabling Matte Line on a Color causes zero colors to be detected | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Fixed | |
| When enabling the matte line on a color softsensor, the color softsensor failed to find any colors. This is caused by file write protection on the computer. This does not happen for Windows 98 or if you are logged in as an administrator on your computer. | |||
| Socket Object doesn't allow connection to itself. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The background socket object does not allow a client connection to itself. The following code was used. The code does work if connecting to a different system/IP address. Socket sock; int Result; Byte out[] = new byte[3]; Byte in[] = new byte[3]; out[1]=1; out[2]=2; out[3]=3; sock = Socket(); Result = sock.Connect("192.168.1.34", 5000); //Result = sock.Connect("192.168.1.34", 5003); //Result = sock.Connect("127.0.0.1", 5000); DebugPrint("Result1="+Result); Result = sock.Send(out); Result = sock.Recv(in); Result = sock.Close(); | |||
| SoftSensor Parameters available in Script are missing in help file | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The softsensors parameters that are available to a script softsensor are not shown in the tree view under scripting in the help files. | |||
| Socket Constructor for background script not documented in help file. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The socket() constructor in not documented in the 2.4 help files. The Socket() function must be called before using the connect() function. ie Socket sock; sock=Socket(); Result=sock.Connect("192.168.1.34",5001); | |||
| Images missing in the DeviceNet Communications Help File | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| Several of the image from the DeviceNet SmartLink manual are missing in the help files. | |||
| Reading noise with code 128 reader causes system to hang. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| Reading noise with code 128 reader causes system to hang. You can still connect (telnet) to a system, but you are no longer able to run inspections. | |||
| Barcode reader does not fail with "Minimum Contrast" even if it is configured so if it is able to read the barcode. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| Set the "Min contrast" pass condition to that above the image contrast. The sensor will pass if the barcode is readable. | |||
| Invalid memory access exception when writing a float or double to a DVT register on a 54X system. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| Write a floating point number, preferrably a double, to an unaligned register address. | |||
| Ethernet to Serial Converter document refers to old software. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: In Progress | |
| The Moxa Ethernet to Serial Converter document for part number CON-ET2 is written for an older version of NPort Express. It is written for Version 1.01 instead of 1.02 and some of the menus have changed. The Raw Mode setting is set in the OpMode menu instead of the serverConfig menu. | |||
| Documentation of Reserved Registers is incorrect | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The integration note Using DVT Registers to Monitor and Change the State of Virtual IO has two errors in the bit table. The DVT register numbers should be reversed. That is, 10 and 11 should be reversed. Also, The Template/Digital Relearn input should be in bit location 1 of Modbus register 4 where the Dis.Run mode is. | |||
| Setting Gateway causes SmartImage Sensor to disappear from Network Neighborhood | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | Status: Fixed | |
| When an ethernet gateway is set for a SmartImage sensor, the sensor will not appear in the Network Neighborhood after cycling power on the SmartImage sensor. | |||
| DoubleToString is incorrectly documented in the online help file. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| DoubleToString should be listed as a global function instead of a method. The correct way to use it is: str = DoubleToString(num,dec); where str is the target string, num is the double or float to be converted, and dec is the number of places to the right of the decimal that should be displayed. | |||
| IP address from the ethernet address dialog is being incorrectly parsed. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.5 FrameWork Beta 5 | Status: Fixed | |
| IP address entered as 192.168.000.013 is being parsed as 192.168.0.11. | |||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.3 FrameWork Release | Status: Fixed | |
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. The number displayed on the result table is negative and it doesn't change when the edge position changes. This was confirmed on a 540 system, but would not occur on the emulator. | |||
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.3 FrameWork Release | Status: Fixed | |
| Rotational Positioning Find Edge in Parallelogram does not provide the correct X offset. The number displayed on the result table is negative and it doesn't change when the edge position changes. This was confirmed on a 540 system, but would not occur on the emulator. | |||
| Blob Angle defaults to 90 degrees on a 544 emulator | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.3 FrameWork Release | Status: Fixed | |
| When using a blob selector to compute the angle for a blob, the blob angle always outputs 90 degrees. This happens on a 544 emulator but not on a 540 emulator. | |||
| Blob Angle defaults to 90 degrees on a 544 emulator | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.3 FrameWork Release | Status: Fixed | |
| When using a blob selector to compute the angle for a blob, the blob angle always outputs 90 degrees. This happens on a 544 emulator but not on a 540 emulator. | |||
| Leaving Script Debug window open when disconnecting from system can crash UI | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.5 FrameWork Release | Status: Fixed | |
| Leave the script debug output window open and disconnect from camera (or emulator). Then try and close the dialog that is left open. UI crashes. | |||
| Using Percent of Reference Intensities do not allow you to reference two different softsensors. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.4 FrameWork Release | Status: Verified Fixed | |
| When using the percent of reference intensities as a thresholding method, only one softsensor can be referenced. If two softsensors are reference then the softsensor used in the high reference gets copied to the low reference. | |||
| Active checkbox does not deactivate the color pixel counting softsensor | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| When the active checkbox on the general tab of a softsensor is unchecked, the softsensor should not be processed during the inspection. This behavior does not occur in the color softsensor. ---------------- The active checkbox works the same on all sensors. It just prevents the sensor failing result to fail the product. DVT | |||
| FrameWork 2.4.3 cannot load into a 530 System while FrameWork 2.4.2 is running | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| FrameWork 2.4.3 (Service Release 3) cannot load on top of FrameWork 2.4.2. The firmware is loaded onto the camera but the Status light remains off and the Result light is illuminated green. The system will not show up in the NetWork neighborhood. This has only been verfied to occur in the Series 530 systems. To Load FrameWork 2.4.3 into these systems, first place the system in Diagnostics, change the IP address to a valid one and load the firmware. | |||
| Background script dialog too small, Close and Help Buttons are hidden. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.5 FrameWork Beta 10 | Status: Fixed | |
| When the background script dialog is open, there are scroll bars on the left side. You must scroll down to view the close and help buttons. | |||
| % below threshold reports a four-digit integer rather than a number in the range 0-100 | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Verified As Designed | |
| Number reported by the % below threshold in an intensity SoftSensor is a four-digit integer instead of a number from 0 to 100 percent. The value returned is 0 to 100 scaled by 100 to have 2 decimal places of accuracy. DVT | |||
| DebugPrint not working well | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.4 FrameWork Release | Status: Fixed | |
| When Fwk 2.4.3 is connected to a system (not emulator) the DebugPrint statement will print "NULL" unless consecutive DebugPrint statements are used, in that case, only the last statement prints "NULL" | |||
| Blob sensor crashes the camera when positioned exactly at the edge of the image. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.4 FrameWork Release | Status: Fixed | |
| Draw blob sensor exactly at the edge of the image. | |||
| FOV Balance not working on partial image captures | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.5 FrameWork Beta 5 | Status: Fixed | |
| Framwork 2.4 does not support partial image captues. 2.4 Release 2+ prevents the camera from crashing but still does not perform the FOV Balance. 2.5 Does support partial image captures | |||
| Threshold in template match using reference intensities. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.4.4 FrameWork Release | Status: Verified Fixed | |
| When using reference intensities for computing threshold in the template match tool, reopening reference dialog results in high reference is selected both as low and high reference. If no change is made the tool though uses the initially selected low intensity reference and therefore the function of it is allright. ---------------------- This is not related to template match. Any sensor using reference intensity thresholding had this problem. It had been fixed in 2.4.4 DVT | |||
| Potential crash on partial window image captures | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.5 FrameWork Beta 13 | Status: Fixed | |
| There is a potential for 542C, 544 and 544C cameras to crash when partial window image capture is used. | |||
| Inspect function in script gets called in play mode. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Fixed | |
| The Inspect function appears to be called by the system during the playback inspection, since the system continues to take inspections even after the running of inspections is disabled. | |||
| ObjectFind learns and marks the SoftSensor perimeter as part of the Object | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | Status: Reproduced | |
| The ObjectFinds perimeter is treated as part of the object and its edges it found. | |||
| Color space Delta E cmc(l:c) ratio not set properly | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: 2.6 FrameWork Beta 2 | Status: New | |
| cmc(l:c) ratio was (0:0) it was changed to (2:1) | |||
Resolved Issues | |||
| Scale Softsensors lose their reference. | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 17 | ||
| When openning the scale factor softsensor parameters, the referenced softsensor is missing. | |||
| Scale factor cannot reference the script softsensor's distance. | |||
| Version Effected: 1.4 FrameWork SR1 | 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. | |||
| Access Correct Password can change with certain characters | |||
| Version Effected: 1.4 FrameWork SR1 | 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. | |||
| Product non-recognition of Results Graph Threshold Change | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: 2.4 Beta 6 FrameWork | ||
| If you have an Intensity SoftSensor in a Product that has been saved to flash, and you adjust the threshold limit on the graph in the Results Table, the store product Disk (i.e. FrameWork) does not recognoze that there has been a change made to the Product. | |||
| Image Streaking/Pixels Bleeding | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 14 | ||
| The image has pixels streaking through it and it is difficult to obtain a good image. The default gain set by the Emulator is 2.01, and any Product created in the Emulator and loaded into the SmartImage Sensor will have the gain set incorrectly. | |||
| distance measurement reports incorrect value | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 8 | ||
| Two Area Edge Line SoftSensors were used to determine the maximum points. The distance between the two SoftSensors was calculated with a Distance SoftSensor. This value does not match with a calculation of the distance in Script using the same points from the same Area Edge Line SoftSensors. Maximum point was selected in each Area Edge Line SoftSensors. | |||
| Editing Annulus Arc will crash user interface | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 13 | ||
| After creating an annulus arc shape right click to enter editing mode. The user interface will immediately crash due to an access violation. | |||
| 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 | ||
| 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. | |||
| Barcode match string check for code would fail on correct code string | |||
| Version Effected: 1.2A Release FrameWork | Version Fixed: 2.4.1 FrameWork Release | ||
| The output string from the barcode sensor contains extra space and '+' characters. | |||
| Digital Output Inverse Polarity is lost when power is cycled on Legend 530. | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4.1 FrameWork Release | ||
| Digital Output Inverse Polarity is lost when power is cycled on Legend 530. When reconnecting and checking the Output parameters, it still says the polarity in inverted, but it actually is not. | |||
| OCR Arc SoftSensor crashes system when upon drawing. | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4.2 FrameWork Release | ||
| The OCR Arc tool will crash upon creating the sensor when the scanning is performed from the inside out. | |||
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. | |||
| A Warning appears when trying to use digital IDs above 15 in the Product Management dialog. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: | ||
| You get a warning in the product management dialog when you selected a product ID above 16. However you can selected more than 16 products on a Series 600 if you reassign some of the I/O to be used for digital product selection. | |||
| 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 | |||
| Inspection time graph does not seem to update. | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: | ||
| The Inspection Time graph does not update and the statistical value remain constant or 0 even after multiple inspections. The inspection time graph only uses values from an actual inspection, if you are only playing images then the inspection time will not change. Make sure inspections are running. | |||
| Emulator Image Sequencing Confusion Point | |||
| Version Effected: 2.3 Beta 8 FrameWork | Version Fixed: | ||
| When using the Emulator, if you have selected an image sequence, and you then restore an image to the PC, when you then re-start RTF, the restored image will cycle in the SID, as opposed to the sequence selected in the Emulator. | |||
| Gain values appears to change by a couple of decimal places when first set | |||
| Version Effected: 2.4 FrameWork Beta 14 | Version Fixed: | ||
| The case where is was noted is with the Product Gain set to 4.00 and the System Gain set to 1.00. Upon closing and reopening the dialog the Product Gain value changed to 3.98. | |||
| Command #Sm | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | ||
| When using the #Sm command to change the match string it will change the match string of all "Readers" in the Product. It works well if you only have one Reader SoftSensor. | |||
| FrameWork script cannot convert type I from Z. | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | ||
| When assigning a value to a boolean parameter using a 0 or 1, (for example, compiling the line: img.AntiBloomingEnable=0;) the script debugger returns an error "cannot convert type I from Z". | |||
| Processing Domain for Color and Segmentation sensors removed by default | |||
| Version Effected: 2.4 Release FrameWork | Version Fixed: | ||
| The ini flag name for the Processing Domain pages were changed. Therefore, they now load as false by default and the pages do not show up. If you want to see the pages, go to Options, Softsensor, and enable them there. | |||
