Jump to content

latigid on

Frequent Writer
  • Content Count

    2,362
  • Joined

  • Last visited

  • Days Won

    130

Posts posted by latigid on

  1. 3 hours ago, gresade said:

    I want to extend my Midibox SEQ V4 with CORE_STM32F4 and V4+ firmware that is based on wilba CS frontpanel with midiphy PCBs. But I did not find schematics to check the connector pin signals, if they are compatible. From first sight it looks like it may be possible. Specifically I want to use:

    Sure, all parts and ports are compatible.

     

    3 hours ago, gresade said:
    • RES-SD PCB to add a SD-card socket (this one is not super important)

    You can also use a wCore if you prefer to breakout your SD card and LEDs to the rear panel, otherwise the DISCO core should work without requiring RES-SD. The wCore J16E header is a combination of J16 plus the LEDs on the DISCO board plus reset.

     

    3 hours ago, gresade said:
    • MIDI8 PCB instead of using the longer-size 2xMIDI_IO

    Just as you wrote

     

    3 hours ago, gresade said:

    The I2C header is 1:1 pinned with the corresponding I2C header on the Core. So it is more convenient to wire up. You can of course go for 8x I2C outs with the firmware "hack", but this was not implemented in the midiphy SEQ v4+ on TK.'s recommendation. Still, it was shown to work in at least one case, so if you feel it is worth it, go for it!

     

    3 hours ago, gresade said:
    • LINETX PCB for the line transmission to eurorack extension

    Basically the same

     

    3 hours ago, gresade said:
    • Eurorack modules (I read they should be compatible somewhere)

    Yes, all fine, AOUT (not AOUT_NG) in the SEQ config.

     

    3 hours ago, gresade said:

    Are the connectors on these boards compatible to the  CORE_STM32F4 connectors? Is there a documentation on the board schematics (especially the connectors pinout)?

    There are schematics on the wiki but all was designed to be 1:1 pinned with existing boards.

     

    3 hours ago, gresade said:

    Looking at the I2C PCB , there are 4 flat-cable connectors at the bottom at the board, what are they good for? I need more Midi outs, not ins, so maybe sticking with the MIDI_IO and using two I2C PCB to get 8 outs may make more sense (especially space wise), the Heidenreich case has not so much space.

    The I2C modules can theoretically connect analogue inputs and the ADCs are quite decent. So these headers are used to connect the AINs. In practice there is nothing in the software to scan them, so the headers should remain unpopulated unless you plan to write I2C drivers/modify the app.

    Greetings,
    Andy

     

  2. Probably MABPM 5S. DIN sockets are quite standard -- no surprise :)

    To be extra careful, measure the distance between pins at the edge of the PCB. Should be 10mm but there are two standards, hence both can be used on the PCB (two pairs of holes). 

  3. I have the same "IDC crimping tool" but favour simply using a bench vise. For micromatch MOW cables I leave the polarising tab outside and it works well for me. If you have different tools that work for you, all good!

    As far as testing other cable types go, there is a plan to build a "backpack"/"shield" that spans across the IDC16s. Then in theory any connector could be wired in. 

    It's a really fun project to build and you can see it working straight away. :)

  4. Hi Alistair,

    Generally I would only populate parts where there is a silkscreen indicator. This is certainly a double-sided board and the Core is quite a basic circuit, so you won't need any jumpers I am 99% sure. All pin headers seem to be indicated with a J prefix.

    Any plated holes that don't have a corresponding silkscreen mark are probably vias that join the top and bottom copper planes. You will probably be able to see the copper tracks leading to the vias from the difference in colour. Or if there is no track, the via connects to a 0V/ground plane But yes, it is harder to make out with black solder mask!

    If you are unsure, put your multimeter in continuity test mode (or resistance) and check the electrical connections. 

    Best,
    Andy

  5. Is it a two-layer board with green soldermask? Then no bridges are required.
    If it is a single-layer board, find the "quickview" or .brd file on uCapps. Probably the red wires represent the top bridges, with blue as the bottom layer already patterned on the copper side.

    Feel free to post a picture of your board here to check.

  6. You could write an NGR script to address LEDs in sequence:

    https://github.com/midibox/mios32/tree/master/apps/controllers/midibox_ng_v1/cfg/midiphy

    It is a very hacky script and could be much nicer with a few for loops.

    You can use the MIOS terminal command

    set dout all 1

    (or 0 if the cathodes sink into 595 inputs). It really depends on your setup, whether you have transistors, whether you drive LEDs in a matrix etc.

    You will need a better +5V PSU though as whatever MCU you are using might drop out of regulation with too much draw.

     

  7. Not sure if it is supported as I think it expects a Standard Control Surface (SCS). 

    To change the "LCD configuration" you first must upload the bootloader app and choose the appropriate LCD type (including OLEDS :) )

  8. Some people noticed that the LoopA can get stuck in booloader hold mode. As a potential remedy, install resistors R101 and R102. If you don't have the exact values it doesn't really matter. JPA0 should be left unjumpered except if you want to enforce bootloader hold.

    With the resistors installed the state of PA0 is properly defined rather than floating. If you don't notice the issue, no need to change it! The BOM is updated to reflect this.

×
×
  • Create New...