Jump to content

latigid on

Frequent Writer
 View Profile  See their activity

  • Posts

    2,516

  • Joined

  • Last visited

  • Days Won

    147

 Content Type 

Posts posted by latigid on

  1. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by latigid on

    Good work!

    After ~10 years of soldering with a conical 0.5mm tip, I have recently discovered the joy of a 1.6mm chisel tip. It really is night and day with SMT as you get great heat transfer to the flat pads (always heat the pad if possible), then apply 0.5mm solder to the pin et voilà! 

    With a conical tip I always had to use the side of the iron for SMT and the heating was much more tedious. Still the conical tip is better for larger THT components, pots and jacks etc.

    I have both irons at hand and just plug what's needed into the soldering station :)

  3. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by latigid on

    It's been a while, sorry. The same jumper is on the Line Transmit board, is it closed? You have the option of external power, as there could be losses through the DB-25 cable.

    I've added the info for both boards in their respective BOMs. Sorry for any confusion.

  6. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by latigid on

    Just now, electrodancer said:

    ive set the shift registers in the hw file (10 and 11) but no gates clocks and no cv...also the power led on the aout-ng does not light up

    Not a good sign. How is the AOUT_NG being powered? There's an extra jumper on the midiphy Line Receiver that connects to the +5V buss. Is it closed?

    Wrong cabling? Let's see a photo of your setup. What Line Driver boards were you using for the older SEQ?

     

  9. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    6 hours ago, niles said:

    I checked continuity and everything seems fine. The cable is something I did have wrong at first, so perhaps I fried a MCU pin or two. Is there a diagnostic program or command I could run in MIOS Studio that would confirm the pins are 100%?

    I'm not sure if there's a tool for SD card diagnostics. There is a dedicated app for a "mass storage device", but it's only built for LPC/STM32F1.

     

    6 hours ago, niles said:

    I'm using shrouded cable sockets and they are oriented correctly I think (please see photos though).

    Sockets look okay

     

    6 hours ago, niles said:

    I did order a few more SD sockets (arrow has free one day shipping today :) so I'll replace that just in case. It was simple enough to remove.

    Worth a try. Once when soldering a DISCOVERY F4 Core, my sockets were overheated. I don't know exactly what happened, but the SD card actually overheated and burned up somehow when I inserted it. Take care when soldering the socket. If you can't manage the smaller pins (in the datasheet they have function names, not pin names) then try leaving them unsoldered. They aren't connected to the pin header (NC in schem).

    It might also be possible to overheat when soldering down the IDC shrouded header.

    6 hours ago, niles said:

    The SD cards I've tested all format correctly under windows. I found a 32MB one (canon SDC-32M) that is formatted FAT, and a newer 8GB Kingston SDHC (SD4/8GB) that is formatted FAT32. They only contain SEQ_L.NGC , the file from the first post in the seq v4+ thread. Both have the same result.

    The 32MB would be perfect! It might be useful to have a blacklist/whitelist of SD cards. At the moment I think mine are 4 GB, not sure of the speed.

     

    6 hours ago, niles said:

    2019-03-27_18-54-08_157.jpg

    The cable is assembled correctly but the leftmost socket might be skewed (or the cable was cut on an angle or it's an unhelpful camera angle). Check for shorts on the cable (e.g. by plugging into the sockets). Note that some pins are intentionally doubled up (see schematic).

     

     

     

  10. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted · Edited by latigid on

    Please provide pictures of the boards, cables and the make/source/sizes of SD cards.

    Did you use shrouded headers? If so, you can't plug the cables in the wrong way, unless they're incorrectly assembled.

     

    21 hours ago, niles said:

    Thanks for the ongoing help. Do you know how to format FAT8 on a windows 10 machine? I have been googling but can't find any program. I did find an older post by TK that says formatting via MIOS Studio is the best method by doing sdcard_format, but it fails with this:

    Try to format using some sort of FAT setting. Is the format successful in Windows?

     

    Quote

    If I had the cable backwards on one end by accident at some point would that have done some damage somewhere?

    Not seen before, but I guess so? You could've damaged the SD card, the MCU pins or both. Again, can you still format the SD cards or are they unresponsive in Windows?

     

    Quote

    If I lay the cable down flat, with the connector holes pointing up, the notches are on the same side of each connector. I assume that's the right orientation.

    That's right, but above you were saying that maybe the cables were backwards? Were they incorrectly assembled before? Shrouded headers or not? See above comments

     

    Quote

    Edit - Also just in case it helps, only the green LED has been lighting up. 

    J16E carries the LED signals too. If there was a "backwards cable", then something funny could've happend there. But you don't get many LED signals with _NG. More are active with the SEQ app.

     

    Here's the schematic. The SD card pinout follows the datasheet that you can get from Mouser.

    SD-J16E.thumb.JPG.6195d2df97f0bd2402800a

     

    Check for continuity of pins back to the Waveshare 407v board (with the power off). Check that adjacent pins are not shorted. Make another cable or use the one from an OLED at least temporarily (don't use the OLED cable!)  You can measure voltage at the SD card. You won't see much with a multimeter on the other pins, but you can use a scope or logic probe if you have one.

    Also, it is possible to overheat these SD sockets. What temperature settings did you use? Were you heating the pins for a long time?

     

  11. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Try to format the card, I think FAT8 is the best. Then try again. 

    If you've used shrouded headers, then the cables will always plug in the same way. When making IDC cables, ensure that the notch/nub points in the same direction relative to the cable strands unless otherwise noted. 

    Some SD cards don't seem to work, e.g. if the size is huge like 32 GB (MIOS will use a very small fraction of that).

  13. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    If you don't measure continuity from 0V (ground) to the pin, you can run a bodge wire as shown. This is viewed from the rear of the board. The via is tented, so the pin on the 2x25 header might be better, but you'll have to go around to the other side of the PCB (the headers are on the same side as the IC).

    5c99bf440b5d3_IC1Abodge.JPG.3a786fa480a9

  14. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    1 hour ago, gotkovsky said:

    Also, in the tutorial video (that I'm following closely), Peter says at 2:11:55 to jumper J15_S on the wCore PCB to 3.3V. Should I still do that if I power my V4+ with a 5V phone adapter? Or should I jumper J15_S to 5V?

    J15 sets the OLED voltage, which should always be 3v3.

     

    1 hour ago, gotkovsky said:

    I'm coming close to an end on the V4+ build, and just had a question regarding its power requirements.
    I'd like to power the SEQ without any computer, using the USB hub and a regular 5V/1A phone USB plug, if possible. I've read on the forum that MBSEQV4 power comsuption doesn't exceed 1A, is that still the same with the V4+?

     

    54 minutes ago, Smithy said:

    Thats a good question actually! 

    I wonder if Peter or Andy have a USB "doctor" stick to test, they're really quite handy.

     

    Peter's done it with a USB power bank. I think the total draw was 0.8A or less, but best for Peter to check in.

    • Like 1

  15. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    No problem. From your SMT soldering and parts placement it looks like you've taken a lot of care with the build. Some of the THT pins look like they might benefit from a bit more solder, so make sure you have a proper solder filet from the pad to the pin. Could be the light/angle of the photo though. 

  16. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Just now, gotkovsky said:

    Sorry about that, just edited my post!

    Yes, I tried to reflow all of them, checked for shorts or anything else but I'm still having the same issues.

    lemec_rear.thumb.jpg.ae900a18ca15bf0b893

    lemec_front.thumb.jpg.4dd8685f751f312df2

     

    I'm pretty sure your problem is that these parts are not installed. Make sure that you do have bussed resistor networks (9 resistors, not 5 resistors) and align the dot with the marking on the PCB (ask if you are unsure).

     

     

    • Like 1

  18. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    1. Please edit the post to not include such a long string of DIN messaages. A few lines will suffice. 

    2. Please upload the images to the forum so others can be helped when the offsite links no longer work. 

    The typical error here is an incorrect part or soldering for the 10k resistor network on the JA board (see previous posts in this thread). 

  19. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    1 hour ago, niles said:

    Lastly, I was able to load the project.hex file posted from Hawkeye in an earlier post, but is there a newer, official build by TK for this?  I have been looking and only found the SVN, no idea how to compile..was hoping the latest firmware binary would just be able to download somewhere obvious. I have a ways to go in this build and can only work a little bit at a time so I'm not too worried right now. However, if there is a seq v4+ firmware version specific to this kit, might be helpful if it's available on the midiphy page. Just a suggestion.

    The latest official firmware files are available from http://ucapps.de/mios32_download.html. There is also a thread where "pre-releases" are sometimes available:

    I would prefer to keep firmware in one location. I added the link to the parent page on midiphy.com, but unfortunately I'm not clever enough to make it clickable. Perhaps Peter can sort it out ;)

     

  20. Troubleshooting midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Just now, niles said:

    Thank you - I wasn't sure how much of that cable I'd need for this kit and was hesitant to tear it apart. 

    Recommended cable lengths are given at the end of the BOM here.

     

     

    Just now, gotkovsky said:

    Hello!

    I'm almost done building all the PCBs, and I'm having another issue uploading MBSEQ App on the Waveshare, just searched a few hours on the forum but couldn't find an answer.

    So I got MIOS Studio 2.4.8 running (on MBP High Sierra), but the MIOS32 midi I/Os don't show up on MIOS Studio (just displays << none >>). I tried several options but nothing worked so far (tried booting different versions of MIOS Studio, restarting MIOS Studio or PC several times, MIOS Studio on another Macbook running Mavericks too).

    Here's all the infos I could gather: 

    —Red PWR led on the Waveshare is lit.
    —VBUS led on the Waveshare is not lit.
    —Checked the soldering on all PCBs and nothing looks wrong.
    —Waveshare's pinheaders are not fully engaged on low-profile headers (but I can't seem to push them further).

     

    I'd greatly appreciate a bit of help is anyone has a clue, thanks in advance!

     

     

    Did you use the drop-down menu to select a MIDI port?

    Check all jumper settings and try to use the onboard USB micro to connect to your computer.

×
×
  • Create New...