Zam

Hi Yes you have to try ! I use them for my last design, also with digital print for label, definitely high qualities and industry grade for "affordable" price. Five studs here to attach the illuminated tact switch pcb, as the big push button (+ bracket) at bottom. Best Zam

Hi Welcome here 401 won't work... you need the 407 man ref :STM32F407G-DISC1 Best Zam

Hi Same here with large .NGC, when editing via file browser and save, sometime time out happen en completely corrupt the SD card (need a reformat in OSX...) One possible explanation I have in my use case (I can actually repeat it sometimes) is when the communication to/from the core is full active with lot of data transfer, like "debug on" with lot of sysex stream, or when tuning my system with lot of jitter and data coming from AINSER, or if the system is active/connected to the DAW and I update parameter/configuration via MIOS studio at the same time. Something in the MBNG and MIOS32 don't work well when flooded with data. Best Zam

Hi Not sure to completely get it, but did you try your encoder forwarding to a sender, with as many requested sender id (same hw_id sender) forwarding to led. Best Zam

Hi For the most basic possible DIY synth (or I better say AC generator in this case...) I get some amazing sound with this few decades old electronic kit for kid !!! Best Zam

Hi Benoit No problem, I'm also in a middle of consuming work (studio relocation...) Nice new box you create ! What is the precision of the analog in/out ? are they able to handle DC signal? Best Zam

Hi Sorry mistake, I mean USB and RTPM... Best Zam

Hi It work, connected to a computer or standalone, via USB or NRPN. Best Zam

Hi Lat I just have a look, old is C, new is D Best Zam

Hello Dendy MBHP and MIOS support 4x4 midi DIN port and 4x4 usb midi Best Zam

Hi tago Yes you need one RC line per chips, connector J19 used fort this purpose only offer two RC line by default If you need 40 analog pot you better go with AINSER64 which use 8 multiplexer around MPC3208 for a total of 64 input, with a single RC line. Best Zam

ok Best Zam

How is that possible with 12bit DAC ??? Best Zam

Hi I think reading the NG manual is a good start, what you need is part of NG possible configuration. I won't explain here because it's already well done by TK at the user manual and specificaly at .NGC configuration. As a start for your use case take a look at button toggle mode, radio group parameter and bank parameter, also .NGL configuration for everything related to labels. Best Zam

Hi tago Why don't you order from Tim/SmashTV ? You ask for a full set MBHP pcb, I don't think you will find better place ... Best Zam

Hi tago "simple" design only allow two chips/line for J19 SPI port, you can do more with modification. If, as you say, you need at least 40 pot/fader you better go with the 8x8 multiplexed version (AINSER64). If you want better jitter performance for sure you build is a mess, I suggest you to monitor your servo ref voltage first, you will see how it move... If you respect the keys I give before, you can have 50 cm wire between pot and ADC (that's what I have considering trace at both pcb and the wire). If everything else is strong the only drawback with long wire is the voltage drop, but it will be constant and you can map/scale value at soft side Also I'm not sure but I don't see any capacitor with your build, maybe your jitter come from chips/line/clock noise going all around your build No it's not , I don't call more than 1% jitter a working system Best Zam

Hi all 1 step jitter for 7 bits (128 value) is huge !!! it's more than 40mV for 5V supply, there is for sure and issue with your build. Keys for low jitter: -A perfect grounding, with same 0V reference for both servo and AD chips Vref -Quality power supply with low ripple, good line and load regulation, optional sense is a must -shorter wire as possible -optional low pass RC filter can be added Following all this for my build, running AIN at 11bit (2048 steps) give very low jitter, less than 1 step value change per sec, around 2mV jitter. So the system is finally configured at 10bit ... rock solid ! Best Zam

Hi benoit Thanks for your time and explanation. I think I mainly get it, except I use wrong terminology So to be sure I understand well I will reformulate/quote what I see at my system with correct definition you give. Then I still have a problem here... Why then the KissBox (endpoint) is able to separate data comming from two endpoint through two session, and forward them to two different SPI port for MIOS ? OK, not sure If that's what I need, I better explain what I want to achieve. I'm using MCU protocole to drive 16 physical fader at MB_NG side. Protocol need one midi port for each 8 fader, using ch1 for most data BUT channel 1 to 8 pitchbend for 14 bit fader position data. So I need two midi port each using 8 chn to perform this. The targeted design is to have n core, each one for 8 fader, Cores connected together (via SPI midi ?) Master core have RTPM card, handle first 8 fader, and just act as router for other core from/to RTPM separate session, which have separate endpoint at other side so DAW can see n MCU device. Best Zam

Hi Djordje Welcome here Did you drop a message/mail to Tim (SmashTV) ? have a look here --> http://www.avishowtech.com/buyWU.html Best Zam

Hi I have now success using the RTP midi with my MIDIbox There is one thing puzzling me. When trying to emulate two Mackie control at two different midi ports, SPI1 and SPI2 When I open let say 2 sessions with the midi setting (OSX) and configure different ports at MB_NG for two events AINSER (sending data from MIDIbox to DAW): EVENT_AINSER id= 1 hw_id=1 ain_mode=direct type=PitchBend chn= 1 range=map120 value=0 ports=00000000000000001000 #(for SPI1) EVENT_AINSER id= 2 hw_id=2 ain_mode=direct type=PitchBend chn= 2 range=map120 value=0 ports=00000000000000000100 #(for SPI2) both event send midi data to both session 1 and session 2. In my use case 4 fader are moving at DAW (1, 9 and 2, 10 with two MCU configuration) when I move the fader connected to Ain But if I setup different ports for two event CV (receiving data from DAW to MIDIBox)): EVENT_CV id=1 type=PitchBend chn=1 range=map130 value=0 ports=00000000000000001000 #(for SPI1) EVENT_CV id=2 type=PitchBend chn=2 range=map130 value=0 ports=00000000000000000100 #(for SPI2) everything is fine, DAW fader 1 change only CV 1 (fader 1 move and not fader 9) and DAW fader 9 only change CV2 (fader 10 and not fader 2) To simplify, all SPI midi ports going out from midibox through KissBox are merged to every session opened. But it work fine the other way, one session send data from computer = one SPI port receive data at midibox All router node at .NGC are set to 0... I there some router at the KissBox ??? that merge everything in one way only ? Best Zam

Hi If you mean in series that's for sure But you can hook one diode at posV and one at 0V, will protect positive over voltage to posV+0.7V and negative over voltage to 0V-0.7V. can be a safe move with bipolar supply component next to the DAC. I have to admit I don't do this with my Ain/Aout pcb design... Ain mpc3208 already have them integrated, don't remember for the tlv5630 But I add at all Ain/Aout an RC filter, it improve jitter, in my use case at least. Best Zam

Thanks Novski ! Yes it become better and better. Hope I can share a rock solid system soon. Best Zam

Hi All Some update 89MotioN 8 fader loaded Best Zam

Hi Psy don't be psycho I care about KiCad !!! but not sure a dedicated midibox wiki tutorial is useful, KiCad grow up more and more (tks to CERN) and there is already lot of tuto/forum/help all around. I don't see any "special" lib request for actual midibox project, 99% of component used is standard. BUT for what I understand the wiki is open, so if you feel the need for this, you can start it Best Zam

https://forum.kicad.info/t/importing-graphic-file/1882 Best Zam