latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Everything posted by latigid on

  1. Troubleshooting midiphy SEQ v4+

    Nice to hear you got it resolved!  The (tented) via that you mention is the SO signal, so that ties in perfectly with your observations. The likely short was to 0V, so the 595 registers never received any bits to shift in. Best, Andy
  2. Troubleshooting midiphy SEQ v4+

    Please post your troubleshooting issues here and we will do our best to get everything up and running! The more info you provide, the better the answer can be formulated. What did you try so far? What wasn't working? Pictures, pictures, pictures!  
  3. blm 16x16+x Costs - Calculation

    I'm also looking forward to the new design :)
  4. Troubleshooting midiphy SEQ v4+

    That's the correct orientation for RNs. I think the set dout command should still work after an .NGC is loaded. If you can't set the DOUT pins, then the sink side (cathodes) of your matrix don't work. As the behaviour is common to both boards, my guess is that there is an issue on the Core or one of the connecting cables. Check IC1B pins 4/5/6 (4=0V, 5=buffer output, 6=buffer input for SO) and back to PB15 on the MCU. It could be a soldering issue with the J8/9 header, the IC or that the header pins don't make sufficient contact to the female connector or similar. Check IC1B, pins 11/12/13 (RC1) and back to PB12 on the MCU, though the shift in should still occur on the RC2 pulse, which from your working encoders suggests that part of the SRIO chain is functional.  
  5. Sure you can buy protoboard without copper or just drop a normal piece in the etching solution or even file off the metal. It's also no issue to widen some of the holes.
  6. Troubleshooting midiphy SEQ v4+

    How are your 10-pin resistor networks oriented? The 74HC165 inputs of IC3 should be at about +5V You haven't soldered the switches in, so are you confident that you are properly closing the switch pads? Maybe try to bridge them with metal tweezers or similar. Make sure set debug on is active. You should be able to control the 74HC595 pins (or resistors R1-8 from the MIOS terminal with set dout x 0|1. Each 595 has 8 outputs so IC2 is 24-31 for _R and 0-7 for _L. During normal running of the (correct) .NGC you should measure some voltage on the pins of IC2, which controls the sink driver transistors.  
  7. How about veroboard/perfboard? Needs fairly standard spacing to work though.
  8. Troubleshooting midiphy SEQ v4+

    Photos of the rear of the PCBs would be good. Did you measure any input with set debug on?  Try connecting only JA and test with seq_l. Try connecting only lemec_l and test with seq_r. 
  9. midiphy Eurorack Expander Modules

    Hello, Peter made an awesome video (4k quality!) demonstrating the assembly of the following modules Euroceiver (line driver receiver in the rack), power distribution A1 Expander (AOUT based on MAX5500) D1 Expander (DOUTX1 for gates plus protection) D2/D3 Expanders (likewise for clocks and triggers) Feel free to use this thread for any discussion or troubleshooting. Have fun building your modules!     
  10. midiphy Eurorack Expander Modules

    What is the jumper setting with J5? Choose USB to power it this way. (check the +5V rail is not shorted to 0V)
  11. MIDIbox SEQ V4 Release + Feedback

    Thanks for the clarification on the CV channels. I could see a usecase for four modules if the velocity function was added, which I didn't remember BTW! This could add some expression, e.g. as a mod source mixed into a VCA -- great! And the accent trigger on the spare gates is awesome. For the drum triggers, I figured it was a code issue, as the clocks are easy to calculate in advance. In the meantime I think Andrew implemented a pulse stretcher in hardware, but if it is not too much effort I'm sure more software flexibility would be welcomed. Besides, we have the option of the standard trigger length, which I guess is one "step" long? Best, Andy  
  12. MIDIbox SEQ V4 Release + Feedback

    I find the proposal too cryptic. It would IMO be more intuitive to display more information on the FX page/menu.
  13. midiphy Eurorack Expander Modules

    Awesome, have fun with the CV! A small case is a sensible idea as it can keep the modular addiction contained :) Thank you for the framework and codebase to enable development of these modules. Best, Andy
  14. midiphy SEQ v4+

            We're just about ready for launch of the new SEQ v4+. This thread serves as a proper introduction, you can also ask questions on hardware etc.  I first became aware of the SEQ around 2008. This was about the time of the migration point of V3 to V4 and the Wilba design. I finally got my hands on a Wilba front panel in 2012 and I was rocking the hardware soon after. Around the end of 2016 I felt there was room for improvement.  a number of my TL1100 buttons were failing on my unit there was still no "standard" case available, also the rear panel was not well defined the PCB supply situation was (IMO) non-transparent and confusing for new users I had ideas about hardware changes What started as a simple question morphed into a multi-page idea thread. It was clear that the idea of incorporating a 16x4 matrix was not feasible from a software perspective, but it at least catalysed the idea towards a flexible "selection row" and other handy features. i liked the idea of mechanical keyswitches for their quality and very reasonable price. I then worked on a concept of illuminating these, finally settling on a misused superflux LED through a Matias switch. It became clear that a "complete solution" would require redesign of all of the boards, so I spent the winter of '16/'17 doing that. This entailed sourcing hardware items such as high-quality OLED displays, Matias switches and keycaps, a new Core breakout board etc. I periodically checked in with @TK. to confirm the right direction for the hardware (matrix routing and button features). Without saying, the SEQ platform is an incredible piece of work and TK. deserves a lot of credit and praise. From the start, I was in contact with @AdrianH about potential case designs. He has taken all board outlines and done the CAD work himself. I think you will find the case an excellent solution to cramming a lot of hardware inside while keeping the panels clean.  Peter @Hawkeye is the co-partner of MIDIphy. He handles the business side and also webdev. Perhaps more importantly, he is a very enthusiastic builder and documenter of all the designs. Normally I will do a test version, but the product photos and demos are usually his. I have spent endless hours discussing and debating/reasoning with him and there is always a positive and fruitful outcome. Hats off to you!   So: thanks for all of your interest so far. The aim is to provide you the best opportunity to build your very own SEQ. Andy --- Video Build Tutorials ---   --- MIDIbox NG Downloads (for testing) --- SEQ_L.NGC fluxtest.ngr
  15. midiphy SEQ v4+

    #21 ! and Holy Modular Batman! That's all DIY too !!?? Awesome!
  16. seqv4 problem

    Note that the Wilba board is wired in a way that the switch bodies carry some signals too. Think of the switch with two halves.  A A' B B' When the switch is not pressed, A still connects to A' and B to B'. Think of it like a clipped resistor leg soldered between the two PCB pads. The idea/function is to act as a "bridge" to avoid lots of vias or a 4-layer board, as you can effectively jumper the signals over and under each other. When you press the switch, then the switch acts as you think it should and connects parts A + B. Naturally all contacts are connected when the switch is depressed.   I would be tempted to load MB_NG and manually check the functions. E.g. you can read DIN events with set debug on (short the "cathode" part of the switch to 0V/ground) and simulate a matrix with set dout x y and try to gauge if the switch works that way.
  17. Troubleshooting midiphy SEQ v4+

    Hello, I can't offer much help because I can't quite understand the things I've highlighted in bold. If you can clarify those points I'll do my best. At a guess, the problem might lie with IC4 as it processes channels 7+8.
  18. Troubleshooting midiphy SEQ v4+

    Woohoo! If you wish you can post a picture in the main thread and claim your serial number :)  
  19. Troubleshooting midiphy SEQ v4+

    Try the boot config on flash. Also rescan devices in MIOS Studio normally doesn't work. At least for me I have to restart each time the MIDI device changes i.e. after each firmware update and reset. Consider the following troubleshooting earlier in the thread:   Good luck!
  20. Troubleshooting midiphy SEQ v4+

    And how was the display issue resolved btw?
  21. Troubleshooting midiphy SEQ v4+

    Did you restart MIOS Studio after updating? You say Discovery, but are you using one of those or a Waveshare 407v board? If it's the latter, what are the settings on the switches? What jumpers are present? You can stuff the JPA0 jumper on the wCore board if you need to reflash from bootloader hold mode.
  22. I can't quite picture the concept, could you draw something?
  23. Troubleshooting midiphy SEQ v4+

    Always check for shorts! On experience this is typically caused by a bad cable or excess copper on the connector end shorting on the OLED PCB. Depending on when your parcel arrived Peter might have put a piece of kapton tape on the OLED. You can try with a piece of paper or tape. Also check R33D on the Core is 560R.
  24. Troubleshooting midiphy SEQ v4+

    Do you still get a DIN event in MIOS Studio? Is the switch soldered in properly? The associated diode? If the other switches in the column work, then the matrix is okay and the issue might be with the LED itself or the switch of course.
  25. Troubleshooting midiphy SEQ v4+

    Check T14 and R14! Do you measure any voltage out of pin 2/R14? Follow that down to T14. When you read the T14 label right way up, you should have continuity to R14 on the top-right pin, +5V on the top left pin. The bottom pin is the source current for your green LEDs on columns 3/7.