Issue receiving sysex dump from DX7

--isgrCPvlljxjYxfiJfTV
Content-Type: multipart/alternative; boundary="s79XzfwI1YDH1acxKE6x"

--s79XzfwI1YDH1acxKE6x
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi there and thanks for accepting me into this group.

As a quick introduction of myself, I'm from Germany, I have a number of 80=
s and 90s Yamaha synths, a nice bit of other equipment and some, albeit lim=
ited, knowledge in electronics (more of a software developer).

I recently bought a DX 7 Mk 1 - according to the chips' timestamp it's pro=
bably built in fall 1983. I have an issue with it where I am a bit stuck.
When I try to dump the internal memory, no MIDI interface recognizes any d=
ata, but something is being sent.

The setup I have for testing:
DX7 Mk 1 - MIDI out to a MOTU MIDI Express
No-Name USB-MIDI converter connected to the MOTU
Behringer FCA1616 connected to the MOTU

Process for dumping the memory (if I understood the manual correctly, ther=
e should not be an issue there):
Switch on DX7 ... :-)
FUNCTION - 8 (MIDI Channel 1) - 8 - YES (Sysinfo avail) - 8 - YES

Then I can see that the MOTU receives and relays something (the appropriat=
e LEDs are all on for a time). I can see on both MIDI interfaces (no-name c=
able and FCA1616) that something is coming in, BUT no software on a PC (inc=
luding DX Manager) sees any usable data.
It's the same if I plug the interfaces directly into the DX7 (the MOTU hel=
ps sometimes, my no-name cable for example has issues talking to a CS1x dir=
ectly, but all is fine if the MOTU relays the data).

The DX7 can receive sysex, so I can send patches to it. Controller message=
s come out of the DX7. When dumping the sysex, the interfaces recognize the=
 controller message for the "+1 YES", but after that nothing.

Another thing that makes me wonder if there is an issue with my DX7 is: wh=
en I switch it on, the MOTU registers a repeating signal coming in, but it =
is not relaying that (maybe the incoming is not strong enough?), but after =
having tried to dump sysex, this quick repeating signal is relayed (output =
LEDs start flickering).

And yet another potential hint: when the MOTU relays incoming signals back=
 to the DX7, I actually see some data which looks very much like a sysex du=
mp, but only the FCA1616 recognizes this f**ed up data stream, a small snip=
pet of the data is:
F2 48 45
F2 41 56
F2 59 4D F2 45 54 F2 4C 32 F2 35 40
If you remove the "F2"s, you get the name of one of the stored voices "HEA=
VYMETAL25"

So, something somehow is coming.

Is it an issue you have seen? My only ideas are that either the sending ra=
te is somehow wrong or the electrical level is not "strong enough", and the=
 factual feedback when the MOTU sends all back to the DX7 barely raises the=
 level above recognition? I mean, I'm purely guessing here, I also suspecte=
d the firmware, but according to https://narkive.com/7ucQVoto.10 the abilit=
y to dump a sysex is not known to be a problem of a firmware.

Any sensible idea, anything I could try, would be most welcome.

Maybe one more piece of potentially relevant info: when I pluck my TX7 int=
o the same cables, all is well.

In the end this is for me more of a purist problem, as I would like to hav=
e my synthesizers all work to spec. I'm not planning on programming voices =
on the DX7 itself, I use software editors for that, and as I *can* send the=
 patches over... Anyway, I don't like broken hardware :-)

Cheers, Florian

--s79XzfwI1YDH1acxKE6x
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi there and thanks for accepting me into this group.<br /><br />As a quick=
 introduction of myself, I'm from Germany, I have a number of 80s and 90s Y=
amaha synths, a nice bit of other equipment and some, albeit limited, knowl=
edge in electronics (more of a software developer). <br /><br />I recently =
bought a DX 7 Mk 1 - according to the chips' timestamp it's probably built =
in fall 1983. I have an issue with it where I am a bit stuck.<br />When I t=
ry to dump the internal memory, no MIDI interface recognizes any data, but =
something is being sent.<br /><br />The setup I have for testing:<br />DX7 =
Mk 1 - MIDI out to a MOTU MIDI Express<br />No-Name USB-MIDI converter conn=
ected to the MOTU<br />Behringer FCA1616 connected to the MOTU<br /><br />P=
rocess for dumping the memory (if I understood the manual correctly, there =
should not be an issue there):<br />Switch on DX7 ... :-)<br />FUNCTION - 8=
 (MIDI Channel 1) - 8 - YES (Sysinfo avail) - 8 - YES<br /><br />Then I can=
 see that the MOTU receives and relays something (the appropriate LEDs are =
all on for a time). I can see on both MIDI interfaces (no-name cable and FC=
A1616) that something is coming in, BUT no software on a PC (including DX M=
anager) sees any usable data.<br />It's the same if I plug the interfaces d=
irectly into the DX7 (the MOTU helps sometimes, my no-name cable for exampl=
e has issues talking to a CS1x directly, but all is fine if the MOTU relays=
 the data).<br /><br />The DX7 can receive sysex, so I can send patches to =
it. Controller messages come out of the DX7. When dumping the sysex, the in=
terfaces recognize the controller message for the "+1 YES", but after that =
nothing.<br /><br />Another thing that makes me wonder if there is an issue=
 with my DX7 is: when I switch it on, the MOTU registers a repeating signal=
 coming in, but it is not relaying that (maybe the incoming is not strong e=
nough?), but after having tried to dump sysex, this quick repeating signal =
is relayed (output LEDs start flickering).<br /><br />And yet another poten=
tial hint: when the MOTU relays incoming signals back to the DX7, I actuall=
y see some data which looks very much like a sysex dump, but only the FCA16=
16 recognizes this f**ed up data stream, a small snippet of the data is:<br=
 />F2 48 45<br />F2 41 56<br />F2 59 4D F2 45 54 F2 4C 32 F2 35 40<br />If =
you remove the "F2"s, you get the name of one of the stored voices "HEAVYME=
TAL25"<br /><br />So, something somehow is coming.<br /><br />Is it an issu=
e you have seen? My only ideas are that either the sending rate is somehow =
wrong or the electrical level is not "strong enough", and the factual feedb=
ack when the MOTU sends all back to the DX7 barely raises the level above r=
ecognition? I mean, I'm purely guessing here, I also suspected the firmware=
, but according to <a href=3D"https://narkive.com/7ucQVoto.10" target=3D"_b=
lank" rel=3D"noopener">https://narkive.com/7ucQVoto.10</a> the ability to d=
ump a sysex is not known to be a problem of a firmware.<br /><br />Any sens=
ible idea, anything I could try, would be most welcome.<br /><br />Maybe on=
e more piece of potentially relevant info: when I pluck my TX7 into the sam=
e cables, all is well. <br /><br />In the end this is for me more of a puri=
st problem, as I would like to have my synthesizers all work to spec. I'm n=
ot planning on programming voices on the DX7 itself, I use software editors=
 for that, and as I <strong>can</strong> send the patches over... Anyway, I=
 don't like broken hardware :-)<br /><br />Cheers, Florian

--s79XzfwI1YDH1acxKE6x--

--isgrCPvlljxjYxfiJfTV
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#20425): https://groups.io/g/YamahaDX/message/20425
Mute This Topic: https://groups.io/mt/59988412/2509863
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/YamahaDX/unsub  [[email protected]]
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-

--isgrCPvlljxjYxfiJfTV--