Date   

Re: UnO2 Programming Help Needed

Nick S
 

I do apologise, 24c16 is the generic part no as per the schematic, not 27c16.


Re: UnO2 Programming Help Needed

Tortellini
 
Edited

OK for IC6, but where is 27C16 ?


Re: UnO2 Programming Help Needed

Nick S
 

IC6, 27C16.


Re: UnO2 Programming Help Needed

Tortellini
 

which eeprom should be changed on the motherboard?


Re: UnO2 Programming Help Needed

chrisw_63
 

I can solder the larger Surface Mount stuff.  I don't have the tools for BGA's.  As long as the EEPROM isn't a BGA package or similar, it's not that hard to solder by hand.  You just need a small chisel point tip, a steady hand, and some solder braid.  If the package is really small, get a magnifying glass to check for good solder joints, bridged pins, etc.  For desoldering, a larger tip can help.


Re: UnO2 Programming Help Needed

ossandust
 

I think you are correct, this is a hardware issue. Looks very much like a defective EEPROM chip indeed: such a memory is arranged in rows and columns, an internal defect can cause data of each 2 successive rows to be stored on the same row. Since the Behringer preset info is stored in equally spread blocks of memory (for instance 2 preset blocks on each "row") this could result in data of preset 1 & 2 being overwritten by preset 3 & 4, and so on. As mentioned before, with Behringer/UnO firmware such a defect will just cause preset content to be moved around. However with UnO2 firmware, this would cause the series of commands to become corrupted, and that can make the unit behave completely crazy, as you have seen. "patchdump was successfully sent" also proves that there is no issue with your MIDI interface, all the data is correctly received, it's storing the data which fails. 
A new EEPROM costs around 0.5$, you'll just need someone with the necessary skills to replace a small surface mount component.


Re: UnO2 Programming Help Needed

Tortellini
 

thanks David Grosz and ossandust for your help.

I have probably a hardware issue.

I back the FCB1010 to the stock EEPROM and i have one other issue...
When i change the parameters of the footswitch 1 and after i change the parameters of the footswitch 3, the footswitch 3 erase the footswich 1. Same for 2 and 4.
it's totaly crazy, i want to throw it out by the windows !!!

A video of my problem : https://youtu.be/ZgO4pGt1NRc

ossandust : yes i have the popup "The patchdump was successfully sent"


Re: UnO2 Programming Help Needed

ossandust
 

It is all very logical, and can have 3 different causes : 

1. the setup being corrupted during transfer. Can you please confirm whether or not you see the popup "The patchdump was successfully sent" in UnO2ControlCenter? If you see this message, we can rule out an interface problem, if you don't see this message, the SysEx transfer fails and this causes the issue you see.
2. a firmware bug. In that case I will be able to reproduce the same behavior on my setup if I use the exact same setup, and then I can find out what is going wrong. The main question here is: did you use a different setup file in the second video, compared to the first video? If so, please send me the 2 different setup files so that I can reproduce the problem here. If the setup did not change, it proves that the issue is not with the firmware chip, but the cause is rather ; 
3. a hardware issue, like the EEPROM chip (= setup storage) which no longer works reliably. With standard Behringer or UnO firmware, this can remain unnoticed because that firmware has a very rigid structure of storing the different PC/CC/Note messages for each preset on a fixed location, and the setup content cannot influence the controller behavior. UnO2 firmware works completely different, it reads and interprets the setup content, which can contain a wide range of commands. If one byte in such a command is corrupted, the whole system can become unstable as you see in your first video. In your second video, the system no longer is unstable (you can select presets, activate DirectBank, the switch LEDs behave as expected...) but the preset content is corrupted. 

Of course I understand that this looks very much like an UnO2 firmware problem to you, so please email me your setup files so that I can either rule that out or solve it asap. I will stop shipping UnO2 chips until I have been able to investigate this.

regards,
Xavier


Re: UnO2 Programming Help Needed

David Grosz
 

Tortellini

Now I am moderately new but I modified your above setup and added to it
to make the Stomps toggle on/off each button press. 

What I do to save outside the editor is to copy and paste from editor to Notepad
so if you copy and paste this into your editor you can see what and how I changed it

Also under your Presets 0-18 do you mean to send CC messages?  Presets would be PC messages


Let me if this fixed your issue

Dave




On Tuesday, April 5, 2022, 02:49:21 AM PDT, Tortellini <tortellini49fr@...> wrote:


hello,
I'm new on the UNO2 univer and i'm totally lost !

i just want prog my FCB1010 for send the message CC #1  when i press the pedal 1, CC #2 when i press pedal 2 ....

i have this prog but it's not work.

Please help me !

[EDIT: Subject changed by Moderator, to remove Tag and expand]

PRESETS =
{
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
}

EFFECTS =
{
Stomp1
Stomp2
Stomp3
Stomp4
Stomp5
Stomp6
Stomp7
Stomp8
Stomp9
Stomp10
Stomp11
Stomp12
Stomp13
Stomp14
}



