latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Community Reputation

238 Excellent

About latigid on

  • Rank
    MIDIbox Guru

Profile Information

  • Gender Male
  1. Troubleshooting midiphy SEQ v4+

    Many thanks for reporting and I'm glad it works! Is the hub also connected to the computer and sending data that way? There is an OTG startup sequence where the devices have to decide who's the boss. Maybe things don't make it that far if there's too much going on with the datalines. Just speculation!
  2. midiphy Eurorack Expander Modules

    Sorry, I managed to upload one twice. The quell PCB functions as a terminator, so you clamp unused inputs to 0V.  
  3. IMG-20200524-112838.jpg

    © 2020 latigid on

  4. midiphy Eurorack Expander Modules

    I recently designed Eurorack versions of DIN and AIN, still need to test but hopefully in the next few weeks,   @Antichambre maybe you should start your own thread as to not mix up things, thanks. Have fun! Andy
  5. IMG-20200524-111714.jpg

    © 2020 latigid on

  6. IMG_20200524_111705.jpg

    © 2020 latigid on

  7. IMG_20200524_111651.jpg

    © 2020 latigid on

  8. IMG-20200524-111642.jpg

    © 2020 latigid on

  9. midiphy Eurorack Expander Modules

    Not sure I understand fully. You adjust the trim pot to get the scaling as linear as possible, i.e. the trimmer should be set so each octave step is as close as possible to the target voltage. Then you use the SEQ encoders to finely adjust for each volt setting. The DAC can't drive negative bits, so there is a limit to the lowest setting. But the remaining octaves should be very linear. Did you already see @Hawkeye's video on the calibration procedure?
  10. midiphy SEQ v4+

    Sounds like it could be a software bug, in which case the following thread is the place for it:
  11. Troubleshooting midiphy SEQ v4+

    One other idea: you could try plugging directly into the 407v board (mini USB cable). Here is the schematic, maybe some of the jumpers are helpful?  
  12. Out-of-stock parts for midiphy BOM tool

    Some Mouser parts have longer lead times at the moment. Here's a few suggestions: 595-SN74HC595DR -> 595-SN74HC595D (just non-reel packaging) 490-SJ1-3535NG -> 490-SJ1-3535NG-BE (blue) 594-K104K15X7RF53L2 -> 75-1C10X7R104K050R 806-KCDX-5S-S2 -> reichelt Conrad CR1206-JW-331ELF SMD resistors just use a 220R or 71-CRCW1206330RJNEAC WP154A4SUREQBFZGW Kingbright LED, tricky to find a frosted one, but basically any generic CC RGB LED will do, or a bicolour 3-pin is fine but normally not available in "nice" green. *** Feel free to post your suggestions or if you can't find a part.
  13. midiphy SEQ v4+

    There's a few settings in the HWCFG to check e.g. (search "fast") # the speed value for GP encoders which is used when the "FAST" button is activated: ENC_GP_FAST_SPEED 3 # Auto FAST mode: if a layer is assigned to velocity or CC, the fast button will be automatically # enabled - in other cases (e.g. Note or Length), the fast button will be automatically disabled ENC_AUTO_FAST 1 # the speed value for the BPM encoder which is used when the "FAST" function is activated ENC_BPM_FAST_SPEED 3   Can you check if altering these changes things to your liking? Of course, some features might have been "broken" by hard-coding functions. In the Wilba SEQ version, there was one common fast button, no matter what encoder was pressed. In the v4+ we have all of the encoders on dedicated DIN inputs (matrix) to allow for different customisation. 
  14. Troubleshooting midiphy SEQ v4+

    The v4+ does nothing different to your previous method: the ID pin is grounded when in OTG mode and floating otherwise. Maybe check pin PA10 is correctly grounded on the wCore PCB/breakout? Cabling issue or missing contact through the 2x25 pinheader? Perhaps the value for R3 on the USB board is too conservative and 100R would be better.  
  15. Troubleshooting midiphy SEQ v4+

    Hi George, I'm not 100% on how it all works and could be wrong, but to my knowledge you shouldn't see any MIDI data on the computer from the slaved device plugged into USBA. So my first guess is that you should unplug the computer; you can't (or shouldn't be able to) have the SEQ as both host and slave at the same time. You could then check the SEQ MIDI monitor and route it out a different DIN port. Second thought is that the controller (which ones, so we can consider making a whitelist?) does not initialise properly. Best, Andy