Search the Community

Showing results for tags 'AINSER64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 6 results

  1. AINSER64 I2S Conflict

    I've been slowly working on integrating analog controls into the lovely Goom port for the STM32F4 and hit a bit of a roadblock.  The AINSer64 module won't initialize (no pulsing link light).  I can get it to work only if I disable the last line of the following function.  Commenting it out and returning 0, allows the AINSer64 to do its job, the link led pulses and turning knobs send debug messages with proper pin numbers and values. The Goom synth also works just fine without any of the AINSER code present.  Currently the AINSER64 is setup on J19 / SPI 2. s32 SYNTH_Init(u32 mode) {        // initialize the AINSER module(s)   AINSER_Init(0);   // start task   xTaskCreate(TASK_Synth_Update, "SynthUpdate", configMINIMAL_STACK_SIZE, NULL, PRIORITY_TASK_SYNTH_UPDATE, NULL);   xTaskCreate(TASK_AINSer_Scan, "AINSerScan", configMINIMAL_STACK_SIZE, NULL, PRIORITY_TASK_AINSER_SCAN, NULL);       //use J10A.D0 for performance measurements   MIOS32_BOARD_J10_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP);   // start I2S DMA transfers   return MIOS32_I2S_Start((u32 *)&sample_buffer[0], SAMPLE_BUFFER_SIZE, &SYNTH_ReloadSampleBuffer); }   I2S is enabled in the config file.  I saw that it can conflict with the SRIO SPI, tried setting SRIO_SPI to 0, with no luck.  I wasn't sure if that applied here or not.   Have tried this same code with ReloadSampleBuffer as an empty function, with the same results.  I'm assuming the issue is somewhere in the I2S_Start function, but reading through that I didn't notice any obvious issues.   Other AINSer apps like MIDIO128 work fine.  I did have issues with the Jitter Monitor though - it just scrolls endlessly, returning empty results for all modules.  I haven't delved deeper into that since the module was returning results without any issues outside of trying to implement it in Goom. Any insight into what might be happening here? Thanks Jeff
  2. Hi !!! Why can not I use potentiometers over 10K? I noticed that the 50k (linear B) potentiometers connected on the ainser64 board do not send CC = 63 when it is midway (5V / 2 = 2.5V), but sends CC = 63 when it is just over halfway down (2.90 V) at the entrance of 4051. Sorry, my english.   Tks, Marco
  3. After over a year of development, I would like to start documenting my Midibox_NG project in this thread to collect as much information as possible for similar future projects. The idea is to keep all findings, questions and struggles concerning this projects in one thread to keep myself organised and to help future digital/analog synth developers. As the title predicts, the goal of this project is to design and develop an all in one box digitised analog synth, similar to the MiniMoog Voyager. The synth will be controlled solely over midi. An LPC17 with Midibox_NG running acts as the main brain to read digital pots and switches of the control panel, save and recall presets as well as to drive the synth through multiple analog and digital outputs. Analog synth hardware: 1x LFO 2x Modulation Bus 3x VCO incl. waveshapers as well as additional loops for other effects than the waveshapers (documented on: 1x Noise generator 1x Ext_In 1x Mixer stage 1x 5Pulser ( 1x Ring modulator 1x Phaser effect 2x Moog ladder LP filter (to create a stereo effect through filter cutoff spacing) 1x Moog T904B HP filter (to create a band pass together with one of the LP filters ( 2x ADSR (for filter and volume) 1x Stereo VCA 1x Headphone preamp 1x +/-15V & +5V switching power supply (I learned, that it is much easier to develop circuits with the additional "headroom" of +/-3V in comparison to a +/-12V supply) 1x Power board to generate +/-12V for the AOUT_NG modules as well as +10V clean reference voltage.   Resources All the analog circuits are redesigned and relayouted to be uC controllable. They are mainly based on the following modules: - Ninni Bergfors' Moog based bergfotron modules ( - Original Moog D schematics ( - Original Micromoog schematics ( - Yves Usson's Yusynth ( - René Schmitz's modules ( - Carsten Toensmann's Moog Modular Clone ( - Vinnui's Modbus concept ( The original idea was to use the Moog D schematics solely and as many original parts as possible. But after already acquiring many old parts for a reasonable amount of money, I dumped the idea when the last Chinese seller of UA726 remakes went off market. However, I don't regret the decision, as I am very happy with my results so far with more modern parts, which are not nearly as energy hungry as the old stuff. Midibox Hardware: 1x LPC17 core module 1x KS0108 based graphic LCD 1x SD card reader 1x AINSER64 module 1x DIO_MATRIX module 1x DOUT module (own design with partly high power shift registers for switching relays) 4x AOUT_NG modules Development Roadmap (fully implemented, partly done, not touched yet): - HARDWARE Power Board - HARDWARE Midibox modules (excl. DOUT) - HARDWARE VCO & waveshaper board (incl. trimming & tuning) - HARDWARE LP filter  - HARDWARE HP filter & filter switching circuit - HARDWARE 5Pulser - HARDWARE Ring Modulator (on the breadboard and PCB layouted) - HARDWARE ADSR (PCB layouted) - HARDWARE DOUT module - HARDWARE control panel pots & switches  - HARDWARE Mixer including overdrive LED circuit - HARDWARE VCA & headphone preamp - HARDWARE LFO, MOD BUS, Noise generator circuits and PCB - HARDWARE Casing - HARDWARE Phaser (planned as a seperate module, since not enough AOUTS available) - SOFTWARE Utilising AINSER64 and AOUT_NG at one port () - SOFTWARE Controlling multiple AOUT_NG modules at once () - SOFTWARE VCO octave switch option (thanks TK) - SOFTWARE Multiple rotary switches locking each other out (softwarebug ironed out, thanks again, TK) - SOFTWARE Controlling Digital switching ICs (binary input) by DOUTs (signal switching related topic) - SOFTWARE synth fine tuningrange (+/- 3 semitones, steps as fine as possible) -> solved in the analog section, without midibox assistance - SOFTWARE VCO detuning -> semitone detuning works, free detuning not implemented in MBNG) - SOFTWARE Midibox_NG menu structure -> initial work done - SOFTWARE Preset save and recall - SOFTWARE Midi control of parameters (excl. tone & pitch bend)

    I'd like to buy an AINSER64 (maybe a couple of them) or AINSER8 boards or modules
  5. AINSER64 problems

    Hi, i'd like to have some help with my AINSER64 used in a MIDI128IO config :   i've mounted the unit, 'shortcuted' several unused inputs. When i plug it to the core, the yellow and red lights light on. But the green 'link' one sometimes remains lit, or unlit. that seems to indicate a problem. In MIOS Studio, i see a bunch (i guess 64) of CCs going to 0 when i unplug the AINSER. Any idea of what i am doing wrong ?   Thank you,   louis
  6. Is this possible, or do I need to get another AINSER64 board?     I'm building a keyboard controller. I have 1 AINSER64 with all the 64 inputs being used, can I chain a kb module to it? In other words, can I simply connect the J1 output from a kb module to the J2 input on my AINSER64 board?