latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Everything posted by latigid on

  1. 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
  2. Troubleshooting midiphy SEQ v4+

    Cheers!  Don't worry about the other board, the main thing is the SEQ lives! Well done! You can change the so-called TPD mode by navigating through Utility > Options #11. You can also test the hardware with SEQ_L.NG again; the CC 16 slider should light up the JA matrix. 
  3. 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!  
  4. Troubleshooting midiphy SEQ v4+

    Hmm, 2000 posts    How is pin 1 bodged? Do you measure +5V to it? I would bridge to the empty J89 socket, pins 3/4. You can see the wider trace to it in your image.
  5. Troubleshooting midiphy SEQ v4+

    You'll get it, don't worry :).
  6. Troubleshooting midiphy SEQ v4+

    As before, the common cause here is floating DIN inputs resulting from poorly soldered resistor networks (cold joints or incorrect polarity). Another possibility is that pins of the 165 are shorted together. Imagine if the clock line was shorted to an input, like pin 2 to pin 3, then you might get a weird feedback loop, or if pin 1 was shorted to pin 2, which would shift in the inputs on every clock. Did you swap the cables?
  7. Troubleshooting midiphy SEQ v4+

    A personal taste thing, but you can always make it your own :).
  8. midiphy SEQ v4+

  9. STP16 as alternative to HC595?

    Looks like a nice chip, worth a try! Pinout is much better than a 595.
  10. midiphy SEQ v4+

    Cool! Normally issues on the activity matrix are related to a dodgy cable or soldering on the ICs/resistor network.
  11. Troubleshooting midiphy SEQ v4+

    IC17 should be connected to power. There are two larger plated through-hole vias that you can consider using.
  12. Troubleshooting midiphy SEQ v4+

    Keep on trying and it should work someday :)
  13. Troubleshooting midiphy SEQ v4+

    If the switches work, your issue is on the anode side. Check the soldering around IC2 and R1-6. Reset with _NG loaded and don't load an NGC file. You can control the outputs manually with    set dout x boolean set dout all 0 set dout all 1   e.g.  set dout 15 1 set dout 6 0 turns on the lower anode row and sinks current on SW9,14   set dout 14 1 set dout 5 0 turns on the second-to-bottom anode row and sinks current on SW10,15.   Measure the output pins (15, 1-7) on the 595s to check the voltages. Might be a dodgy 595?    
  14. Troubleshooting midiphy SEQ v4+

    Hi Pat, Good that the other issues are sorted. For the multiple LEDs, load up _NG again and look at the DIN events (set debug on) when you push the buttons. Probably you get just one switch event per press/per depress. If the LED events are back to normal perhaps the HW config file is mis-configured? I'm a bit surprised that not all of the bottom row is on. Maybe SW17 has its LED in backwards? In fact, check all LEDs for correct polarity. Check whether pins of R1/R2 are shorted together.  Check whether any of the cathodes are shorted together. For this, test for continuity between the top-left pads (as viewed from the front of the MEC switches. As usual, pictures of the soldering would be useful for diagnostics.    
  15. Troubleshooting midiphy SEQ v4+

    Not sure. Disconnect all PCBs, connect lemec_L directly to the Core J89 (without JA) and load seq_R.ngc. You can also connect lemec_R directly to the Core, but you need the following modifications: ################################################################################ # Left Panel ################################################################################ ... # 8x8 Button/LED matrix - we emulate "normal" LED/Button functions: DOUT_MATRIX n=1 rows=8 inverted_sel=1 inverted_row=1 sr_dout_sel1=4 sr_dout_r1=5 led_emu_id_offset=1001 DIN_MATRIX n=1 rows=8 inverted_sel=1 inverted_row=0 sr_dout_sel1=4 sr_din1=2 button_emu_id_offset=1001   (i.e. offset the DOUTs by three)
  16. Troubleshooting midiphy SEQ v4+

    Maybe a short on the power rail? Or else soldering around pins 1/2/9/10? From the pictures, many of the joints look a bit "cold", where the solder forms a ball rather than a nice fillet. Try reflowing the pins. Pins 1 and 2 on 165s are the strobe/clock lines. They shouldn't be shorted together or to +5V/0V, and all 165s carry the same signals (check continuity between chips). Pin 10 is the serial input and receives serial data from the next 165 in the chain, so IC1 (pin 10) receives from IC2 (pin 9). You can compare voltages, signal traces etc. from the functional lemec_L. Also make sure that the connections between the plate PCB and le mec are correctly made (through-board headers).      
  17. Troubleshooting midiphy SEQ v4+

    Nice build, looks great! You can post in the main thread now if you want. Seems like you're done troubleshooting!
  18. Troubleshooting midiphy SEQ v4+

    Hi Alex, Maybe try pushing the 407v board in a bit more into the 2x25 pin headers? You can test for continuity between the top pin of the 407v and the bottom pin of the wCore PCB. You should have continuity on the pins on the broken-out USB PCB (D-, D+) all the way back to the MCU pins (PA11, PA12). Looking from the bottom of the USB PCB, the data connections are on the left of the USB B connector, but the five-pin 0.1"/micromatch should suffice. The D+ line is closer to the edge of the board where the plug comes in. Check the position of the host/slave switch on the USB PCB portion. Should be up for normal USB. Edit: pictures look okay from what I can see. Sometimes the forum dislikes PNG I think; you can try a different format.
  19. New eurorack modules from midiphy - preview

    Not sure yet, more likely alu. Will try different panel styles.
  20. blm 16x16+x Costs - Calculation

    Of course!
  21. Question about MIDI wiring

    Probably doable, but I think it would be easier and safer to interface outside of the box. Do you know how much physical space is inside? Photo? I don't see the benefit of plugging in the MIDI cable versus soldering it. Have you considered using a MIDI hub/4x4 router box? You could also use a USB router for the power connections.
  22. Troubleshooting midiphy SEQ v4+

    Sounds like you're nearly there, good job!  MIDI8 is basically plug-and-play. The MIDI output is essentially one resistor to the MCU pin and one pull-up resistor, not much more than that You can debug MIDI output by using the SEQ's built-in router. So you could plug a physical cable from OUT1 to IN2, then set the router IN2 to USB1 for instance. This can be compared against MIDI output with the track event set to USB. If you think about it, you should also be able to route piano-roll data from MIOS studio to any MIDI OUT port: in the SEQ route USB1 to OUTx. It does sound quite weird though, so maybe it is how the Neutron is interpreting the data? Can you try another synth? Please share your patch from the SEQ or initialise the track etc.
  23. Troubleshooting midiphy SEQ v4+

    Looks to be an issue with T7/R24/D16/R7 or pin 1 on IC2.
  24. New eurorack modules from midiphy - preview

    Do you need a new driver for the other DAC? MAX5500 seems like it has just as good performance and costs the same.
  25. Troubleshooting midiphy SEQ v4+

    Good that you fixed it, and good info for future builders, thanks!