Emax

For testing the Emax MIDI port, I would recommend a (free) software like MidiOx and of course a (USB-)MIDI adapter. With this kind of software you can send/receive individual SYSEX messages, which is great for testing purposes because you can use it as a kind of terminal utility. The SYSEX specs can be found on Emulatorarchive.
But using EMXP via MIDI is an alternative (not as a terminal though...)

The errorcode that you receive from the Emax is - as expected - the "wrong" reply on the "change timeout" instruction; this means that the communication already fails during the asynchronous 31250 baud mode, so the Teensy++ never even gets into SYNC mode.

BTW: if you use EMXP with the Emulator-II via RS422, the Teensy++ should go in SYNC mode at all times. So in the period between launching the "bank upload/unload" from EMXP and the moment you get the 990 errorcode, the XCK of the Teensy should be INPUT and the device should be in SYNC mode. That's because the ASYNC 31250 baud mode is only used at the very beginning in a fraction of a second to put the EII in "Mac Control" mode after which EMXP immediately instructs the RS422 port to go into SYNC mode - EVEN if the instruction to put the EII in ASYNC mode failed (!). This failure is also covered by the 990 errorcode. 

///E-Synthesist

--- In emax@yahoogroups.com, "Adam" <fake@...> wrote:
>
> Got the Emax I error code but i had not time to test the sysex stuff on the emax. btw. how can i test that? (EMXP via MIDI perhaps?)
> 
> the error code from Emax was different:
> 
> errorcode 1048
> 
> emax doesnt give the expected sysex response response is 0 0 0 0 exprected response is f0 18 2 38
> 
> going home, i am falling apart now :(
>