Notes
We need to rename the repos, requirements repos. W2W repo should be renamed to bonding core.
Metrology computer is windows is talking to ACS, cameras, using TIEMachine library. We might run into speed issues, and we will adjust if that’s the case.
Need to define the API via TIEMachine
GetImage(camera1)
GetDisplacement()
tricky due to closed loop control
recordData() records data locally
uploadData() pushes to CSV
need to manage disk space with local data storage.
XWT: 2nd week of january we need to be able to control the pinlift
Open the application
Have a pinlift subsystem
Have a ACS subsystem
Manual control activity
Use stripped down version of MRAlpha to achieve this.
XWT: 1st big deadline - end of March we want to bond clear wafers
Topography sensors up/down facing mapping both wafers to find center.
We want to have part of the new architecture deployed by this deadline.
In TIEMachine we can update the logger class as a c++ library.
XWT/XOT: 2nd big deadline - end of June bonding real wafers on both XOT and XWT.
XWT: UI contractor engineer hire, REACT and REST
Web Server: NodeJS with shared memory access via c++ dll and possible gRPC to communicate to other machines
New Comms Susbsystem
For example each motioncontroller will get its own shared memory adapter.
What is in Bonding Core?
We have HW Subsystems
ACS Motion contorller
Zaber MC
IO MC
Logic Subsystems
Pinlift
Stage
Zhead
High level Subsystem (Orchestrators)
Motion
Ideally we have all this in c++, but we will keep sequences in matlab
State machines
Sequences
Processes
Activities
TIEMachine needs configuration management
Need a tool that is able to push the latest build to the other computers.
Add tasks for Pinlift long duration tests on the test bench.