1 / 8

TRD Feeserver/controlEngine

TRD Feeserver/controlEngine. Kai Schweda, University of Heidelberg. R. Bramm, B. Doenigus, T. Dietel, D. Emschermann, M. Kessenbrock, T. Krawutschke, C. Lippmann, J. Mercado, M. Neher, K. Oyama, B. Schockert, J. Steckert, G. Tsiledakis. J. Mercado, G. Tsiledakis. PVVS-Inject. FED Server.

taran
Download Presentation

TRD Feeserver/controlEngine

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TRD Feeserver/controlEngine Kai Schweda, University of Heidelberg R. Bramm, B. Doenigus, T. Dietel, D. Emschermann, M. Kessenbrock, T. Krawutschke, C. Lippmann,J. Mercado, M. Neher, K. Oyama, B. Schockert, J. Steckert, G. Tsiledakis

  2. J. Mercado, G. Tsiledakis PVVS-Inject FED Server B. Schockert M. Kessenbrock, K. Oyama T. Dietel, R. Bramm InterCom Layer FEE Client V. AngelovT. KrawutschkeC. LippmannJ. MercadoK. OyamaK.S. FEE Server FEE Server FEE Chain (3 Layers) PVSS (DIM - Client) #1 User: 1 PVSS/FSM #2 Intermediate: 1 InterCom + DB #3 540 DCS boards 8(6) ROBs each: ControlEngine / FeeServer Config. DB CommandCoder FEE Server

  3. Communication w/ MCMs Frame MCMAddress: 7f Source Bit: 1 HopCounter: 24 Command: 0a Address: e43a Data: 86000000 • Single Read/Write to MCM • Verify frame content • Fast Read implemented  10-20x faster • Implement FastWrite for config • ? More than 2 broken MCMs/scsn links : addressing is more complicated (Tom, Ken) Scsn-link dcs board dcs-board

  4. Chamber Testing • Check communications lines • Check memory on MCM • Check NI/readout lines • Check ORI • output in dataBase format • lots of code from robTester (Jorge) • scripts (Ken, Tom)  user interface (Jorge) • logging to PVSS (Andreas, Uwe) • Feeserver ACK (Sebastian, Benjamin)

  5. Optical Readout Interface • Readout: HalfChamberMerger to ORI checked by controlEngine (jtag) • Read EEPROM (ORI configuration) • Write EEPROM (Venelin) • Check LTC (Venelin)

  6. Chamber Configration • send standard config to chamber • ! Could not take data at CERN • Need individual patches, e.g. for dead MCM • Patchmaker (Ken, Tom) • small changes in controlEngine

  7. Data Points • chamber status information to PVSS provided by dataPoints, e.g. low voltages, configuration, dead MCM, high temperature • offline needs part of information • list of parameters for all TRD-DCS (Dariusz, Raphaelle) • more discussion (All)

  8. Wishlist… • Implement FastWrite for chamber configuration • Fix acknowledge channel (Sebastian, Benjamin, Tom) • Enable writing to ORI EEPROM (Venelin) • Read LTC information (Venelin) • implement more data points, e.g. new MCM-temps (Uwe) • Clean up code (Uwe) • Logging to PVSS (Uwe, Tom) • Patchmaker for chamber configuration (Ken, Tom) • crc32 checksums on TRAP chip (Venelin)

More Related