ilmenator

--

Yeah, I've lost pads 10 and 11. 10 probably doesn't matter because it seems as if it was solitary with no connection leading towards it, but 11 seems to be the one going to the via hole next to it. Where does this connect to? I will run a thin wire there...

I was thinking of clipping the legs carefully one by one and then removing them as I proceed - has anybody tried this before?

Thanks Andy, that was the hint I needed. Looks like my "client" ordered the wrong parts - maybe he used an old(er) BOM version? Just a guess, I'm not going to check this further. Now let's get creative with the removal of the bad boy...

Having a problem with the JA board here, which seems to act like an antenna. I get lots of MIDI messages in MIOS Studio when doing the MBNG check, and LEDs randomly flash. When coming closer with my hand and when turning the PCB in my hand, random activity shows. [707799.972] 92 2b 7f Chn# 3 Note On G-1 Vel:127 [707799.976] b0 12 01 Chn# 1 CC# 18 = 1 [707799.976] 90 41 00 Chn# 1 Note Off F-3 (optimized) [707799.980] b0 12 02 Chn# 1 CC# 18 = 2 [707799.983] b0 12 03 Chn# 1 CC# 18 = 3 [707799.983] 92 2b 00 Chn# 3 Note Off G-1 (optimized) [707799.986] 90 41 7f Chn# 1 Note On F-3 Vel:127 [707800.071] 92 2b 7f Chn# 3 Note On G-1 Vel:127 [707800.075] b0 12 04 Chn# 1 CC# 18 = 4 [707800.075] 90 41 00 Chn# 1 Note Off F-3 (optimized) [707800.079] b0 12 05 Chn# 1 CC# 18 = 5 [707800.082] b0 12 06 Chn# 1 CC# 18 = 6 [707800.082] 92 2b 00 Chn# 3 Note Off G-1 (optimized) [707800.085] 90 41 7f Chn# 1 Note On F-3 Vel:127 [707800.131] 92 2b 7f Chn# 3 Note On G-1 Vel:127 [707800.135] b0 12 07 Chn# 1 CC# 18 = 7 [707800.135] 90 41 00 Chn# 1 Note Off F-3 (optimized) [707800.139] b0 12 08 Chn# 1 CC# 18 = 8 [707800.142] b0 12 09 Chn# 1 CC# 18 = 9 [707800.142] 92 2b 00 Chn# 3 Note Off G-1 (optimized) [707800.145] 90 41 7f Chn# 1 Note On F-3 Vel:127 [707800.191] 92 2b 7f Chn# 3 Note On G-1 Vel:127 [707800.195] b0 12 0a Chn# 1 CC# 18 = 10 [707800.195] 90 41 00 Chn# 1 Note Off F-3 (optimized) [707800.199] b0 12 0b Chn# 1 CC# 18 = 11 [707800.202] b0 12 0c Chn# 1 CC# 18 = 12 [707800.202] 92 2b 00 Chn# 3 Note Off G-1 (optimized) [707800.205] 90 41 7f Chn# 1 Note On F-3 Vel:127 [707800.251] 92 2b 7f Chn# 3 Note On G-1 Vel:127 [707800.254] 90 41 00 Chn# 1 Note Off F-3 (optimized) [707800.255] b0 12 0d Chn# 1 CC# 18 = 13 [707800.258] b0 12 0e Chn# 1 CC# 18 = 14 [707800.262] b0 12 0f Chn# 1 CC# 18 = 15 or also [707853.154] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.175] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.214] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.235] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.256] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.295] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.316] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.337] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.355] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.376] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.414] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.436] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.495] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.516] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.534] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.555] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.594] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.615] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.675] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.696] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.756] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.777] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.795] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.815] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.876] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.896] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.914] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.935] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.957] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707853.977] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707853.995] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707854.016] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707854.034] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707854.055] 92 2a 00 Chn# 3 Note Off F#1 (optimized) [707854.076] 92 2a 7f Chn# 3 Note On F#1 Vel:127 [707854.097] 92 2a 00 Chn# 3 Note Off F#1 (optimized) are examples of what goes on. 595s and the 165 are soldered properly, 1N4148 diodes are in correctly, as well as the LEDs. I can trace RC, SC, SO, SI lines from ICs to the header ok, as well as +5V and GND. Where should I look next? A set of schematics would come in handy now!

That's true, my bad! The mixup happens when soldering the connector to the wrong side of the PCB.

