TIE Novel Products Software Team
Github: https://github.austin.utexas.edu/Texas-Institute-for-Electronics/MRAlphaController
Contributors:
@…
@…
@…
@…
11/18/2025: W2W
Summary
@… is testing MRAlpha codebase on the W2W machine. A lot has changed since our last test session with the additions of futures and sequences.
The findings from Jeff:
The Zaber error is a zaber library timeout error. That makes me think it's very likely serial port delays/etc stuff going on. I think it's highly likely switching to Ethernet will solve those issues.
It appears that the ACSProgramController still has synchronous waits in its futures code, which might cause many problems. I thought I got that checked in but must not have; I'll look into that this afternoon.
It looks like Josh made a great correction to the axis position error - good find! Those bubbled up errors on reading futures can be tricky to track down.
11/24/2025: W2W
@…
Summary
Zaber performance is blocking further progress; current state is untenable.
Manual stage control and manual process control are too unresponsive to use.
Registration frequently fails when checking Zaber, while all other stages register correctly.
Current config has many subsystems disabled to isolate core functionality.
Multiple recurring errors encountered throughout the day (attachments referenced).
Josh is willing to give up their block tomorrow for someone else to investigate.
Logfiles |
|---|
11/25/2025: W2W
@…
Summary
Need updated safe positions for XYZ. Z safe position is 1.0 now.
Update SI-F1000 sensor conversion units to microns, not mm. And the units are off by a couple decimal points.
Things I needed to do to get mapping the wafer chuck (almost) working.
Use reed_cr branch.
Remove line 13 of BondingParametersEnum. Remove ZHeadDieLoadHeight from enum.
Change zheadSafePosition to -1.5 in System/+InterferenceChecks/+PrecisionStage/FR1589_ZHeadInSafePostionCheck.m
Simulate Zaber motion controller so polling timeouts dont block all progress.
Do not simulate zsensor_1, make it SiF1000 sensor.
Move everything to safe positions
Move XYT stage to 215, 45
Move ZHead to -1.4
Comment out all steps in Bond Wafer to Wafer sequence except mapmaterial step.
Files/Images/Errors | Notes |
|---|---|
921 microns == 92119mm - Need to change conversion in the code. Observe ZHead level without wafer loaded. This is mapping the chuck. Stepped zhead down until sensor could read measurements reliably. | |
25-Nov-2025 15:27:52.128 info: Preparing raster scan...
25-Nov-2025 15:28:08.391 error: Error using SubSystems.ZaberMotionController.ZaberMotionController/isAxisRegistered (line 212)
| When attempting to start the mapping of wafer chuck, motion errored out due to zaber connection failing. |
config | |
logs | |
github branch | https://github.austin.utexas.edu/Texas-Institute-for-Electronics/MRAlphaController/tree/reed_cr |
11/26/2025: W2W
@…
Summary
Zaber connection issues resolved by switching to ethernet and updating config along with System.m.
We don’t need to map the full wafer, just need a small surface area to generate plane.
Manual Process control UI is unreliable, need to fix crashes and weird UI resizing bug.
Update “safe positions” for precision stage. ZHead is good at 1. Also update ZHeadPreBond position to something close enough for the sensor to read measurements on the wafer.
Files/Images/Errors | Notes |
|---|---|
config used | |
https://github.austin.utexas.edu/Texas-Institute-for-Electronics/MRAlphaController/tree/reed_cr | |
ZHead chuck map | |
logs |
12/4/2025: W2W
@…
Summary
The app does take 20ish seconds to start up for the first time due to starting all of the threads.
The goal of today was to make the app reliable. It will not crash and responds to input in a timely manner.
It takes 1-3 seconds to switch from one activity to another.
# | Error | Notes |
|---|---|---|
1 |
| Zaber timed out at init, loaded manual process control, got these errors, could not switch out from manual process control and app hung for 5 min before crashing. |
2 | 04-Dec-2025 08:51:41.546 error: Error using SubSystems.ZaberMotionController.ZaberMotionController/initialize (line 345) | Zaber timing out on init. Will document troubleshooting steps.
|
3 | App is slowing to a crawl. Can barely get functionality. Opening manual process control took 1min from button press. |
|
4 | 04-Dec-2025 09:22:43.223 error: Display Stage Controls ERROR:
04-Dec-2025 09:22:43.944 error: Display Stage Controls ERROR:
04-Dec-2025 09:22:44.835 error: Display Stage Controls ERROR: | Display stage controls error blowing away the log with futures issues. This needs fixing. FIX: This happens when you open the activity wit hout having registered motion. I removed the logging of the error as we can just ignore this. |
5 | 04-Dec-2025 09:29:15.463 error: IR Moiré Measurement Main Activity ERROR:
| Similar stack trace to display stage controls error blowing away the log with futures issues. This needs fixing. FIX: This happens when you open the activity without having registered motion. I removed the logging of the error as we can just ignore this. |
6 |
| Not sure what this was about. Needs attention. |