Psykhaze

@Hawkeye MB-Programma V0.1 setup at work:

A simple search on the forum would have helped =)

This might help in understanding Serial Parrallel Interface (SPI) and I2C : https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus https://en.wikipedia.org/wiki/I%C2%B2C I add these entries in the wiki right now Basics>Digital Electronics Bests, JK

The SSD1322 controller works the same behind the display itself . Means connections stays the same , but only what differs is how you handle it trough software. The concept with OLED is that each display require a specific CS line. Then other lines are serial chained . I mean multiple SSD1306 connection schem could be also ok for multiple SSD1322 if i don't mess up myself. But then some coding work needed. Be aware that graphical display consumes lot more CPU than classical text based displays, that might be the limiting factor in chaining SSD1322 Graphical OLEDs Bests, JK

@tago tried to do my best to centralize infos in the wiki . But much information around , not always simple. Digging is also a part of the game =) While you give yourself some time to understand things and to wait for answers, you're on a good path =) Bests, JK

http://wiki.midibox.org/doku.php?id=oled so yes.

Good to see you're digging the things @tago ! Seems your coding experience will help =) Keep us tuned when you received the hardware and started the experiments ! Wanna see your work around displays ! Bests, JK

This thread gives good answers about the total number of SSD1306 Displays you can manage with MIOS32 : So kind of a lot could be managed at same time by multiplexing CS lines (See Latigid Display Line Driver) Imagine total display surface as one big matrix of pixels . Each X/Y values on SSD1306 screens in UCApps Schematics corresponds to offsets for each screen (eg your offset in the total display matrix) Also about OLEDs i am wondering about Text- based references natively supported by MIOS ? I've seen some working on photo without digging more. May some peoples experienced with this could answer about ? I'll try by my side to dig the forum more. Bests, JK

Maybe. By my side I prefer THT but i'd say that's some taste. The fact is just smd soldering is harder than through hole. Tried to think in a end user way . Once again, i feel like it's a question of taste . For sure choosing SMD is rationnal about some technical issues and soldering-doable. But i feel like you're thinking "Designer Side" and taking as admitted that SMD is a future that everyone should be ok with ? just having 100mm height +2HP multiple width constraints is almost a simple design rule. Now kiCAD is a correct alternative to Eagle, things have moved. As latigid said , we are coming from different backgrounds and may have some different advices on technical issues ,as well as different tastes. It is good to see different alternatives solutions to a same problem. We are quite off-topic so then let's re focus discussion on eurorack TPD =) Bests, JK

Defining standards is almost useful for everybody. I totally agree with some "standard" Power connector concept . We should define some common design rules to follow in upcoming designs. For example @latigid on , @ilmenator , @Altitude, following your experience on PCB design, we should define some list about design rules/issues in PCB making in wiki ( Having ground plane, Decoupling caps etc....) Eurorack size format is also about following some standards . It's maybe some "fashion" , you may not like it but I mean no "common" real size-format has been taken in consideration before in MBHP to me. (maybe excepted mb-6582 and pactec case?) Most of MBHP PCB designed were having arbitrary size and designed to fit in standalone boxes. Trying to have some common base in different works should lead to homogenic MBHP things.Defining standards is for example what made the web grow. Eurocard specs is for sure good point Most of musicians are used to rack hardware things, in 19" or Euro now. That was also a point for me about sticking to 2^X HP-width . Just notice that even on modulbox-ng i made some compromise by having some panels 24 HP. but 24 = 3x8 , so it fit for symmetry. @ilmenator Also really sorry about that , but the thing about re thinking my TPD order is also that i won't have the full V4 Seq but only V4L. Then TPD makes really less sense. Regarding SMD components, to me it should be avoided as much as possible. Most peoples aren't dealing easy with SMD soldering, and I'm the first. i know sometimes component size is an issue and the choice of having SMD components is also related to the fact it's sometimes not available DIP/PDIP package. But in order to keep PCB assembly accessible to most of us , if DIP could be choosen, i think it should be better. Imagine some noob buying some pcb+kit and missing his SMT solderings, ending in hating this precise way of handling. Just my thoughts. I hope many Full V4 Seq owners will find interest in this great TPD expander re-sized. Really nice about rethinking it Bests, Jerome

Depends on your usual rack alignments. By my side i try to stick to 2^X form width factors as much as possible because of symmetry and not having only one row in cases. Moreover i'm maniac with alignments. Ex graphic designer... Like things not in mess. But you might want save as much place as possible and not caring about global alignments because having just one row in your rack =) 14HP is 2HP multiple but not 2^X form - 16 is . Bests, Jerome

just to be sure, are you using SMT components? when i see 74hc595 footprints i wonder? I'm not sure then about the order... Moreover that i can obtain same result with modulbox-ng expanders in the end. Sorry about that. Bests, Jerome

hi illmenator, so in the end you see it's not such a bad idea to eurorack the thing =) I advice you to stick to 16 HP, maybe a little wider but better for rack integration, stays a 2^X form. Could update my order with this one ? Bests, Jerome

what's about the total setup used ? Bests, Jerome

Cool nice job bro !

I had the same problem at the beginning =) Just try to take enough time to get your mind clear . A french saying says "Night brings advice" Bests, Jerome

You're asking much at a time =) If you like to build a custom Interface instead of something already designed, you would have much programming to do and maybe MB-NG is the best point. Was telling about existing stuff. Your point about dealing with special parts could be understood , but you have much code to read , there's already much existing in current apps. Just to tell , wiki get a lot of informations on the hardware side of connecting these OLED parts. (as well as some others) Then what you can do with software is up to you. Just to make your work easier you should see if any exisitng thing couldn't be taken as base. And try to team up with peoples who have same focus, your point of generic synth controller is more or less even known. (eg MB-CV V2 / MB-Programma) Bests, JK

Thanks for the precision peter , i didn't get why at first sight =) now clear. Bests, JK

@tago Please first read about all that you've been told. Your goal seem to be very close to MB-Programma project Have a look there , make your mind and then ask questions ;) Bests, Jerome

I might not give you the exact precise answers about MIOS32 programming you ask about because did not entered the MIOS32 thing deeply yet myself. In terms of global programming there are already some behaviours coded into MIOS32 Apps you can have some look to base upon . This "menu offset" thing is for sure already been coded in some way. i know global API functions but far to know a lot. Still need some hours reading code by my side. Bests, JK

Based upon some Standard control surface (SCS) , you can make some cool menu things if you are not afraid of programming. Toggle switches may be managed with DIN modules and LEDs with DOUT modules. Analog inputs by AINSER8 or AINSER64. You can then link your inputs/outputs in your MIOS application to corresponding display behaviour. But maybe MIDIO128 already offers some of what you need? Bests, JK

Original photos seems to be dead links. I wish i could see these. Bests, JK

That's already a good thing you try :) i understand your point.I hope Tim will answer you asap. Bests, JK