Cognex Knowledge Base Search
KnowledgeBase Home |
|||
| Latest 2.3 Version: 2.3 Release FrameWork | |||
| Release Date: Jun 30 2001 12:00AM | |||
New Features | |||
| Added support for BC412 barcodes | |||
| Version Added: 2.3 Beta 1 FrameWork | |||
| Support was add to FrameWork and SmartReader to read BC412 1-D barcodes. This functionality is in FrameWork 2.3 Beta 1 and SmartReader 1.1 Beta 1. Two variations are supported: the SEMI specified variety and the IBM variety. | |||
| PDF417 Barcode Reading added. | |||
| Version Added: 2.3 Beta 2 FrameWork | |||
| A PDF-417 reader was added as a reader in the 1D reader softsensors. PDF417 is a stacked barcode which contained a large amount of data. Since it is a dense code if is important to zoom in on the code to achieve the proper resolution. The smallest areas should be no less than 3-4 pixels wide. Truncated PDF417, Macro PDF417, and codes with Byte Compaction are not currently supported. | |||
| New Features added to OCR Tool | |||
| Version Added: 2.3 Beta 2 FrameWork | |||
| The following new features have been added to the OCR softsensors. 1) searching on the first character or all characters, 2) reporting the matching score for each character(available in Script, Datalink and in a new table graph), 3) setting to not use aspect ratio independence (useful for searching), 4) setting to use high resolution mode (useful for some difficult to read and large characters), 4) Pattern Naming an ocr string (only one object must be present at the time of learning), 5) setting to limit the number of characters (useful for searching). | |||
| Added Modbus Master Timeout control | |||
| Version Added: 2.3. Beta 3 FrameWork | |||
| Added a control to the modbus master for controlling the timeout and polling rate when a slave it is trying to communicate with cannot be found. The defaults are 3 seconds for a timeout and 100 ms for a polling rate. These controls also help prevent problems that may occur if there is communication problems between a master and a slave over modbus. | |||
| Added Warn and Fail conditions to OCR for Character Scores | |||
| Version Added: 2.3 Beta 4 FrameWork | |||
| Added Warn and Fail conditions to OCR for the Minimum Character Scores. | |||
| Added Arrow to 1D Readers. | |||
| Version Added: 2.3 Beta 4 FrameWork | |||
| An arrow was added to the 1D reader to show the direction of scan. | |||
| Merged FrameWork 2.2 Release changes with FrameWork 2.3 Beta 7. | |||
| Version Added: 2.3 Beta 7 FrameWork | |||
| Changes that were included in the FrameWork 2.2 release were transferred over to the Latest Beta version of FrameWork 2.3 Beta 7. These include some Modbus and Ethernet communications changes as well as others. | |||
| DebugPrint function added to Script | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| The DebugPrint function allows you to sent data to a debug window for information feedback without having to use Datalink strings. The Debug information can be accessed through a terminal (#J+ / #J-) or via the user interface. | |||
| Added GetImageID function to Script | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| The GetImageID() function was added to Script which allows you to get the ImageID of the current inspection. This can potentially be used in combination with the activeX control to synchronize images with data. | |||
| Multi Dimensional Array and reference array support added to Script. | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| Support for multi dimensional arrays of primitives and objects were added to script and support for arrays of references (i.e. Strings, Sensors, Products or other objects.) | |||
| Network Browsing support added to FrameWork | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| Network Neighborhood was added to the PC Communications dialog. This searches the subnet for Series 500 systems and System currently running FrameWork 2.3 Beta 8 or greater. | |||
| OCR reading along an Arc | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| An annulus arc shape was added to the OCR SoftSensor. This allows for polar unwrapping of characters.The new shape is drawn in a different manner from the current arc type shapes. The process is 1) click and hold at the upper left hand side of the character string, 2) drag to the upper right corner of the character string, and release, 3) move mouse to define radius and click and hold, 4) drag to define the thickness of the arc and release. | |||
| New Output Parameter added to OCR SoftSensor | |||
| Version Added: 2.3 Beta 8 FrameWork | |||
| A new output parameter was added to the OCR SoftSensor which returns the distance from the character to the left edge of the SoftSensor ROI. This was added to facilitate measuring the relative positions of characters which could be helpful in script to added spaces to a string. | |||
| Reshape Capability added to OCR Annulus shape | |||
| Version Added: 2.3 Beta 9 FrameWork | |||
| Added reshaping capabilities to the annulus arc editing. There are several possible modes (enter reshape mode by right clicking when shape is being editing): 1) move entire shape by selecting inside and moving, 2) rotate the arc by selecting one of the endpoints along first arc. Rotates about the endpoint not selected keeping the arclength fixed. 3) while in mode (2) hold shift and the arc length will change without rotating. 4) selecting the handle along the middle of the first arcthe radius can be varied. 5) selecting either of the endpoints of the second arc the depth can be changed. | |||
| Advanced Strobing Capabilities added. | |||
| Version Added: 2.3 Beta 9 FrameWork | |||
| Advanced Strobing Capabilities added for the Series 500. The new features allow the integrated light to be kept on continuously and the control of multiple strobe outputs. | |||
| Support for setting image digitizing rate added. | |||
| Version Added: 2.3 Beta 9 FrameWork | |||
| Added support for setting the digitizing rate for each product. The digitization rates are 13 ms, 26 ms and 40 ms. Most non-precision measurement applications can use 13 ms. The default is 26 ms and 40 ms should be used for applications were measurements are critical. | |||
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". | |||
| distance measurement reports incorrect value | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.4 FrameWork Beta 8 | Status: Verified Fixed | |
| 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 | Status: Fixed | |
| After creating an annulus arc shape right click to enter editing mode. The user interface will immediately crash due to an access violation. | |||
| 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. | |||
| 2D Advanced Search crashes SmartImage Sensor | |||
| Version Effected: 2.3 Release FrameWork | Version Fixed: 2.2 Beta 10 FrameWork | Status: Fixed | |
| When the intersection of two candidate lines was calculated to be outside the SoftSensor Bounding Box the firmware would crash and the SmartImage Sensor would lock up. | |||
| 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. | |||
| 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 | Status: Fixed | |
| 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 | Status: Fixed | |
| The OCR Arc tool will crash upon creating the sensor when the scanning is performed from the inside out. | |||
Resolved Issues | |||
| Script Editor window sometimes disappears. | |||
| Version Effected: 2.1.1 Release FrameWork | Version Fixed: 2.3 Beta 8 FrameWork | ||
| Sometimes the position of the edit window for script was not stored to the FWK ini file correctly. | |||
| 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 | ||
| Fixed support for the IVal[] and DVal script parameters in datalink. These parameters did not show up datalink previously. | |||
| Definition of an Array variable not accepted by Script Compiler | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: 2.3 Beta 2 FrameWork | ||
| The script compiler would give an error when compiling an array variable declaration with the initialization when the bracket [] where placed next to the base type instead of next to the variable name, ie. int[] x = new int[10]. | |||
| Loading SmartLink sensor could cause SmartSensor Crash. | |||
| Version Effected: 2.2 Release FrameWork | Version Fixed: 2.3 Beta 7 FrameWork | ||
| Loading a Product File with a SmartLink SoftSensor could cause the SmartSensor to crash if a string argument is NULL. Would only occur if the SmartLink SoftSensor mistakely was saved without correct string informatin. Caused by String Format function not handling a null argument correctly. | |||
| 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 | ||
| 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. | |||
| Some data from dialog not transferred when OK is selected. | |||
| Version Effected: 2.0.1 Release FrameWork | Version Fixed: 2.3 Beta 10 FrameWork | ||
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. | |||
