Apertus Association

Mentors: Student: Vinayak Sankar

<p>The AXIOM Remote is a device used to control the AXIOM Beta range of cameras. The aim of this project is to develop an automated test system to test the various electronic components on the Axiom Remote from the AXIOM Beta.</p>

Mentors: Student: tpw_rules

<p>nMigen is an HDL toolkit implemented in the Python programming language. By using nMigen instead of traditional HDLs like Verilog or VHDL, gateware can be developed in less time, with less bugs, and with extremely powerful abstractions that enable code clarity and conciseness. apertus° has already developed prototype nMigen gateware for the AXIOM Micro, but wishes to extend it to support the sensor, FPGA, and HDMI interface of the AXIOM Beta. This work will develop in nMigen and demonstrate on real hardware an end-to-end imaging prototype for the AXIOM Beta: sensor control over SPI, sensor readout PHY from LVDS, pixel remapper based on existing implementation, 4K to Full HD downscaling debayerization, and final image output to HDMI.</p>

Mentors: Student: anuejn

<p>The AXIOM recorder software can record moving images from axiom cameras via either USB3 or Ethernet. Currently, that software is only a CLI tool that is difficult to use in the field and has severe accessibility hurdles for not technically inclined users. This project will develop an easy to use and performant GUI to ease the operation of the recorder.</p>

Mentors: Student: SeifEldeen Emad

<p>The project's main goal is to create a Simulation/Emulation of the CMV12000 sensor currently used in the AXIOM Beta. The HDL could be placed as a direct interface integrated into the ZYNQ design or into a separate FPGA acting as a full sensor emulation.</p>

Mentors: Student: Aman Singh (eppisai)

<p>Firmware as the name suggests is a bridge between User and hardware/features of Axiom Remote. Hence, there is a need for Firmware to follow good UI/UX principles,at the same time should not be heavy on the CPU.</p> <p>AXIOM-Remote General UI guidelines clearly mentions how things flow in AXIOM-Remote firmware, and the correct structure and plan one should keep in mind. I tend to follow the structure and at the point of dilemma or turmoil would discuss with mentors.</p> <h4>Task mentioned in Firmware Improvement and Extension</h4> <ul> <li>Event handling (button interactions, turning the rotary knob, etc.)</li> <li>Page setup </li> <li>Add new UI classes</li> <li>Text input GUI</li> <li>Histogram, scopes and other graphs drawing</li> <li>Optimize drawing</li> <li>Add transition animations</li> <li>Unit tests to verify proper implementation</li> </ul>