dinama

I try to connect three 40x2 display to MBHP_CORE_STM32F4 board in a MIDIbox NG controller. The first two display are connected to J15A and J15B. For third display i tried to recompile the MIDIbox NG application with following options in mios32_config.h for optional third Enable line (pin A6 of J5B): #define MIOS32_BOARD_LCD_E3_PORT GPIOB #define MIOS32_BOARD_LCD_E3_PIN GPIO_Pin_0 every time i get the same error " project_build//c/MIOS32/mios32/STM32F4xx/mios32_board.o: In function `MIOS32_BOARD_J15_PortInit': c:/MIOS32/mios32/STM32F4xx/mios32_board.c:927: undefined reference to `LCD_PIN_E3' project_build//c/MIOS32/mios32/STM32F4xx/mios32_board.o: In function `MIOS32_BOARD_J15_E_Set': c:/MIOS32/mios32/STM32F4xx/mios32_board.c:1118: undefined reference to `LCD_PIN_E3' collect2.exe: error: ld returned 1 exit status make: *** [project_build/project.elf] Error 1 "make all" terminated with exit code 2. Build might be incomplete. " I use Eclipse for compiling. I didn't understand something. I'm not a coder. In the CORE_LPC17 Module there was J28 for connecting other displays but not on MBHP_CORE_STM32F4 board. I need some help. Thanks all for your help and your time.

No news? Is there a way to read two consecuitive bytes from a received sysex and assign to a hardware controller? From pag. 35 of Xva1 manual: XVA1 can be controlled also by using the dedicated external UART, by using pins 26 (TX) and 27 (RX) in the CMOD-A7 module. The external UART is set to send/receive at 500 kbps, 8-bit, one stop bit, no parity. Command are: r = Loads a program from EEPROM w =Writes active program into EEPROM. s= Sets specified parameter to specified value. g =Gets active value for specified parameter ...... is there a way to use these commands in my midibox? is possible to send command like this from a midibox to the synth? If there is no solution the last thing i can do is to manually copy all preset from eeprom and save every preset in the sd card. I fear that 500 parameters for every preset are too many to save on sd card. I have bad experience with sd card. I prefer eeprom. thanks

I'd like to make an hardware control surface for fantastic XVA1 synth (https://www.futur3soundz.com/xva1-synthesizer) The synth use a 24LC1025 I2C EEPROM memory to store preset. All parameters in XVA1 can be controlled via MIDI System Exclusive messages. The message format for the messages is as follows: F0 44 00 P1 P2 V1 V2 F7 Where: P1 P2 = Parameter number, 0~511 in two hexadecimal 7-bit values. V1 V2 = Value, 0~255 in two hexadecimal 7-bit values . So i use encoder on MBNG to change value like this ( example for filter-1-cutoff where P1=0x00 and P2=0x48) EVENT_ENC id= 1 hw_id = 1 bank=1 fwd_id=LED_MATRIX:1 fwd_to_lcd=1 range= 0:255 type=SysEx stream="0xf0 0x44 0x00 0x00 0x48 ^val_h ^val 0xf7" ports=100011000000000 lcd_pos=1:1:1 label="filter1_cutoff %3d" All is ok It is also possible to request a SysEx Dump Get Program Dump (512 parameter values) F0 43 uu 04 04 00 00 F7 Where uu = unit number.( In my case 0x00) So i implemented a button to request a dump and store it in a general receiver EVENT_BUTTON id= 80 button_mode=OnOnly type=SysEx stream="0xf0 0x44 0x00 0x04 0x04 0x00 0x00 0xf7" chn= 1 range= 0:1 offset= 0 ports=100011000000000 lcd_pos=1:1:1 label="get dump" EVENT_RECEIVER id= 1 type=SysEx stream="0xf0 0x43 0x00 ^dump 0xf7" ports=1000100000001000 fwd_to_lcd=1 lcd_pos=1:1:2 label="Received SyxDump" This part is ok. Using MIDI-OX software i can see the 1024 byte of the dump that synth out of its midi out port. Now the problem. I'd like to use syxdump_pos parameter to update the value af any controller to reflect the current value stored in the current selected program in the synth memory. syxdump_pos fails because it points to a single byte in the ^dump , while the parameter value consists of two bytes. I'm not a programmer but in MIDIbox NG repository i find this section in mbng_event.c file case MBNG_EVENT_SYSEX_VAR_VAL: match = 1; pool_item->value = (pool_item->value & 0xff80) | (midi_in & 0x7f); break; case MBNG_EVENT_SYSEX_VAR_VAL_H: match = 1; pool_item->value = (pool_item->value & 0xf07f) | (((u16)midi_in & 0x7f) << 7); break; case MBNG_EVENT_SYSEX_VAR_VAL_N1: match = 1; pool_item->value = (pool_item->value & 0xfff0) | (((u16)midi_in << 0) & 0x000f); break; case MBNG_EVENT_SYSEX_VAR_VAL_N2: match = 1; pool_item->value = (pool_item->value & 0xff0f) | (((u16)midi_in << 4) & 0x00f0); break; case MBNG_EVENT_SYSEX_VAR_VAL_N3: match = 1; pool_item->value = (pool_item->value & 0xf0ff) | (((u16)midi_in << 8) & 0x0f00); break; case MBNG_EVENT_SYSEX_VAR_VAL_N4: match = 1; pool_item->value = (pool_item->value & 0x0fff) | (((u16)midi_in << 12) & 0xf000); break; Is it possible to edit this file to get a solution to my problem?how? Can anyone help me find a solution? Thanks in advance. UCapps is a fantastic place.

