latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Everything posted by latigid on

  1. 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!
  2. midiphy gates/clocks module

    Thanks for the feedback! Re: AOUT_NG: in the MIDIbox paradigm, CV/gate is split into AnalogueOUT and DigitalOUT modules. The assembly above is the DOUT side, which was previously available as a PCB build using a DOUTX4 module, but you needed to provide your own 3.5mm jacks. There have been various solutions over the years, like using Ken Stone breakout PCBs, also Altitude did a combination that had eight each of CVs/gates/clocks/triggers. The AOUT side will be a different design to AOUT_NG. I had a previous incarnation in through hole, but this version is more compact and simplified. (The other one had CV range switches and fine-tune control, but was only four channels in I think 10HP.)   Here's a teaser of transmute8 fresh from OSHPark (thanks for the image Peter!), not tested and won't be for a little while. Hope you like 1206 resistors (or 0805 if you wish!)! Best, Andy  
  3. DINX1 on MIOS8 no load signal on RC-line?

    Yep, should be the other way around. SER is an input, and the data flows out QH back to the Core.
  4. DINX1 on MIOS8 no load signal on RC-line?

    If you have an F4 32-bit Core, you can use MIDIbox_NG to debug DINs. The RC "pulse" at pin 1 should be every 1ms I think. Check the wiring/stripboard layout? Check the correct signals are sent from the PIC J9 (I think).
  5. DINX1 on MIOS8 no load signal on RC-line?

    CLI inhibits clocking in of data. If it floats, probably nothing will be read. SH should be high "most of the time" as this sends a constant data stream, even if the tail is empty. When RC pulses low, the inputs are read and shifted out. The number of SRs shouldn't matter. Did you try "set debug on" in MIOS? Not sure if that's enabled for PIC uCapps. Maybe there's another app you can test?
  6. DINX1 on MIOS8 no load signal on RC-line?

    What is pin 15 connected to? Should be 0V (ground). Please draw a nice diagram of what you have stripboarded, or compare carefully with the DINX1 schematic. Normally, pullup resistors are used. What are your switches switching to?
  7. MIDIbox CV V2 Concept

    I attempted to come up with a "standard" controller and TK. worked on the hardware a bit. I even have some of the control surface PCBs left if you would like to try, however I don't think the idea as it stood will be pursued any more. The fact is that an iPad or other tablet running Lemur gets you 90% of the way there and might be nicer than a 20x2 LCD? You can use SVN checkout software such as Tortoise to get the source and compile, no worries.
  8. 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!  
  9. Troubleshooting midiphy SEQ v4+

    At least on Windows you should power cycle the Core between updates. (EDIT: I mean close and restart MIOS, the MCU is automatically reset after updating.) If you really can't get it to boot/be detected any more, JPA0 is there to help on the wCore PCB. If you stuff this jumper, the bootloader will hold during startup. Normally you can then flash in another .hex again.
  10. binaire+octal

    From the album midiphy_euro

    midiphy gate/clocks/triggers module, 4HP
  11. Troubleshooting midiphy SEQ v4+

    Schade/dommage!  You might be able to remove the Matias switches (if really necessary) with your soldering iron heating both pins at once and pulling it out with the other hand/use a vice. A simple vacuum pump can also work wonders. If the LEDs still work, then the sink side of the matrix is okay. Not sure what could be fried just from pushing together.
  12. Troubleshooting midiphy SEQ v4+

    Hi, On lemec_L, left side and both versions, right side, the encoder can touch the header pins. Best is to trim both sides (encoder pins are easier) first and also put a piece of kapton tape or similar between. From the sounds of it, you followed the testing procedure and had all DINs working before soldering in the Matias? Please try to isolate/insulate first and see if that fixes the issue. You can also check if there are longer through-hole components (especially diodes) that short out in beween. If not, please upload a good photo of the rear of the assembly and I will try to help.
  13. midiphy SEQ v4+

    Cases should be ready any day now. They were undergoing final painting this past week. The supply will also be limited, but the next run will be larger. Please consider that we don't have a proper warehouse, so it's impractical to store dozens at a time. We also made a slight revision to the plates to make OLED cabling easier.  We understand that the cases are proving to be the bottleneck and we're working on the supply. Thanks for your patience! 
  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. Using AOUT with Buchla 1.2v/octave

    Maybe TL07x op amps have a limited voltage swing. Check that the output can reach 13.81 V with (I assume) +/-15V power supply (from the data sheet it looks like it should). +/-18V might have more headroom but is pushing the maximum specs. 
  16. Troubleshooting midiphy SEQ v4+

    Looks like R16 is not soldered correctly?
  17. Using AOUT with Buchla 1.2v/octave

    It's a good fix and totally okay from an electrical perspective. You're essentially multiplying by a different number as the DAC doesn't give the correct range by itself.
  18. Troubleshooting midiphy SEQ v4+

    No worries, you provided good info (voltages and pictures) and had a decent attitude. If it works, we're very happy!  
  19. Troubleshooting midiphy SEQ v4+

    Ah yep, set dout x 0|1 is the correct syntax. You could try the same on the second 595 chip, these would be dout 8--15. You've copied the same terminal data each time, but I assume you turned the correct outputs on and off. Note that pressing the up arrow on the computer keyboard will go through a history of the terminal commands.  
  20. Troubleshooting midiphy SEQ v4+

    Thanks for the voltages, so the issue seems to be on the sink side of the matrix.  As you're troubleshooting the _L board and the _R board works fine, it would seem as though the data is getting though correctly. Could you try the following commands in MIOS terminal: set dout d0 1 %turns first output on set dout d0 0 %turns first output off set dout d7 1 %turns eighth output on Here you manually set the pins, so this can rule out any errors from the software side. You can also try it with the .NGC loaded. When d0=1, the first four encoder switches should work when pressed. set d0=0, then d1=1 should allow the first four Matias switches. If the component values/types, cabling and soldering are all sound, then I'm beginning to suspect a dud IC. Could have been overheated or subject to static for example.  
  21. What does this do over other sequencers?

    I don't actually know the capabilities of the Cirklon. You can find the feature list here and see if it fits your style?  The SEQ is best if you can DIY, but we know of instances where others have offered units prebuilt. The SEQ has different track types that are either monophonic with lots of trigger or parameter layers, or polyphonic that simplifies the sequence to notes. I don't know what you mean by accumulators. You can use so-called loopback tracks to control other tracks. Watch the latest demo by TK. (ucapps youtube channel) Track 13 looks to have a slow clock divider that transposes other tracks
  22. Troubleshooting midiphy SEQ v4+

    It might be interesting to solder down the superflux cathodes, then you could check if the problem is on the sink side or the DIN side. IC2 is the sink side of the matrix; you can see the sink part of the matrix here on the left. MIOS pulses each output in turn and this allows the switches to conduct to 0V when pressed (also lighting LEDs when that column of LEDs is on). This registers as a switch press in MIOS by the 165 inputs going low.   IC3 is the DIN part of the matrix. D0-D7 represent the switch columns and there are eight per board from left to right. D0-D7 connect to the anodes of diodes located above Matias switches and beside MEC switches.   As you have a functional lemec board, you can compare voltages on the two. The only difference with the _R board is that there are three extra shift registers (74HC595) at the start of the chain.  Because you have some activity with encoders, the issue lies with either the DIN or sink side of the matrix. Do all encoders work? If so the SC, RC2 and SI lines are all fine. Check that the correct resistor networks are installed (also the orientation), check that you have +5V on all aforementioned 4148 diode anodes,   
  23. Troubleshooting midiphy SEQ v4+

    Soldering looks clean and it's correct to omit IC6 and R17/C7. Software-wise, how are you testing? Are the boards chained left to right or did you test each one separately? Using the _L configuration will not work if the first board is _R as the matrix is offset by three SRs. Hardware ideas: the transistor types are wrong or swapped, mixed up with a BAT diode etc. For the missing encoder, on lemec with the plate removed, check J3, 8th pin from the left, to pin 5 on IC5, 9th pin to pin 6, respectively. The pins should have +5V on them. If you (carefully) short the pins to 0V, do the encoder/DIN events trigger? If not it could be a cold solder joint or a short to 0V (e.g. IC5, pin 8). Now connect the plate PCB. You should have continuity back to IC5. If not, check that the pin header makes good contact with the through-board header.  
  24. Troubleshooting midiphy SEQ v4+

    Do the encoder pins contact the pin header below? Try trimming the pins, also isolate with a bit of tape.      
  25. Troubleshooting midiphy SEQ v4+

    Have you tried restarting MIOS Studio between updates? Jumper settings appear correct. You can also measure resistance between the USB B port (with power off) and PA11/PA12 on the socketed Waveshare MCU breakout, should be 22R.