Logs

---

Aug 11 - Aug 17 '25

• Moved ETL lpGBT configuration to csv to speed up testing while DB upgrade is under development
• MUX64 controller class development continued: MUX64 Testing Report
  • Correct raw ADC value is now being readout
  • Need to debug voltage translation
• Finalized proposal for how to update Database Schema: DB Proposal

Aug 04 - Aug 10 '25

• Created a test instance of the DB to test changes
  • Database instructions
• Tested first part of new uniform routes and agnostic code on BTL Tray
• Started fixing values in test instances of DB to match Tamalero config for ETL

Jul 28 - Aug 03 '25

• Investigated behavior of when the lpGBT links lock to Serenity: Locking Notes
• Started writing MUX64 controller class for the MUX64 chip on the ETL Readout Board
  • MUXUT ADC readout needs to be debugged
  • Mux64 branch code file in MTD DAQ Gitlab
• Started working on making existing MTD software code agnostic to ETL or BTL
• Started planning on how to make the DB format uniform for both ETL and BTL

Jul 21 - Jul 27 '25

• Ran KCU + Tamalero Test with only Master lpGBT link connected
  • Realized dirty fibers + incompatible fibers caused communication issues
• Cleaned fibers and created new optical fiber setup to Serenity
  • Can communicate fully with lpGBT on RB through Serenity now (downlink sending data correctly and receiving response on uplink)
  • Full report: New Setup Test

Jul 14 - Jul 20 '25

• Tried testing different links for uplink: Serenity uplink test
  • Still unable to lock onto or read any data from uplink
• Reviewed Hardware setup and learned more about optical fiber connections
  • VTRX+ Specs
  • BTL - CC Schematic
  • ETL - RBv3 Schematic
• Found when timeout error is sent
  • When EMP Throws SCCIC Timeout
  • Reviewed firmware and ipbb

Jul 07 - Jul 13 '25

• Ran fresh mtd sw on Serenity flashed with FEC12 Firmware, detailing all changes to software to establish communication with lpGBT 0x73 on link 4
  • Detailed report: Fresh lpGBT MTD Setup on Serenity
  • Encountered the same issues where timeout errors occurred even when trying to run lpgbt_main.py with correct lpGBT address and link
  • Slides summarizing status: Initial communication with lpGBT
• Downlink tests confirmed we can control LEDs connected to master lpGBT
• Ran Tamalero power-up configuration tests and can see master lpGBT ready light turn on rbv3 schematic

Jun 30 - Jul 06 '25

• Confirmed that you do not need to run any lpGBT setup/configuration with KCU105 to control GPIO pins
• Attempted low level C++ script to test controlling GPIOs with Serenity but saw timeout errors after very write as it attempted to do a subsequent read
• Attempted Python script to test controlling GPIOs with Serenity, script ran all the way through but nothing was seem on oscilloscope
• Successfully able to control GPIO pin on RB with Serenity
  • lpGBT Address 0x73; Link number 4; connections file
  • Set multiwrite to false (this allowed for the writes to actually be dispatched)
  • Write GPIO 8 direction to output by writing to then setting the value of the GPIO to low then high after 5 seconds
    • Each write needed to be wrapped around a try/catch block to force a write and catch timeout errors

Jun 23 - Jun 29 '25

• Presented slides summarizing difference in power up configuration before the first read. Slides: Power-up Config
• After consulting with Alex realized we were trying to debug at a too high level, instead focus on blind writes to control GPIO pins on lPGBT
  • Started repo and writing test scripts for debugging purposes: MTD ETL Tests
  • Set up oscilloscope setting up with KCU105 + Tamalero setup

Jun 16 - Jun 22 '25

• Notes on Tamalero lpgbt powerup sequence which detailed all the setup that is done before the first read happens with KCU105
• Started looking into detail how the MTD sw sets up lpgbt before first read happens with Serenity

Jun 09 - Jun 15 '25

• Debug docker image for tamalero until fully tested and working on mtddaq01 computer at TIF with (KCU105 and RBv3)
• Link installation/set up with Serenity finished
• Tried running MTD DAQ software with FEC5 and FEC12 versions of the firmware loaded onto the Serenity and could not get links to lock or any communication with the lpGBT (both with cassette fiber layout and individual link fiber layout)
• Started to look into the differences in power-up sequence and configuration of the lpGBT in MTD Software vs Tamalero

Jun 02 - Jun 08 '25

• Set-up test bench at TIF using mtddaq01 computer with Tamalero set-up (KCU105 and RBv3)
  • Dependency issues for Control-hub and uHAL on when trying to run Tamalero on TIF computer -> Started working on docker image for tamalero to run Tamalero+KCU105 set-up on any computer
• Waited for fiber link installation on Serenity