hitherescotty

Yes I do have one spare LED. I will be traveling for a few days so I will do these tests on Jan 28. I'll update you when I try them.

Sorry if I wasn't clear before Thorsten. No I cannot upload the firmware either. When I query the Sammich, MIOS studio reports "No response from MIOS8 or MIOS32 core!" If I try to send setup_sammich_sid.hex anyway, I get "WARNING: no response from core" If I reboot the sammichSID, my PC/Mac receives f0 00 00 7e 40 00 01 f7 and the transfer begins. After it finishes, sammichSID appears no different, still says READY. Tests I have tried: TEST MIDI1 looks OK. TEST MIDI2 fails. TEST OUT1 passes. TEST IN1A and TEST IN1B look OK. I have not yet tried TEST IN2, IN3, IN4, IN5, IN6, or IN7.

Thanks for the help thus far guys, but I am still having the same problems. The new optocoupler does not change anything. Sorry if I was not being clear, but I did TEST MIDI2 already (exactly as described) and it fails. But I also fail TEST PC1 when trying to echo SysEx messages. With TEST PC1 failing, I don't conceive how I could possibly pass TEST MIDI2. If my interface is the problem then of course the TEST MIDI2 is also going to fail... From the MIDI Interface Troubleshooting Guide. The part I fail is highlighted: Checking the MIDI Interface via Loopback TEST PC1: ensure that the MIDI interface of your computer is working: loopback the MIDI Out of your computer to the MIDI In of your computer with a MIDI cable. Press the Query button, a loopback should be detected as shown here. Send some MIDI notes with the virtual keyboard; MIDI events displayed by the OUT monitor should also be displayed by the IN monitor as shown here. Now test SysEx transfers by typing some arbitrary strings into the MIOS terminal input window as shown here (note that the MIOS terminal itself is mostly only supported by MIOS32 - but it's a nice debugging help in this situation. Next steps: Loopback not working at all: there seems to be a problem with your MIDI cable, with the MIDI interface or your the MIDI interface driver (google for solutions). MIDI Notes are received, but no MIOS Terminal messages: it seems that your MIDI interface doesn't handle SysEx messages correctly. See also the Blacklist. Sometimes it helps to update the driver. Loopback is working in all cases: it seems that your MIDI interface works reliable, continue with the next chapter

Sorry I didn't get a chance to try it out last night but I will definitely tonight. Thorsten, what I mean was that excluding the core, if I try to send SysEx via Loopback using my Mac (or PC's) interface alone, the messages don't echo. Anyway, I will try tonight and report back.

Thanks for the tip nILS. I'm getting a replacement optocoupler in about 1 hour. I will try it later tonight and see if it fixes my problems. However, this still doesn't explain why I can't get my MIDI interfaces to echo SysEx messages via Loopback...

OK so no, I m failing this test. Shorting rx and tx does not result in a loopback. I do get a f0 00 00 7e 40 00 01 f7 message into MIOS studio when I power cycle the core, which makes me assume that MIDI Out is working fine. Is that a safe assumption? TEST IN1A/B look fine to me. I am thinking perhaps my core's MIDI port polarity is the problem. Should this be the next thing I test? If so, how do you recommend going about testing it?

Thanks Thorsten. I will try this. Just to clarify, which IC am I to remove?

The optocoupler is definitely installed correctly. But forget the core for a minute, because I can't even get my MIDI interface to echo the MIOS messages via Loopback. Yes I am using MIOS Studio v2.4.2. On both the PC and Mac. My assumptions about Mandolane, etc are just from reading old forum posts which I suppose are no longer applicable.

Hi folks, I am building a sammichSID from the recent batch and have an issue. I am at the stage where I am trying to use MIOS Studio to speak to the Sammich. After turning on the Sammich while plugged in, I saw a single f0 00 00 7e 40 00 01 f7 message in the MIDI In window. And now when the Sammich turns on I get "MIOS V1.9" and then "Ready." When querying I received a "No response from MIOS8 or MIOS32 core!" message and started following the Troubleshooting guide. So when testing my interface via Loopback, I got a detected feedback loop. Good! But when I tried to send a SysEx command, I didn't get an echoed response. In other words, I fail at this step becaue the grey messages aren't repeated back in black: http://www.ucapps.de/mios_studio/mios_studio_feedback_sysex.png So I tried my 2 other interfaces on both my Mac and PC, no luck. I even went out and bought a fourth device on the whitelist (the MOTU FastLane USB). No luck (and $60 bucks down the drain). I must be missing something... Please help!!!! I have been reading alot about Mandolane maybe helping here, but the mandolane website appears to be offline :( EDIT Oh one more note, when sending these messages, the LEDs for both input and output light up on the MOTU device. So I feel like some kind of filtering must be happening on the software end. Or maybe I just need better Java MIDI drivers? When I route through my Sammich and Query, I do NOT get input LEDs to light up. So maybe there is another problem, but I figured I would start with the loopback.