Change Details

placeholder: UART is the preferred way to go it can be done via USB as well as RS232 and RS485 add UART comms to daemon, extend parameters and check communication between axiom remote and daemon. The PIC32 handles the low level stuff and the electrical interface On top of that to use UART over USB (or HID, which might be interesting too) on the PIC32, the USB stack needs to be implemented. Documentation: http://ww1.microchip.com/downloads/en/DeviceDoc/61126F.pdf http://ww1.microchip.com/downloads/en/DeviceDoc/60001191G.pdf (section 11) https://www.microchip.com/forums/m1017383.aspx So the suggested steps would be something like: 1) plan what PIC32 based device(s) are realized via USB - any development board with the PIC32 works 2) make a test setup with Harmony (Microchips USB Framework) to see how/that it works 3) adapt this to work without the Microchip libraries/framework **Goals:** - ? **Prerequisites:** - ? **Language Skills:** - ? **Difficulty:** ? **Mentors:** ? To get in touch with any mentor check the [[ https://www.apertus.org/GSoC-2019-Mentor-Contact-List | Mentor Contact List]].

To be able to control the camera from AXIOM Remote, a communication channel has to be implemented, this includes extending AXIOM Remote firmware, as well as control daemon. Main preference is UART via USB, RS232 or RS485 **Goals:** - Add UART/socket communication to the control daemon - Extend the daemon with parameters which can be controlled by the firmware later - Add UART communication to the AXIOM Remote firmware - Implement additional menus to control previously added parameters **Prerequisites:** - Embedded systems basics (we use a Microchip PIC32MZ CPU) - Full Manual: https://www.alliedelec.com/m/d/1e5e0c2adda09fc1913391ccd4594515.pdf **Language Skills:** - C for PIC32 firmware - C++ for control daemon **Difficulty:** Low - Medium **Mentors:** Andrej, Herbert **Notes:** - The PIC32 handles the low level stuff and the electrical interface - On top of that to use UART over USB (or HID, which might be interesting too) on the PIC32, the USB stack needs to be implemented. - So the suggested steps would be something like: - plan what PIC32 based device(s) are realized via USB - any development board with the PIC32 works - make a test setup with Harmony (Microchips USB Framework) to see how/that it works - adapt this to work without the Microchip libraries/framework (see **Documentation** below) **Documentation:** http://ww1.microchip.com/downloads/en/DeviceDoc/61126F.pdf http://ww1.microchip.com/downloads/en/DeviceDoc/60001191G.pdf (section 11) https://www.microchip.com/forums/m1017383.aspx To get in touch with any mentor check the [[ https://www.apertus.org/GSoC-2019-Mentor-Contact-List | Mentor Contact List]].

placeholder:To be able to control the camera from AXIOM Remote, a communication channel has to be implemented, this includes extending AXIOM Remote firmware, as well as control daemon. Main preference is UART via USB, RS232 or RS485 UART is the preferred way to go**Goals:** - Add UART/socket communication to the control daemon - Extend the daemon with parameters which can be controlled by the firmware later it can be done via USB as well as RS232 and RS485 add UART comms to daemon, extend parameters and check communication between axiom remote and daemon.- Add UART communication to the AXIOM Remote firmware - Implement additional menus to control previously added parameters The PIC32 handles the low level stuff and the electrical interface**Prerequisites:** On top of that to use UART over USB (or HID, which might be interesting too) on the PIC32, the USB stack needs to be implemented.- Embedded systems basics (we use a Microchip PIC32MZ CPU) - Full Manual: https://www.alliedelec.com/m/d/1e5e0c2adda09fc1913391ccd4594515.pdf Documentation:**Language Skills:** http://ww1.microchip.com/downloads/en/DeviceDoc/61126F.pdf- C for PIC32 firmware http://ww1.microchip.com/downloads/en/DeviceDoc/60001191G.pdf (section 11) https://www.microchip.com/forums/m1017383.aspx- C++ for control daemon **Difficulty:** Low - Medium So the suggested steps would be something like: 1) plan what PIC32 based device(s) are realized via USB - any development board with the PIC32 works**Mentors:** Andrej, Herbert **Notes:** 2) make a test setup with Harmony (Microchips USB Framework) to see how/that it works- The PIC32 handles the low level stuff and the electrical interface 3) adapt this to work without the Microchip libraries/framework- On top of that to use UART over USB (or HID, which might be interesting too) on the PIC32, the USB stack needs to be implemented. **Goals:** - So the suggested steps would be something like: - ? **Prerequisites:** - plan what PIC32 based device(s) are realized via USB - any development board with the PIC32 works - make a test setup with Harmony (Microchips USB Framework) to see how/that it works - ? - adapt this to work without the Microchip libraries/framework (see **Documentation** below) **Language Skills:****Documentation:** - ? **Difficulty:** ? **Mentors:** ?http://ww1.microchip.com/downloads/en/DeviceDoc/61126F.pdf http://ww1.microchip.com/downloads/en/DeviceDoc/60001191G.pdf (section 11) https://www.microchip.com/forums/m1017383.aspx To get in touch with any mentor check the [[ https://www.apertus.org/GSoC-2019-Mentor-Contact-List | Mentor Contact List]].