Editing Move Motion Controller

[[Category:Hardware]]

== Move Hardware ==
*Model reference
**'''CECH-ZCM1U''' (bought in ?)
**'''CECH-ZCM1E''' (bought in europe)

*Main board reference
**'''YCON2_1.01''' (dissassembled photos ---> http://www.ifixit.com/Teardown/PlayStation-Move-Teardown/3594/1)
**'''YCON2.5_1.03''' (different Bluetooth chip, different 2-axis gyro "PR425A 2117 AEWEP")

*Note some components and testpoints (TP) are differet between models.

=== STM32F103 VBT6 Y (ARM Cortex-M3 32bit@72MHz SRAM20Kb FLASH128Kb RISC Microcontroller) ===
U19 <br />
http://www.st.com/mcu/devicedocs-STM32F103VB-110.html

http://www.st.com/stonline/stappl/st/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/DATASHEET/CD00161566.pdf

{| class="wikitable"
|-
! style="background-color:#DDDDDD;" | '''Reference''' !! STM32 (Device family) !! F (Procut type) !! 103 (Device subfamily)!! V (Pin count)!! B (Flash memory size) !! T (Package) !! 6 (Temperature range) !! Y (Options)
|-
| style="background-color:#DDDDDD;" | '''Description''' || STM32= ARM-based 32-bit microcontroller || F= general-purpose || 103= performance line || T= 36 pins <br /> C= 48 pins <br /> R= 64 pins <br /> V= 100 pins || 8= 64 Kbytes <br /> B= 128 Kbytes || H= BGA <br /> T= LQFP <br /> U= VFQFPN || 6= -40 to +85 ºC <br /> 7= -40 to +105 ºC || Unknown
|-
|}

*Firmware
**Board '''YCON2_1.01''' (STM32F103) Original Firmware Dump (region unknown) ---> http://www.eissq.com/ps3_move/files/1e93d333d39a9b0d43a47489503859a2-7.html

*Firmware dump analisys (wrote by nico @ Kenn Sebesta blog)
 
 Actually, there seems to be 3 vector tables:
 
 8000000 (size 0x0040) NVIC vectors
 8000800 (size 0x0094) Bootloader vectors
 8002800 (size 0x0130) Application vectors
 
 The subroutine at 8000040 seems to call either the bootloader reset vector (at 8000142) or the application reset vector (at 800016E).
 
 The thing is, the shortened bootloader vectors (provided this is actually the bootloader code), does not contain any I2C or UART interrupt vectors, and only USB_LP_CAN_
 RX0 vector seems to contain active code (as far as communication is concerned).
 
 Seems like the CPU and Bluetooth module use some form of UART to communicate, is that correct ?
 ...
 ..
 .
 The first thing to look for is the base address of the BIN file in memory, and further what the memory map looks like. Kenn has already provided this info in his example project, but these can be extracted from the STM32 datasheet also. We know that the first byte of the BIN file maps to address 0x08000000 in memory. We know that internal SRAM start at 0x20000000.
 
 Second thing is to locate the vectors table (see STM32 datasheet) and the reset vector, because it gives you the entry point of the firmware and other useful info. The vectors table is also relocatable in this case (register SBC_VTOR, STM32 programming manual page 134), so there may be multiple vectors tables (and there is).
 
 The vectors table is actually a big jump table. I'm using the following trick to find other tables (be it vectors or switch / case jump tables). We know that addresses are 32 bit (ARM) and highest byte is always 0x08, so we can use a simple hex dump of the BIN file and search using the regular expression "08 .. .. .. 08" (dot meaning any single character). If you use a text editor with search results highlighting (vim for example), then jump tables just catch your eye. There are not so many of them. I used this technique to find the three vectors tables listed earlier. They're distinctive because of their first 32 bit word (0x20000400 which oughts to be the address of the stack top according to the STM32 datasheet).
 
 The vectors table also provides you with pointers to interesting subroutines. If Bluetooth is what you're looking after, just follow IT vector number 39 (USART3) since we know thanks to Kenn that STM32 and Bluetooth chips communicate via UART number 3. Then try to figure out what the firmware should look like: when a Bluetooth output report is coming to the Move, an interrupt is generated in the STM32, the input report is fetched serially from the Bluetooth chip into some buffer (or ring buffer), and the buffer is parsed, either synchronously in the IT handler itself, or a message is sent from the IT handler to some lower priority task. Difficulty is to figure out the relevant tasks and to identify them in the disassembled code.
 
 The jump tables trick can also be used to identify the code that parses Bluetooth output reports (faster). It's very likely that such a jump table is used to call a specific Bluetooth command handler for each Bluetooth command supported by the Move. In that case the jump table is a table of function pointers. The idea is to list the jump tables, then try to find one in the same region as the IT handler. The start address of the jump table should be present in some code that can be traced back to the IT handler. This provides info on how many Bluetooth commands are supported, which ones and eventually what they're doing (after a fair amount of disassembly, I admit).

*Bootloader
**STM32 Arm-Cortex bootloader: http://www.micromouseonline.com/2009/05/08/stm32-arm-cortex-bootloader/?doing_wp_cron=1348086547.3716659545898437500000
**Sony bootloader: ''there are two sections in the beginning that are blanketed by empty flash: one from 0x00000 to 0x006B7 and the other from 0x00800 to 0x027BB. My guess is that the first section is the NVIC table and that the second is a bootloader''. calibration data stored at last 0x800 bytes starting from 0x0001F800 ? (from Kenn Sebesta blog)

*JTAG programmer
3.3V and http://www.amontec.com/openocd.shtml compatible e.g: "bus pirate" https://www.sparkfun.com/products/9544

First of all, please save your original firmware image. Even if you don't plan to ever use your Move as a game controller again, this is a good test if your JTAG connection works. It's also supposed that the firmware contains device specific calibration values. If you replace your original firmware with firmware from another Move, it may not work as expected. Newer Moves may have code protection enabled. You can easiely disable code protection via OpenOCD but this will erase flash and make it impossibe to save the original firmware. 

To make a dump of the original firmware run:
{{Keyboard|content=<syntaxhighlight lang="bash">
    > dump_image my_original_move_firmware.bin 0x8000000 0x20000
    dumped 131072 bytes in 6.391000s (20.028 kb/s)
</syntaxhighlight>}}

To write a dump run:
{{Keyboard|content=<syntaxhighlight lang="bash">
    > flash write_image erase my_original_move_firmware.bin 0x8000000
    auto erase enabled
    wrote 131072 bytes from file myoriginal_move_firmware.bin in 10.704000s (11.958 kb/s)
</syntaxhighlight>}}

*Buses:
**3x USART (bluetooth @ 230,400 baud,...)
**2x SPI
**2x I²C (magnetometer,...)
**1x USB
**1x CAN
*Pinout

<div style="height:555px; overflow:auto">
{| class="wikitable"
|-
! Pin # !! Name !! Type !! 5v tolerant !! colspan="6" | Firmware Function !! colspan="3" | Move Board TestPoints !! Notes
|-
! colspan="4" | !! colspan="3" | ARM-Cortex !! Sony !! MoveCopter !! Others? !! YCON2_1.01 !! YCON2.5_1.03 !! Others ? !!
|-
! colspan="4" | !! Main !! Alternate !! Remap !! colspan="7" | 
|-
| 1 || PE2 || || || || || || TRACECK || || || TP21 || || || 
|-
| 2 || PE3 || || || || || || TRACED0 || || || TP22 || || || 
|-
| 3 || PE4 || || || || || || TRACED1 || || || TP23 || || || 
|-
| 4 || PE5 || || || || || || TRACED2 || || || TP24 || || || 
|-
| 5 || PE6 || || || || || || TRACED3 || || || TP25 || || || 
|-
| 6 || V<sub>BAT</sub> || || || || || || || || || Vcc || || || Supply for RTC and backup registers
|-
| 7 || PC13-TAMPER-RTC || || || || || || || || || SW10 || || || 
|-
| 8 || PC14-OSC32_IN || || || || || || || || || SW11 || || || 
|-
| 9 || PC15-OSC32_OUT || || || || || || || || || SW12 || || || 
|-
| 10 || V<sub>SS_5</sub> || || || || || || || || || TP69 || || || 
|-
| 11 || V<sub>DD_5</sub> || || || || || || || || || TP68 || || || 
|-
| 12 || OSC_IN || || || || || || || || || || || || 
|-
| 13 || OSC_OUT || || || || || || || || || || || || 
|-
| 14 || NRST || || || || || || || || || TP54 || || || Connected to ground through reset switch. Can also be used for '''JTAG NRST''' debugging
|-
| 15 || PC0 || || || || || || ADC12_IN10 || || || Gyro_y || || || Gyroscope Y-channel input
|-
| 16 || PC1 || || || || || || ADC12_IN11 || || || Gyro_x || || || Gyroscope X-channel input
|-
| 17 || PC2 || || || || || || ADC12_IN12 || || || Gyro_z || || || Gyroscope Z-channel input
|-
| 18 || PC3 || || || || || || ADC12_IN13 || || || Acc_y || || || Accelerometer Y-channel input
|-
| 19 || V<sub>SSA</sub> || || || || || || || || || || || || 
|-
| 20 || V<sub>REF-</sub> || || || || || || || || || || || || 
|-
| 21 || V<sub>REF+</sub> || || || || || || || || || || || || 
|-
| 22 || V<sub>DDA</sub> || || || || || || || || || || || || 
|-
| 23 || PA0-WKUP || || || || || || WKUP || || || SW8 || || || Normally pulled to ground by 10kΩ
|-
| 24 || PA1 || || || || || || ADC12_IN1 || || || Acc_x || || || Accelerometer X-channel input
|-
| 25 || PA2 || || || || || || || || || || || || 
|-
| 26 || PA3 || || || || || || ADC12_IN2 || || || Acc_z || || || Accelerometer Z-channel input
|-
| 27 || V<sub>SS_4</sub> || || || || || || || || || TP70 || || || 
|-
| 28 || V<sub>DD_4</sub> || || || || || || || || || || || || 
|-
| 29 || PA4 || || || || || || || || || || || || 
|-
| 30 || PA5 || || || || || || || || || || || || 
|-
| 31 || PA6 || || || || || || || || || || || || 
|-
| 32 || PA7 || || || || || || || || || || || || 
|-
| 33 || PC4 || || || || || || ADC12_IN14 || || || Gyro_7 || || || Gyroscope pin7. Constant 1.25V. Possibly a comparison feedback for the gyroscope?
|-
| 34 || PC5 || || || || || || || || || || || || 
|-
| 35 || PB0 || || || || || || || || || || || || 
|-
| 36 || PB1 || || || || || || ADC12_IN9 || || || Joystick_9 || || || Analog trigger reading
|-
| 37 || PB2 || || || || || || || || || || 
|-
| 38 || PE7 || || || || || || || || || TP33 || || || 
|-
| 39 || PE8 || || || || || || || || || || || || 
|-
| 40 || PE9 || || || || || || || || || || || || 
|-
| 41 || PE10 || || || || || || || || || || || || EXT connector Pin 3
|-
| 42 || PE11 || || || || || || || || || || || || EXT connector Pin 4
|-
| 43 || PE12 || || || || || || Interrupt || || || Mag_14 || || || Magnetometer pin14. Interrupt to signal new sample ready
|-
| 44 || PE13 || || || || || || || || || || || || 
|-
| 45 || PE14 || || || || || || || || || || || || 
|-
| 46 || PE15 || || || || || || || || || TP34 || || || 
|-
| 47 || PB10 || || || || || || I2C2_SCL || || || Mag_15 || || || Magnetometer pin15 clock
|-
| 48 || PB11 || || || || || || I2C2_SDA || || || Mag_16 || || || Magnetometer pin16 data
|-
| 49 || V<sub>SS_1</sub> || || || || || || || || || || || || 
|-
| 50 || V<sub>DD_1</sub> || || || || || || || || || || || || 
|-
| 51 || PB12 || || || || || || || || || || || || 
|-
| 52 || PB13 || || || || || || || || || || || || 
|-
| 53 || PB14 || || || || || || || || || || || || 
|-
| 54 || PB15 || || || || || || || || || || || || 
|-
| 55 || PD8 || || || || || || USART3_TX || || || BT_7 || || || Bluetooth pin7 transmitter
|-
| 56 || PD9 || || || || || || USART3_RX || || || BT_6 || || || Bluetooth pin6 receiver
|-
| 57 || PD10 || || || || || || || || || TP51 || || || 
|-
| 58 || PD11 || || || || || || DIO || || || U6_6 || || || TPS63030 regulator enable
|-
| 59 || PD12 || || || || || || || || || || || || 
|-
| 60 || PD13 || || || || || || || || || || || || Reacts slowly to USB plug. Logic LO when USB plugged in, HI when not.
|-
| 61 || PD14 || || || || || || || || || || || || Reacts slowly to USB plug. Logic LO when USB plugged in, HI when not.
|-
| 62 || PD15 || || || || || || || || || || || || 
|-
| 63 || PC6 || || || || || || || || || || || || 
|-
| 64 || PC7 || || || || || || || || || || || || 
|-
| 65 || PC8 || || || || || || || || || || || || 
|-
| 66 || PC9 || || || || || || DIO || || || R_39 || || || 1.25V???
|-
| 67 || PA8 || || || || || || DIO || || || BT_36 || || || Bluetooth pin36. Constant 85Hz PWM
|-
| 68 || PA9 || || || || || || DIO || || || BT_15 || || || Bluetooth pin15. Varying TTL signal
|-
| 69 || PA10 || || || || || || DIO || || || BT_14 || || || Bluetooth pin14. Very occasional, only really seen at startup. SPI chip select?
|-
| 70 || PA11 || || || || || || USBDM || || || TP26 || || || Connected through 2.1Ωresistor
|-
| 71 || PA12 || || || || || || USBDP || || || TP27 || || || Connected through 2.1Ωresistor
|-
| 72 || PA13 || || || || || || JTMS || || || TP56 || || || Can also be used for '''JTAG SWDIO''' debugging
|-
| 73 || N.C || || || || || || || || || || || || Not Connected
|-
| 74 || V<sub>SS_2</sub> || || || || || || || || || || || || 
|-
| 75 || V<sub>DD_2</sub> || || || || || || || || || || || || 
|-
| 76 || PA14 || || || || || || JTCK || || || TP57 || || || Can also be used for '''JTAG SWCLK''' debugging
|-
| 77 || PA15 || || || || || || JTDI || || || TP55 || || || Can also be used for '''JTAG JTDI''' debugging
|-
| 78 || PC10 || || || || || || DIO || || || TP38 ? || || ||
|-
| 79 || PC11 || || || || || || DIO || || || TP37 ? || || ||
|-
| 80 || PC12 || || || || || || || || || || || || 
|-
| 81 || PD0 || || || || || || || || || || || || 
|-
| 82 || PD1 || || || || || || || || || || || || 
|-
| 83 || PD2 || || || || || || || || || || || || 
|-
| 84 || PD3 || || || || || || || || || || || || 
|-
| 85 || PD4 || || || || || || || || || || || || 
|-
| 86 || PD5 || || || || || || || || || SW13 || || || 
|-
| 87 || PD6 || || || || || || || || || || || || Reacts slowly to USB plug. Logic LO when USB plugged in, HI when not.
|-
| 88 || PD7 || || || || || || DIO || || || || || || Reacts instantly to USB plug. Logic HI when USB plugged in, LO when not.
|-
| 89 || PB3 || || || || || || JTDO || || || TP58 || || || Can also be used for '''JTAG JTDO''' debugging
|-
| 90 || PB4 || || || || || || JNTRST || || || TP59 || || || Can also be used for '''JTAG JNTRST''' debugging
|-
| 91 || PB5 || || || || || || || || || || || || 
|-
| 92 || PB6 || || || || || || || || || || || || EXT connector Pin 5
|-
| 93 || PB7 || || || || || || || || || || || || EXT connector Pin 6
|-
| 94 || BOOT0 || || || || || || || || || || || || 
|-
| 95 || PB8 || || || || || || || || || SW15 || || || 
|-
| 96 || PB9 || || || || || || || || || SW14 || || || 
|-
| 97 || PE0 || || || || || || || || || SW9 || || || 
|-
| 98 || PE1 || || || || || || || || || || || || 
|-
| 99 || V<sub>SS_3</sub> || || || || || || || || || || || || 
|-
| 100 || V<sub>DD_3</sub> || || || || || || || || || || || || 
|-
|}
</div>

=== STM LPR425AL (2-Axis Gyroscope) ===
The 2-axis gryoscope (likely an STM LPR425AL) is an analog sensor measuring rotation along the x- and y-axes

Is covered with a metal shield to avoid interferences (marked as 067S8 in some models), this makes his identification dificult

=== Y5250H 2029 K8QEZ (Z-Axis Gyroscope) ===
alt.no.: Y5250H 2005 4Y84AQ <br />
alt.no.: Y5250H 2024 GPECQ <br />
U14 <br />

=== Kionix KXSC4 10227 2410 (3-Axis Accelerometer) ===
[[Image:Kionix KXSC4.gif|400px|thumb|right| Kionix KXSC4 <br /> 3-Axis Accelerometer]][[Image:Kionix KXSC4 application squematic.jpg|800px|thumb|right| Kionix KXSC4 <br /> application squematic]]
alt.no.: Kionix KXSC4-XLU 90831 3909 <br />
alt.no.: Kionix KXSC4 10115 2010 <br />
U12 <br />

Tri-Axis, 1.5g – 6g, Low Power Analog, 5x5x1.2mm DFN

The KXSC4 is a high-performance, low-power, analog output tri-axis accelerometer. This  accelerometer is delivered in a 5 x 5 x 1.2 mm, 14-pin, DFN package with an operating temperature range of -40°C to +85°C.

The KXSC4 has a full-scale output range of ±2g and operates from a 1.8 V to 3.6 V DC supply (factory-programmable).

*Features:
**Factory-programmable, internal low-pass filter
**Low current consumption: 0.05 µA in standby, 230 µA at full power
**Factory-programmable ±1.5g to ±6g range
**Supply voltage range: 1.8 V to 3.6 V
**Analog output
**Embedded features
***Motion detection
***Orientation detection: report changes in face up, face down, +/- vertical and +/- horizontal orientation
***Self-test function
**RoHS compliant

http://www.kionix.com/accelerometers/kxsc4

http://www.kionix.com/sites/default/files/KXSC4%20Product%20Brief.pdf

http://www.kionix.com/sites/default/files/KXSC4-2050%20Specifications%20Rev%203.pdf

*Pinout
{| class="wikitable"
|-
! Pin # !! Name !! Description !! Move Board Notes
|-
| 1 || GND || ''Ground''. || 
|-
| 2 || N.C || ''Not Connected Internally''. || 
|-
| 3 || N.C || ''Not Connected Internally''. || 
|-
| 4 || Vdd || ''Power supply input''. Decouple this pin to ground with a 0.1uF ceramic capacitor (C<sub>1</sub>). || Decoupled with capacitor C42 
|-
| 5 || Reserved || '''Reserved''' (must be "Pulled-up to VDD" for normal operation). || Connected to pin 4
|-
| 6 || ST || '''Self Test''' ("Pulled-down to GND" = normal operation. "Pulled-up to VDD" = self-test mode). || Connected to ?
|-
| 7 || Enable || '''Enable pin''' ("pulled-up to VDD" =  normal operation. "Pulled-down to GND" = standby). || Connected to ?
|-
| 8 || X output ||  '''X-channel analog output''' (Optional filter capacitor, C<sub>2</sub>). || Connected to MCU pin# '''24 (PA1)'''.
|-
| 9 || Y output || '''Y-channel analog output''' (Optional filter capacitor, C<sub>3</sub>). || Connected to MCU pin# '''18 (PC3)'''.
|-
| 10 || Z output || '''Z-channel analog output''' (Optional filter capacitor, C<sub>4</sub>). || Connected to MCU pin# '''26 (PA3)'''.
|-
| 11 || GND || ''Ground''. || 
|-
| 12 || N.C || ''Not Connected Internally''. || 
|-
| 13 || N.C || ''Not Connected Internally''. || 
|-
| 14 || GND || ''Ground''. || 
|-
|}

*Output
1.6V is the zero output. The accelerometers have a scale of about +0.250V increment for each "g". Assuming that the chip is able to go full scale from 0V to 3V, this gives an absolute output of +-6g (this range is a configuration programmable at factory)

=== AKM AK8974 (3-Axis Magnetic Compass) ===
alt.no.:AKM8974 948D <br />
alt.no.:AKM8974 008F <br />
U13 <br />
http://www.chipworks.com/seamark.aspx?sm=s4%3BDatedfl11%3BDevCategory12%3BMEMS+Devicesm12%3BReleaseMonthm10%3BDeviceTypefl10%3BReportCode12%3BEXR-0908-802&cw=detail2

*Pinout
{| class="wikitable"
|-
! Pin # !! Name !! Description
|-
| 1 || || 
|-
| 2 || || 
|-
| 3 || || 
|-
| 4 || || 
|-
| 5 || || 
|-
| 6 || || 
|-
| 7 || || 
|-
| 8 || || 
|-
| 9 || || 
|-
| 10 || || 
|-
| 11 || || 
|-
| 12 || || 
|-
| 13 || || 
|-
| 14 || || 
|-
| 15 || || 
|-
| 16 || || 
|-
|}

=== Cambridge Silicon Radio BC4RE A16U (Bluetooth transmitter) ===
U8? <br />
http://www.csr.com/products/technology/bluetooth

*Pinout
<div style="height:555px; overflow:auto">
{| class="wikitable"
|-
! Pin # !! Name !! Description
|-
| 1 || || 
|-
| 2 || || 
|-
| 3 || || 
|-
| 4 || || 
|-
| 5 || || 
|-
| 6 || || 
|-
| 7 || || 
|-
| 8 || || 
|-
| 9 || || 
|-
| 10 || || 
|-
| 11 || || 
|-
| 12 || || 
|-
| 13 || || 
|-
| 14 || || 
|-
| 15 || || 
|-
| 16 || || 
|-
| 17 || || 
|-
| 18 || || 
|-
| 19 || || 
|-
| 20 || || 
|-
| 21 || || 
|-
| 22 || || 
|-
| 23 || || 
|-
| 24 || || 
|-
| 25 || || 
|-
| 26 || || 
|-
| 27 || || 
|-
| 28 || || 
|-
| 29 || || 
|-
| 30 || || 
|-
| 31 || || 
|-
| 32 || || 
|-
| 33 || || 
|-
| 34 || || 
|-
| 35 || || 
|-
| 36 || || 
|-
| 37 || || 
|-
| 38 || || 
|-
| 39 || || 
|-
| 40 || || 
|-
|}
</div>

=== ALPS 503A 04C (Radio Module) ===

=== LED2 (High Power RGB LED) ===
6 pins surface mounted RGB 2^24

*Soldered to the board with a ribbon cable (no connectors) with 4 lines marked as:
**LED_B
**LED_G
**LED_R
**LED_4R5 (VDD line)

=== TPS63030 (High Efficient Single Inductor Buck-Boost Converter) ===
alt.no.:CEE TI J 04P0 <br />
U6 <br />

=== Texas Instruments BQ24080 (1-cell Li-Ion Charger) ===
alt.no.:BRO 01J PDH2 <br />
alt.no.:BRO 04K 0948 <br />
U1 <br />

=== Li-Ion (Battery Pack) ===
4-168-108-01 / LIS1441<br />
3.7V 1380 mAh <br />
(typ 1520mAh) <br />
Charge Current: 1.4A <br />
Charge Voltage: 4.25V <br />

=== External Conectors ===
[[Image:Move controller connectors.jpg|400px|thumb|right| Move controller connectors]]

==== USB connector ====
USB (Mini-B type) standard connector 5 pins

http://pinoutsguide.com/Slots/USB_pinout.shtml

==== Charging Station Pads ====
2 copper pads that are part of a little PCB with no traces that works as a support for the pads. Are soldered (no connectors) to the main board with 2 wires: black (ground) red (volts)

http://www.youtube.com/watch?v=TkPFKrlWWwk

*This pads are common and has the same size and position than the [[Move Navigation Controller]]

==== Extension Connector ====
Marked in the plastic as "ext" and refered as "extension connector" in the [[Move Sharp Shooter]] "Instruction Manual.pdf"

8 pins custom made (exact alternative part not found yet)

This connector is used to communicate with the [[Move Sharp Shooter]] gun. The buttons, trigger, etc... of this gun can send signals to the move controller

{| class="wikitable"
|-
! EXT connector pin number <br /> (from left to right) !! Connected to main board !! MCU default firmware function !! sony firmware function <br /> (pinout remapped ?) !! MoveCopter firmware function <br /> (pinout remapped)
|-
| 1 || colspan="4" | 3.2v
|-
| 2 || colspan="4" | 3.2v
|-
| 3 || MCU pin 41 (PE10) || TIM1_CH2N ||  || {{no}}
|-
| 4 || MCU pin 42 (PE11) || TIM1_CH2 || || PPM output (input for the PC telemetry app)
|-
| 5 || MCU pin 92 (PB6) || I2C1_SCL || || USART1 TX (serial transmitter). Added to the project after D-lite manual
|-
| 6 || MCU pin 93 (PB7) || I2C1_SDA || || USART1 RX (serial receiver). Added to the project after D-lite manual
|-
| 7 || colspan="4" | GND
|-
| 8 || colspan="4" | GND
|-
|}

*Notes
**All the squematics and pinouts in "D-lite MoveCopter manual" and "Kenn Sebesta blog" related with this connector are taken directly from the main board (not from the external connector). The squematics explained in these pages are from an old model with different number of pins (some of them duplicated or displaced). There are at least 3 different board models where this pins are different, but in all models the lines are reordered at the "EXT connector" (and reduced to 8), all models has the same pinout externally explained here in ps3devwiki
**In MoveCopter bootloader several pins of MCU has been remaped, included 3 pins of "EXT connector" (for input/output data), and the 3 RGB lines from the LED + 1 line from the rumble motor (to controll 4 servo motors for the helices of the quadcopter)

 Obsolete not-acurate notes
 The connector is soldered in a "children board" identifyed as "connector board", is connected with the "main board" with a 12 traces ribbon cable (and 2 pressure connectors).
 Only 4 lines of the ribbon cable are used for data signals (protected with a resistor and a diode in the children board) + 1 line for "ground" and 1 line for 3.2volts
 I will upload a complete squematic of this sub-circuit later

==Software Related Projects==

===PSL1GHT===
* https://github.com/ps3dev/PSL1GHT/tree/master/samples/input/gemsample
* https://github.com/ps3dev/PSL1GHT/tree/master/samples/input/gemtest

<!--// PS3 homebrew support for move controller by faking the device as a wireless mouse, there is no support for native firmware move modules/functions (yet) //-->

===The PS Move API===
Is a library to access the Sony Move Motion Controller via Bluetooth and USB directly from your PC (Linux, Mac OS X, Windows) without the need for a PS3. Mobile platforms are also supported (or planned): Support for MeeGo 1.2 Harmattan is already working, support for Android is in the works. The library is free software, released under a Simplified BSD License, so you can use it in both open source and proprietary closed-source applications, as long as you follow the license terms. 

http://thp.io/2010/psmove/

Git repository: https://github.com/thp/psmoveapi

===Move On PC===
PS Move Motion Controller as input device on PCs and mobile devices
May 2012: We are participating in the Google Summer of Code. We will keep you updated about our progress here. The old code base will be archived in the Downloads section soon, and we will base our future MoveOnPC work on Thomas Perl's "PS Move API" project, but add support for tracking and computer vision to the library.

Blog: http://moveonpc.blogspot.com.es/

http://code.google.com/p/moveonpc/

===Move Framework for Windows===
With the Move Framework, you can integrate all the possibilities of motion tracking in your programs and games!. There are SDK's for C++ and C# developers. The project is no longer maintained

http://code.google.com/p/moveframework/ (src available with svn)

===Motion In Joy for Windows===
MotioninJoy is a driver, designed by a developer unconnected with Sony, intended to use all the features of the Sixaxis and Dualshock 3 controllers on a PC running Windows. 

http://www.motioninjoy.com

http://www.motioninjoy.com/wiki/help

http://forums.motioninjoy.com/viewtopic.php?f=33&t=929

==Hardware Related Projects==

===Kenn Sebesta blog (PS3 Move hacking)===
http://www.eissq.com/ps3_move/

===D-Lite MoveCopter ===
"CopterControl bootloader" port for "Move controller"

Is a custom bootloader/firmware for the ARM STM32 microcontroller series. The installation is composed by the "bootloader" (move hardware specific, installed by JTAG) and the "flight firmware" (common for all STM32 microcontrollers, installed by USB)

The flight firmware is intended to stabilish a flying quadcopter using data from position sensors (like the gyroscopes and the 3-axis acelerometers in move)

http://vimeo.com/25983655

http://wiki.openpilot.org/display/Doc/D-Lite%27s+PS3+MoveCopter

http://forums.openpilot.org/topic/5526-coptercontrol-on-a-game-controller/

http://forums.openpilot.org/topic/5526-coptercontrol-on-a-game-controller/page__st__40#entry24579

http://forums.openpilot.org/topic/5526-coptercontrol-on-a-game-controller/page__st__140#entry80016

http://git.openpilot.org/changelog/~br=D-Lite%402fMoveCopter_MARG/OpenPilot

http://wiki.openpilot.org/display/CC/CopterControl+Home

http://wiki.openpilot.org/display/Doc/Ground+Control+Station+User+Manual

http://www.openpilot.org/products/openpilot-coptercontrol-platform/

http://forums.openpilot.org/topic/5526-coptercontrol-on-a-game-controller/page__st__140#entry81223

{{Console}}

[[Category:Peripherals]]