Emax

I am very well aware of this. Looking at XCK1 with a scope seems like it's in output state.

Btw, can i know a little what tipical issues you or your friends faced with their EMUSER's?

Maybe i made a huge mistake i can't see yet.

thanks,

A


--- In emax@yahoogroups.com, "esynthesist" <esynthesist@...> wrote:
>
> I'm not 100 pct sure what the exact situation is with your XCK1 pin, but the EmuSer's firmware WILL put the clock in SYNC mode once EMXP instructs it to do that. This is done only if high speed communication is required, for normal SYSEX communication internal clocking is used at MIDI baudrate (which is also used by EMXP with the Emax through RS422). 
> So for high speed communications (=actual transfer of bank and sample data) the EmuSer MUST receive the clock signal from the Emax instead of clocking itself. This is basically the "heart" of the EmuSer, and the reason why most other USB/RS422 devices don't work with E-Mu samplers. So the firmware contains a piece of code which changes the a flag on the XCK port when it receives a baudrate setting of 500000. 
>  
> ///E-Synthesist
> 
> --- In emax@yahoogroups.com, "Adam" <fake@> wrote:
> >
> > We've tried to build the EMUSER around the Teensy++ board, and we had no success so far.
> > 
> > It seems like that upon bank transfer, the clock disappears on the XCK1 pin .
> > When unplugging-replugging the board the clock will come back.
> > 
> > We suspect the pin changes the direction (the input will become an output) 
> > 
> > Has anyone actually tried the firmware on THIS version of the Teensy ?
> > 
> > Any help is appreciated.
> > 
> > thanks!
> >
>