MIDIbox

User Tools

Site Tools

Trace: • projects
mf_ng_module

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
mf_ng_module [2016/08/05 15:42] – psykhazemf_ng_module [2016/08/05 19:27] (current) – [Introduction] psykhaze
Line 13: Line 13:
   * find a solution which is DIY friendly and doesn't require additional gear for something which isn't part of the MBHP yet   * find a solution which is DIY friendly and doesn't require additional gear for something which isn't part of the MBHP yet
   * find a solution which can be easily tested and troubleshooted (no need to learn new processes)   * find a solution which can be easily tested and troubleshooted (no need to learn new processes)
 +
 +{{ ::neonking:mbhp_mf_ng_final1.jpg?600 |}}
  
 And the result is: And the result is:
  
-  * a dedicated PIC controller controls the motorfaders directly.+  * a dedicated **PIC controller** controls the motorfaders directly.
   * the firmware can be updated via MIDI!   * the firmware can be updated via MIDI!
-  * motorfaders are accessed via MIDI - this allows standalone usage, cascading (to chain multiple modules), and the re-use of existing infrastructure such as MIOS, MIOS Studio and MIOS Bootloader +  * **motorfaders are accessed via MIDI** - this allows standalone usage, cascading (to chain multiple modules), and the re-use of existing infrastructure such as MIOS, MIOS Studio and MIOS Bootloader 
-  * the module can either be connected to a PC directly, or controlled from a second PIC or STM32 or LPC17 (note that MBHP_CORE_LPC17 has a third and even a fourth MIDI IO port at TTL level so that the available two MIDI IO pairs are still free)+  * **the module can either be connected to a PC directly, or controlled from a second PIC or STM32** 
   * native support of various protocols (e.g. PitchBender, CCs, even Logic Control and Mackie Control Emulation)   * native support of various protocols (e.g. PitchBender, CCs, even Logic Control and Mackie Control Emulation)
   * support for 8 touch sensors   * support for 8 touch sensors
   * instead of TC4427 I'm using L293D now - not at least because of the integrated diodes.   * instead of TC4427 I'm using L293D now - not at least because of the integrated diodes.
-  * due to the direct motor control connections, the PIC is now able to generate PWM with 50 uS steps for improved motor speed control while a motor is moved +  * due to the direct motor control connections, **the PIC is now able to generate PWM with 50 uS steps for improved motor speed control** while a motor is moved 
-  * since the firmware is dedicated for this task, there was enough memory free to integrate advanced features, such as runtime-calibration and motor position tracing which are supported by MIOS Studio:+  * since the firmware is dedicated for this task, there was enough memory free to integrate advanced features, such as **runtime-calibration and motor position tracing** which are supported by MIOS Studio
  
 ===== Parts List ===== ===== Parts List =====
Line 34: Line 36:
 ===== Compatible Motorfaders ===== ===== Compatible Motorfaders =====
  
-  * ALPS RASON11M9 {{http://ucapps.de/mbhp/MF_NG_connection_diagram.pdf|Intercaonnection Diagram}}+  * ALPS RASON11M9 {{http://ucapps.de/mbhp/MF_NG_connection_diagram.pdf|Interconnection Diagram}}<sup>UCapps</sup> 
 + 
 +===== PIC Source Code ===== 
 + 
 +  * {{http://ucapps.de/mbhp/mbhp_mf_ng_v1_005.zip|MF_NG PIC Code}}<sup>UCapps</sup>
mf_ng_module.1470411744.txt.gz · Last modified: 2016/08/05 15:42 by psykhaze