FantomXR

I need to do some investigation on this. But I assume the Product ID is what counts here.

You are wrong! ;-) I added these lines to the mio32_config.h file of the desired application (no bootloader rebuild needed). // Following settings allow to customize the USB device descriptor #define MIOS32_USB_VENDOR_ID 0x16c1 // sponsored by voti.nl! see http://www.voti.nl/pids #define MIOS32_USB_VENDOR_STR "Test" // you will see this in the USB device description #define MIOS32_USB_PRODUCT_STR "Test2" // you will see this in the MIDI device list #define MIOS32_USB_PRODUCT_ID 0x0405 // ==1023; 1020-1029 reserved for T.Klose, 1000 - 1009 free for lab use #define MIOS32_USB_VERSION_ID 0x0200 // v1.00 The original which I found in the bootloader is this: // Following settings allow to customize the USB device descriptor #define MIOS32_USB_VENDOR_ID 0x16c0 // sponsored by voti.nl! see http://www.voti.nl/pids #define MIOS32_USB_VENDOR_STR "midibox.org" // you will see this in the USB device description #define MIOS32_USB_PRODUCT_STR "MIOS32 Bootloader" // you will see this in the MIDI device list #define MIOS32_USB_PRODUCT_ID 0x03fe // ==1022; 1020-1029 reserved for T.Klose, 1000 - 1009 free for lab use... 0x3fe is required if the GM5 driver should be used #define MIOS32_USB_VERSION_ID 0x1010 // v1.010 I assume that windows takes the VID and the PID to identify the device. If you change those values for your second application, this works perfectly. Windows recognizes both devices! Also MIOStudio is able to edit both applications! :-)

@Duggle: I did some more searching on this topic. And I found some useful informations in the bootloader-source code. There you can define unique USB data f.e. Vendor ID, etc.pp. Unfortunately I'm not able to compile the bootloader... I get some errors and the file in the end is only 15kb compared to the bootloader from ucapps.de which is at 150kb or so...

it's around the actual position. If the fader is at 105, it sometimes jitters on 106 / 107 f.e. Of course VREF and standard V+ (5V) do not share the same trace. I attached a screenshot of the PCB: https://www.dropbox.com/s/ibrunxjkxhdqs5z/BournsPTA.png?dl=0 VREF is the big trace on the very top of the PCB. J1 is the input, J2 forwards the unused analog inputs of IC2, which I need for nine faders on this PCB. I'll do what you suggested! Thank you for your help! I use Bourns PTA slide-pots with 10k.

Hm... damn it! I also don't know who to ask with such topic...

Hello Zam, thanks for your reply. It's not jittering like a lot of values are send by the slide pot. It's just like every now and then (like every 2-3 seconds but sometimes it stays stable for ever) it sends a value. So maybe I want to have it too perfect ;-) What I'd like to have is a kind of "IDLE" function, which I found in the mios32_ain.h in /svn/mios32/trunk/include/mios32/ It's description reads: // define the deadband which is used when an AIN pin is in "idle" state // this helps to avoid sporadical jittering values // Set this value to 0 to disable the feature (it's enabled by default) #ifndef MIOS32_AIN_DEADBAND_IDLE #define MIOS32_AIN_DEADBAND_IDLE 230 #endif // define after how many conversions the AIN pin should go into "idle" state // - "idle" state is left once MIOS32_AIN_DEADBAND_IDLE is exceeded. // - "idle" state is entered once MIOS32_AIN_DEADBAND hasn't been exceeded for // MIOS32_AIN_IDLE_CTR conversions // 3000 conversions are done in ca. 3 seconds (depends on number of pins!) // allowed range: 1..65535 #ifndef MIOS32_AIN_IDLE_CTR #define MIOS32_AIN_IDLE_CTR 3000 #endif I thought it may be possible to move the slider into the desired position f.e. to value 64 and "lock" it so it only sends any further CCs if the slide pot changes significantly. Regarding my wiring: The slide pots are mounted on a PCB which I designed. 5V track is at 0,8mm and GND is designed as plane. The faders are scanned through an AINSER64 module. But this I also designed by myself. The 74HC595 and the MCP3208 are sitting on the mainboard, while the 4051 are directly mounted on the fader-PCB. The cable to the fader PCB is about 30cm. The faders are running at 7bit. 11bit leads to a lot of jitter. Power through USB at the moment, but I'll change that too a MeanWell 5V powersupply.

Hey people, I searched the NG-firmware for the parameter, which set's the deadband of the AINSER-inputs. I found this: #define MIOS32_AIN_DEADBAND 31 But if I change that to f.e. 100 or more it doesn't change anything. My problem is, that my slide potentiometer have some jittering (even when the pinrange is set) when they are not at 0 or 127. I also found the parameter #define MIOS32_AIN_IDLE_CTR 3000 But changing this value also doesn't make any difference. Does anybody know where to set this value? Thanks, Chris

