ilmenator

Sh*t, I forgot - sorry for that misinformation, bwanatikh!

You want to look at MIDIbox Link.

Use a saw... :blink:

Hi Greg, you seem to have identified the modules that you need for this already. You could now try to see which of the elements on the modules / boards you actually need, e.g. on the DIN board there are four times 8 inputs - if you need less, and everything must be very compact, then you reduce that number, and place every component you need on your own / custom made printed circuit board. This would require that you take a look at the schematics, design the board (probably using SMD parts), and then have your board fabricated somewhere. From this you can see that it involves quite some effort. Also, having the board fabricated is not for free. I believe it would be a good idea to start building a prototype of what you want using the available modules, see if that does what you want, and then afterwards go for a more compact and integrated (one PCB) solution. Hope this helps, and good luck!

Yes, that is the fastest, most straight forward and convenient way to get sound!

A few years back I received exactly the same answer from Thorsten, and it turned out that he was completely right - with the MIOS C functions, everything I needed at that time could be implemented very easily. Go for it! :thumbsup:

What about KICAD? It's free, has netlist connectivity, it's pretty straight forward to use, and EAGLE libs can be converted from EAGLE itself. I guess the same is true for designs/boards, but I have never done that myself.

Just want to make sure my PM is not lost :thumbsup: .

Thanks! I have created a new set of library files for the encoders in KICAD, also converted from EAGLE. I mainly changed the pin numbers, font size, and the line width so that they better match with the other KICAD libraries. I have not built a board with these either, which means using the lib is at your own risk :tongue: If someone has the time to create a KICAD parts library page in the WIKI, similar to what exists for EAGLE, feel free to upload this file as well! Best, ilmenator encoder.zip

Congratulations! Now we want to see pictures! :flowers:

Hi all, I am looking for KICAD library files for the ALPS STEC16 and Bourns PEC11 rotary encoders usually used in MIDIbox projects. Has anyone ever used KICAD to build a board that had these encoders? Thanks, ilmenator

Check your voltmeter!

Just to add my 2 cents, these switches are awesome - I desoldered about 150 or so of them from older equipment, as they give a very nice tactile feedback. Also, they are still quite stylish - especially with the 3mm LED in one of the corners.

Huhu... :twitch: !

I can second that. They are not exactly cheap, and occasionally they did mess up things. But when they did, they were quick to react and always chose the fastest manufacturing and shipping that was possible. (They even overdid this once: I remember UPS trying to deliver a panel at 6:20 in the morning at a University... :rolleyes: )

The link is fine, and it is all accessible now. Unfortunately (?), the Internet tends to be an evolving place, people come and go, their interests change, ... in short, things just happen. Then, it's good to have documentation in the one place meant for it. We'd really like to encourage you to make use of that :flowers: !

Great project, congratulations! Why don't you upload the documentation to the WIKI? You know, <broken record> offlinsite docu is bad </broken record>!

It was probably the older bootloader, it's been a while since I last played with it. Whatever happened, after programming the bootloader again with the STM Flashloader demo tool, my core32 now behaves as it should :frantics: . Maybe I should have done that straight away, but I was curious as to why that thing suddenly misbehaved. Thanks, ilmenator

This is what I get when connecting my core32 board to a Windows XP machine using MIOS Studio 2.0. Doesn't look more successful than on Win 7, so it may not be an OS-related issue.

Windows 7 32bit, so I assumed that the "known issue" entry is not relevant for me. Well, this is a V1 board, so I only have J23 available, there is no J27. Does it suffice to close J23? I'll try on a Win XP machine later and report back. Thanks, ilmenator

Hi, I have a strange problem that I just can't figure out myself - my STM32_V1 board does not accept any uploads anymore. Here is the story: After a year or so in storage, I recently got out my STM32_V1 board. This board used to work fine, and I was able to upload apps to it before. What was a little strange when I re-activated it was that the MIDI ports did not show any sign of life. So, when switching the board on, no message would be sent from neither of the two MIDI outputs. I am not sure if this is normal, but with the old Core8 you would get some message, so I assume that is a problem. Anyways, I connected the STM32-V1 board via USB, and everything seemed to work fine. I was able to upload a few applications using the new MIOS Studio 2.0, until I decided to try the upload of the SEQ_v4 application. That one went fine as well, but since then, the Core behaves in a really strange way. Whenever I power up the board for the first time, re-scan the MIDI-ports, set MIDI input and output ports to MIDIbox SEQ v4, the status of the board seems fine, see screenshot "04.jpg". If I press the START button in MIOS Studio, I end up with what you can see in "05.jpg". After that, no more communication with the core is possible, and I have to unpower the core, re-scan MIDI ports, power up the core again, and re-scan the MIDI ports again to get a status message from the core. And so on... This is really frustrating. I thought I would master the whole system fairly well, but I have no clue what is going on here :wacko: ilmenator

Patrick, I am having difficulties opening the .7z file in your original post. 7-Zip gives me an "Incorrect Command Line" error. Could you please upload that in "regular" .zip format again? (Or, tell me what I am doing wrong :unsure: ?) Thanks, ilmenator

Not sure about this assumption. At first, I was also thinking that it would be very bothersome to enter the codes every time for every little change. After a while I realized that it actually forces you to be more structured, and to do it right the first time. This in fact I regard as very positive. If you really have something to say that needs to go in the Wiki, the captcha won't keep you from putting it there.

Sound examples? :whistle:

Poste doch mal die exakte Teilenummer, damit man erkennen kann, ob die Fader MIDIbox-kompatibel sind!