Cognex Knowledge Base Search

KnowledgeBase Home
Latest 2.6 Version: 2.6.4 FrameWork Release
Release Date: Dec 23 2003 12:00AM

Known Issues

Other

FrameWork UI looses communication when long output pulse widths are used.
Version Effected: 1.3 FrameWork Version Fixed: Status: Reproduced
A dialog box is displayed that states "Communications has been lost with the SmartImage sensor, would you like to disable communications". The status/ready LED light is constantly off. This is typically caused by having an output pulse width larger than your time between triggers.
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.
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.
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.
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.
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.
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.
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.
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.
% 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
ObjectFind advanced perimeter checking does not work.
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
Using the advanced perimeter check in ObjectFind does not change the results of an objectfind inspection.
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.
FWKEmulator crashes when manipulating some of the ObjectFind parameters
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
The Emulator crashed when modifying an ObjectFind shape and also when changing the ObjectFind Parameter to use advanced perimeter checking.
Gradient Graph still shows threshold when using intensity theshold in measurement softsensors.
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
When an intensity threshold is use with a measurement softsensor, the red intensity threshold line is drawn on the gradient graph as the default graph. This can be miss leading when altering the threshold.
Advanced Measurement parameters not disabled on intensity threshold
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
Some of the advanced measurement parameters should be disabled when an intensity threshold is used for a measurement softsensor. These include all of the line scan parameters.
Ethernet Terminal Controller stays connected when the process is stopped in the dialog
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
When an Ethernet Terminal controller is setup as Datalink it continues to send data even after the process is explicitly stopped.
ObjectFind does not distinguish between inner and outer edges.
Version Effected: 2.5.0 FrameWork Release Version Fixed: Status: Reproduced
ObjectFind does not distinguish between inner and outer edges.
DVT System files reverse the order of the products when backing up and restoring.
Version Effected: 2.5.1 FrameWork Release Version Fixed: Status: Reproduced
When backing up and restoring a dvt system, the internal product IDs will be reverse. This should only affect individuals using scripts and the active X control.
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)
Image Marking incorrect for measure across line softsensor when using intensity thresholding
Version Effected: 2.5.6 FrameWork Release Version Fixed: Status: Reproduced
When using a measure across line softsensor with an intensity threshold and intensity marking enabled, the entire area defined by the two points is marked instead of the line.
FrameWork does not warn that IP address is already in use.
Version Effected: 2.5.6 FrameWork Release Version Fixed: Status: Reproduced
A message box exists stating that the IP address you are trying to select is already in use in the network, however, this message is not being displayed when setting an incorrect IP address.
Terminal command to save all products #PFS alway saves all products
Version Effected: 2.5.7 FrameWork Release Version Fixed: Status: Reproduced
The #PFS should save only the products which have been changed, however, it saves all the products to flash.
Emulator does not stop when exitting FrameWork.
Version Effected: 2.5.8 FrameWork Release Version Fixed: Status: Reproduced
When exiting FrameWork asks if you would like to stop the emulator. Answering yes does not stop the emulator program.

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 changes Match String for all "Readers" in the Product.
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.