Step 2. Make the E1 aware of the SysEx response
In this case, the manual details how the response’s header and payload looks like. We’re not always that lucky. But even if documentation is available, bear in my there are almost always errors in it. So while using it, be sure to check if it corresponds to the reality.
In this step, we make sure the E1 is considering the SysEx response for parsing.
The manual states the response looks as follows:
Let’s compare this with the response we see in midi-Ox:
Good 
We can safely state the header of the message in midi-Ox corresponds to the one in the manual.
However this header, 12 bytes long (we disregard the SysEx Start byte as part of the header), has only the first 8 bytes that should be the same for any A-station (hopefully): bytes 9 and 10 transmit Software Version and Version Increment, both of which we are unsure they are the same for all A-stations out there.
For this reason I will not use all 12 bytes to identify the response, but only the first 8 bytes. I’m practically sure that byte 7 (the Message Type) will ensure this response is perfectly identifiable in all cases as the Current Sound Dump from the A-station.
So let’s define this response header in the preset now.
I could of course again define each byte here one after the other in the Messages tab:
But instead let’s go the the json tab, copy the Request part, paste it into the Response Header and amend it to fit just those expected first 8 bytes of the response:
will now become:
- Notice I’ve left out the sysExChannel in the response, but instead replaced it with “7F”. The parsing seems to work better if no functions are added to the response header. And anyways manuals states the response is always 7Fh.
In the messages tab, we can change the response name: allthough that is not strictly necessary, it just reads better.
Now go into the Mapping tab of the Editor, and enable MIDI-learn using the Mic-symbol
Then press the upper right button on the E1 (which sends out the Dump Request SysEx.
‘Lo and Behold’, the magic happens 
, and we get to set the response SysEx laid out for us in the Editor:
Check the following:
- the response’s total length is 142 bytes, which equals the length mentioned in midi-Ox. That’s good
- the E1 editor adds an byte number, starting at 0, at the left of each byte after the header. But because I chose a header that is 4 bytes shorter than the actually one, be aware to correct the byte count accordingly: as the manual states that the payload of the message (called the ‘PROGRAM BLOCK’) is 128 bytes long, I will end up with 4 bytes more. You can do the math yourself with the screenshot below, that shows the end of the message, that this too is correct.
- be aware the responses shown contain both the F0h (SysEx start) and F7h (End of Exclusive) bytes