Sure you can, you have crimped the connector to the cable the wrong way round. There is a little marking in the form of a triangle on the connector - this should match the red wire, as it marks pin 1. It looks as if you have ignored this. That's what I already suggested above.

That sounds like a cabling issue to me. You probably crimped the cable the wrong way round (or used a cable that was crimped the wrong way without you noticing).

Glad to hear that you've got it working! Best, ilmenator

Sure, if my counting is correct then AOUT_NG and DOUT together have 5 output shift registers. Hence you need to increase the number of the OUT SRs by 5: ################################################## # Optional LED Track Position Display # See also http://www.midibox.org/dokuwiki/doku.php?id=tpd_pcb ################################################## # set to 1 or 2 to enable the relative track position display # 0: TPD disabled # 1: TPD enabled - columns are cathodes, rows are anodes # 2: TPD enabled - columns are anodes, rows are cathodes TPD_ENABLED 2 # define the DOUT shift register to which the columns are connected (0=disabled) TPD_COLUMNS_SR_L 15 # for a 16x16 TPD: define the SR to which the right columns are connected (0=disabled, use only 8x8 TPD) TPD_COLUMNS_SR_R 12 # define the DOUT shift register to which the green LED rows are connected (0=disabled) TPD_ROWS_SR_GREEN_L 13 # define the DOUT shift register to which the right green LED rows are connected (0=disabled, use only 8x8 TPD) TPD_ROWS_SR_GREEN_R 10 # define the DOUT shift register to which the red LED rows are connected (0=disabled) TPD_ROWS_SR_RED_L 14 # define the DOUT shift register to which the right red LED rows are connected (0=disabled, use only 8x8 TPD) TPD_ROWS_SR_RED_R 11 The same goes for the BPM and Step digit SRs!

True - thanks for fixing that!

Great! Why does your link first send me to Facebook? And Facebook then asks me if I really want to leave?

Sure, unless the component breaks and you need a replacement. But I don't want to discourage you from going that route!

There is probably a single manufacturer for this product. I would not invest a lot of time into this, if there is a single seller and none of the big players like Mouser or Digikey have this, noone knows how long this spare part will be available to the public. Quite a bit of risk, don't you think?

Basically what you do is count the number of additional shift registers (input shift registers, output shift registers) located in the chain before the TPD and add that number to the respective shift register counts in the TPD section of the config file. As both Aout and Dout contain only output shift registers, the config entry for input SR of the TPD stays the same, but the output SR numbers will change. In your second posting / variant the config stays the same as the additional SRs come after the TPD.

If you are selling individual MIDIbox gear that you have used yourself there is no need to ask for permission! Good luck, ilmenator

According to his "Location" that is London, UK.

Yes, that would be the MIDIbox Wiki.

It is great that you have come up with such a document/page! Please, upload that to the MIDIbox Wiki. We have seen a lot of effort lost over time because authors lost interest in MIDIbox for whatever reason, and then their website went offline, and all the fine documentation disappeared. No matter how enthusiastic you might be right now, there is a certain danger involved in offsite documentation. In short: offsite docu = bad. Thanks!

If nothing shows up: it's easy enough to create the footprint yourself in KiCAD, you'll be surprised!

Now don't quote me on that, but I've had this running with cables of 50cm length... The thing is that it depends on a number of variables, so you will have to try it. 30cm sounds like it will work, though. But - no guarantees...

That's definitely pushing the limits - I'd say go with the line driver module.

Thanks Peter, I never really doubted this - I can see how much work was put into this project. I'm glad to see the documentation coming up, eventually and as your time allows! I do not care so much about the format, and at least with the tools that I use, a PDF file is only a mouse click away... ...but of course verification and validation is essential before putting out documentation. Thanks, and keep up the good work!

I'm aware of that already, but that is a reverse-engineering process that I'd rather not spend my time on. If the schematic was clean enough to create the board file with, then that is clean enough. I understand the term "priority" a little differently, but hey... It's good to see progress with our beloved SEQ!

Sure, that is always an option. However, having two different config files doesn't really make sense with the underlying functionality being exactly the same. But then, that approach also leaves a lot of freedom for changes, so that could possibly be a good solution as well. I don't think you'd need to be afraid of schematics in the public - on the contrary, it would probably help you a lot once you have to do troubleshooting and support on your customers' builds. This community has been awesome in the past when it came to solving build problems. However, I do respect your priorities. I'm looking forward to seeing the v4+ taking off!