200e

Just want to make sure...
Are you changing the settings on the 292e before you recall the patch from the 225e?
Once a patch is saved, and you change one of the module's parameters while its remote 
enable is on, the 225e's red select light will blink, indicating that a current parameter has 
not been saved.
Also, I tend to use the global remote enable feature on the 225e preset manager.  If you 
press the data switch a few times (maybe 3) there is a global remote enable setting.  
Setting this to on will  remote enable all of the modules.  Maybe try this first, just to make 
sure the 225e is talking to the other modules.
I have to admit that for as easy as it is to operate the 225e, I've had some pretty serious 
user errors that made me think patches were not getting saved.  So make sure you do 
experiment with it.
-tom


--- In 200e@yahoogroups.com, "code842" <code842@...> wrote:
>
> never having used the store function before, now i wonder how to use 
> it. and why it doesn't work out the way i do it:
> 
> store:
> 1) 225e: ensure that the red "select" LED is on
> 2) any other module (e.g. 292e): press "remote enable" once -> red
> 3) on 225e: press the "current / store" button
> 4) optionally name the patch
> 
> is that it? no visual confirmation for successful storage?
> 
> recall:
> 1) "remote enable" the receiving module (e.g. 292e)
> 2) 225e: with the DATA wheel select the preset to load
> 3) 225e: press "recall / stored"
> 
> nothing happens. so i guess, the preset is either not properly saved 
> or not properly recalled.
> 
> can somebody help, please?
> tnx
>