Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 2.1 Version: 2.1.1 Release FrameWork | |||
| Release Date: Sep 06 2000 12:00AM | |||
New Features | |||
| Background Script Enhancements | |||
| Version Added: 2.1 Release FrameWork | |||
| Implemented in the FrameWork 2.1 is an OCR SoftSensor. The OCR reader is fully trainable and can even read symbols. Please refer to the Reader SoftSensor section for detailed information on the OCR SoftSensor. | |||
| ObjectFind SoftSensor | |||
| Version Added: 2.1 Release FrameWork | |||
| Functions have been added to the Script SoftSensor to allow the monitoring and setting of I/O from a background script. In addition, functions and methods associated with Products have been added. These functions can be found in the DVT Script Reference Manual and the help files. | |||
| Modbus Master Communications Driver | |||
| Version Added: 2.1 Release FrameWork | |||
| The Modbus Master allows multiple SmartImages Sensors to communicate and share information with each other. It also allows communications between other Modbus devices. | |||
| Changed default Ethernet rate to support a larger number of PC Cards | |||
| Version Added: 2.1.1 Release FrameWork | |||
| The Ethernet transmission rate was changed so the older Laptop Ethernet cards would perform better with the larger amount of data DVT sends out. For best performance on a Laptop computer an Ethernet card with Cardbus technology should be used. | |||
Known Issues | |||
| Direction of scanning fixed for some precision measure shapes | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| Direction of scan for some measurement softsensors was didsplayed wrong in the userinterface. However, scanning was correct for actual inspection. | |||
| DataLink will display results over ethernet when inspections are not running | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| Datalink results were output over ethernet when the system is play mode but not running inspections. The system should only output datalink results after each run mode inspection. | |||
| OCR SoftSensor could cause the system to crash if the SoftSensor moves off the image. | |||
| Status: Verified Fixed | Version Fixed: 2.1.1 Release FrameWork | ||
| The OCR SoftSensor could cause the SmartImage sensor to crash it is referencing another SoftSensor for position and that SoftSensor causes the OCR SoftSensor to move off the image. | |||
| Problems sometimes decoding UPC, Codabar and USS-39. | |||
| Status: Verified Fixed | Version Fixed: 2.2 Beta 7 FrameWork | ||
| UPC, Codabar and USS-39 1D barcodes sometime would not decode correctly. This was fixed in FrameWork 2.2 Beta 7. | |||
| SmartLink SoftSensor could cause UserInterface to crash. | |||
| Status: Verified Fixed | Version Fixed: 2.2 Beta 10 FrameWork | ||
| Added a check in Parse() in the SmartLink sensor to check the validity of grid data row/column values before using them to access the grid data array. FrameWork 2.10 did not properly support saving SmartLink to product files leaving off the row/column values. Trying to load one of those files would cause the GUI to crash. | |||
| I get an error message:The SmartImage Sensor currently has too many active user interface connections. | |||
| Status: Verified Fixed | Version Fixed: 2.3 Beta 10 FrameWork | ||
| When using a SmartLink has connected to the Model 630, any attempt to open FrameWork and connect to the Model 630 is met with an error. Too many user connections. | |||
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. | |||
| Direction of scanning fixed for some precision measure shapes | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| Direction of scan for some measurement softsensors was didsplayed wrong in the userinterface. However, scanning was correct for actual inspection. | |||
| DataLink can cause system to crash | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 3 FrameWork | Status: Verified Fixed | |
| The system can crash and lose communications when manipulating Datalink through the user interface. Typically this issue occurs after the product containing the datalink string is saved to flash memory. | |||
| DataLink will display results over ethernet when inspections are not running | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| Datalink results were output over ethernet when the system is play mode but not running inspections. The system should only output datalink results after each run mode inspection. | |||
| OCR SoftSensor could cause the system to crash if the SoftSensor moves off the image. | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.1.1 Release FrameWork | Status: Verified Fixed | |
| The OCR SoftSensor could cause the SmartImage sensor to crash it is referencing another SoftSensor for position and that SoftSensor causes the OCR SoftSensor to move off the image. | |||
| Emulator does not work correctly with Windows ME or Windows XP. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 5 FrameWork | Status: Verified Fixed | |
| Typically the Emulator uses port 5000 of the the IP address 127.0.0.1. The IP address 127.0.0.1 is an internal IP address of a PC. This can cause problems with the new "Universal Plug and Play" option in Windows ME and Windows XP which autodetects on port 5000. To fix this problem, support was added to FrameWork and the Emulator to support communications on a different port. Add the lines: EmulatorSystemTerminalPort=5010 and EmulatorDataLinkPort=5011 to the [Ethernet] sections of both the FWK.ini and FWKEmulator.ini files. Or you can disable the Universal Plug and play option on Windows ME by going to the Add/Programs icon of the Control Panel and uncheck the "Universal Plug and Play" checkbox under the Windows setup tab. The same thing should be done with the SmartReader.ini and SmartReaderEmulator.ini files. | |||
| Opening the Datalink terminal window causes FrameWork to become unresponsive | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 4 FrameWork | Status: Verified Fixed | |
| When opening the Datalink terminal window in FrameWork the user interface could could a very long delay which makes the user interface unresponsive. | |||
| Threshold marker disappears when softsensor graphs are set to B&W mode | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 3 FrameWork | Status: Verified Fixed | |
| When histogram and pixel graphs are switched from the default color mode to the black and white mode, the threshold can appear to disappear. | |||
| Exception thrown on PC when OCR graphs are set to Black and White | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Verified Fixed | |
| Changing the color scheme of the OCR graph from color mode to black and white mode could cause the PC to throw an exception. | |||
| Setting threshold from the OCR graph could cause strange problems. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Verified Fixed | |
| The OCR histogram graph allowed the movement of the threshold even when the threshold type of the OCR softsensor was set to computed. Changing the threshold value via the OCR histogram graph when the threshold type was set to computed would result in some corrupted data and some strange results. | |||
| SoftSensors which shapes could not be undone. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Verified Fixed | |
| SoftSensors without shapes such as the math and script softsensors were not added to the undo buffer. Therefore, operations done to them could not be undone. | |||
| DataLink can cause PC to hang up | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Verified Fixed | |
| There was several issues associated with the DataLink user interface windows which could cause the PC to not respond. These were addressed in FrameWork 2.2. | |||
| Script Editor window sometimes disappears. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.3 Beta 8 FrameWork | Status: Verified Fixed | |
| Sometimes the position of the edit window for script was not stored to the FWK ini file correctly. | |||
| Selecting a graph for the SmartLink SoftSensor could hangup computer | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 1 FrameWork | Status: Verified Fixed | |
| Graphs which were unsupported for the SmartLink SoftSensor could be selected and subsequently cause the PC to hang. | |||
| Precision Measure Torus not position referencing properly. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 8 FrameWork | Status: Verified Fixed | |
| The FindCircle and the FindCircle Arc would not reference some positioning softsensors correctly. | |||
| Drawing Translational SoftSensor near edge of Image could cause crash. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 8 FrameWork | Status: Verified Fixed | |
| The system could crash when a Translational SoftSensor is drawn near the edge of the image. | |||
| Emulator Image update slow on Windows ME | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 8 FrameWork | Status: Verified Fixed | |
| Image updates on Windows ME could be slow when using the emulator. This has be fixed in FrameWork 2.2 Beta 8. | |||
| EAN8+8 and EAN8+5 1D barcodes not read. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 7 FrameWork | Status: Verified Fixed | |
| The UPC EAN8+2 and EAN8+5 barcodes could not be read. This was fixed in FrameWork 2.2 Beta 7. | |||
| Problems sometimes decoding UPC, Codabar and USS-39. | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.2 Beta 7 FrameWork | Status: Verified Fixed | |
| UPC, Codabar and USS-39 1D barcodes sometime would not decode correctly. This was fixed in FrameWork 2.2 Beta 7. | |||
| Emulator gives error when loading product file's serial parameters | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 7 FrameWork | Status: Verified Fixed | |
| When restoring a system product file to the emulator, the emulator would give an error stating that some parameters could not be transfered. The problem was do to the emulator handling the serial parameters sent to it. This was fixed in FrameWork 2.2 Beta 7. | |||
| Precision Measure Torus causes crash if it moves off image. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 7 FrameWork | Status: Verified Fixed | |
| The Precision Measurement Torus could cause system to crash if the torus moves off the image. Fixed in FrameWork 2.2 Beta 7. | |||
| Font List not copied when OCR SoftSensor was duplicated. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 6 FrameWork | Status: Verified Fixed | |
| When duplicating an OCR SoftSensors the font list was not copied to the new OCR SoftSensor. | |||
| Problems occurred when referencing a string in Datalink that was greater than 100 characters. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 5 FrameWork | Status: Verified Fixed | |
| Problems occurred when referencing a string in Datalink that was greater than 100 characters. This was fixed in FrameWork 2.2 Beta 5. It will now be the maximum of the length of the input string or that specified by the format statement. | |||
| System crash when OCR SoftSensor moved off image. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 3 FrameWork | Status: Verified Fixed | |
| If OCR softsensor moves off the image and graph data is requested the system could crash. Fixed in FrameWork 2.2 Beta 3. | |||
| System crash when using OCR and DVT thresholding | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Verified Fixed | |
| Marking of an OCR softsensor when it moved off the image would cause the system to crash. | |||
| Using GetProduct function could cause crash. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 2 FrameWork | Status: Fixed | |
| Using the GetProduct function in a script could cause a crash do to a memory leak. This was fixed in FrameWork 2.2 Beta 8. | |||
| GetExposure and GetGain Contain wrong sytnax in Script Manual | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| The line P= Product1; should read P=GetProduct("Product1"); | |||
| GetProductById() script function documented incorrectly in Script Manual | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| In the 2nd Edition of the Script manual, the script function GetProductById() is incorrectly labeled as GetProductByID(). That is, the D in Id should not be capitalized. | |||
| Binary Script Example is incorrect in the Script Reference Manual | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| There are several aspects to the binary script example in Chapter 5 of the Script Reference Manual. Outputs User1-User 6 should not be used since these outputs are automatically updated by FrameWork after each inspection thereby turning them off. Instead Output 19 - Ouput 24 should be used. These are designed for script functions. In addition, a new long variable should have been used for the NumFeatures parameter and the & (bitwise and) operator should have been a | (bitwise or) operator. | |||
| System Status Bit Example in Script Reference Guide is incorrect | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| The Setting a System Status Bit example in the 2nd Edition of the Script Reference manual incorrectly uses the User1 output as the status bit. Instead one of the Outputs dedicated for script should have been used like Output 24. | |||
| Several bit manipulation which set multiple bits are incorrect in script manual | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| On page 59 and 61 of the 2nd edition of the script reference manual the SetOutputs function is called in examples to set multiple bits at the same time. In these examples a | (bitwise or) operator should be used instead of an & (bitwise and) operator. | |||
| GetInspectProduct() script function not documented in script manual | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| The GetInsectProduct() function is not documented in the 2nd edition of the script reference manual. This function is used to return the current inspection product when setting a product variable. For example, Product prod; prod=GetInspectProduct(); This functions makes simplifies things when a product is duplicated. | |||
| Precision Measure graph always corresponds to the 3 o'clock position | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| The graph associated precision measure find circle and arc softsensor would always display the inspection at the 3 o'clock position. Even if the softsensor was rotated. This was corrected in FrameWork 2.2 Beta 10. | |||
| Profibus UserInputLength always set to zero in the Series 700. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| In series 700 systems with built in profibus, the profibus parameter UserInputLength would always be set to 0. | |||
| Scanning 1D barcode softsensor may not scan the in the originally drawn region. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| Changed the 1D barcode reader to always do a scan along the line drawn. Previously it would not do a scan where drawn if an even number of scans was specified. Now, in that case, an extra scan is done along the center line. This was done so that the threshold, contrast, min. intensity, and max. intensity reported to the GUI are from along the drawn line just as the graph already was. | |||
| Threshold for scanning 1-D softsensor may not be as expected. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| Fixed problem in 1D barcode reader where the threshold used for an inspection along a scan line is not always from calculations done along that same line. DLG | |||
| Template may cause a crash if the user double clicks rapidly. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| Fixed a crash that would occur in Template if the user rapidly double-clicks when drawing the sensor. It was an issue of not properly handling an error message returned by SURectangle() resulting in a member variable not being set before use. DLG | |||
| Flash icon does not change when the Datalink parameters are applied. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| Fixed a bug in DataLink where if a change is Apply'ed then Cancel is hit the save to flash icon does not change for the product. | |||
| SmartLink SoftSensor could cause UserInterface to crash. | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Verified Fixed | |
| Added a check in Parse() in the SmartLink sensor to check the validity of grid data row/column values before using them to access the grid data array. FrameWork 2.10 did not properly support saving SmartLink to product files leaving off the row/column values. Trying to load one of those files would cause the GUI to crash. | |||
| Fixed support for the IVal[] and DVal script parameters in datalink. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.3 Beta 1 FrameWork | Status: Verified Fixed | |
| Fixed support for the IVal[] and DVal script parameters in datalink. These parameters did not show up datalink previously. | |||
| 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. | |||
| 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. | |||
| I get an error message:The SmartImage Sensor currently has too many active user interface connections. | |||
| Version Effected: 2.1 Release FrameWork | Version Fixed: 2.3 Beta 10 FrameWork | Status: Verified Fixed | |
| When using a SmartLink has connected to the Model 630, any attempt to open FrameWork and connect to the Model 630 is met with an error. Too many user connections. | |||
| 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". | |||
Resolved Issues | |||
| When saving products to PC the Data Link strings are sometimes left out | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| When the product is saved to the PC the data link strings for some or all products are not saved. This has been traced to the UI not having successfully read the data when querying product parameters. | |||
| Changing to the datalink driver will switch to the driver and then not accept any commands or send any output. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| After changing to datalink, you could not change back to the system terminal driver to initiate FrameWork or System Terminal commands. This has been fixed. The *T- system command changes the datalink terminal back to the system terminal mode. You can then use the #Tb and #Tt command to permanently set the port to system terminal. This is all handled automatically by FrameWork now. | |||
| Terminal times out while connecting to a system with many products. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| After loading the attached *.dvt file to an 800 the FrameWork UI will not be able to reconnect. Everything works fine loading the product file but the problem appears after the UI has disconnected from the system and tries to reconnect. | |||
| Very long input strings in the Datalink strings tab will cause the computer to lockup and proper values will not be output. | |||
| Version Effected: 1.4 FrameWork SR1 | Version Fixed: 2.1.1 Release FrameWork | ||
| If an input string has been entered that results in a string being sent to the firmware that is longer than 200 char the user interface will lockup the next time the datalink box is opened. | |||
| Invalid Param shows up in the sample display for datalink and Invalid Format shows up in the terminal window. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1 Release FrameWork | ||
| The gradient threshold for datalink has not been implemented in FrameWork 1.3. | |||
| Invalid Parameter shows up in the terminal window for datalink. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| The scale factor should not be shown as a valid parameter under individual measurement softsensors. | |||
| The intensity parameter setting shifts by a fractional amount when the apply or ok buttons are pressed. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| The intensity parameters are rounded incorrectly when they are sent to the processor. Therefore, each time the apply button or the ok button is pressed in the blob softsensor, the parameters change by a fractional amount. | |||
| F8 does not bring up the histogram graph for a blob generator softsensor. | |||
| Version Effected: 1.3 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| When you have the blob generator selected F8 brings up the Pass/Warn/Fail graph instead of the histogram graph. | |||
| Memory allocation seen as failure cause for a Measure Across Area softsensor. | |||
| Version Effected: 1.4 FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| The Measure Across Area softsensor returns an incorrect failure code when no edges are found. It returns a Memory Allocation Error instead of a No Edges Found result. | |||
| Datalink values continue to be transmitted via Ethernet when inspection are off. | |||
| Version Effected: 1.4 FrameWork SR1a | Version Fixed: 2.1.1 Release FrameWork | ||
| If you are using datalink across ethernet, the values will continue to be sent if you have play mode on but running of inspection off. This is not the case if you are sending values over the serial port. | |||
| Blob Softsensor changes preprocessing values when restoring product from the PC. | |||
| Version Effected: 1.4 FrameWork SR1a | Version Fixed: 2.1.1 Release FrameWork | ||
| The size for step of preprocessing is incorrectly read in as 10 when restoring a blob generator softsensor from the PC. You must manually edit the step 2 preprocessing size value when you restore the product. | |||
| Dynamic scale function in the Scale Softsensor does not work. | |||
| Version Effected: 1.4 Framework SR2 | Version Fixed: 2.1.1 Release FrameWork | ||
| When clicking on the dynamic function of the scale softsensor, the softsensor result status changes to fail and the scale calculations do not work. | |||
| Blob Selector stops reporting blobs | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.1.1 Release FrameWork | ||
| After creating a Blob Generator and Selector, if the Generator SoftSensor is moved on the SID, applied to the new position, and then the Undo button is checked, the Selector will no longer report any Blobs being found. | |||
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 | |||
