latigid on

Frequent Writer
  • Content count

    2,106
  • Joined

  • Last visited

Everything posted by latigid on

  1. Troubleshooting midiphy SEQ v4+

    Hmm, I think that's the wrong part. The bussed network has a "2" prefix. Cross-check the part here: You should have only one piece of 652-4816P-T2LF-10K and two of 652-4816P-1LF-10K .   Best, Andy  
  2. Troubleshooting midiphy SEQ v4+

    Check pin 16 of the RN is connected to +5V. All 165 digital inputs (pins 3-6, 11-14) and pin 10 should be at +5V, possibly excepting 5 and 6 connected to the encoder. Check for continuity between DIN pins (they should typically not be connected). What is the part number of the RN just to be sure?   Photos would help, and a common problem is that the cable is not assembled properly. Try again with another cable.    
  3. How did i manage to fry my STM32 disco board?

    This one confuses me too. The blue button is the "boot hold" function, used to repair a corrupt upload or other. What you want to do is upload the bootloader app, which could be done from boot hold or the normal flash. Thereafter load _NG again.
  4. How did i manage to fry my STM32 disco board?

    The red LED continues to blink, no issue there.
  5. How did i manage to fry my STM32 disco board?

    You need to update the firmware of the ST-LINK, then it'll work properly after.
  6. midiphy SEQ v4+

    You can use a Disco board for a SEQ v4/v4+.  Have fun! 
  7. How did i manage to fry my STM32 disco board?

    Connecting a +5V power source to any 3v3 lines will do it.
  8. The HAARP, an Hardware Advanced Arpeggiator.

    Looks well thought out, nice job!
  9. 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. 
  10. 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.
  11. Troubleshooting midiphy SEQ v4+

    You'll get it, don't worry :).
  12. 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?
  13. Troubleshooting midiphy SEQ v4+

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

    Sure!
  15. STP16 as alternative to HC595?

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

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

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

    Keep on trying and it should work someday :)
  19. 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?    
  20. 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.    
  21. 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)
  22. 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).      
  23. 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!
  24. 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.
  25. New eurorack modules from midiphy - preview

    Not sure yet, more likely alu. Will try different panel styles.