latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Everything posted by latigid on

  1. Troubleshooting midiphy SEQ v4+

    Thanks for the follow up! You're certainly not to blame for this, so I'll ask the fab what happened. Looks like the copper substrate was scratched from the beginning or some of the mask rubbed off before etching. Let us know privately with any subsequent order and we can spare you some $$ for the trouble.
  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. Control LEDs without HC595

    I think you need to define your parameters. How many LEDs? How many spare I/O or GPIO can you use? Does an LED matrix with multiplexing go far enough?
  4. Troubleshooting midiphy SEQ v4+

    Hi Adam, I don't fully get it: are you able to illuminate both superflux LEDs (red) in this column? Also, is it the _L or _R board and what is the version number? You can see the board trace should connect all "red" LEDs in this row, but the SJ part will not be connected to the LED until the resistor is placed. This sets the output for the MEC LED but you were talking about superflux?   I can see a scratch on the board in your picture, is it related? If you're feeling masochistic you could sand back the solder mask and see where the copper stops (if it does). If the trace I marked with a "?" really doesn't connect, I would suggest to use a 1k THT resistor as indicated with the red mark. It would also be possible to use one of the 2/3 positions, but the matrix addressing will need changing in the HWCFG file.  
  5. Quad IIc Midi R2 PIC Firmware

    You're welcome. Device IDs are hardwired using IO pins directly on the PCB (or selected with jumpers on oldschool I2C modules).  
  6. Quad IIc Midi R2 PIC Firmware

    Here you go: is the parent page with all info.
  7. midiphy SEQ v4+

    I mean RS-422 is supposed to drive almost a mile, but I'm not sure if the MIDIbox would like that :).  
  8. 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
  9. midiphy SEQ v4+

    Hi, We currently use this one from Reichelt: TK. suggests up to five metres (so <15') would work but I haven't heard otherwise yet.
  10. Impressive and elegant design crammed into a DIN socket with a 3.5mm jack output.    
  11. crimic - hamsterrad (art-music video)

    Might be my favourite one so far!
  12. midiphy Eurorack Expander Modules

    Hi Paul, The modules should be compatible with all Core versions. The digital gates etc. were typically done with GPIO pins for older Cores. Best, Andy
  13. 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!     
  14. IC not available anymore

    You cannot substitute for HC logic in this case. HCT is required to level-shift the logic to +5V, whereas a 3v3 3V signal pushes the threshold limits of a HC chip powered at +5V. 595-SN74HCT541N should be suitable.
  15. midiphy SEQ v4+

    True as far as I understand the structure of the chips, though I think the maximum current drawn could be 150mA per chip IIRC? Normally if they are overloaded the supply voltage begins to sag. In this case it's academic though, as we use bipolar driver transistors for both sides of the matrix. So the actual current could be somewhere near the ohmic value.
  16. midiphy SEQ v4+

    Four hours of stress testing just done. In MIOS Studio "set dout x 1" where 0<x<7 inclusive sets the sink sides active and  "set dout y 0" where 8<y<15 inclusive sets the source sides active. I tested a mixture of red, green and mixed LED colours. No burn out or overheating of any parts. Colour and brightness after the test are identical to those of a non-stressed board (running in normal multiplexed mode for both). This doesn't mean that you should run your matrix like this (and if you did you would lose control over LED and switch registration), but it shows that a "failure" with the LED drawing the full theoretical current will not instantly damage the LED. At least there will be enough time for you to notice and reset the unit :-).  
  17. midiphy SEQ v4+

    No worries! I know Peter and a few others ran a mixed colour scheme and it seemed to work out well, though the current drive through the LEDs might get a bit non-linear I think. Stress test is currently running with the "worst-case" matrix fully on, so no multiplexing. Half an hour in and nothings burned out yet. What do you think is a fair test time?
  18. midiphy SEQ v4+

    If you're concerned with the LED lifetime then simply increase the values of the RJ resistors to a current you are comfortable with. I would consider the probability of an LED matrix "freezing" in the way you describe as a low risk though.  
  19. midiphy SEQ v4+

    Not sure if this is a grumbling post about schematics not being supplied? You bought the PCBs, so you are welcome to the schematics if you send an email in reply to your order confirmation. Snippets of the schematics are supplied in part throughout the troubleshooting thread. This is generally a better way to provide targeted help to builders and I'm very responsive in that regard. So, rant over! :-) If that wasn't your intention, then I'm sorry. The LEDs are indeed multiplexed as is typical for MIDIbox projects and driven through bipolar transistors. The key datum is actually the peak forward current per chip, listed as 100mA. True, our multiplexing speed and fraction is slower and larger than the given conditions. All of the LEDs have been put through a burn-in test using the same circuit as the one in the SEQ, so we know that they are good. Also, these are superflux LEDs with much higher current-carrying capacity than your typical LEDs. Have fun building!
  20. midiphy Eurorack Expander Modules

    Hi, We currently use this one from Reichelt: TK. suggests up to five metres would work. So I guess that means 16 feet in Freedom Units. Unfortunately I couldn't find a decent one from Mouser but if you need to get all of your parts there,  571-1658613-2 plus 26-way ribbon could do the job (and would be less bulky than a cable). Another famous sequencer does it that way :).
  21. blm 16x16+x Costs - Calculation

    It's getting there! Next in the pipeline is the LoopA, then the BLM.
  22. midiphy gates/clocks module

  23. midiphy gates/clocks module

      Prototype of an 8x "DOUT" module. It is a simple build of two stacked PCBs called "binaire" and "octal". I reckon it can be done in an hour or less. In the SEQ v4+ context it can be configured as  8 gates, in combination with 8 CVs (in the works) 8 configurable clocks, or 7 clocks plus one start signal 8 triggers. Up to 64 triggers can be generated with the SEQ! Each output has an LED that illuminates with a positive gate. The modules are designed to be easily chainable, so decide how many are needed in your system. 4HP width. It would also work with other SEQ versions. More info to come!
  24. The J16 port is physically the same on the wCore, the E part just breaks out the LEDs (GPIO) and reset switch to the panel. The Waveshare board of course might have layout differences compared to the Discovery. The pull-up resistors for the J15 display port required changes that I didn't fully investigate, but it works so I'm happy :).
  25. STM32 F4 AIN problem

    I've reached the end of where I could offer help. If it was working before, switch back to a previous firmware version? I think TK. modified _NG to accommodate mixtures of AIN ports as inputs and outputs, so maybe something to do with that! Best of luck, Andy