Sorry my mistake

after many attempts with my midiboxNG i can say that ain_mode=Snap and ain_mode=Parallax do not work. Maybe there will be a solution with next firmware

i tryed the new version http://www.ucapps.de...v1_027_pre2.zip ain_mode=Snap still not work

yes. still exist

Hi. I have some problem with ain_mode=Snap this is a part of my configuration file These are the pots configuration EVENT_AINSER id= 57 type=PolyPressure chn= 1 key= 71 range= 0:127 offset=0 ports=1000100000001000 ain_mode=Snap lcd_pos=1:1:1 label="CH RATE %3d" EVENT_AINSER id= 58 type=PolyPressure chn= 1 key= 72 range= 0:127 offset=0 ports=1000100000001000 ain_mode=Snap lcd_pos=1:1:1 label="CH PHASE %3d" EVENT_AINSER id= 59 type=PolyPressure chn= 1 key= 73 range= 0:127 offset=0 ports=1000100000001000 ain_mode=Snap lcd_pos=1:1:1 label="CH DEPTH %3d" EVENT_AINSER id= 60 type=CC chn= 1 cc= 91 range= 0:127 offset=0 ports=1000100000001000 ain_mode=Snap lcd_pos=1:1:1 label="CH DRYWET %3d" EVENT_AINSER id= 61 type=CC chn= 1 cc= 7 range= 0:127 offset=0 ports=1000100000001000 ain_mode=Snap lcd_pos=1:1:1 label="VOLUME %3d" ... these are buttons for recall snapshots ..... EVENT_BUTTON id= 1 fwd_id=LED:1 type=Meta meta=setSnapshot meta=LoadSnapshot meta=DumpSnapshot range= 1:1 radio_group=1 button_mode=OnOnly lcd_pos=1:1:1 label="%Cmem%S" EVENT_BUTTON id= 2 fwd_id=LED:2 type=Meta meta=setSnapshot meta=LoadSnapshot meta=DumpSnapshot range= 2:2 radio_group=1 button_mode=OnOnly lcd_pos=1:1:1 label="%Cmem%S" EVENT_BUTTON id= 3 fwd_id=LED:3 type=Meta meta=setSnapshot meta=LoadSnapshot meta=DumpSnapshot range= 3:3 radio_group=1 button_mode=OnOnly lcd_pos=1:1:1 label="%Cmem%S" EVENT_BUTTON id= 4 fwd_id=LED:4 type=Meta meta=setSnapshot meta=LoadSnapshot meta=DumpSnapshot range= 4:4 radio_group=1 button_mode=OnOnly lcd_pos=1:1:1 label="%Cmem%S" ... this is the button for save snapshot EVENT_BUTTON id= 18 type=Meta meta=SaveSnapshot meta=DumpSnapshot button_mode=OnOnly lcd_pos=1:17:1 label="%Csave mem%S" when i move the pots of of EVENT_AINSER events the output value jumps directly to the new conversion value ( like in Direct mode) not like in Snap mode definition " whenever a new value is received from external, pot/fader movements won't generate MIDI events until it passed beyond the new position" The strange thing is thant if i change the ain_mode from Snap to Relative all it's ok I try to delete the .ngs file from sd card so that a new one will be created but i have the same problem. thanks for help

Hi everyone. Is possible to have in midibox ng the option "snapshot at power on" present in midibox64? I wish at the power-on, midibox ng automatically send the actual values ​​marked by the position of the potentiometers connected to ainser64 module. I see in the list of .ngc parameter "RetrieveAinserValues:" and the various "SetSnapshot:"-"LoadSnapshot:"-"SaveSnapshot:"-"DumpSnapshot:" but i realy don't know where and when i can use it for my purpose. Maybe with a dummy led functions? Please help

please give me a news. i'd like to finish my project. thanks

news, please

Any news?

Ok i think this is the line where the flag is reset in user tick bcf MB_STAT2, MB_STAT2_PWR_SNAPSHOT_REQ So why every time i change bank i don't have value stored in bank but the snapshot value?

i think it's better for me to use [AUTO_SNAPSHOT] enabled because when in bank1 i push button 18 = FF 04 01 @OnOnly (or FF 02 01 if i don't want to save the value in bank1) i want to jump to bank 2 and restore value stored in bank2 and sent it to midi out. maybe the problem is the flag that i set in meta-handler for my special button MB64_META_Handler bsf MB_STAT2, MB_STAT2_PWR_SNAPSHOT_REQ return maybe USER_Tick function in main.inc don't clear the flag

Sorry but after a few attempts i discovered a problem. i use your solution and i assign to a button the meta handler. MB64_META_Handler bsf MB_STAT2, MB_STAT2_PWR_SNAPSHOT_REQ return but now with [AUTO_SNAPSHOT] enabled when i change bank with button 17-18-19 midibox don't recall the values stored in bankstick but everytime make a snapshot of current pot position. if i use [AUTO_SNAPSHOT] disabled midibox recall the values stored in bankstick but don't sent it to midi out port. This is the part of .ini file where the meta event is assigned to button 17 = FF 04 00 @OnOnly 18 = FF 04 01 @OnOnly 19 = FF 04 03 @OnOnly 20 = F0 00 7F @OnOnly