Hey people, I have two MIDIboxes here and I have some trouble with connecting them to Windows. I configured both cores to single-usb and I gave them individual names (f.e. Key and Controller). I also set the device ID of Key to 0 and of Controller to 1. If I now connect both MIDIboxes to my computer (running Win10) the thing is, that MIOStudio is not able to differentiate between both cores although I did set different device IDs. Also both cores will have the same name! It depends on which core I connect at first. If I connect Key at first, both MIDIboxes will be namened "Key". Also my DAW names them the same but adds a number behind the name. So the first MIDIboxes is "Key" and the second "Key #2". Is there any workaround for this issue? thanks, Chris

Hey people, I have an idea in mind but I don't know if it's possible to program it. It seems like a challenge. Let's assume we have a midi-keyboard and a strip of WS2812 on top of the keys. What I want to do is, visualizing the split-zones of the keyboard. My DAW is able to send tons of different values f.e. CC, NoteOn, SysEx, NRPN, and so on. My first idea was to assign a CC to the LEDs f.e. CC16. If I now send CC64 to the MIDIbox, all LEDs would light up which are <= 64. But what if I only want LED10-LED16 to light up and not the LEDs which are lower than that? Another idea: Assign a CC-value to every LED f.e. value 0 = LED1, value 1 = LED2, etc. But that would mean, that A LOT of MIDI data has to be sent to the MIDIbox on patch-change. So is there anything I overlook? Do you have any other ideas how to address a range of WS2812 LEDs? Thanks, Chris

Great!! Thank you very much!

Hi! Thanks for your reply! I think using a RC delay sounds like the simplest solution. But why should I set this pin to high? And do you have any idea what kind of values to choose? thanks, Chris

Hey people, everytime I switch on the MIDIbox, all LEDs will light up for a fraction of time. Is there any chance to avoid this behaviour? I think it has something to do with the initialization-process. I already tried to put a capacitor (100uF) between VDD and GND, but this didn't change anything... Thanks, Chris

Hey, it's a FATAR TP/40H with 76 keys. I ordered it directly from FATAR.

Okay! I got it! This code works great: EVENT_RGBLED id=1 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP1 EVENT_RGBLED id=2 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP2 EVENT_RGBLED id=3 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP3 EVENT_RGBLED id=4 type=cc cc=16 rgb=0:5:0 dimmed=1 range=MAP4 EVENT_RGBLED id=5 type=cc cc=16 rgb=8:5:0 dimmed=1 range=MAP5 EVENT_RGBLED id=6 type=cc cc=16 rgb=5:0:0 dimmed=1 range=MAP6 MAP1/BYTEI 0:0 21:127 MAP2/BYTEI 0:0 21:0 42:127 MAP3/BYTEI 0:0 42:0 63:127 MAP4/BYTEI 0:0 63:0 84:127 MAP5/BYTEI 0:0 84:0 105:127 MAP6/BYTEI 0:0 105:0 127:127

I tried now a few different things but I was not able to get a few WS2812-LEDs working as LED-Ring or bar. Any ideas how to get this working?

Hm okay. But if I have a strip of 6 LEDs and I want them to show the status of a fader or encoder like a led-bar or led-ring which sends f.e. CC16, how to do that? Or isn't it possible yet? Maybe I could assign different ranges to the LEDs...this is the only workaround I could think of at the moment i have another idea for lightning the encoders. So no need for PCBs or encoders. Will share it as soon as I've tested it. ;-)

Does someone know if it's possible to use the WS2812 as matrix? I'm afraid that there is no parameter called EVENT_RGBLED_MATRIX. So there might be a workaround that I don't know? I'm looking for a replacement for the classic encoder led rings and those WS2812 seem to be a great alternative. Thanks!

Great build!! Have a good time with your family!

Haha. So you have some of them left I guess. ;-) but why did you choose to order encoders without switches?

Yeah! Looks great! And where do you get the clearshaft encoders from? :)

Hey Andy, could you please post a picture of the WS2812 Board? I'm interested in how it looks like! Thanks, Chris

I think it all depends on the time you want to invest. From my experience I can tell that it needs more time as you might plan ;) Also it depends on what kind of PCBs you have available. Faders are quite easy to solder even without a PCB. Buttons are more crucial especially if you want to use buttons that are not able to be mounted on the frontpanel directly and need a PCB. I think the most time consuming work will be to solder the LED-rings. As far as I know there is no ready-2-go solution at the moment and no PCBs are available for 16 LED rings. Some time ago there was a bulk order for those: http://www.midibox.org/dokuwiki/doku.php?id=mb-lre8x2cs_pcb But I think Jerome is not active in the forum anymore. Anyway: If you have good soldering skills and you are able to solder SMD than I can help you out. I have some SMD-LED-Ring PCBs a while ago. But those are 0603 SMDs you need to solder by hand... and it's 16*16pc = 256 LEDs = 512 pads ;) What do you mean by scribble strip?

Yes. You need to update the firmware of the STM. More informations you can get on ucapps on the STM core site.

So now the problem is, that if I change a parameter via the terminal command and save it, those values are not overtaken into the NGC file.... hm....

Some more investigation in this: I made a MIDI-loop going from OUT1 to IN1. This works great! So it seems that I can not address the parameters directly but need to build a midi loop to control those values from external controllers.