Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Everything posted by latigid on

  1. Great job #26! :) That's a phenomenal achievement for a first DIY.
  2. http://www.midibox.org/dokuwiki/doku.php?id=seqv4plus_jog
  3. As well check the polarity of the diodes and that no LED legs are broken.
  4. That's the SRIO chain, good luck!
  5. Maybe the resistor network is soldered the wrong way around? Have you checked the cables for short circuits? Are other boards connected in the chain? What MIOS events do you see with set debug on?
  6. Hi Robert, what resistor network is installed?
  7. Sorry, the bottom of the case is welded by the corners. Btw, the seq_r.NGC file was completely the wrong thing. https://github.com/midibox/mios32/pull/8 but still needs to be approvied by TK. If you post a picture of the finished unit you get your serial number!
  8. The clear ones are on midiphy if that helps.
  9. If you can't get a vice, this is also a nice sort of tool: https://www.dicksmith.com.au/da/buy/bourne-electronics-idc-plug-crimper-crimp-tool-t1540/ Vice is nicer though, as once the cable is in and the connector is in place, you can control the angle of the cable to avoid shorts and overlaps.
  10. Awesome to hear! Most of the time it's the cables ;-) For seq_r.ngc testing, it's possible that .NGC file is buggy. I was baffled as to why the hardware would be fine in one config but not the other. It's something to check. For now, it is of course fine just to test with the _l config file and swap boards around for the finale. Sorry about the bugs and hope to see the SEQ running soon!
  11. Should work, just remember to use the correct SEQ HWCFG file. Like the .NGC, the left/right suffix refers to the position of the JA board. You can also add boards one by one for the _NG testing, good idea. It would even be possible to make a custom .NGC based on the _R file and adjust the shift register addressing to test lemec _R first in the chain. You need to adjust the positions of the shift registers because there are three extra ones (that go off to the JA matrix) before the "main" BLM and encoder scanning ones. Maybe some cables are twisted? They should run in a nice chain, correct? Do all of the IDC shrouded header notches have the correct orientation? You might consider reformatting the SD card or reflashing the app.
  12. I faintly remember an issue like this where the Core OLED power jumper was not installed, also check OLED cabling and R33D. This one:
  13. A few steps forward... :) The seq_r (or _l) file must be loaded to trigger LED events with the pushbuttons. Check that MIOS Studio is sending events on Ch. 1 for the JA matrix. Check that there is sufficient clearance between the board stack and isolate the J8/9x pin headers if needed.
  14. Trying the other encoder board means you swapped the other SEQ-plate onto le mec _R? Then the issue is probably on le mec_R. The encoder pins for ENSW3 are connected to pins 6 and 7 of J1 for both PCBs of the stack. Pin 1 is identified with a square solder pad (on the left when viewed from the top, so right-to-left if you're looking at the bottom of le mec). IC1 is the 165 shift register reading this encoder. You should measure continuity to pins 3 and 4 from the encoder pins. If not, check the soldering on the headers and that the interconnections are sound (were longer male pinheaders used?). You can also carefully short pins 3 and 4 to 0V (ground) and see if DIN events are registered. Use "set debug on". Here's a composite of what I wrote above:
  15. Glad you're having fun! Something to do while locked indoors! :) You should find "Do Not Fit" notes on the BOM page (scroll down) https://www.midiphy.com/en/shop-details/137/47/midibox-seq-v4-lh-full-essential-kit- Just say if you need specific advice for a particular board. If you run out of shrouded headers you could also use a normal 0,1" dual pin header row.
  16. Wow, looks awesome! Thanks! I know what you mean about side viewing though, sometimes you're peering into the next switch. Something like this is also used (I have no experience with it): https://www.keyboardco.com/product/filco-danish-and-norwegian-part-ninja-keyset-and-key-puller.asp (or just the one on mech https://mechanicalkeyboards.com/shop/index.php?l=product_detail&p=1411 ) With a different keycap set, go figure. But the wire puller grabs the diagonal edges. Good if you have to pull a whole QWERTZ/Y layout and have no single rows :)
  17. Can we see? Would be the first SEQ with them! What tools did you use? A wire puller?
  18. Sounds about right to me (could be a voltage meter/probe thing)! But if you've already ordered the replacement it wouldn't hurt to swap it.
  19. All good, happens to us all! Without any input (i.e. DAC is not sending any voltage) all octal LEDs should be red, because 0/2048*gain - 5 = -5V. This also assumes all of the LEDs have the correct orientation. (As a sanity check, you can test the octal board with a binaire board to verify that all LEDs can be controlled.) It's possible that the op amps didn't appreciate the reverse power or the heat or both. So I would be tempted to replace all TL074s. Measure on both sides of R1, do you get a proper +5V reference? If not, consider replacing the LM4040. Viel Erfolg!
  20. What rail is shorted? I always measure +12V-0V and -12V-0V or any rail to 0V before powering up. Photos of the board would be useful. Do all op amps have the correct orientation? What about the electrolytic caps? Check the pin headers J1 and J2 for shorts. 0V pins are in the middle, rails on the outside. The schematic just has all of the 1206 caps lined up, so it would be easiest to tell you where to look. It is a pretty simple circuit: the +12V is on op amp pins 4 and the adjacent caps (C6/8/10/12), -12V on op amp pins 11 and adjacent caps (C7/9/11/13). Check all around the power section C2-C5 and the beads L1/2 R1 is the voltage reference, so check there too. Good luck! Andy
  21. J19 should work as connected! What rail is shorted? I can show where the rail is on a layout, that's probably easier. I would say to check the cable, but you're using a flying bussboard, so if another connector is fine then the issue must be on the transmute8. Best, Andy
×
×
  • Create New...