SWEEPS =
{
PedalA
PedalB
}
USE_DIRECT_BANK

BANKS =
{
   Direct Bank : Stomp1 | Stomp2 | Stomp3 | Stomp4 | Stomp5 | Stomp6 | Stomp7 | Stomp8 | Stomp9
   bank 1      : 0      | 1      | 2      | 3      | 5      | 6      | 7      | 8      | 9    
   bank 2      : 10     | 11     | 12     | 13     | 14     | 15     | 16     | 17     | 18    
}

CHANNEL DEVICE = 1

INIT_FCB =
{
Pedal 1 = PedalA
Pedal 2 = PedalB
}

Preset 0 =
{  
         SendMidi DEVICE CtrlChange 0 127
}

Preset 1 =
{  
         SendMidi DEVICE CtrlChange 1 127
}

Preset 2 =
{  
         SendMidi DEVICE CtrlChange 2 127
}

Preset 3 =
{  
         SendMidi DEVICE CtrlChange 3 127
}

Preset 4 =
{  
         SendMidi DEVICE CtrlChange 4 127
}

Preset 5 =
{  
         SendMidi DEVICE CtrlChange 5 127
}

Preset 6 =
{  
         SendMidi DEVICE CtrlChange 6 127
}

Preset 7 =
{  
         SendMidi DEVICE CtrlChange 7 127
}

Preset 8 =
{  
         SendMidi DEVICE CtrlChange 8 127
}

Preset 9 =
{  
         SendMidi DEVICE CtrlChange 9 127
}

Preset 0 =
{  
         SendMidi DEVICE CtrlChange 10 127
}

Preset 10 =
{  
         SendMidi DEVICE CtrlChange 11 127
}

Preset 11 =
{  
         SendMidi DEVICE CtrlChange 12 127
}

Preset 12 =
{  
         SendMidi DEVICE CtrlChange 13 127
}

Preset 13 =
{  
         SendMidi DEVICE CtrlChange 14 127
}

Preset 14 =
{  
         SendMidi DEVICE CtrlChange 15 127
}

Preset 15 =
{  
         SendMidi DEVICE CtrlChange 16 127
}

Preset 16 =
{  
         SendMidi DEVICE CtrlChange 17 127
}

Preset 17 =
{  
         SendMidi DEVICE CtrlChange 18 127
}

Preset 18 =
{  
         SendMidi DEVICE CtrlChange 19 127
}

SWEEP PedalA = SendMidi DEVICE CtrlChange 126 0-127
SWEEP PedalB = SendMidi DEVICE CtrlChange 127 0-127


Re: UnO2 Programming Help Needed

Tortellini
 

it's probably a problem with the UNO2 chiptset because when i return to the stock chipset ( V2.5) all works normaly.


Re: UnO2 Programming Help Needed

Tortellini
 

It's very strange, i can flash the FCB1010 X10, i have never the same result !

Look my new video, when i press a footswitch i have a very long midi message

https://youtu.be/73UU4E3yPbc


Re: UnO2 Programming Help Needed

ossandust
 

On Tue, Apr 5, 2022 at 04:30 PM, Tortellini wrote:
all is ok, no error message
If you see a popup "The patchdump was successfully sent" in UnO2ControlCenter, then there is no problem with the interface. But then there might be a hardware issue, because the video shows that the unit doesn't function normally - LEDs blinking, all menu LEDs going on, that's not something which can happen normally... Of course a firmware bug cannot be excluded (this is a new firmware version which has just been released) but this version has been under test for several weeks now, and I never ran into a similar issue. 


Re: UnO2 Programming Help Needed

Tortellini
 



I tested with 3 midi interface.
with MIO and DigitalLife the connection test don't work.
Only the Roland interface works.
When i transfert the prog to the FCB1010 all is ok, no error message, but.... the FCB1010 don't works correctly...

It's totaly crazy !!!


Re: UnO2 Programming Help Needed

ossandust
 

Indeed a problem with sending the patchdump to the FCB1010. Normally the "88" on the display should disappear after a few seconds, indicating that the patchdump is finished, and ControlCenter should say "The patchdump was succesfully sent". Might be an issue with the MIDI-USB interface, although the smaller sysex messages seem to work correctly (connection test, requesting firmware version,...) . Trying a different interface is the only advise I can think of for now...


Re: UnO2 Programming Help Needed

Tortellini
 

thanks for your answer.

I have probably a problem when i send the prog to the FCB1010.

i make a video of my probleme :

https://youtu.be/QK4OYokIqms


Re: UnO2 Programming Help Needed

ossandust
 

I don't see any issue with this setup, if you send it to the FCB1010 I would indeed expect a CC message being sent on each switch click.


UnO2 Programming Help Needed

Tortellini
 

hello,
I'm new on the UNO2 univer and i'm totally lost !

i just want prog my FCB1010 for send the message CC #1  when i press the pedal 1, CC #2 when i press pedal 2 ....

