1 Printed Circuit Boards
1.1 PCB Version 0.9
The first development prototype of the AXIOM Remote printed circuit board (V0.9) has been designed and routed, ordered, received and populated. This first version is not meant to be perfect (for testing we just used a simple 6x6mm Alps push-button type - not the more expensive ones with better haptic feedback) but should provide a good foundation for developers to focus on ensuring that the menus work and how to create an intuitive and pleasant user experience when operating an AXIOM camera.
PCB Source files: 
1.2 Version 2 Prototype
- Remove Second Knob (For menu navigation and the changing of parameters so far we found no use for it designing the UI).
- In the future we may add flash memory for storing of images - for version 2 we left it out. So far we have not exceeded the PIC32MZs internal storage memory but if we want to make the internal help system more extensive with lots of added illustrations/images it might be required to add more flash storage. Routing looks challenging for a 2 layer PCB... consider dropping it again for now.
- Remove left side rocker switches. So far we have not found any function for them. They are prone to being switched accidentally as they stand out from the device quite far. Having buttons/switches on the left side of the remote prevents it from being attached to the camera/rig on that side.
- Remove top side pushbuttons. So far we have not found a real application for them. In line with good user interface design / user experience these buttons need labels so the user clearly sees what is going to happen when he presses them. This is difficult as the label would not be visible from the front of the device.
- Reduce number of RGB LEDs to two (for status LEDs: State and Operation). So far we have not discovered any real world benefit to having RGB LEDs to illuminate pushbuttons. Changing the button illumination color to indicate something happening while pushing it makes little sense as while pushing it the users finger is covering the button making it impossible for the user to see it.
- Having one white LED per pushbutton could make sense that as it could indicate which buttons are currently active (requires buttons to show significant transparent surface so the light can shine through). We will see if we have enough lanes/space for that or revert to using one white LED for multiple buttons illumination.
- add 4 more holes to PCB somewhere close to eachs PCBs corners so the enclosure back can be screwed together with the enclosure front.
- rounded corners for PCB so it fits into enclosure better, 5mm radius
- to save space some cutouts on the PCB would be handy for adding thread mount points to the enclosure in the middle of each side
- shall we add additional PCB screw holes near the push buttons to add additional stability and prevent the PCB from being bent by force being applied to push buttons. Screw holes take away quite a big amount of routing space so the goal is rather to add support pillars without screws from the enclosure back where the pcb could be prone to bending due to buttons being pushed.
- replace slide switches for ON/OFF and LOCK with pushbuttons
- button placement CAD drawing:
Enclosure Work in Progress CAD Design:
- move screws to corners
- try squeezing PCB with same screws and rubber o-rings
- move attachment points to enclosure bottom part
2 Electronic Components
- Core Processor: A PIC32MZ was chosen. Two additional smaller PIC16 are used for handling push button, rotary encoder and LED IO.
Higher resolution and more complex device like iphone 4 replacement display (326 PPI 3.5" 960×640 px) or http://www.ebay.com/itm/OEM-HTC-Droid-DNA-ADR6435-Original-LCD-Screen-Display-Repair-Replacement-Parts-/350711245261 smaller bezel )(documentation through: https://hackaday.io/project/364-mipi-dsi-display-shieldhdmi-adapter) were considered but not used to reduce complexity.
- 3D accelerometer to measure device orientation was considered but not implemented - there is really only one orientation that the Remote is designed for.
- AXIOM Remote is currently powered externally via 5V DC supply (internal batteries might be considered for the future: 4x AA battery tray -> cumbersome - lithium ion battery pack that is integrated into the remote and is automatically charged through 5V/camera would be preferred)
- currently the firmware is programmed with a PICkit2 directly into the PIC32MZ flash memory - in the future this shall be done over USB - having a separate microSD card containing the devices firmware is not planned.
- The AXIOM Remote has no requirement for internal RTC (plus button cell battery) - instead timecode is synced with/by a connected AXIOM Beta.
Beta connectivity through Hirose HR10A-7P-4S (a bit expensive but massive)
or alternatively 4 pin 2.5 or 3.5mm audio cables:
plus metal receptor on Beta and Remote:
RS232C as Beta <-> Remote protocol4
Toogle Switches APEM ZL series
2.1 Buttons/Rotary Encoders/Connectors:
ALPS SRBE210200 low profile rotary encoder + push switch (only 12 detents though)
EM11B16140AE 15mm shaft, magnetic encoder, 16 detents, 20+€ very expensive - https://www.alps.com/prod/info/E/HTML/Encoder/Incremental/EM11B/EM11B16140AE.html
Bourns PEC11L - 15mm shaft, 20 detents 1-2€ / pc - PEC11S-929F-S0015 https://www.bourns.com/docs/product-datasheets/pec11s.pdf?sfvrsn=601089f1_5
We evaluated several buttons for their haptic characteristics:
ALPS SKSTAAE010 (grey color code in picture above): https://www.alps.com/prod/info/E/HTML/Tact/SurfaceMount/SKST/SKSTAAE010.html
Marquardt 3006.2100 (blue color code in picture above) https://www.marquardt-switches.com/tact-and-key-switches.html?&no_cache=1&tx_produktkatalog2_pi1%5Bmode%5D=overview&tx_produktkatalog2_pi1%5Bmodifier%5D=0&tx_produktkatalog2_pi1%5Bvalue%5D=3006 costs 3+€ per piece though with integrated white illumination.
ALPS SKPRAAE010 (black color code in picture above)
SMT type rotary encoders: