Yep - I agree. Especially the way the 2 relays have to be
"tapdance"-programmed in the UnO version I find very confusing myself
(although it was the most logical way I could think of to add the
third state)


--- In fcb1010_uno@..., "sliding_billy_hamilton"
<sliding_billy@h...> wrote:

The Ripwerx editor gives a much better visual than
the "tap dance."

This was sort of my point about using Ripwerx (I didn't want to
offend - you've been programming the FCB longer than any of us I
think). It sounds as if you (Ed) might have been missing a
setting. The Ripwerx editor gives a much better visual than
the "tap dance."

Chris

--- In fcb1010_uno@..., "ossandust" <ossan.dust@p...>
wrote:

Hey Ed,

Sorry if I'm telling things here which are obvious to you :

one of the new features with the UnO firmware (and possible cause

of

confusion) is that you can set expression pedals to "No Change" in

the

patch setup - meaning that the expression pedal will just remain

on or

off when you select that patch.
The behaviour you describe below is the expected behaviour if

preset1

is programmed to have expr.B "disabled" instead of "off".
Go to patch setup and check if the LED of switch 5 is on: if it's

not,

the firmware works ok.
(see FCB_UnO_v1_0_2_ProgrammingChart.pdf , upper right

picture, "pedal

B enable")
Same story for the switches : they have an added "No change"

state. Go

to patch setup and doublecheck that the LEDs of switch 1 and 2 are
both on.


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>

wrote:

I am beginning to think I have a bad v1.0.2b chip. I am not

having

much luck getting any of the features to work right.

For example, set to non-stompbox mode. Configure preset 1 to

use

only Expression A. Set 2 to use both A and B.

Select A, and only expression A light is lit up. Select 2 and

both

lights are on. Reselect 1 and both lights are still on.

I can't get the switches to do anything, with any setting.

Ed

Hey Ed,

Sorry if I'm telling things here which are obvious to you :

one of the new features with the UnO firmware (and possible cause of
confusion) is that you can set expression pedals to "No Change" in the
patch setup - meaning that the expression pedal will just remain on or
off when you select that patch.
The behaviour you describe below is the expected behaviour if preset1
is programmed to have expr.B "disabled" instead of "off".
Go to patch setup and check if the LED of switch 5 is on: if it's not,
the firmware works ok.
(see FCB_UnO_v1_0_2_ProgrammingChart.pdf , upper right picture, "pedal
B enable")
Same story for the switches : they have an added "No change" state. Go
to patch setup and doublecheck that the LEDs of switch 1 and 2 are
both on.

The last tests referenced where done directly with the pedal and no
PC connection.

Ed


--- In fcb1010_uno@..., "sliding_billy_hamilton"
<sliding_billy@h...> wrote:

Ed, this may sound funny, but have you tried programming it with
Ripwerx (just to see if the chip takes/holds the info)? I know

your

editor will be an alternative to Ripwerx, but... It would be good

to

see what takes and what doesn't from a "known-good" sysex file

also.

Perhaps you could post your sysex for a behavioral comparison.

Then

you could compare the behavior of someone else's sysex.

Chris

--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am beginning to think I have a bad v1.0.2b chip. I am not

having

much luck getting any of the features to work right.

For example, set to non-stompbox mode. Configure preset 1 to use
only Expression A. Set 2 to use both A and B.

Select A, and only expression A light is lit up. Select 2 and

both

lights are on. Reselect 1 and both lights are still on.

I can't get the switches to do anything, with any setting.

Ed



--- In fcb1010_uno@..., "ossandust" <ossan.dust@p...>
wrote:

Hey Ed,

just to eliminate 1 possible cause : did you check the actual
behaviour of relay1 after changing the global setting? Does it
actually change from 'momentary' to 'toggling' as expected? If

it

does, I have no clue what's going on. If it does not react as
expected, you have an eeprom save issue.
Unfortunately, your UnO version 1.0.2b did contain a bug in the
eeprom save functionality (caused by the extension of the

memory

used). I believe this bug is only noticeable in certain

combinations

of eeprom content, as only some UnO users reported the problem.
If this is the problem, I'm afraid you're paying the price for

being

an "early adopter" - sorry for that!...
In any case I would recommend an upgrade to version 1.0.2c,

that

version seems to be really stable.

Greetz,
OssanDust


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

I am setting it manually, saving config, then dumping Sysex

for

review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-

bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not

chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back

via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one

to

read

correctly. All the other settings seem to read

correctly,

but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

Ed, this may sound funny, but have you tried programming it with
Ripwerx (just to see if the chip takes/holds the info)? I know your
editor will be an alternative to Ripwerx, but... It would be good to
see what takes and what doesn't from a "known-good" sysex file also.
Perhaps you could post your sysex for a behavioral comparison. Then
you could compare the behavior of someone else's sysex.

Chris

--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am beginning to think I have a bad v1.0.2b chip. I am not having
much luck getting any of the features to work right.

For example, set to non-stompbox mode. Configure preset 1 to use
only Expression A. Set 2 to use both A and B.

Select A, and only expression A light is lit up. Select 2 and both
lights are on. Reselect 1 and both lights are still on.

I can't get the switches to do anything, with any setting.

Ed



--- In fcb1010_uno@..., "ossandust" <ossan.dust@p...>
wrote:

Hey Ed,

just to eliminate 1 possible cause : did you check the actual
behaviour of relay1 after changing the global setting? Does it
actually change from 'momentary' to 'toggling' as expected? If it
does, I have no clue what's going on. If it does not react as
expected, you have an eeprom save issue.
Unfortunately, your UnO version 1.0.2b did contain a bug in the
eeprom save functionality (caused by the extension of the memory
used). I believe this bug is only noticeable in certain

combinations

of eeprom content, as only some UnO users reported the problem.
If this is the problem, I'm afraid you're paying the price for

being

an "early adopter" - sorry for that!...
In any case I would recommend an upgrade to version 1.0.2c, that
version seems to be really stable.

Greetz,
OssanDust


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to

read

correctly. All the other settings seem to read correctly,

but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

I am beginning to think I have a bad v1.0.2b chip. I am not having
much luck getting any of the features to work right.

For example, set to non-stompbox mode. Configure preset 1 to use
only Expression A. Set 2 to use both A and B.

Select A, and only expression A light is lit up. Select 2 and both
lights are on. Reselect 1 and both lights are still on.

I can't get the switches to do anything, with any setting.

Ed



--- In fcb1010_uno@..., "ossandust" <ossan.dust@p...>
wrote:

Hey Ed,

just to eliminate 1 possible cause : did you check the actual
behaviour of relay1 after changing the global setting? Does it
actually change from 'momentary' to 'toggling' as expected? If it
does, I have no clue what's going on. If it does not react as
expected, you have an eeprom save issue.
Unfortunately, your UnO version 1.0.2b did contain a bug in the
eeprom save functionality (caused by the extension of the memory
used). I believe this bug is only noticeable in certain

combinations

of eeprom content, as only some UnO users reported the problem.
If this is the problem, I'm afraid you're paying the price for

being

an "early adopter" - sorry for that!...
In any case I would recommend an upgrade to version 1.0.2c, that
version seems to be really stable.

Greetz,
OssanDust


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to

read

correctly. All the other settings seem to read correctly,

but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

Will try some other combos. I have two FCB units now. One has the
v1.0.2b chip and the other an older OEM 2.3.12 chip. I have a OEM
2.4.1B chip in a bag I can also use.

Ed


--- In fcb1010_uno@..., "ossandust" <ossan.dust@p...>
wrote:

Hey Ed,

just to eliminate 1 possible cause : did you check the actual
behaviour of relay1 after changing the global setting? Does it
actually change from 'momentary' to 'toggling' as expected? If it
does, I have no clue what's going on. If it does not react as
expected, you have an eeprom save issue.
Unfortunately, your UnO version 1.0.2b did contain a bug in the
eeprom save functionality (caused by the extension of the memory
used). I believe this bug is only noticeable in certain

combinations

of eeprom content, as only some UnO users reported the problem.
If this is the problem, I'm afraid you're paying the price for

being

an "early adopter" - sorry for that!...
In any case I would recommend an upgrade to version 1.0.2c, that
version seems to be really stable.

Greetz,
OssanDust


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to

read

correctly. All the other settings seem to read correctly,

but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

Hey Ed,

just to eliminate 1 possible cause : did you check the actual
behaviour of relay1 after changing the global setting? Does it
actually change from 'momentary' to 'toggling' as expected? If it
does, I have no clue what's going on. If it does not react as
expected, you have an eeprom save issue.
Unfortunately, your UnO version 1.0.2b did contain a bug in the
eeprom save functionality (caused by the extension of the memory
used). I believe this bug is only noticeable in certain combinations
of eeprom content, as only some UnO users reported the problem.
If this is the problem, I'm afraid you're paying the price for being
an "early adopter" - sorry for that!...
In any case I would recommend an upgrade to version 1.0.2c, that
version seems to be really stable.

Greetz,
OssanDust


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to

read

correctly. All the other settings seem to read correctly, but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

Ed,

I don't remember seeing any problems with this. I'm not sure what
to think. Take a second look at Ossandust's programming guide. I
think setting this SW1 function has a slightly different sequence
than with stock firmware. I remember getting confused once or twice
setting the thing up.

mike

--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

--- In fcb1010_uno@..., "Mike Riley" <the-bug@a...>

wrote:

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage

with

UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in

global

mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via

sysex?

mike


--- In fcb1010_uno@..., "edwardtdixon"

<eddixon@m...>

wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to

read

correctly. All the other settings seem to read correctly, but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

I am setting it manually, saving config, then dumping Sysex for
review. When I read the dump, the switch 1 is still zero.

I have v1.0.2b of the UnO firmware.

Ed

I'm not 100% sure what you are asking.
That bit is for SW1 latch. This particular bit did not chage with
UnO - it appeared with OEM v2.4 and has not changed since...

Do you mean that you are setting it manually at the FCB in global
mode, and it then does not appear in the dump?

Or, are you trying to set it via sysex, then read it back via sysex?



mike


--- In fcb1010_uno@..., "edwardtdixon" <eddixon@m...>
wrote:

Docs show bit 7 of byte 2026, but I cannot get this one to read
correctly. All the other settings seem to read correctly, but

this one

shows up as unset regardless of the firmware setting.

Any ideas?

Ed

Docs show bit 7 of byte 2026, but I cannot get this one to read
correctly. All the other settings seem to read correctly, but this one
shows up as unset regardless of the firmware setting.

Any ideas?

Ed