How to test Midi module for hardware issue

[mmazurek]

Hey guys,

Anyone know how I can physically test the little midi module in my Voyager?

Midi out is working fine.
Midi in is not responding (no little light coming on at all).

Sitting here with the little part popped out and a multi-meter scratching my head.
The actual 'in port' is passing signal to the inside, so I know it's not simply the midi jack.

Wondering if I can test something to see if this part just needs replacing.

[Markyboard]

Hi -

It might really help if you gave a complete run down of your midi configuration and midi related settings in the Voyager. This connector module is the last part I would suspect and I suggest you reinstall it.

[mmazurek]

Only setting on the Voyager available for midi are the midi channel for in/out (both on 1).

It appears I stopped receiving midi data during the OS update to 3.5.
Powering up, led's light up in sequence normally, then it asks for Bank D.

After several failed attempts to 'finish' the update properly, I realized I simply wasn't receiving midi in any more (no midi led blinking on when midi data sent). Midi out seems fine.

Tried two midi interfaces (emagic Unitor8 and an iConnectMIDI2 USB midi device).
Tried on mac (sysex librarian) and PC (Midi-OX).

Tested in both with the software as well as a keyboard controller.

Phoned in to support and spoke with a technician. We went through the above, and he suggested it might be a hardware issue.

Thinking the module itself would be cheaper than shipping costs alone for the synth, I'm exhausting all options prior to sending it in. (testing for failure of the module, or possibly bypassing the module to get the OS properly installed again)


Hitting 'no' after restarting, the unit seems to work fine outside of the touchpad no longer functioning.
It does not offer some of the new menu items in the full 3.5 update.

[Markyboard]

Understood - thanks for that detail. Again I really don't think that module is the problem. Without a good OS load I can see where midi would be affected.

Loading the OS is tricky and requires both a reliable interface and the right buffering. I use Midi Ox with a MOTU MTP-AV on a Windows PC. Have you tried different buffer size/number? I believe number = 64 and size = 1024 is recommended. Not saying this is the problem and it could be a hardware issue. But if this problem started with trying to upgrade the OS than chances are it's simply that the loaded OS state is currently messed up.

[mmazurek]

Any current attempts to complete the OS does nothing.
The screen simply is awaiting the OS sysex dump.

The data is going out the midi port, but nothing happening in the voyager.
No midi light blinking, nothing.

It's as if there were nothing plugged in to the midi in jack.


Also, nothing from the midi input is passing to midi 'thru'.
Another clue that 'seems' like a hardware issue?

[Markyboard]

Yeah, it sounds bricked. Best to send it off to Moog. Still doubt its the hardware but you never know.

Btw midi thru wont work without the processor receiving the input data. And even when working Sys Ex data is not routed to midi thru - only channel data.

Good luck.

[mmazurek]

Thanks for the help.

The midi thru was tested simply by plugging in a keyboard controller midi out to the voyager input.
Thru to another module (volca), to see if it passed through (with the voyager powered up of course).
It didn't.

[GregAE]

Try contacting Rudi Linhard first. He's the Voyager's firmware developer and might be able to help you out here:

info@lintronics.de

- Greg

[RL]

Hi folks,

when MIDI thru is not working too it's a broken PC900 or the 74HCT14 chip.

[Markyboard]

My bad- reviewing some generic midi interfaces on line I see I misspoke.
Thanks Rudi!

[mmazurek]

Thanks Rudi!

New module is on the way (hopefully saving me hundreds of $'s).