i have this prog but it's not work.

Please help me !

[EDIT: Subject changed by Moderator, to remove Tag and expand]

PRESETS =
{
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
}

EFFECTS =
{
Stomp1
Stomp2
Stomp3
Stomp4
Stomp5
Stomp6
Stomp7
Stomp8
Stomp9
Stomp10
Stomp11
Stomp12
Stomp13
Stomp14
}



SWEEPS =
{
PedalA
PedalB
}
USE_DIRECT_BANK

BANKS =
{
   Direct Bank : Stomp1 | Stomp2 | Stomp3 | Stomp4 | Stomp5 | Stomp6 | Stomp7 | Stomp8 | Stomp9
   bank 1      : 0      | 1      | 2      | 3      | 5      | 6      | 7      | 8      | 9    
   bank 2      : 10     | 11     | 12     | 13     | 14     | 15     | 16     | 17     | 18    
}

CHANNEL DEVICE = 1

INIT_FCB =
{
Pedal 1 = PedalA
Pedal 2 = PedalB
}

Preset 0 =
{  
         SendMidi DEVICE CtrlChange 0 127
}

Preset 1 =
{  
         SendMidi DEVICE CtrlChange 1 127
}

Preset 2 =
{  
         SendMidi DEVICE CtrlChange 2 127
}

Preset 3 =
{  
         SendMidi DEVICE CtrlChange 3 127
}

Preset 4 =
{  
         SendMidi DEVICE CtrlChange 4 127
}

Preset 5 =
{  
         SendMidi DEVICE CtrlChange 5 127
}

Preset 6 =
{  
         SendMidi DEVICE CtrlChange 6 127
}

Preset 7 =
{  
         SendMidi DEVICE CtrlChange 7 127
}

Preset 8 =
{  
         SendMidi DEVICE CtrlChange 8 127
}

Preset 9 =
{  
         SendMidi DEVICE CtrlChange 9 127
}

Preset 0 =
{  
         SendMidi DEVICE CtrlChange 10 127
}

Preset 10 =
{  
         SendMidi DEVICE CtrlChange 11 127
}

Preset 11 =
{  
         SendMidi DEVICE CtrlChange 12 127
}

Preset 12 =
{  
         SendMidi DEVICE CtrlChange 13 127
}

Preset 13 =
{  
         SendMidi DEVICE CtrlChange 14 127
}

Preset 14 =
{  
         SendMidi DEVICE CtrlChange 15 127
}

Preset 15 =
{  
         SendMidi DEVICE CtrlChange 16 127
}

Preset 16 =
{  
         SendMidi DEVICE CtrlChange 17 127
}

Preset 17 =
{  
         SendMidi DEVICE CtrlChange 18 127
}

Preset 18 =
{  
         SendMidi DEVICE CtrlChange 19 127
}

SWEEP PedalA = SendMidi DEVICE CtrlChange 126 0-127
SWEEP PedalB = SendMidi DEVICE CtrlChange 127 0-127


Re: Uno2 Tutorials

Augie <csillery@...>
 

Dave,
Again ur awesome to take the time for me. So I guess since I still have the stock chip in the board, then it's a no brainer to put the uno2 chip in. I will only be using it to control my DAW and whatever vsti's that I use.


Re: Uno2 Tutorials

David Grosz
 

Augie

To me having stock chip then UnO chip and then the UnO2 I would say yes it is worth it.

Why?  Well among lots of things simply having virtual heel and toe switches alone makes
it worth the price and being able to select an audio type taper along with a linear taper on
how sweep reacts. 

If thats not enough it turns the FCB1010 into a very powerful midi controller which can send
out multiple commands on multiple midi channels with one button press.  I use the FCB with
the UnO2 chip for switching a guitar rack primarily an Axe Fx and the enclosed pic is what
happens when that preset is pressed, changing multiple PC and CC messages across multiple
midi channels and though currently mainly use the Axe Fx on its own I don't know of any midi
controller under 1800.00 that can do it.

I like the format of the FCB1010 having 10 switches and 2 expression pedals in a great size
and self contained.  Ossan Dust helped me with how to select any of the 768 available presets
of the Axe Fx which is something not possible on other midi controllers including the MFC-101
which is the Fractal controller made to go with the Axe Fx.  The only downfall is the lack of a
display other than what the bank and preset is that your on or if in stomp mode if effect is on
or off.  If I had it to do over again I would consider the TinyBox because of all the above reasons
and it adds bluetooth and the ability to monitor whats happening and displaying on a tablet.

I highly recommend using the UnO2 chip








On Sunday, April 3, 2022, 06:26:42 PM PDT, Augie <csillery@...> wrote:


Dave,
Thanks for your help. I really appreciate it. I still have not installed the chip yet. Is it really worth it?
Augie


Re: Uno2 Tutorials

Augie <csillery@...>
 

Dave,
Thanks for your help. I really appreciate it. I still have not installed the chip yet. Is it really worth it?
Augie

261 - 280 of 9111