Release Notes on BPWin Software
Latest Release/Date:
BPWin 7.0.8 Release Notes
BPWin Highlights Added support for the 3000 series fiber laser peripheral on the 3000 series automated programming systems. The fiber laser is capable of marking machine-readable QR codes and barcodes as well as alpha-numeric characters as small as 0.25mm in height....
BPWin 6.2.7
BPM 3000/4000 Series Autohandler
Added vacuum diagnostic for machines with Whisperteach
Incorporated Z home sequence after failing auto Z teach.
Added 3D vision inspection permission to WABS
BPWin 6.2.6
BPM 3000/4000 Series Autohandler
Added WhisperTeach™ functionality for 4x enabled APS
Improved BPWin launch time by opening inspection software only when it is part of the Workflow.
Resolved crash observed after running two consecutive jobs and removing a peripheral from the workflow in between both sessions.
Added instructions for the user at Pick-and-Place Position Tool Dialog.
BPWin 6.2.5
BPM 3000/4000 Series Autohandler
Corrected an issue where motion controller code would not properly download on legacy machines.
Corrected an issue where connection to UltraVim fails during Scanner Tech Vision inspection teach initialization.
Improved Scanner Tech inspection process by leveraging signals from UltraVim software.
BPWin 6.2.4
BPM 3000/4000 Series Autohandler
Corrected a problem when the site is disabled but the stepper motor will not raise when the user clicks the “close sockets”
Corrected an issue where the machine would not initialize with LPLA Cyberoptics camera
Improvements to Inc120 Cyberoptics usage.
BPWin 6.2.3
BPM 3000/4000 Series Autohandler
Fixed issue with package dimension validation in the package teach.
Device Programming
Legacy Software Release Notes
BPWin Software Legacy Release Notes, starting with BPWin 6.2.1 | Wednesday, September 27, 2017
7.0.4 Release Notes
Highlights
- Added a Z self-test motion diagnostic for 4x systems equipped with a Z encoder. This includes some 4900 and all 4910 autohandler systems. This diagnostic executes a sequence of tests to find possible failures and provides recommended actions. Access the Z self-test in the BPWin Motion Diagnostics accessible through the Autohandler menu: Autohandler->Pick-and-Place->Diagnostics. For example, here is a screenshot of the Motion Diagnostics Report where the Z-axis encoder is not connected to the headboard:
- Improved use of the theta encoder during axis motion to correct failed attempts to arrive at the commanded destination. Added useful debugging log information to help operators pinpoint any hardware faults. In the case of consistent theta failures, the theta speed will decrease incrementally to keep the machine running. This enables operators to finish the current job and address any hardware failures afterward.
Other Updates
- Added logging information to include the list of selected operations when loading Job Master (.bp) and Automated Job Master (.abp) files.
- Upgraded the onboard 64GB eMMC memory sticks used in 8th Generation programmers. Customers with 8th Generation programmers that have memory sticks of 32GB can upgrade to this 64GB memory stick. Contact customer support for details. This is part of BPM’s commitment to supporting legacy programmer models in the field.
- Implemented registry key for administrators to control access to the maximum laser power limit configuration. For further information contact Customer Service.
7.0.3 Release Notes
Updates
- Corrected device placement orientation when automatically removing devices from sockets after sites are taught in sequence. This only occurred when teaching with the options “Full Teach Primary / Fast Teach Secondary”, “Full Teach Every Socket”, or “Fast Validate and Adjust”. This behavior was only present in autohandler systems that use the CyberOptics alignment sensor.
- Resolved errors when running BPWin in APS simulation mode.
- Corrected an undesired change in behavior when teaching automated programmer sites in sequence. The correct behavior is to iterate through them in numerical order. Behavior had changed in BPWin 7.0.1 such that the master site was taught first and then the remaining.
- Improved debugging information given to the operator if:
- The Z encoder test fails during APS initialization.
- The SD cards present in the programmer site mismatch expected serial numbers.
- Resolved a problem where a JobMaster file could not be saved when Custom37 Bad Block Management scheme was selected.
Device Support Update
| Device Name | Programmer | Criticality | Changes Made & Reasons | Socket Module |
| Macronix MX66U51235FXDI-10G | 2800/3800/3800-MK2/4800 | Critical | The algorithm has been updated to resolve reading and verifying issues. | FVE4ASM24BGB, FVE4ASMC24BGJ |
| Atmel ATSAMD20J18A-AU | 2610/3610/4610 | Recommended | Algorithm has been updated to support all non-reserved bits in the user row. | ASMR64TQFP |
7.0.2 Release Notes
Highlights
- Improved the BPWin API to provide users the option to allow BPWin to show message boxes that require operator intervention. By default, the API is aimed to run BPWin unassisted, but this new feature helps users who plan to interact with it in order to resolve arising issues during operation. This feature can be enabled via registry key “ForceToPopupMessageUsingAPI” in the path “BP Microsystems\BPWin\Configuration”.
- Improved RPI format data parser to support listing optional configurations with no right value assignment. RPI is a format specific to Renesas devices.
- Improved software by allowing users to customize the maximum runout threshold for Autohandler Systems. This customization can be done via the registry keys “UpperRunoutRange_mils” and “LowerRunoutRange_mils” in the path “BP Microsystems\BPWin\AutoHandler\Components\Pnp\NozzleRunout”.
- Updated continuity check to improve performance with low voltage devices on all site generations.
Other Updates
- Fixed an issue on the 3X autohandlers where the laser diagnostics dialog would allow the laser door, elevator, and nozzles to move while the door was open.
- Fixed an issue happening after placing a device that sticks to the tip of the nozzle for a few milliseconds. In that event, the device was being grabbed again during upward motion due to incorrectly turning the vacuum on too soon. This issue was only affecting 3X autohandler systems with the LNC-120 Cyber Camera.