Zam

UPDATE ! Seem I find out so I change if( port >= USB1 && port <= USB7 ) to if( port >= USB5 && port <= USB7 ) (to have access to 4 slaves at 4 usb 0 to 3) And in the mean time I set different ID to each cores in the bootloader. So far I'm able to access first Slave core at UART1 from Master core via USB2 port in MIOS studio ! Best Zam

Hello Goyou Not sure to get what you say, if it's a kind of UART line selector between core, this won't work for me, I need all Slaves connected to Master all the time, each slaves show up (for DAW) as different midi device with 4 USB enabled at master (and router config) But I think I find something at mios32_midi.c which seem to lock mios sysex command to USB0 (USB1 port) ///////////////////////////////////////////////////////////////////////////// // This function parses an incoming sysex stream for MIOS32 commands ///////////////////////////////////////////////////////////////////////////// static s32 MIOS32_MIDI_SYSEX_Parser(mios32_midi_port_t port, u8 midi_in) { // ignore realtime messages (see MIDI spec - realtime messages can // always be injected into events/streams, and don't change the running status) if( midi_in >= 0xf8 ) return 0; // TODO: here we could send an error notification, that multiple devices are trying to access the device if( sysex_state.general.MY_SYSEX && port != last_sysex_port ) return -1; // USB upload is only allowed via USB0 // this covers the scenario where other USB1..7 ports are used for MIDI Port forwarding, and a MIOS8 core // is connected to one of these ports // MIOS Studio reports "Detected MIOS8 and MIOS32 response - selection not supported yet!" in this case // By ignoring >= USB1 <= USB7 we have at least a workaround which works (for example) for MIDIbox LC if( port >= USB1 && port <= USB7 ) return -1; last_sysex_port = port; Best Zam

Hi all I'll like to update NG app and config via UART but I can't reach the core with MIOS studio I have a multicore setup, one "master" USB (4 port) to computer and 2 stave (soon 4) with direct UART midi interconnection to master core. Midi data between cores is fine (at 10x speed, no optocoupler) as slave to computer via master. At master I have router active, USB2->IN1 and OUT1->USB2 (for first slave) BUT I can't connect the slave core via master and USB2 port at MIOS studio, do I overlook something ? I have a vaguely memory that connection is constrained to USB1 port, but can't find back where I've seen this in the past...nor forum or wiki. The idea is to not have to connect each core directly to computer to update config... but everything working from a single USB cable (which is already the case except for the config update via MIOS studio...) Best Zam

Hi Gerald Tks for info, I'm not aware of that, I only use NG with my custom controller/fader I'll look at it ! Best Zam

Hi I'm still interested for such blink led function If anyone have an idea ? Best Zam

Hello To have a resistive element reacting to pressure ! Old school: carbon powder inside bag Ultimate old school: asbestos powder inside bag... Best Zam

All answers are in the post you actually quote ! Best Zam

Yes, it's a voltage divider, it will not change what voltage the AD see... and the load difference is marginal here for what we need. Best Zam

Hello WingMa You can use both ALPS fader you show, mixed at same MF_NG should not be a problem. Best Zam

by the way... what is supposed to print &a ? (sorry i'm not use to label... never really add LCD to my midibox and &a is not in the current user manual at label=)

Hello Yes you'r right. Did you try another strategy, like no script(NGR) involved but conditional at NGC according to your flip button I don't have explanation for your issue, but maybe it's linked to label= handling, I mean it's not a midi function/data, so it is forwarded to LCD anyway ??? just an idea... Can you try to set a fwd= to anything from your receiver and check if it effectively forward midi event or not, depending of set_lock or if_equal= status of the event ? Best Zam

It's preferable to not mix Din and Dout in the same chain So if you want to physically chain two different board you better think like different bus passing through when routing all your digital lines and clocks, so at electric side it's two different (Y) chain Din and Dout share the same RC1 ! Best Zam

Not really an error, mostly to "force" DI and DO Y chaining like.

Hello few things... -try to avoid 90° angled traces -try to place capacitor as close as possible to VCC pin of each chips -why don't you use resistor network to gain space an make routing easier ? -a common basic practice is to use one side H traces and other V traces, you mix a lot at both side, I'm sure you can optimize a lot of unnecessary via with this simple rule -dual sided TH component will be a pain to assemble when component hide other side hole, you can place resistor vertically at same side with a 2.54 pitch... Best Zam

Hello Chris Not sure to get it all, but I see your first set of receiver (1 to 9) print label to oled 0x31 to 0x39 but your second set (11 to 19) don't print to the same oled ID, 0x41 to 0x49 ? Best Zam

Hello Varam, welcome here. Just a side note for your "safety", edit your post and remove email, to avoid robot mail tracking If someone can help you, the PM work well here, and you can share contact in this private area. Best Zam

Hello Now I'm used to build my MB_NG with latest pre release and updated code from SVN But thanks for the official release ! Since I use this one for months, I don't catch any bug so far. Best Zam

Hello Latigid Tks for the offer, I'll PM you if I need one. For the moment I'm thinking about it, for a new project, not sure this new core holder fit my needs. Best Zam

Bienvenue ici ! Looking forward. Best Zam

Hello Any drawback with the waveshare core that use VE 512k flash across the 1M for the VG (ST disco) ? Flash is just for the MIOS bootloader right ? I will certainly need compact core soon, waveshare look the perfect footprint. Best Zam

Hello Having two separate planes mean distinction ! If you see it this way no system at all have distinctive 0V ref... as all finally end to the same safety earth point Connecting only one 0v will make ether digital or analogue return path through the other circuit, may not be trouble as you experienced, but it's easy to avoid this and make it fine at start, it's just one more wire... So I still recommand to hook TWO 0V wire, one hooked do DOUT pcb for D signal and one connected to AOUT (analogue side) PCB for CV signal. Best Zam

Hello Tim It depend what is at the other side of the connector... I guess you better separate analogue and digital reference, at least. Best Zam

Already ??? Best Zam

Zener... with all respect... I start thinking you are just a troll here ... TWO page with ppl gently responding to you, trying to help. You still complaining whatever we say. As others, I'm out of this topic. Hope I'll see you in another one with REAL midibox in your hand. Best Zam

Hello I just have a quick look at your ngc (hard to read without text reformatting...) You have some led fwd without led definition also multiple event (same hw_id) with same id For your problem what I suspect is that your button 23/24 have a radio group (2) with respectively range 3 and 4, there is chance that at start the radio group 2 will have value 1 by default. Maybe just try value=3 at EVENT_BUTTON id=502 hw_id=23 Best Zam